From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH 2/2] isar-exclude-docs: delete also links not just files
Date: Fri, 23 Sep 2022 20:07:15 +0200 [thread overview]
Message-ID: <CAJGKYO56DEF2zzDf=oh1OZO9eBw_ZRS8jtj22eHyNPhokEWUqQ@mail.gmail.com> (raw)
In-Reply-To: <20220923183018.4ff0fdd6@md1za8fc.ad001.siemens.net>
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
Il giorno ven 23 set 2022 alle ore 18:30 Henning Schild <
henning.schild@siemens.com> ha scritto:
> I tried that manually and the result looks good. I also tested the
> installation of "openjdk-11-jre-headless", did not work before as
> reported by Roberto, works after.
>
> It is really about doing what that dpkg.conf does, not about making
> sure that package can be installed .. but it can now.
>
> The ubuntu scripts make sure all is like dpkg.conf by re-installing all
> packages that deployed anything to the excluded paths in their
> containers and livecds. But that is really not nice so i would not want
> to copy that pattern.
>
> https://git.launchpad.net/livecd-rootfs/tree/live-build/auto/build#n197
Thanks a lot for your effort in going deep into the question and verifying
the outcome. I appreciate that. R-
[-- Attachment #2: Type: text/html, Size: 1340 bytes --]
next prev parent reply other threads:[~2022-09-23 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 14:53 [PATCH 1/2] isar-exclude-docs: remove only files in postinst Henning Schild
2022-09-23 14:53 ` [PATCH 2/2] isar-exclude-docs: delete also links not just files Henning Schild
2022-09-23 16:30 ` Henning Schild
2022-09-23 18:07 ` Roberto A. Foglietta [this message]
2022-10-06 9:37 ` [PATCH 1/2] isar-exclude-docs: remove only files in postinst Anton Mikanovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJGKYO56DEF2zzDf=oh1OZO9eBw_ZRS8jtj22eHyNPhokEWUqQ@mail.gmail.com' \
--to=roberto.foglietta@gmail.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox