From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: 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 15:59:16 +0100 [thread overview]
Message-ID: <1377269956.6762.92.camel@ted> (raw)
In-Reply-To: <1377269339-6139-2-git-send-email-otavio@ossystems.com.br>
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.
Cheers,
Richard
> ---
> Changes in v5:
> - Resend
>
> Changes in v4:
> - Drop _prepend/_append hack and remove/add DISTRO_FEATURES (thanks to
> RP for the tip).
>
> Changes in v3:
> - Drop _prepend/_append flags from DISTRO_FEATURES to avoid the re-add
>
> Changes in v2:
> - Use data copy to fix wrong prepend/append expanding.
>
> meta/classes/base.bbclass | 4 ++++
> meta/lib/oe/utils.py | 24 ++++++++++++++++++++++++
> 2 files changed, 28 insertions(+)
>
> diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
> index 98b823e..f30f4db 100644
> --- a/meta/classes/base.bbclass
> +++ b/meta/classes/base.bbclass
> @@ -288,6 +288,9 @@ def buildcfg_neededvars(d):
> if pesteruser:
> bb.fatal('The following variable(s) were not set: %s\nPlease set them directly, or choose a MACHINE or DISTRO that sets them.' % ', '.join(pesteruser))
>
> +EXTRA_DISTRO_FEATURES ?= ""
> +EXTRA_DISTRO_FEATURES[type] = "list"
> +
> addhandler base_eventhandler
> base_eventhandler[eventmask] = "bb.event.ConfigParsed bb.event.BuildStarted"
> python base_eventhandler() {
> @@ -297,6 +300,7 @@ python base_eventhandler() {
> preferred_ml_updates(e.data)
> oe.utils.features_backfill("DISTRO_FEATURES", e.data)
> oe.utils.features_backfill("MACHINE_FEATURES", e.data)
> + oe.utils.extra_distro_features(e.data)
>
> if isinstance(e, bb.event.BuildStarted):
> localdata = bb.data.createCopy(e.data)
> diff --git a/meta/lib/oe/utils.py b/meta/lib/oe/utils.py
> index 82987e8..0c9dde0 100644
> --- a/meta/lib/oe/utils.py
> +++ b/meta/lib/oe/utils.py
> @@ -117,6 +117,30 @@ def features_backfill(var,d):
> if addfeatures:
> d.appendVar(var, " " + " ".join(addfeatures))
>
> +def extra_distro_features(d):
> + import oe.data
> +
> + l = d.createCopy()
> + l.finalize()
> +
> + extra_features = oe.data.typed_value('EXTRA_DISTRO_FEATURES', l)
> + if not extra_features:
> + return
> +
> + distro_features = l.getVar('DISTRO_FEATURES', True).split()
> + for feature in extra_features:
> + if feature.startswith('~'):
> + feature = feature[1:]
> + if feature in distro_features:
> + distro_features.remove(feature)
> + else:
> + if feature not in distro_features:
> + distro_features.append(feature)
> +
> + # Avoid readding the removed features later
> + d.delVar("DISTRO_FEATURES")
> +
> + d.setVar('DISTRO_FEATURES', ' '.join(distro_features))
>
> def packages_filter_out_system(d):
> """
next prev parent reply other threads:[~2013-08-23 14:59 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 [this message]
2013-08-23 15:11 ` Otavio Salvador
2013-08-23 15:29 ` Richard Purdie
2013-08-23 15:31 ` Richard Purdie
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=1377269956.6762.92.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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