Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Christopher Larson <clarson@kergoth.com>,
	OpenEmbedded Core Mailing List
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH v5 1/2] base.bbclass: Add support to EXTRA_DISTRO_FEATURES
Date: Fri, 23 Aug 2013 16:31:20 +0100	[thread overview]
Message-ID: <1377271880.6762.97.camel@ted> (raw)
In-Reply-To: <CAP9ODKrtNQt7XeaXbOSTqGWFnna9soB+KRE6UAumoFGVTzr-Mg@mail.gmail.com>

On Fri, 2013-08-23 at 12:11 -0300, Otavio Salvador wrote:
> On Fri, Aug 23, 2013 at 11:59 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Fri, 2013-08-23 at 11:48 -0300, Otavio Salvador wrote:
> >> This allow the addition and removal of distro features easily. To add
> >> a feature, use:
> >>
> >>  EXTRA_DISTRO_FEATURES += "wayland"
> >>
> >> and to remove, use '~' prefix, as:
> >>
> >>  EXTRA_DISTRO_FEATURES += "~x11"
> >>
> >> This code has been mostly copied from Mentor Graphics public layer but
> >> changed the variable name for a more descriptive name. The original
> >> code can be seen at user_feature.bbclass at:
> >>
> >>  http://git.yoctoproject.org/cgit/cgit.cgi/meta-mentor
> >>
> >> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> >
> > I discussed this with Otavio. My personal view is that we should hold
> > off this right now. The removal issues he ran into with poky have been
> > addressed in other ways so there is less of an immediate issue.
> >
> > The better fix for this kind of problem is -=/=- or more likely _remove
> > override support in bitbake. I did propose a _remove patch a while back
> > but Chris has some valid concerns about it, I don't remember the details
> > offhand. I'd much rather we focused on fixing that and getting that
> > merged than trying to add this functionality to every variable.
> 
> Chris, do you know the problems Richard's patch has? I can take a look
> and try to fix it so we can get this in for 1.5.

One more thing, we need to grep the existing metadata and change any
existing _remove in variable names. I seem to remember finding one
somewhere.

Cheers,

Richard





  parent reply	other threads:[~2013-08-23 15:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23 14:48 [RFC PATCH v5 0/2] Pending changes for review/discussion Otavio Salvador
2013-08-23 14:48 ` [RFC PATCH v5 1/2] base.bbclass: Add support to EXTRA_DISTRO_FEATURES Otavio Salvador
2013-08-23 14:59   ` Richard Purdie
2013-08-23 15:11     ` Otavio Salvador
2013-08-23 15:29       ` Richard Purdie
2013-08-23 15:31       ` Richard Purdie [this message]
2013-08-23 14:48 ` [RFC PATCH v5 2/2] uboot-config.bbclass: Allow choose of U-Boot config for machine Otavio Salvador
2013-09-03 19:50   ` 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=1377271880.6762.97.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=clarson@kergoth.com \
    --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