From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] base: make feature backfilling happen earlier
Date: Mon, 28 Jan 2013 15:52:19 +0100 [thread overview]
Message-ID: <ly622hl5r0.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <4710226.v3bfS80rgU@helios> (Paul Eggleton's message of "Mon, 28 Jan 2013 14:19:57 +0000")
Paul Eggleton <paul.eggleton@linux.intel.com> writes:
> Why are you assigning *_FEATURES_BACKFILL at all?
There are some implicit relations between features (e.g. when selecting
'usbhost' I *usually* want 'vfat' or 'ext2' support too). So I have
DISTRO_FEATURES_BACKFILL = "\
largefile nfsroot modules ld-is-gold ${PROJECT_FEATURES} \
${DISTRO_FEATURES_INITMAN} \
${@base_contains('PROJECT_FEATURES', 'alsa', 'sound', '', d)} \
${@base_contains('PROJECT_FEATURES', 'directfb', 'screen', '', d)} \
${@base_contains('PROJECT_FEATURES', 'fb', 'screen', '', d)} \
${@base_contains('PROJECT_FEATURES', 'mmc', 'ext2 vfat', '', d)} \
${@base_contains('PROJECT_FEATURES', 'touchscreen', 'screen', '', d)} \
${@base_contains('PROJECT_FEATURES', 'ubifs', 'mtd', '', d)} \
${@base_contains('PROJECT_FEATURES', 'jffs2', 'mtd', '', d)} \
${@base_contains('PROJECT_FEATURES', 'usbclient', 'usb usbgadget', '', d)} \
${@base_contains('PROJECT_FEATURES', 'usbgadget', 'usb usbclient', '', d)} \
${@base_contains('PROJECT_FEATURES', 'usbhost', 'ext2 vfat', '', d)} \
${@base_contains('PROJECT_FEATURES', 'usbhost', 'usb', '', d)} \
${@base_contains('PROJECT_FEATURES', 'x11', 'screen', '', d)} \
"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "${NO_PROJECT_FEATURES}"
in my distro configuration (I knew; some are machine but no distro
features but this does not matter for me) and want to allow projects to
add new features and to remove default ones.
The default 'pulseaudio' in DISTRO_FEATURES_BACKFILL does not sound sane
to me either...
Enrico
--
SIGMA Chemnitz GmbH Registergericht: Amtsgericht Chemnitz HRB 1750
Am Erlenwald 13 Geschaeftsfuehrer: Grit Freitag, Frank Pyritz
09128 Chemnitz
next prev parent reply other threads:[~2013-01-28 15:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 17:52 [PATCH 0/2] DISTRO_FEATURES compatibility fixes Ross Burton
2013-01-24 17:52 ` [PATCH 1/2] bitbake.conf: unbreak all builds with custom DISTRO_FEATURES Ross Burton
2013-01-24 17:52 ` [PATCH 2/2] base: make feature backfilling happen earlier Ross Burton
2013-01-25 18:06 ` Enrico Scholz
2013-01-28 12:54 ` Richard Purdie
2013-01-28 13:55 ` Enrico Scholz
2013-01-28 14:19 ` Paul Eggleton
2013-01-28 14:52 ` Enrico Scholz [this message]
2013-01-28 15:00 ` Phil Blundell
2013-01-28 15:44 ` Enrico Scholz
2013-01-28 15:58 ` Paul Eggleton
2013-01-28 16:23 ` Enrico Scholz
2013-01-28 16:34 ` Paul Eggleton
2013-01-29 11:07 ` Enrico Scholz
2013-01-28 16:15 ` Phil Blundell
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=ly622hl5r0.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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