public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Uladzimir Bely <ubely@ilbers.de>
Cc: Henning Schild <henning.schild@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH v2 3/3] Changes for a faster build using less disk space
Date: Fri, 6 Jan 2023 18:52:38 +0100	[thread overview]
Message-ID: <CAJGKYO6fTcYdv4JaHDyhwbA2G4Wq6bCOEn-PEamwKhw9pMqrug@mail.gmail.com> (raw)
In-Reply-To: <5434767.rdbgypaU67@home>

On Fri, 6 Jan 2023 at 18:38, Uladzimir Bely <ubely@ilbers.de> wrote:
>
> In the email from Friday, 6 January 2023 18:58:26 +03 user Henning Schild
> wrote:

> Original patch from Roberto included both `--exclude-caches` and `--
> exclude=var/cache/apt/archives"` options for `tar`. First one was expected to
> automatically exclude all directories that contain special CACHEDIR.TAG file
> [1]. But it appeared not to work. Investigating the problem shown that it
> should not be empty file: GNU tar expects file starts with "Signature:
> 8a477f597d28d172789f06886806bc55" line.
>
> It means, all the stuff with multiple "touch CACHEDIR.TAG" was useless and the
> actually only option "--exclude=var/cache/apt/archives" did the trick.
>
> I fixed first and removed second option. But you are right, we can do vice
> versa and it should look even simpler.
>

vice-versa means using --exclude because we know the folders in
advance and left --exclude-caches / --exclude-backups for the pain of
the users...
...as I did because it is simpler in terms of code changes and more
efficient at running time.
:-)

Bests, R-

  reply	other threads:[~2023-01-06 17:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06  6:48 [PATCH v2 0/3] Improving apt cache 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 [this message]
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
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=CAJGKYO6fTcYdv4JaHDyhwbA2G4Wq6bCOEn-PEamwKhw9pMqrug@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