From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>,
Mark Hatle <mark.hatle@windriver.com>
Cc: Phil Blundell <philb@gnu.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH] bitbake.conf: Change WORKDIR to split by PN and version into seperate directories
Date: Sat, 22 Sep 2012 12:43:18 +0100 [thread overview]
Message-ID: <1348314198.10108.197.camel@ted> (raw)
In-Reply-To: <20120921151817.GG10268@jama.jama.net>
On Fri, 2012-09-21 at 17:18 +0200, Martin Jansa wrote:
> On Fri, Sep 21, 2012 at 03:27:48PM +0100, Phil Blundell wrote:
> > On Fri, 2012-09-21 at 15:24 +0100, Richard Purdie wrote:
> > > As per the previous patch, this is really a request for comments, I can
> > > see pros and cons...
> >
> > I've been using this configuration locally for quite some time (it's
> > needed for rm_old_works in particular) and it seems to be an improvement
> > in general.
>
> Last time I was using rm_old_works without this change
> https://github.com/shr-distribution/meta-smartphone/commit/0d4c17de1ba7343d82bb10c311754e29d573c485
>
> I've seen a lot of /usr/src/debug/${EXTENDPE}${PV}-${PR}" on target from
> -dbg packages, which doesn't look right, was this fixed in whatever packs
> source code to -dbg packages?
Probably from the way splitfile2 works in package.bbclass. I think this
should be using ${PF} explicitly if that is what it wants...
Cheers,
Richard
prev parent reply other threads:[~2012-09-22 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 14:24 [RFC PATCH] bitbake.conf: Change WORKDIR to split by PN and version into seperate directories Richard Purdie
2012-09-21 14:27 ` Phil Blundell
2012-09-21 15:18 ` Martin Jansa
2012-09-22 11:43 ` Richard Purdie [this message]
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=1348314198.10108.197.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=mark.hatle@windriver.com \
--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.