From: Martin Jansa <martin.jansa@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: what is the proper way to define a blacklist?
Date: Wed, 6 Aug 2014 11:03:59 +0200 [thread overview]
Message-ID: <20140806090359.GD14848@jama> (raw)
In-Reply-To: <alpine.LFD.2.11.1408060435001.1524@localhost>
[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]
On Wed, Aug 06, 2014 at 04:39:29AM -0400, Robert P. J. Day wrote:
>
> from blacklist.bbclass:
>
> # To use the blacklist, a distribution should include this
> # class in the INHERIT_DISTRO
>
> the only way i see that class being inherited is with the simpler
> form:
>
> INHERIT += "blacklist"
>
> even in distro conf files, except in defaultsetup.conf, which uses:
>
> INHERIT_BLACKLIST = "blacklist"
>
> so should that comment be adjusted? what should it say?
That it's included by default.
see oe-core/74e377eeb6de606b99ed0ff840922261f4a27abc
>
> rday
>
> --
>
> ========================================================================
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter: http://twitter.com/rpjday
> LinkedIn: http://ca.linkedin.com/in/rpjday
> ========================================================================
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2014-08-06 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 8:39 what is the proper way to define a blacklist? Robert P. J. Day
2014-08-06 9:03 ` Martin Jansa [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140806090359.GD14848@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox