From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC][PATCH] bitbake.conf: include machine name in DEPLOY_DIR_IMAGE
Date: Wed, 10 Apr 2013 08:44:00 +0100 [thread overview]
Message-ID: <1365579840.12407.123.camel@ted> (raw)
In-Reply-To: <1365578806-1907-1-git-send-email-koen@dominion.thruhere.net>
On Wed, 2013-04-10 at 09:26 +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.
>
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> ---
> meta/conf/bitbake.conf | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
I'm pretty sure someone proposed something like this (relocating output)
just before danny. Changing something like this just before release is a
*really* bad idea. It breaks the docs and the assumptions the
autobuilder and several scripts (e.g. runqemu and the qemuimage testing)
make about where output ends up.
So as I said last time, if we want to do something like this, lets do it
at the start of development of a release, not the end.
Cheers,
Richard
next prev parent reply other threads:[~2013-04-10 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 7:26 [RFC][PATCH] bitbake.conf: include machine name in DEPLOY_DIR_IMAGE Koen Kooi
2013-04-10 7:44 ` Richard Purdie [this message]
2013-04-10 8:05 ` Koen Kooi
2013-04-10 8:29 ` Martin Jansa
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=1365579840.12407.123.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox