From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Uladzimir Bely <ubely@ilbers.de>
Cc: "Moessbauer, Felix" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 0/3] Improving apt cache
Date: Fri, 20 Jan 2023 08:12:31 +0100 [thread overview]
Message-ID: <CAJGKYO4ZPDP1gCDtbTW82DiU=Gm_Yg+s=ynWhEmySzSQeAcKyg@mail.gmail.com> (raw)
In-Reply-To: <1889300.7Z3S40VBb9@hp>
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
On Fri, 20 Jan 2023 at 08:00, Uladzimir Bely <ubely@ilbers.de> wrote:
> In mail from пятница, 20 января 2023 г. 08:08:03 +03 user Moessbauer,
> Felix
> wrote:
> > On Fri, 2023-01-20 at 07:44 +0300, Uladzimir Bely wrote:
> >
> > > In mail from четверг, 19 января 2023 г. 17:52:37 +03 user Roberto A.
>
> > >
> > > I see the following possible solutions that allows to save space.
> > > 1. Since hardlinks don't work, try to use symlinks.
> >
> >
> > If that works, it clearly is the simplest solution.
> >
>
> Yes, approach with symlinks inside sbuild chroot seems to be working, so
> I'm
> going to use it in patchset v3.
>
The symlink or software link does not work for exportation... I presume,
did you check?
Without changing anything it is easy to confuse an old-built package with
the nwer.
Best regards,
--
Roberto A. Foglietta
+49.176.274.75.661
+39.349.33.30.697
[-- Attachment #2: Type: text/html, Size: 1489 bytes --]
next prev parent reply other threads:[~2023-01-20 7:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 6:48 Uladzimir Bely
2023-01-06 6:48 ` [PATCH v2 1/3] Clean apt cache from debootstrapped rootfs dirs Uladzimir Bely
2023-01-06 6:48 ` [PATCH v2 2/3] Use hardlinks in deb-dl-dir functions Uladzimir Bely
2023-01-06 6:48 ` [PATCH v2 3/3] Changes for a faster build using less disk space Uladzimir Bely
2023-01-06 15:58 ` Henning Schild
2023-01-06 17:38 ` Uladzimir Bely
2023-01-06 17:52 ` Roberto A. Foglietta
2023-01-06 18:11 ` Henning Schild
2023-01-09 6:32 ` [PATCH v2 0/3] Improving apt cache Moessbauer, Felix
2023-01-09 7:39 ` Uladzimir Bely
2023-01-19 7:36 ` Uladzimir Bely
2023-01-19 14:52 ` Roberto A. Foglietta
2023-01-19 16:30 ` Roberto A. Foglietta
2023-01-20 4:44 ` Uladzimir Bely
2023-01-20 5:08 ` Moessbauer, Felix
2023-01-20 7:01 ` Uladzimir Bely
2023-01-20 7:12 ` Roberto A. Foglietta [this message]
2023-01-20 7:23 ` Uladzimir Bely
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='CAJGKYO4ZPDP1gCDtbTW82DiU=Gm_Yg+s=ynWhEmySzSQeAcKyg@mail.gmail.com' \
--to=roberto.foglietta@gmail.com \
--cc=felix.moessbauer@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