public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: "Q. Gylstorff" <Quirin.Gylstorff@siemens.com>
Cc: <isar-users@googlegroups.com>, <jan.kiszka@siemens.com>
Subject: Re: [RFC 0/2] Remove Packages during Postprocessing
Date: Mon, 24 Feb 2020 15:24:16 +0100	[thread overview]
Message-ID: <20200224152416.2aab3ec9@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20200221145348.24250-1-Quirin.Gylstorff@siemens.com>

Hi,

my opinion on that is clear. Fix it upstream or live with those
packages. You are either on a distro or fiddle around and tune
everything until you are the only one on the planet testing your setup.
That is Isar vs. yocto ... whoever thinks they _need_ that should maybe
think again. If they need it they can put it into their own layer or
use yocto ;).
I do not think upstream should carry such hacky features unless we get
better reasoning ... Removing "required" packages has the potential to
break your image in funny ways ... that is much more expensive than a
few MB disc space. All affected packages are likely already cleared and
vulnerabilty monitored by someone else, find that someone and share the
cost!

Henning

On Fri, 21 Feb 2020 15:53:46 +0100
"Q. Gylstorff" <Quirin.Gylstorff@siemens.com> wrote:

> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> 
> Some packages even if the are part of minbase are not necessary
> to run a debian system. Debian has some issues and experiments
> to remove packages from minbase [1]. This feature allows a
> expert user to remove packages from the final image during post
> processing.
> 
> The reason for this are e.g. disk usage reduction and reduction
> of the clearing effort.
> 
> The method to remove packages in postprocessing is a best-effort
> action.
> 
> Another way would be to identify like [1] packages in
> minbase which can be removed without compremising the isar rootfs
> creation and remove them directly after or during bootstrapping.
> If a package is used for a production related feature it should be
> reinstalled.
> 
> 
> [1]: https://wiki.debian.org/BusterPriorityRequalification
> 
> Quirin Gylstorff (2):
>   meta/classes: Add remove packages to rootfs postprocessing
>   meta-isar/images: Remove gcc-8-base from rootfs
> 
>  meta-isar/recipes-core/images/isar-image-base.bb |  4 ++++
>  meta/classes/image.bbclass                       |  2 +-
>  meta/classes/rootfs.bbclass                      | 13 +++++++++++++
>  3 files changed, 18 insertions(+), 1 deletion(-)
> 


  parent reply	other threads:[~2020-02-24 14:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 14:53 Q. Gylstorff
2020-02-21 14:53 ` [RFC 1/2] meta/classes: Add remove packages to rootfs postprocessing Q. Gylstorff
2020-02-21 18:28   ` Jan Kiszka
2020-02-24 13:04     ` Gylstorff Quirin
2020-02-21 14:53 ` [RFC 2/2] meta-isar/images: Remove gcc-8-base from rootfs Q. Gylstorff
2020-02-21 18:29   ` Jan Kiszka
2020-02-24 14:24 ` Henning Schild [this message]
2020-02-25  5:43   ` [RFC 0/2] Remove Packages during Postprocessing Gylstorff Quirin
2020-02-25 13:10     ` Henning Schild
2020-03-17 10:23       ` Gylstorff Quirin
2020-03-17 10:28         ` Jan Kiszka
2020-03-17 10:48       ` Gylstorff Quirin
2022-09-22  5:55     ` Balasubramanian Sundaram
2022-09-22  9:26       ` Henning Schild

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=20200224152416.2aab3ec9@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=Quirin.Gylstorff@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@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