From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Uladzimir Bely <ubely@ilbers.de>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: Better way to handle apt cache needed
Date: Fri, 30 Dec 2022 08:08:26 +0100 [thread overview]
Message-ID: <CAJGKYO5D=rSD1tGObBPi4PiFsdPb5RPZ5m_dPkm3Zb+srmSy5w@mail.gmail.com> (raw)
In-Reply-To: <3494812.dWV9SEqChM@hp>
On Fri, 30 Dec 2022 at 05:38, Uladzimir Bely <ubely@ilbers.de> wrote:
>
> Hello Roberto.
>
> I also did some similar improvements. They are not so radical as yours and the
> benefit is not so big. But anyway, I'm sending 1st version of patchset. For
> the 2nd version I plan to play with your idea with CACHEDIR.TAG and `tar -
> exclude-caches` option and to improve work with additional internal sbuild
> copying that you've already implemented.
>
About the use of hard links, I do not think that it is a problem
because in build we can find 4 rootfs folders in which there are
everything supposed to be on a Linux rootfs included links of every
nature
4114 build/tmp/work/debian-bullseye-amd64/isar-bootstrap-target/1.0-r0/rootfs
4501 build/tmp/work/debian-bullseye-amd64/sbuild-chroot-target/1.0-r0/rootfs
4559 build/tmp/work/debian-bullseye-amd64/buildchroot-target/1.0-r0/rootfs
9064 build/tmp/work/debian-bullseye-amd64/eval-image-debx86/1.0-r0/rootfs
This makes me think that trying to use ISAR on every filesystem that
does not support all this stuff would not be able to create a suitable
rootfs. So, the use of ln -P should not be a problem.
Best regards, R-
next prev parent reply other threads:[~2022-12-30 7:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 9:02 Moessbauer, Felix
2022-12-28 9:21 ` Baurzhan Ismagulov
2022-12-28 9:45 ` Moessbauer, Felix
2022-12-28 10:23 ` Uladzimir Bely
2022-12-28 11:04 ` Moessbauer, Felix
2022-12-29 23:15 ` Roberto A. Foglietta
2022-12-30 4:38 ` Uladzimir Bely
2022-12-30 7:08 ` Roberto A. Foglietta [this message]
2022-12-30 6:05 ` Moessbauer, Felix
2022-12-30 8:27 ` Roberto A. Foglietta
2022-12-30 10:04 ` Moessbauer, Felix
2022-12-30 13:11 ` Moessbauer, Felix
2022-12-30 13:33 ` Roberto A. Foglietta
2022-12-30 13:47 ` Roberto A. Foglietta
2022-12-31 8:59 ` Roberto A. Foglietta
2022-12-31 21:03 ` Roberto A. Foglietta
2023-01-09 8:12 ` Roberto A. Foglietta
2023-01-09 9:58 ` Roberto A. Foglietta
2023-01-19 18:08 ` Roberto A. Foglietta
2023-01-25 4:48 ` Roberto A. Foglietta
2023-02-10 16:05 ` Roberto A. Foglietta
2023-02-14 10:01 ` Roberto A. Foglietta
2023-02-14 16:46 ` Roberto A. Foglietta
2022-12-30 12:29 ` Roberto A. Foglietta
2022-12-28 9:22 ` Florian Bezdeka
2023-01-02 16:15 ` Henning Schild
2023-01-05 6:31 ` Uladzimir Bely
2023-01-05 17:10 ` Roberto A. Foglietta
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='CAJGKYO5D=rSD1tGObBPi4PiFsdPb5RPZ5m_dPkm3Zb+srmSy5w@mail.gmail.com' \
--to=roberto.foglietta@gmail.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