From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: "Arjunan, Srinu (FT FDS CES LX PBU 2)" <srinuvasan.a@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Hombourger,
Cedric (FT FDS CES LX)" <cedric.hombourger@siemens.com>,
"amikan@ilbers.de" <amikan@ilbers.de>
Subject: Re: [PATCH] isar-mmdebstrap: reduce rootfs size as much as possible
Date: Fri, 10 Jan 2025 07:17:58 +0100 [thread overview]
Message-ID: <4c5d3935-5f29-4afc-bf18-aafe02655c1b@siemens.com> (raw)
In-Reply-To: <96433e35-35f8-441a-b447-25123c19fe0e@siemens.com>
On 10.01.25 07:13, Jan Kiszka wrote:
> On 10.01.25 07:02, Arjunan, Srinu (FT FDS CES LX PBU 2) wrote:
>> Hi Jan,
>>
>> I hope this isar-exclude-docs package can be used to exclude the documentation in the image rootfs, but here I introduced this customization for the bootstrap rootfs.
>>
>> Additionally we are cleaning the locales under /usr/share in the bootstrap rootfs.
>>
>> With this reduced size of the bootstrap rootfs, we achieve the sbuildchroot-<host/target> size also reduced.
>>
>
> Still no reason to not use that existing package, maybe extending it. It
> already comes with the configurability that your approach is missing and
> cannot introduce that nicely.
>
Plus, your approach cleans up before all packages have been install,
isar-exclude-docs does that afterwards. So, yours is architecturally
inferior. I really see no reason to go this way.
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/4c5d3935-5f29-4afc-bf18-aafe02655c1b%40siemens.com.
next prev parent reply other threads:[~2025-01-10 6:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 12:17 srinuvasan.a via isar-users
2025-01-09 12:41 ` Cedric Hombourger
2025-01-09 12:58 ` Anton Mikanovich
2025-01-09 13:16 ` Cedric Hombourger
2025-01-09 14:23 ` 'Arjunan, Srinu' via isar-users
2025-01-09 15:20 ` 'Jan Kiszka' via isar-users
2025-01-09 15:27 ` 'Arjunan, Srinu' via isar-users
2025-01-09 15:29 ` 'Jan Kiszka' via isar-users
2025-01-10 6:02 ` 'Arjunan, Srinu' via isar-users
2025-01-10 6:13 ` 'Jan Kiszka' via isar-users
2025-01-10 6:17 ` 'Jan Kiszka' via isar-users [this message]
2025-01-10 7:19 ` Anton Mikanovich
2025-01-10 7:24 ` Cedric Hombourger
2025-01-10 8:04 ` '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=4c5d3935-5f29-4afc-bf18-aafe02655c1b@siemens.com \
--to=isar-users@googlegroups.com \
--cc=amikan@ilbers.de \
--cc=cedric.hombourger@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=srinuvasan.a@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