Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: OpenEmbedded Core Mailing List
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] base.bbclass: Add COMPATIBLE_DISTRO_FEATURES support
Date: Tue, 28 May 2013 17:28:37 +0100	[thread overview]
Message-ID: <1369758517.8846.20.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <CAP9ODKpzC7hM54OQ3dBQ5fBs5D5Fo=vawo1xWWA_wLKY8cPv-w@mail.gmail.com>

On Tue, 2013-05-28 at 13:08 -0300, Otavio Salvador wrote:

> I dislike the 'required' my idea here was each item of the 'compat
> distro features' would be as an OR. Like
> 
> 
> COMPATIBLE_DISTRO_FEATURE = "x11 wayland"

Oh, right, I see.  Sorry, I misunderstood the intent of your original
patch.

Well, then, how about making each item be a regex and having:

REQUIRED_DISTRO_FEATURES = "x11|wayland qt|gtk"

or some such?

All that said, before spending too much more time debating the minutiae
of this particular feature, I'd kind of like to get a better
understanding of what problem it's actually solving.  How many recipes
would actually need to use this mechanism and why?

p.




  reply	other threads:[~2013-05-28 16:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28 15:04 [PATCH] base.bbclass: Add COMPATIBLE_DISTRO_FEATURES support Otavio Salvador
2013-05-28 15:12 ` Phil Blundell
2013-05-28 15:18   ` Otavio Salvador
2013-05-28 15:21     ` Eric Bénard
2013-05-28 15:26       ` Otavio Salvador
2013-05-28 15:31     ` Phil Blundell
2013-05-28 16:08       ` Otavio Salvador
2013-05-28 16:28         ` Phil Blundell [this message]
2013-05-28 16:33           ` Otavio Salvador
2013-05-28 16:36             ` Phil Blundell
2013-05-28 16:39               ` Otavio Salvador

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=1369758517.8846.20.camel@phil-desktop.brightsign \
    --to=pb@pbcl.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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