blacklist.bbclass

blacklist.bbclass

[Dr. Michael Lauer]

Salut,

the blacklisting of packages as found in angstrom.bbclass
is pretty helpful and would be beneficial to all kinds
of distribution configurations in OE. Would there be
a strong objection of renaming this to blacklist.bbclass?

Copying, of course, is also a possibility, but
in my opinion it would only be the second best choice.

Cheers,

:M:

Re: blacklist.bbclass

[Frans Meulenbroeks]

2011/3/18 Dr. Michael Lauer <mickey@vanille-media.de>:
> Salut,
>
> the blacklisting of packages as found in angstrom.bbclass
> is pretty helpful and would be beneficial to all kinds
> of distribution configurations in OE. Would there be
> a strong objection of renaming this to blacklist.bbclass?
>
> Copying, of course, is also a possibility, but
> in my opinion it would only be the second best choice.
>
> Cheers,
>
> :M:

If blacklisting a certain package for all distro's is there then still
a need to keep those blacklisted packages ????

Frans

Re: blacklist.bbclass

[Chris Larson]

On Fri, Mar 18, 2011 at 1:33 PM, Frans Meulenbroeks
<fransmeulenbroeks@gmail.com> wrote:
> 2011/3/18 Dr. Michael Lauer <mickey@vanille-media.de>:
>> Salut,
>>
>> the blacklisting of packages as found in angstrom.bbclass
>> is pretty helpful and would be beneficial to all kinds
>> of distribution configurations in OE. Would there be
>> a strong objection of renaming this to blacklist.bbclass?
>>
>> Copying, of course, is also a possibility, but
>> in my opinion it would only be the second best choice.
>>
>> Cheers,
>>
>> :M:
>
> If blacklisting a certain package for all distro's is there then still
> a need to keep those blacklisted packages ????

Just because the class is named blacklist and *can* be used by any
distro doesn't mean we'd be globally blacklisting something for all
distros.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics

Re: blacklist.bbclass

[Phil Blundell]

On Fri, 2011-03-18 at 21:33 +0100, Frans Meulenbroeks wrote:
> 2011/3/18 Dr. Michael Lauer <mickey@vanille-media.de>:
> > Salut,
> >
> > the blacklisting of packages as found in angstrom.bbclass
> > is pretty helpful and would be beneficial to all kinds
> > of distribution configurations in OE. Would there be
> > a strong objection of renaming this to blacklist.bbclass?
> >
> > Copying, of course, is also a possibility, but
> > in my opinion it would only be the second best choice.
> >
> > Cheers,
> >
> > :M:
> 
> If blacklisting a certain package for all distro's is there then still
> a need to keep those blacklisted packages ????

The class that Mickey is talking about is just the mechanism to allow
blacklisting.  It doesn't actually contain a list of blacklisted
packages; I think that typically goes in DISTRO.conf for distros that
use it.

However, if we do want to rename it to something more global (which I
agree seems like a good idea) then the contents would need a bit of
tweaking since both the variables that it looks at, and the messages
that it outputs, make reference to Angstrom specifically.

p.

Re: blacklist.bbclass

[Tom Rini]

On 03/18/2011 02:35 PM, Phil Blundell wrote:
> On Fri, 2011-03-18 at 21:33 +0100, Frans Meulenbroeks wrote:
>> 2011/3/18 Dr. Michael Lauer<mickey@vanille-media.de>:
>>> Salut,
>>>
>>> the blacklisting of packages as found in angstrom.bbclass
>>> is pretty helpful and would be beneficial to all kinds
>>> of distribution configurations in OE. Would there be
>>> a strong objection of renaming this to blacklist.bbclass?
>>>
>>> Copying, of course, is also a possibility, but
>>> in my opinion it would only be the second best choice.
>>>
>>> Cheers,
>>>
>>> :M:
>>
>> If blacklisting a certain package for all distro's is there then still
>> a need to keep those blacklisted packages ????
>
> The class that Mickey is talking about is just the mechanism to allow
> blacklisting.  It doesn't actually contain a list of blacklisted
> packages; I think that typically goes in DISTRO.conf for distros that
> use it.
>
> However, if we do want to rename it to something more global (which I
> agree seems like a good idea) then the contents would need a bit of
> tweaking since both the variables that it looks at, and the messages
> that it outputs, make reference to Angstrom specifically.

I've had that locally for a long while now (BLACKLIST and just %s is 
unsupported because %s).  So I vote in favor of a generic list distros 
blacklist items class.

-- 
Tom Rini
Mentor Graphics Corporation

Re: blacklist.bbclass

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 18-03-11 20:24, Dr. Michael Lauer wrote:
> Salut,
> 
> the blacklisting of packages as found in angstrom.bbclass
> is pretty helpful and would be beneficial to all kinds
> of distribution configurations in OE.

So include it in your $DISTRO.

> Would there be
> a strong objection of renaming this to blacklist.bbclass?

