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 -- Paul Eggleton Intel Open Source Technology Centre -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
