Skip to contentSkip to conversation

DISTRO_FEATURES only extendable?

PATCH Gary Thomas 2 participants 2 messages Feb 7, 2011

lore
Share & tools
lore
#0 lore raw

I have my own distribution which is an extension of Poky (my DISTRO.conf is based on poky.conf via requires)

Is there some reason that DISTRO_FEATURES is fixed by poky.conf and not overridable? e.g. my systems seldom have WiFi or PCMCIA, so it's silly to include that support.

Would the attached patch be acceptable to the mainstream?

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
meta/conf/distro/poky.conf +1 -1
index aeab039..64a2b1d 100644
@@ -111,7 +111,7 @@ LIMIT_BUILT_LOCALES ?= "POSIX en_US en_GB"
 ENABLE_BINARY_LOCALE_GENERATION ?= "1"
 LOCALE_UTF8_ONLY = "0"
 
-DISTRO_FEATURES = "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi nfs zeroconf pci"
+DISTRO_FEATURES ?= "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi nfs zeroconf pci"
 
 POKY_EXTRA_RDEPENDS = "task-poky-boot"
 POKY_EXTRA_RDEPENDS_qemuarm = "qemu-config"
#1 lore raw
Quoted 8 lines · Gary Thomas

I have my own distribution which is an extension of Poky (my DISTRO.conf is based on poky.conf via requires)

Is there some reason that DISTRO_FEATURES is fixed by poky.conf and not overridable?  e.g. my systems seldom have WiFi or PCMCIA, so it's silly to include that support.

Would the attached patch be acceptable to the mainstream?

Note that there's no reason you can't override it now, just do it after the require of poky.conf :) Of course, using ?= makes it easier to override it from local.conf without using an override, but they are *distro* features after all, its intended to be in the distro's hands.

Signature · 5 lines
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics