[OE-core] [PATCH v2 1/1] classes/whitelist: add class to allow whitelisting recipes from a layer

Paul Eggleton paul.eggleton at linux.intel.com
Fri Aug 28 14:19:13 UTC 2015


On Friday 28 August 2015 11:09:19 Otavio Salvador wrote:
> On Fri, Aug 28, 2015 at 11:00 AM, Paul Eggleton
> 
> <paul.eggleton at linux.intel.com> wrote:
> > On Friday 28 August 2015 10:55:41 Otavio Salvador wrote:
> >> On Fri, Aug 28, 2015 at 3:07 AM, Khem Raj <raj.khem at gmail.com> wrote:
> >> >> On Aug 27, 2015, at 5:36 AM, Paul Eggleton
> >> >> <paul.eggleton at linux.intel.com> 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
> >> 
> >> I am also not in favor of the merge of this.
> > 
> > Do you have a practical alternative that has less downsides?
> 
> I do want people using full layers and offer tools to make fancy
> combinations does not enhance our quality in long term.

OK, sure - but you do appreciate that we do have an underlying problem here 
irrespective of whether this class gets taken into OE-Core or not, right?

Look, if people are really opposed to this then fine, I withdraw it. I just 
hope that it's understood that this class or other equivalent methods *will* 
get used until we fix the problem properly - all it means is the class will get 
copied around instead of being in one place.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



More information about the Openembedded-core mailing list