All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
	openembedded-core@lists.openembedded.org
Subject: Re: [RFC][PATCHv2] bitbake.conf: include machine name in DEPLOY_DIR_IMAGE
Date: Wed, 04 Sep 2013 14:44:54 +0100	[thread overview]
Message-ID: <1378304978.cEImkS9DJd@helios> (raw)
In-Reply-To: <20130828082900.GG3544@jama>

On Wednesday 28 August 2013 10:29:00 Martin Jansa wrote:
> On Wed, Apr 10, 2013 at 10:05:01AM +0200, Koen Kooi wrote:
> > This allows a clean seperation between all image outputs and making it
> > possible to have convinience symlinks to make it ready to deploy. And
> > while it isn't a valid reason, it must be mentioned: BSP layers which do
> > use convenience symlinks already don't step on files owned by others
> > anymore.
> > 
> > I assumed this was the default behaviour in OE-classic, but as it turns
> > out every DISTRO set it to deploy/images/$MACHINE on its own.
> > 
> > Code inspections shows that the all references to the image deploy dir in
> > classes and scripts in OE-core do the right thing and parse the
> > DEPLOY_DIR_IMAGE variable, except runqemu.
>
> Is there some reason why this patch didn't make it into 1.5?

I think it just got missed; looking at the changes made to runqemu I can see a 
couple of concerns (double execution of bitbake -e and one missed change to 
DEPLOY_DIR_IMAGE, albeit only in a message). I'm coming up with a revised 
version now.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


      reply	other threads:[~2013-09-04 13:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10  8:05 [RFC][PATCHv2] bitbake.conf: include machine name in DEPLOY_DIR_IMAGE Koen Kooi
2013-04-14 17:05 ` Martin Jansa
2013-04-14 17:23   ` Koen Kooi
2013-08-28  8:29 ` Martin Jansa
2013-09-04 13:44   ` Paul Eggleton [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=1378304978.cEImkS9DJd@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=koen@dominion.thruhere.net \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.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.