From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Phil Blundell <philb@gnu.org>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] sstate: Add detail to shared area warning
Date: Tue, 02 Oct 2012 23:22:39 +0100 [thread overview]
Message-ID: <1349216559.18301.18.camel@ted> (raw)
In-Reply-To: <20121002221141.GG15881@jama.jama.net>
On Wed, 2012-10-03 at 00:11 +0200, Martin Jansa wrote:
> On Tue, Oct 02, 2012 at 11:00:53PM +0100, Phil Blundell wrote:
> > On Tue, 2012-10-02 at 15:00 -0700, Saul Wold wrote:
> > > - bb.warn("The recipe is trying to install files into a shared area when those files already exist. Those files are:\n %s" % "\n ".join(match))
> > > + bb.warn("The %s recipe is trying to install files into a shared area when those files already exist (please fix %s). Those files are:\n %s" % (d.getVar('PN', True), d.getVar('FILE', True), "\n ".join(match)))
> >
> > That seems potentially misleading: the file that needs fixing isn't
> > necessarily the one that triggers this warning. What would be ideal
> > would be to have it output the names of all recipes that have tried to
> > stage the files in question so that the user can make an informed
> > decision about which one ought to be putting them there.
>
> Maybe something like master.list was before
> http://git.openembedded.org/openembedded-core/commit/?id=603daf343ad3f18c8adb799e3625ae2a18d94f56
> with added recipe name, but that doesn't detect files already
We can list any sstate manifest files (tmp/sstate-control) also adding
that file which may or may not have a listing of it. We might as well
just grep those files and print matches.
We are not going back to a master.list file, its a performance headache.
Cheers,
Richard
next prev parent reply other threads:[~2012-10-02 22:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 22:00 [PATCH] sstate: Add detail to shared area warning Saul Wold
2012-10-02 22:00 ` Phil Blundell
2012-10-02 22:06 ` Saul Wold
2012-10-02 22:05 ` Phil Blundell
2012-10-02 22:11 ` Martin Jansa
2012-10-02 22:22 ` Richard Purdie [this message]
2012-10-03 1:00 ` McClintock Matthew-B29882
2012-10-02 22:20 ` Richard Purdie
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=1349216559.18301.18.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@gnu.org \
/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.