From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: Change in behaviour
Date: Fri, 20 Nov 2015 08:18:33 -0700 [thread overview]
Message-ID: <564F39C9.9070201@mlbassoc.com> (raw)
In-Reply-To: <564F34B8.9020801@balister.org>
On 2015-11-20 07:56, Philip Balister wrote:
> On 11/20/2015 09:47 AM, Gary Thomas wrote:
>> This commit:
>> commit 536b73f55f51fcea555338f9a557fe86c09d00cb
>> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
>> Date: Sun Oct 11 10:21:20 2015 +0100
>> bitbake: data_smart: Only support lowercase OVERRIDES
>> breaks the use of capital letters, specifically in MACHINE names.
>> I use this a lot, along with COMPATIBLE_MACHINE, to share recipes
>> amongst similar machines.
>>
>> The commit says it could be conditional. How hard (and how)
>> would it be to do that?
>>
>
> A little background:
>
> http://openembedded.org/wiki/OEDEM_2015#Metadata
Fair enough + I missed the RFC for the patch that eventually went in.
That said, maybe a warning could be issued if overrides (at least MACHINEOVERRIDES)
are being defined with any upper-case letters rather than the [very silent
and hard to find] new behaviour causing issues?
I'll set off to rework all of my recipes that use upper case
letters in any way - a lot of work I'm sad to say...
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2015-11-20 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 14:47 Change in behaviour Gary Thomas
2015-11-20 14:56 ` Philip Balister
2015-11-20 15:18 ` Gary Thomas [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=564F39C9.9070201@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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.