public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Quirin Gylstorff <quirin.gylstorff@siemens.com>,
	isar-users@googlegroups.com
Subject: Re: [RFC PATCH] meta/classes: Add strip-image
Date: Thu, 4 Sep 2025 10:37:42 +0200	[thread overview]
Message-ID: <90ba0364-32c4-4b41-afe7-9cc3e5deb1f1@siemens.com> (raw)
In-Reply-To: <981ff797-16e0-408a-aa37-68bf7c1f03b5@siemens.com>

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.

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

-- 
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/90ba0364-32c4-4b41-afe7-9cc3e5deb1f1%40siemens.com.

  reply	other threads:[~2025-09-04  8:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-03 15:20 'Quirin Gylstorff' via isar-users
2025-09-03 16:19 ` 'Jan Kiszka' via isar-users
2025-09-03 17:13   ` 'Quirin Gylstorff' via isar-users
2025-09-04  8:37     ` 'Jan Kiszka' via isar-users [this message]
2025-09-04  9:43       ` 'Quirin Gylstorff' via isar-users
2025-09-05  7:30         ` Andreas Naumann
2025-09-05  8:43           ` 'Jan Kiszka' via isar-users

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=90ba0364-32c4-4b41-afe7-9cc3e5deb1f1@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=quirin.gylstorff@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