Why is a rename needed? SHR is already using it as is.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNg9x+MkyGM64RGpERApRIAKCaBrrX6A/yyoIMuRrELdeJCTqs1gCggw93
q+51Hc05SmGVgocnoEJeR10=
=+KOd
-----END PGP SIGNATURE-----

Re: blacklist.bbclass

[Frans Meulenbroeks]

2011/3/18 Phil Blundell <philb@gnu.org>:
> On Fri, 2011-03-18 at 21:33 +0100, Frans Meulenbroeks wrote:
>> 2011/3/18 Dr. Michael Lauer <mickey@vanille-media.de>:
>> > Salut,
>> >
>> > the blacklisting of packages as found in angstrom.bbclass
>> > is pretty helpful and would be beneficial to all kinds
>> > of distribution configurations in OE. Would there be
>> > a strong objection of renaming this to blacklist.bbclass?
>> >
>> > Copying, of course, is also a possibility, but
>> > in my opinion it would only be the second best choice.
>> >
>> > Cheers,
>> >
>> > :M:
>>
>> If blacklisting a certain package for all distro's is there then still
>> a need to keep those blacklisted packages ????
>
> The class that Mickey is talking about is just the mechanism to allow
> blacklisting.  It doesn't actually contain a list of blacklisted
> packages; I think that typically goes in DISTRO.conf for distros that
> use it.
>
> However, if we do want to rename it to something more global (which I
> agree seems like a good idea) then the contents would need a bit of
> tweaking since both the variables that it looks at, and the messages
> that it outputs, make reference to Angstrom specifically.
>

Ah ok, thanks for the explanation!

Frans

Re: blacklist.bbclass

[Philip Balister]

On 03/18/2011 06:28 PM, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 18-03-11 20:24, Dr. Michael Lauer wrote:
>> Salut,
>>
>> the blacklisting of packages as found in angstrom.bbclass
>> is pretty helpful and would be beneficial to all kinds
>> of distribution configurations in OE.
>
> So include it in your $DISTRO.
>
>> Would there be
>> a strong objection of renaming this to blacklist.bbclass?
>
> Why is a rename needed? SHR is already using it as is.

What is oe-core doing? I would think they would want to make this more 
generic. The solution may be to adopt what happens there.

Philip

Re: blacklist.bbclass

[Graeme Gregory]

On 18/03/2011 19:24, Dr. Michael Lauer wrote:
> Salut,
>
> the blacklisting of packages as found in angstrom.bbclass
> is pretty helpful and would be beneficial to all kinds
> of distribution configurations in OE. Would there be
> a strong objection of renaming this to blacklist.bbclass?
>
> Copying, of course, is also a possibility, but
> in my opinion it would only be the second best choice.
>
As the author I object to renaming it.

We have played this rename game before and Im still not happy with the
results of the last time.

I also object on the grounds of the amount of abuse I got from some
other distro maintainers for implementing this, which is the reason it
is called angstrom.bbclass.

Graeme

Re: blacklist.bbclass

[Tom Rini]

On 03/18/2011 04:09 PM, Graeme Gregory wrote:
> On 18/03/2011 19:24, Dr. Michael Lauer wrote:
>> Salut,
>>
>> the blacklisting of packages as found in angstrom.bbclass
>> is pretty helpful and would be beneficial to all kinds
>> of distribution configurations in OE. Would there be
>> a strong objection of renaming this to blacklist.bbclass?
>>
>> Copying, of course, is also a possibility, but
>> in my opinion it would only be the second best choice.
>>
> As the author I object to renaming it.
>
> We have played this rename game before and Im still not happy with the
> results of the last time.
>
> I also object on the grounds of the amount of abuse I got from some
> other distro maintainers for implementing this, which is the reason it
> is called angstrom.bbclass.

OK.  Can we change the message so it says ${DISTRO} doesn't support, 
rather than Angstrom doesn't support?

-- 
Tom Rini
Mentor Graphics Corporation

Re: blacklist.bbclass

[Graeme Gregory]

On 19/03/2011 22:40, Tom Rini wrote:
> On 03/18/2011 04:09 PM, Graeme Gregory wrote:
>> On 18/03/2011 19:24, Dr. Michael Lauer wrote:
>>> Salut,
>>>
>>> the blacklisting of packages as found in angstrom.bbclass
>>> is pretty helpful and would be beneficial to all kinds
>>> of distribution configurations in OE. Would there be
>>> a strong objection of renaming this to blacklist.bbclass?
>>>
>>> Copying, of course, is also a possibility, but
>>> in my opinion it would only be the second best choice.
>>>
>> As the author I object to renaming it.
>>
>> We have played this rename game before and Im still not happy with the
>> results of the last time.
>>
>> I also object on the grounds of the amount of abuse I got from some
>> other distro maintainers for implementing this, which is the reason it
>> is called angstrom.bbclass.
>
> OK.  Can we change the message so it says ${DISTRO} doesn't support,
> rather than Angstrom doesn't support?
>
Heh, your slow, do a git pull :-)

Graeme