On 22 May 2015 at 12:20, Martin Jansa <[email protected]> wrote:
>
> > @@ -741,7 +741,6 @@ COMBINED_FEATURES = "\
> > ${@base_both_contain("DISTRO_FEATURES", "MACHINE_FEATURES", "ext2",
> d)} \
> > ${@base_both_contain("DISTRO_FEATURES", "MACHINE_FEATURES", "vfat",
> d)} \
> > ${@base_both_contain("DISTRO_FEATURES", "MACHINE_FEATURES", "irda",
> d)} \
> > - ${@base_both_contain("DISTRO_FEATURES", "MACHINE_FEATURES",
> "pcmcia", d)} \
>
> Is it worth removing here? this wasn't moved to meta-oe.
I've wondered why COMBINED_FEATURES involves a hard-coded list of features,
if we just generate it as a union of both sets then we get future proofness
(cf Cristian's patch to add nfc) and extensibility for free.
Ross
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
