From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>,
"[ext] Christian Storm" <christian.storm@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH] isar-image-base: purge installation logs of installed packages
Date: Mon, 20 Nov 2017 17:23:10 +0100 [thread overview]
Message-ID: <af07a630-5ad5-002f-09fd-d88869d2a849@siemens.com> (raw)
In-Reply-To: <20171120165925.73100f2b@md1em3qc>
On 2017-11-20 16:59, [ext] Henning Schild wrote:
> It does not matter how much space we can save with individual
> directories and we might as well start the discussion on 40k. I think
> we will need a cleanup script to run after multistrap, or (better) as a
> hook to the last package we install.
>
> That mechanism needs to be customizable from a layer and it
> needs to be optional. So the configscript is the wrong place.
...and modularized so that you can select something like "remove package
data base" on a per project basis and without having to write and
maintain the rules for that yourself.
Jan
>
> Henning
>
> Am Fri, 10 Nov 2017 11:28:08 +0100
> schrieb "[ext] Christian Storm" <christian.storm@siemens.com>:
>
>> Signed-off-by: Christian Storm <christian.storm@siemens.com>
>> ---
>> meta-isar/recipes-core/images/files/debian-configscript.sh | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git
>> a/meta-isar/recipes-core/images/files/debian-configscript.sh
>> b/meta-isar/recipes-core/images/files/debian-configscript.sh index
>> 33b2b53..b0e3f6d 100755 ---
>> a/meta-isar/recipes-core/images/files/debian-configscript.sh +++
>> b/meta-isar/recipes-core/images/files/debian-configscript.sh @@ -76,6
>> +76,9 @@ fi localepurge apt-get clean
>>
>> +# Purge installation logs of installed packages
>> +rm -f /var/log/dpkg.log /var/log/alternatives.log
>> +
>> # Undo setup script changes
>> if [ -x "$TARGET/sbin/start-stop-daemon.REAL" ]; then
>> mv -f $TARGET/sbin/start-stop-daemon.REAL
>> $TARGET/sbin/start-stop-daemon
>
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2017-11-20 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 10:28 Christian Storm
2017-11-17 15:28 ` Alexander Smirnov
2017-11-17 16:38 ` Christian Storm
2017-11-20 15:59 ` Henning Schild
2017-11-20 16:23 ` Jan Kiszka [this message]
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=af07a630-5ad5-002f-09fd-d88869d2a849@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=christian.storm@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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