From: Constantin Musca <constantinx.musca@intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH] poky-tiny.conf: blacklist inappropriate image options
Date: Wed, 21 Nov 2012 18:12:04 +0200 [thread overview]
Message-ID: <50ACFD54.4090808@intel.com> (raw)
In-Reply-To: <50AC01FD.7090104@linux.intel.com>
On 11/21/2012 12:19 AM, Darren Hart wrote:
> Hi Constantin,
>
> On 11/19/2012 04:39 AM, Constantin Musca wrote:
>> Blacklist all images that aren't core-image-minimal-*
>>
> This needs a description as to what the problem is and why this change
> is needed. Note that the bug is here for reference, but cannot be relied
> upon to provide context. That is what the git log is for.
>
> I believe the core-image-rt image should also build, but I haven't tried
> recently. trace-cmd might break that.
>
> What sort of error is the user presented with when trying to build one
> of the blacklisted images?
>
> As I've stated in the bug, I'd be happier with an image whitelist than a
> blacklist as it is hopelessly unmaintainable. Have we explored the
> whitelist approach?
>
> Finally, please remember to CC the maintainer of the files you are
> modifying when that information is obvious. It is also good practice to
> CC the active bugzilla commenters when available.
>
> Thanks,
>
> Darren
>
>> [YOCTO #2565]
>>
>> Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
>> ---
>> meta-yocto/conf/distro/poky-tiny.conf | 17 +++++++++++++++++
>> 1 file changed, 17 insertions(+)
>>
>> diff --git a/meta-yocto/conf/distro/poky-tiny.conf b/meta-yocto/conf/distro/poky-tiny.conf
>> index d40748e..121534e 100644
>> --- a/meta-yocto/conf/distro/poky-tiny.conf
>> +++ b/meta-yocto/conf/distro/poky-tiny.conf
>> @@ -120,3 +120,20 @@ MACHINE_ESSENTIAL_EXTRA_RDEPENDS = ""
>> # will build perl in case this package is installed. Since we don't care about
>> # this script for the purposes of tiny, remove the dependency from here.
>> RDEPENDS_${PN}-mtrace_pn-eglibc = ""
>> +
>> +INHERIT_DISTRO += "blacklist"
>> +PNBLACKLIST[build-appliance-image] = "not buildable with poky-tiny"
>> +PNBLACKLIST[core-image-base] = "not buildable with poky-tiny"
>> +PNBLACKLIST[core-image-basic] = "not buildable with poky-tiny"
>> +PNBLACKLIST[core-image-clutter] = "not buildable with poky-tiny"
>> +PNBLACKLIST[core-image-gtk-directfb] = "not buildable with poky-tiny"
>> +PNBLACKLIST[core-image-lsb] = "not buildable with poky-tiny"
>> +PNBLACKLIST[core-image-lsb-dev] = "not buildable with poky-tiny"
>> +PNBLACKLIST[core-image-lsb-sdk] = "not buildable with poky-tiny"
>> +PNBLACKLIST[core-image-rt] = "not buildable with poky-tiny"
>> +PNBLACKLIST[core-image-rt-sdk] = "not buildable with poky-tiny"
>> +PNBLACKLIST[core-image-sato] = "not buildable with poky-tiny"
>> +PNBLACKLIST[core-image-sato-dev] = "not buildable with poky-tiny"
>> +PNBLACKLIST[core-image-sato-sdk] = "not buildable with poky-tiny"
>> +PNBLACKLIST[core-image-x11] = "not buildable with poky-tiny"
>> +PNBLACKLIST[qt4e-demo-image] = "not buildable with poky-tiny"
>>
Hi Darren,
I will come back with build errors for incompatible images as soon as I
test all the images using the poky-tiny distro. Do you agree with the
following whitelist approach?
- create poky-tiny.bbclass in meta-yocto which will contain an anonymous
python function for checking whether a package is a whitelisted image
- the whitelist variable (configurable from poky-tiny.conf) will be
called TINY_IMAGE_WHITELIST
Cheers,
Constantin
next prev parent reply other threads:[~2012-11-21 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 12:39 [PATCH] poky-tiny.conf: blacklist inappropriate image options Constantin Musca
2012-11-20 22:19 ` Darren Hart
2012-11-21 16:12 ` Constantin Musca [this message]
2012-11-21 17:27 ` Darren Hart
2012-11-21 17:44 ` Paul Eggleton
2012-11-21 19:35 ` Darren Hart
2012-11-22 8:32 ` Richard Purdie
2012-11-26 16:41 ` Darren Hart
2012-12-06 5:30 ` Saul Wold
2012-12-06 13:13 ` Constantin Musca
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=50ACFD54.4090808@intel.com \
--to=constantinx.musca@intel.com \
--cc=dvhart@linux.intel.com \
--cc=poky@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.