From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv4] core/pkg-generic: check proper package installation
Date: Sun, 29 Nov 2015 19:27:08 +0100 [thread overview]
Message-ID: <20151129192708.5120d6a3@free-electrons.com> (raw)
In-Reply-To: <20151129181007.GF3630@free.fr>
Hello,
On Sun, 29 Nov 2015 19:10:07 +0100, Yann E. MORIN wrote:
> Well, I for one would prefer we fail right on the culprit package,
> rather than port-pone the check until the end. This way, it is obvious
> which package is the cuplrit.
It's a matter of trade-off between the benefits and the additional
complexity. IMO, the benefits of failing immediately on the culprit
package are not that big. When we'll look at the incorrectly installed
files, it will in 99% of the cases be obvious from which packages the
files are coming, and in the 1% remaining cases, a simple "find" on a
file with a name that isn't too generic will give us the answer.
> Except we now have a file-> package mapping (thanks to your graph-size),
> so we could re-use that in a target-inalise hook, indeed.
>
> Well, except maybe not... Can target-finalise be called before we have
> all the host packages (most notably the filesystem image generators)?
The dependencies of rootfs generators are added to PACKAGES, so they
are built before target-finalize:
in fs/common.mk:
PACKAGES += $$(filter-out rootfs-%,$$(ROOTFS_$(2)_DEPENDENCIES))
in Makefile:
target-finalize: $(PACKAGES)
> > Or alternatively, use the existing instrumentation hooks.
>
> Arnout did not like that, hence why I put in the common install rule.
What was Arnout reasoning?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-11-29 18:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 19:15 [Buildroot] [PATCHv4] core/pkg-generic: check proper package installation Yann E. MORIN
2015-11-06 22:55 ` Arnout Vandecappelle
2015-11-06 23:07 ` Yann E. MORIN
2015-11-06 23:12 ` Arnout Vandecappelle
2015-11-09 13:20 ` Luca Ceresoli
2015-11-09 14:52 ` Arnout Vandecappelle
2015-11-29 17:58 ` Thomas Petazzoni
2015-11-29 18:10 ` Yann E. MORIN
2015-11-29 18:27 ` Thomas Petazzoni [this message]
2015-11-29 20:04 ` Yann E. MORIN
2015-11-29 20:31 ` Arnout Vandecappelle
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=20151129192708.5120d6a3@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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