> On Aug 28, 2015, at 1:34 AM, Paul Eggleton <[email protected]> > wrote: > > On Thursday 27 August 2015 23:07:44 Khem Raj wrote: >>> On Aug 27, 2015, at 5:36 AM, Paul Eggleton <[email protected]> >>> wrote: >>> >>> Allow restricting recipes brought from a layer to a specified list. This >>> is similar in operation to blacklist.bbclass, but instead specifies a >>> per-layer whitelist of recipes (matched by PN or BPN) that are able to >>> be built from the layer - anything else is skipped. This is potentially >>> useful where you want to bring in a select set of recipes from a larger >>> layer e.g. meta-oe. >> >> For the record, I am not in favor of such feature in OE, Distros can still >> use BBMASK if they wish to > > This is significantly easier to use than BBMASK though. (Perhaps that's why > you > don't like it?)
I don’t think its about technical merits of the patch. I understand its pretty well writter. Its if we want to provide more tools and ways which can be bad for layer health in general which are besides oe-core. > > I think we need to be realistic here as I said in my most recent reply to the > other thread - people will do this using whatever mechanism is available > whether we like it or not. And what are they saying by doing so? They're > effectively telling us that they can't consume the recipes in the way we are > currently collecting them together. We know what the proper fix for the > problem > is (increased splitting of large layers such as meta-oe), it may not be easy > but other than workarounds like this I don't see an alternative. > > Cheers, > Paul > > -- > > Paul Eggleton > Intel Open Source Technology Centre
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
