public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
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: Thu, 9 Jan 2025 16:29:53 +0100	[thread overview]
Message-ID: <0744e847-638a-40fe-bed6-b1f7267132f7@siemens.com> (raw)
In-Reply-To: <PUZPR06MB574753915306A59D6DA6F6EA88132@PUZPR06MB5747.apcprd06.prod.outlook.com>

On 09.01.25 16:27, Arjunan, Srinu (FT FDS CES LX PBU 2) wrote:
> I validated the isar-mmdebstrap-target rootfs with and without docs, I could able to see approx  17MB differences.
> 

That is not my point.

Are you trying to optimize the intermediate artifact sizes or the final
image? The latter should also be addressed by using isar-exclude-docs.
The former would need some stronger motivation, I would say...

Jan

> Note: compared the compressed rootfs (rootfs.tar.zst) file
> 
> Many thanks,
> Srinu
> 
> -----Original Message-----
> From: Kiszka, Jan (FT RPD CED) <jan.kiszka@siemens.com> 
> Sent: 09 January 2025 20:50
> To: Arjunan, Srinu (FT FDS CES LX PBU 2) <srinuvasan.a@siemens.com>; isar-users@googlegroups.com
> Cc: Hombourger, Cedric (FT FDS CES LX) <cedric.hombourger@siemens.com>; amikan@ilbers.de
> Subject: Re: [PATCH] isar-mmdebstrap: reduce rootfs size as much as possible
> 
> On 09.01.25 13:17, srinuvasan.a via isar-users wrote:
>> From: srinuvasan <srinuvasan.a@siemens.com>
>>
>> reduce the rootfs image size by excluding man and doc, this changes 
>> significantly reduce size from (~80MB) to (~64MB).
>>
> 
> What's the (final) difference to isar-exclude-docs?
> 
> Jan
> 
> --
> Siemens AG, Foundational Technologies
> Linux Expert Center


-- 
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/0744e847-638a-40fe-bed6-b1f7267132f7%40siemens.com.

  reply	other threads:[~2025-01-09 15:30 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 [this message]
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
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=0744e847-638a-40fe-bed6-b1f7267132f7@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