From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: isar-exclude-docs vs. openjdk et al.
Date: Fri, 9 Apr 2021 10:30:05 +0200 [thread overview]
Message-ID: <20210409103005.0d904d99@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <51fed86f-7579-3f42-4780-c84e18bf4117@siemens.com>
Hi,
not sure that doc purging is really allowed or whether we are messing
with stuff we better should not mess with.
Am Thu, 8 Apr 2021 20:54:28 +0200
schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> Hi all,
>
> there seems to be a conceptual issue with isar-exclude-docs purging
> documents in its postinst hook: If other packages are configured after
> isar-exclude-docs and those packages expects certain doc paths to be
> still there, see openjdk [1], they will fail.
>
> How to solve that?
> - maintain a list of conflicting packages in that recipe?
This is going to be cumbersome but when having a packet that needs its
docs, we probably should not install that cleaner.
> - convert the package to a post-process hook?
would still break apt-get update of packages that need their docs
> - find a way to ensure a compatible ordering when running our
> postinst?
again going to break apt-get
Looking at this one example it does not really need its docs, it just
expects them in "its own hack". My guess is that the problem can be
reproduced in a ubuntu container (where the no-docs stuff is coming
from), and can be used to report an issue so that the
update-alternatives script looks for the files conditionally. Or maybe
write a patch for that package and MR it on salsa directly.
If you are installing java you probably can store a few MB of docs ;)
Henning
>
> Jan
>
> [1]
> https://groups.google.com/g/isar-users/c/uIHgzvCGLwU/m/tuOchY6BAgAJ
>
next prev parent reply other threads:[~2021-04-09 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 18:54 Jan Kiszka
2021-04-09 8:30 ` Henning Schild [this message]
2021-04-09 13:01 ` Jan Kiszka
2021-04-10 8:46 ` Henning Schild
2021-04-12 8:47 ` Silvano Cirujano Cuesta
2021-04-12 8:58 ` Silvano Cirujano Cuesta
2021-04-12 18:35 ` Henning Schild
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=20210409103005.0d904d99@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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