Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: DORA RFC: FILESOVERIDES in dora
Date: Mon, 18 Nov 2013 11:10:18 +0000	[thread overview]
Message-ID: <1384773018.6460.202.camel@ted> (raw)

We have an issue in the dora branch at the moment. When I merged in the
set of bug fixes post release, I added:

http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=dora&id=0bd63125c3b44a656e44f2a76cc5f832c9db4bbd

which wasn't entirely intentional. It changes the behaviour of
FILESOVERRIDES. The bug there is real with "arm" overrides being
preferred to "armv7a" for example and other strange/incorrect ordering.
It was in fact impossible to override certain things which people needed
to in some circumstances and defeated the purpose of OVERRIDES.

I don't doubt this change is correct in master, the question is whether
it should be in dora. The issue is that some layers don't work correctly
before/after the change and we now have a bit of a confused situation.

Our options are either:

a) Revert the change in the branch. Anyone who adapted to the correct
behaviour on the branch would need to revert those changes

b) Keep this change in there and adapt layers to fix any incorrect
behaviour.

I'm open to either option but I think this needs discussion before we do
anything. I'd appreciate other people's views, particularly those of
layer maintainers.

Cheers,

Richard




             reply	other threads:[~2013-11-18 11:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 11:10 Richard Purdie [this message]
2013-11-18 11:15 ` DORA RFC: FILESOVERIDES in dora Burton, Ross
2013-11-18 11:18   ` Otavio Salvador
2013-11-18 12:46   ` Robert Yang
2013-11-18 14:25     ` Burton, Ross
2013-11-18 15:37   ` 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=1384773018.6460.202.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=liezhi.yang@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox