From: John Keeping <john@metanate.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] support/scripts/check-uniq-files: ignore reinstalled packages
Date: Fri, 27 Apr 2018 11:31:19 +0100 [thread overview]
Message-ID: <20180427113119.591e8441.john@metanate.com> (raw)
In-Reply-To: <1437404419.346987.1524766955385.JavaMail.zimbra@datacom.ind.br>
On Thu, 26 Apr 2018 15:22:35 -0300 (BRT)
Henrique Marks <henrique.marks@datacom.ind.br> wrote:
> ----- Mensagem original -----
> > De: "John Keeping" <john@metanate.com>
> > Para: buildroot at buildroot.org
> > Cc: "John Keeping" <john@metanate.com>
> > Enviadas: Quinta-feira, 26 de abril de 2018 13:27:31
> > Assunto: [Buildroot] [PATCH] support/scripts/check-uniq-files:
> > ignore reinstalled packages
>
> > If a package is rebuilt, then any files it installs will be listed
> > multiple times in the file list and check-uniq-files will report
> > that these files are touched by more than one package even though
> > it is the same package listed multiple times.
> >
> > Switch to storing the package names in a set so that each package
> > can only appear once.
>
> I can confirm we have problems rebuilding packages using buildroot
> 2018-02.1. The 3 files "package-file-list" are increasing in size
> when we rebuild packages (make <pkg>-rebuild or make
> <pkg>-reinstall), and the compilation time is increasing linearly
> with every rebuild, but the increase is noticeable.
I hadn't considered this aspect of the problem. Maybe we are better
fixing the root cause of the problem with a patch like this:
-- >8 --
diff --git a/package/pkg-generic.mk b/package/pkg-generic.mk
index 1c9dd1d734..edc2c9349c 100644
--- a/package/pkg-generic.mk
+++ b/package/pkg-generic.mk
@@ -64,6 +64,7 @@ GLOBAL_INSTRUMENTATION_HOOKS += step_time
# $(3): suffix of file (optional)
define step_pkg_size_inner
cd $(2); \
+ $(SED) '/^$(1),/d' $(BUILD_DIR)/packages-file-list$(3).txt; \
find . \( -type f -o -type l \) \
-newer $($(PKG)_DIR)/.stamp_built \
-exec printf '$(1),%s\n' {} + \
-- 8< --
But I don't know enough about the build process to know if this is safe
in the presence of top-level parallel build.
Regards,
John
next prev parent reply other threads:[~2018-04-27 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 16:27 [Buildroot] [PATCH] support/scripts/check-uniq-files: ignore reinstalled packages John Keeping
2018-04-26 18:22 ` Henrique Marks
2018-04-27 10:31 ` John Keeping [this message]
2018-04-28 21:29 ` Yann E. MORIN
2018-05-03 16:27 ` Angelo Compagnucci
2018-05-03 16:36 ` John Keeping
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=20180427113119.591e8441.john@metanate.com \
--to=john@metanate.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.