From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] core/pkg-generic: check proper package installation
Date: Thu, 27 Oct 2016 10:46:58 +0200 [thread overview]
Message-ID: <20161027104658.6edfaae3@free-electrons.com> (raw)
In-Reply-To: <878ttajief.fsf@dell.be.48ers.dk>
Hello,
On Thu, 27 Oct 2016 10:38:48 +0200, Peter Korsgaard wrote:
> > commit: https://git.buildroot.net/buildroot/commit/?id=938f47c7e89362e7b824dbd0bd1ee9839d56d603
> > branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>
> > Some packages misbehave, and install files in either $(STAGING_DIR)/$(O)
> > or in $(TARGET_DIR)/$(O) .
>
> > One common reason for that is that pkgconf now prepends the sysroot path
> > to all the paths it returns. Other reasons vary, but are mostly due to
> > poorly writen generic-packages.
>
> > And a new step hooks to check that no file gets installed in either
> > location, called after the install-target and install-staging steps.
>
> Didn't we just discuss that this duplicates the proposed
> leak-of-host-paths stuff Samuel is working on?
It does, but Samuel's work is not merged, and this is already useful by
itself. It can always be removed once Samuel's work is merged.
I guess Samuel is working first on the host rpath relativization, then
the target rpath cleanup, and finally the target "leak of host path"
stuff. So it might be a while before Samuel's patches are ready and
merged.
And Yann's patch has already uncovered an issue with the Bellagio
package.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-10-27 8:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 20:36 [Buildroot] [git commit] core/pkg-generic: check proper package installation Thomas Petazzoni
2016-10-27 8:38 ` Peter Korsgaard
2016-10-27 8:46 ` Thomas Petazzoni [this message]
2016-10-27 8:56 ` Peter Korsgaard
2016-10-27 9:04 ` Thomas Petazzoni
2016-10-27 9:39 ` Vicente Olivert Riera
2016-10-27 15:34 ` Vicente Olivert Riera
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=20161027104658.6edfaae3@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 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.