From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gylstorff Quirin <quirin.gylstorff@siemens.com>,
Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [RFC 0/2] Remove Packages during Postprocessing
Date: Tue, 17 Mar 2020 11:28:12 +0100 [thread overview]
Message-ID: <a022e363-cc45-1ffe-c81e-9348bdaadac0@siemens.com> (raw)
In-Reply-To: <789f5ab1-983a-5005-715f-eb45f6620227@siemens.com>
On 17.03.20 11:23, Gylstorff Quirin wrote:
>
>
> On 2/25/20 2:10 PM, Henning Schild wrote:
>> Am Tue, 25 Feb 2020 06:43:55 +0100
>> schrieb Gylstorff Quirin <quirin.gylstorff@siemens.com>:
>>
>>> On 2/24/20 3:24 PM, Henning Schild wrote:
>>>> 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
>>>
>>> Hi Henning,
>>>
>>> I understand your concern and I think you are right. But some people
>>> already hack the build process in similar ways and this is a way to
>>> give them some support.
>>
>> I guess it might be a good idea to tell those hackers to comment here
>> or share their reasons with you. My guess is that their need is
>> questionable and they did not fully understand the consequences. It
>> should probably be discarded as premature optimization and removed from
>> the downstream layer, instead of added upstream.
>>
>> Even if they carefully looked at the consequences for the packages they
>> remove, a generic upstream feature would ease the hack for people less
>> careful.
>
> FYI
>
> I got the same patch yesterday again for stripping a rescue system to
> fit into a NOR Flash.
>
We should move on with the series, looking into technical issues (if
any). I do think such a functionality is better provided upstream than
hacked up multiple times downstream.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2020-03-17 10:28 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 ` [RFC 0/2] Remove Packages during Postprocessing Henning Schild
2020-02-25 5:43 ` Gylstorff Quirin
2020-02-25 13:10 ` Henning Schild
2020-03-17 10:23 ` Gylstorff Quirin
2020-03-17 10:28 ` Jan Kiszka [this message]
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=a022e363-cc45-1ffe-c81e-9348bdaadac0@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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