[OE-core] [oe-core][PATCH 0/1] blacklist: add BPNBLACKLIST support

[Mark Hatle]

On 6/22/16 5:35 PM, Khem Raj wrote:
> 
> On Jun 22, 2016 2:59 PM, "Joe Slater" <jslater at windriver.com
> <mailto:jslater at windriver.com>> wrote:
>>
>> We have encountered some issues with the use of PNBLACKLIST in recipes.
>> In particular, PNBLACKLIST[pkg] will not suppress building of lib32-pkg
>> or lib64-pkg so world builds can fail unexpectedly.
>>
>> One solution could be to implement BPNBLACKLIST[] which checks BPN instead
>> of PN when a recipe is being parsed.  I have included a patch to do this.
>>
>> If this were adopted, there are many recipes under meta-openembedded that
>> should probably changed to use BPNBLACKLIST instead of PNBLACKLIST.
> 
> Bpn will also mean native and nativesdk among others. I think its better to list
> multilibs explicitly.

This is intentional.

The problem with saying we have to list multilibs explicitly.  multilib naming
is arbitrary.  I can say that it probably fits the pattern of lib64, lib32,
libn32 and libx32.... but it doesn't have to.

But then I'd also need to blacklist native and nativesdk versions as well.. so
for a simple recipe that for some reason I want blacklisted, it's easier to hack
the recipe to just blacklist itself -- then enter 7 or more blacklists.

Using the BPNBLACKLIST I can blacklist a single recipe with one command and not
worry about multilibs, class extensions, etc.

(The patch leave PNBLACKLIST, specifically so that in the case where you want
only partial usage blacklisted you can.)

--Mark

>>
>> Joe Slater (1):
>>   blacklist: add BPNBLACKLIST support
>>
>>  meta/classes/blacklist.bbclass |   24 ++++++++++++++++++++----
>>  1 file changed, 20 insertions(+), 4 deletions(-)
>>
>> --
>> 1.7.9.5
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core at lists.openembedded.org
> <mailto:Openembedded-core at lists.openembedded.org>
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> 
> 
>