All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Larson <clarson@mvista.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] policy about nonworking recipes
Date: Thu, 21 May 2009 14:12:18 -0700	[thread overview]
Message-ID: <4A15C3B2.7020709@mvista.com> (raw)
In-Reply-To: <4A15C20E.6020509@balister.org>

Philip Balister wrote:
> Koen Kooi wrote:
>> On 21-05-09 22:20, Rolf Leggewie wrote:
>>
>>> I think that, eventually, "bitbake world" should be working again and
>>> usable as a test case.
>>
>> A laudable goal...
>>
>>> I suggest to use COMPATIBLE_MACHINE because I
>>> assume that to be the more common issue.
>>
>> NAK, we have a perfectly good EXCLUDE_FROM_WORLD = "1" for that, 
>> which is already used in lots (well, 23) recipes and classes.
>
> Good point, after thinking about the COMPATIBLE_MACHINE idea, I was 
> thinking it would also need to be paired with COMPATIBLE_DISTRO also. 
> Using the existing EXCLUDE_WORLD would be simpler solution in my mind.
>
> I'm still interested in what other people think. 

Sounds like EXCLUDE_FROM_WORLD + DEFAULT_PREFERENCE would be all that's 
necessary to get nonworking-style functionality without moving the 
recipes, indeed.  At least this way we ensure the recipes stay 
*parsable*, which is more than we can say for the current bits :)

-Chris



  reply	other threads:[~2009-05-21 21:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21 20:20 [RFC] policy about nonworking recipes Rolf Leggewie
2009-05-21 20:41 ` Koen Kooi
2009-05-21 21:05   ` Philip Balister
2009-05-21 21:12     ` Christopher Larson [this message]
2009-05-21 21:36     ` Rolf Leggewie
2009-05-21 21:12   ` Rolf Leggewie
2009-05-21 21:46     ` Koen Kooi
2009-05-21 21:53       ` Philip Balister
2009-05-21 22:59       ` Rolf Leggewie
2009-05-21 23:29         ` Philip Balister
2009-05-21 23:46         ` Rolf Leggewie
2009-05-22  7:57         ` Yuri Bushmelev
2009-05-21 21:16   ` Rolf Leggewie

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=4A15C3B2.7020709@mvista.com \
    --to=clarson@mvista.com \
    --cc=openembedded-devel@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.