Op 10 apr. 2013, om 09:44 heeft Richard Purdie <richard.pur...@linuxfoundation.org> het volgende geschreven:
> 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 <k...@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. It is weird that runqemu gets some vars from bitbake -e, and others from hardcoding them. v2 should address that. > 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. I sent it to be in time for the start of the new release :) It sure wasn't meant to go into 1.4. regards, Koen _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
