public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 2/2] Clean apt cache from debootstrapped rootfs dirs
Date: Tue, 3 Jan 2023 10:01:25 +0100	[thread overview]
Message-ID: <CAJGKYO6pzHDg9TJhGVs5BcCX1omKcNY+LGP4zJYz_KpuxAhPaQ@mail.gmail.com> (raw)
In-Reply-To: <20230102173306.4116a115@md1za8fc.ad001.siemens.net>

[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]

Il Lun 2 Gen 2023, 17:33 Henning Schild <henning.schild@siemens.com> ha
scritto:

> Am Fri, 30 Dec 2022 05:38:58 +0100
> schrieb Uladzimir Bely <ubely@ilbers.de>:
>
>         chroot "${ROOTFSDIR}" /usr/bin/apt-get -y clean
>
> I did not look into the details, but maybe that is what one might want
> after most of not all calls to deb_dl_dir_export.


Hi all,

There is a specific function/task that do that in rootfs post processing
which means that clean the apt cache BEFORE importing it (*).

Then with the schroot only patchset (which misaing the dpkg base class to
rip off buildchroot but it is straightforward to achieve) there is just one
need of this after inage finalisation (but just for aesthetic reasons due
to the use of ln -P).

(*) that task is currently also removing debian lists which is not intended
for and IHMO the two ROOTFS_FEATURE should be separated.

However, inserting at the end of deb_dl_export would simply the whole
architecture. Moreover, every import/export if packages should also do the
same with apt-get update lists in such a way it will be run faster also
with a slow Internet connection.

Another trick that matters to implement: wic stuff is produced into a local
schroot mount point and then moved outside causing a duplication of disk
I/O while using the final destination immediately will save that burden and
when the inage is about 10Gb, is not a little thing.

All these stuff can be seen in the branch 'schroot' of my fork plus some
fixes.

Best regards, R.

[-- Attachment #2: Type: text/html, Size: 2349 bytes --]

      reply	other threads:[~2023-01-03  9:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30  4:38 [PATCH 0/2] Improving apt cache Uladzimir Bely
2022-12-30  4:38 ` [PATCH 1/2] Use hardlinks in deb-dl-dir functions Uladzimir Bely
2022-12-30  7:29   ` Moessbauer, Felix
2022-12-30  8:29     ` Roberto A. Foglietta
2022-12-30  4:38 ` [PATCH 2/2] Clean apt cache from debootstrapped rootfs dirs Uladzimir Bely
2022-12-30  9:03   ` Roberto A. Foglietta
2023-01-02 16:27   ` Henning Schild
2023-01-02 16:33   ` Henning Schild
2023-01-03  9:01     ` Roberto A. Foglietta [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=CAJGKYO6pzHDg9TJhGVs5BcCX1omKcNY+LGP4zJYz_KpuxAhPaQ@mail.gmail.com \
    --to=roberto.foglietta@gmail.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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