Re: isar-exclude-docs vs. openjdk et al.

[Jan Kiszka <jan.kiszka@siemens.com>]

On 09.04.21 10:30, Henning Schild wrote:
> 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 ;)
> 

Yeah, the case that triggered that is a bug, not a real scenario. I'm
lacking a feeling how common that combination is and if there might be
realistic combinations as well.

Jan

> Henning
> 
>>
>> Jan
>>
>> [1]
>> https://groups.google.com/g/isar-users/c/uIHgzvCGLwU/m/tuOchY6BAgAJ
>>
> 


-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux