Re: [RFC PATCH] meta/classes: Add strip-image

[Andreas Naumann <anaumann@emlix.com>]

Hi,

Am 04.09.25 um 11:43 schrieb 'Quirin Gylstorff' via isar-users:
>
>
> On 9/4/25 10:37, Jan Kiszka wrote:
>> On 03.09.25 19:13, Quirin Gylstorff wrote:
>>>
>>>
>>> On 9/3/25 18:19, Jan Kiszka wrote:
>>>> On 03.09.25 17:20, 'Quirin Gylstorff' via isar-users wrote:
>>>>> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>>>>>
>>>>> This class provides the optional functionality to strip packages
>>>>> and files from a image. This allows the user to reduce the image
>>>>> size.
>>>>>
>>>>> IMPORTANT: This is an expert feature and can lead to broken images.
>>>>> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>>>>> ---
>>>>>
>>>>> The default settings will reduce the space around 40MB. It is 
>>>>> currently
>>>>> a RFC to collect information about the usage.
>>>>>
>>>>> Should we integrate by default or should the user add this on demand?
>>>>> For a default integration I would drop the deletion:
>>>>>    - /vmlinuz*
>>>>>    - /boot
>>>>>    - /usr/include
>>>>>    - initramfs-tools
>>>>>
>>>>
>>>> The approach isar-exclude-docs takes for docs cannot be used here? And
>>>> we want that approach to stay for cleaning docs? Or what is the 
>>>> relation
>>>> between the two?
>>>
>>> We can use isar-exclude-docs or the use the same implementation. I
>>> didn't use it as it only removes around 3M  from /usr/share/docs in my
>>> tests from against an unmodified target.
>>>
>>> The second part is that isar-exclude-docs is executed during the 
>>> pacakge
>>> installation.
>>> Which makes it impossible to remove other files(e.g. /usr/bin/apt-*).
>>>
>>
>> Would be great if we could have only one mechanism in the end that is
>> powerful enough to express all removal scenarios.
>
> That would be more possible with the proposed strip-image class as it 
> works on post rootfs installation. I could extend the class for the 
> copyrights case of isar-exclude-docs in a v2.

I can image this being a more logical flow than adding packages to 
remove things, which feels a bit counter-intuitive to me.

However, I had a quick look and there's already a few removal functions 
in the rootfs.class itself. I guess this is where default removals go?

Coming from Embedded, I'm used to rootfs by default having no doc, 
man-pages, headers and so on. But maybe Isar has a different policy? Is 
it stated somewhere?

regards,
Andreas

>
> Quirin
>>
>> Jan
>>
>
-- 
Andreas Naumann

emlix GmbH
Headquarters: Berliner Str. 12, 37073 Goettingen, Germany
Phone +49 (0)551 30664-0, e-mail info@emlix.com
District Court of Goettingen, Registry Number HR B 3160
Managing Directors: Heike Jordan, Dr. Uwe Kracke
VAT ID No. DE 205 198 055
Office Berlin: Panoramastr. 1, 10178 Berlin, Germany
Office Bonn: Bachstr. 6, 53115 Bonn, Germany
http://www.emlix.com

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/89e1fec9-810a-4c1f-8c2b-e637a96157bb%40emlix.com.