From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] core/pkg-generic: only save latest package list
Date: Tue, 01 May 2018 23:01:25 +0200 [thread overview]
Message-ID: <87wowndra2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180501122841.13818-1-john@metanate.com> (John Keeping's message of "Tue, 1 May 2018 13:28:41 +0100")
>>>>> "John" == John Keeping <john@metanate.com> writes:
> When rebuilding a package, simply appending the package's file list to
> the global list means that the package list grows for every rebuild, as
> does the time taken to check for files installed by multiple packages.
> Furthermore, we get false positives where a file is reported as being
> installed by multiple copies of the same package.
> With this approach we may end up with orphaned files in the target
> filesystem if a package that has been updated and rebuilt no longer
> installs the same set of files, but we know that only a clean build will
> produce reliable results. In fact it may be helpful to identify these
> orphaned files as evidence that the build is not clean.
> Signed-off-by: John Keeping <john@metanate.com>
> ---
> Changes in v3:
> - Use touch instead of redirect to avoid truncating the file
Committed to 2018.02.x, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-05-01 21:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-29 13:07 [Buildroot] [PATCH] core/pkg-generic: only save latest package list John Keeping
2018-04-30 16:47 ` Yann E. MORIN
2018-04-30 16:56 ` John Keeping
2018-04-30 19:41 ` Yann E. MORIN
2018-05-01 11:13 ` [Buildroot] [PATCH v2] " John Keeping
2018-05-01 12:04 ` Yann E. MORIN
2018-05-01 12:26 ` John Keeping
2018-05-01 12:28 ` [Buildroot] [PATCH v3] " John Keeping
2018-05-01 12:31 ` Yann E. MORIN
2018-05-01 13:26 ` Thomas Petazzoni
2018-05-01 21:01 ` Peter Korsgaard [this message]
2019-01-04 13:12 ` Yann E. MORIN
2019-01-04 15:30 ` Nicolas Cavallari
2019-01-04 17:51 ` Yann E. MORIN
2019-01-05 10:23 ` Nicolas Cavallari
2019-01-05 16:39 ` Yann E. MORIN
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=87wowndra2.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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