From: Gabriel Barbu <gabriel.barbu@enea.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: How to add a distro feature from an image recipe?
Date: Thu, 17 Apr 2014 18:21:16 +0300 [thread overview]
Message-ID: <534FF16C.50207@enea.com> (raw)
In-Reply-To: <1766435.4H2Ncp94dv@peggleto-mobl5.ger.corp.intel.com>
On 4/17/2014 5:52 PM, Paul Eggleton wrote:
> On Thursday 17 April 2014 17:48:48 Gabriel Barbu wrote:
>> On 4/17/2014 5:28 PM, Paul Eggleton wrote:
>>> On Thursday 17 April 2014 17:24:17 Gabriel Barbu wrote:
>>>> On 4/17/2014 4:42 PM, Paul Eggleton wrote:
>>>>> On Thursday 17 April 2014 11:27:16 Gabriel Barbu wrote:
>>>>>> Or, if not, what would be the best way to achieve this?
>>>>>> The need is that I have a number of images and only want to add a
>>>>>> certain
>>>>>> distro feature (ptest) to just one or two of them (some test images).
>>>>>
>>>>> You can have ptest enabled in the distro but ptest packages installed
>>>>> only
>>>>> in certain images. That is the only way this kind of thing can work. If
>>>>> enabling the ptest in DISTRO_FEATURES is causing changes in an image
>>>>> where ptest is not installed, that should be considered a bug.
>>>>
>>>> Yes, I was afraid it’s this way :)
>>>> Alright, I can settle for just not having them installed.
>>>>
>>>> But what I’m witnessing now is that having:
>>>> "ptest" in my DISTRO_FEATURES, and
>>>> no "ptest-pkgs" in IMAGE_FEATURES
>>>> results in the image having ptests installed.
>>>
>>> Is that bug 5702, or something else?
>>>
>>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=5702
>>>
>>> Cheers,
>>> Paul
>>
>> Possibly more. Right now I only see:
>> ./dbus-ptest/ptest
>> ./perl/ptest
>>
>> in a custom image I have, but I will also try with a bigger image to
>> check if I get more.
>
> So the dbus-ptest one we're aware of (and the fix is on the mailing list) but
> it would be interesting to know how the perl-ptest one got there.
>
> Cheers,
> Paul
>
Right, I will investigate.
Best regards,
Gabriel
prev parent reply other threads:[~2014-04-17 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 11:27 How to add a distro feature from an image recipe? Gabriel Barbu
2014-04-17 11:35 ` Josep Puigdemont
2014-04-17 12:37 ` Gabriel Barbu
2014-04-17 13:42 ` Paul Eggleton
2014-04-17 14:24 ` Gabriel Barbu
2014-04-17 14:28 ` Paul Eggleton
2014-04-17 14:48 ` Gabriel Barbu
2014-04-17 14:52 ` Paul Eggleton
2014-04-17 15:21 ` Gabriel Barbu [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=534FF16C.50207@enea.com \
--to=gabriel.barbu@enea.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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