Re: How to add a distro feature from an image recipe?

[Gabriel Barbu <gabriel.barbu@enea.com>]

On 4/17/2014 4:42 PM, Paul Eggleton wrote:
> Hi Gabriel,
>
> On Thursday 17 April 2014 11:27:16 Gabriel Barbu wrote:
>> Is there a specific mechanism to add a distro feature from an image recipe?
>> DISTRO_FEATURES_append does not seem to work from an image-*.bb or from a
>> packagegroup-*.bb.
>
> You can't do this I'm afraid. DISTRO_FEATURES influences how components are
> built, and aside from via dependencies and placing files in the sysroot, one
> recipe cannot influence how another is built. If you think about how the system
> produces package feeds and how these would be expected to be able to be
> installed from a running target system, if it were possible to set these kinds
> of options from the image you would have situations where you would build one
> image and then build another and packages would change, possibly in ways that
> would not be compatible with the first image - so that wouldn't be practical.
>
>> 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.
>
> Cheers,
> Paul
>

Hi Paul,

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.

And thanks to your explanation, I understand better I’m likely looking 
at a bug.
I will investigate closer.

Thanks,

Gabriel