DISTRO_FEATURES and shared SSTATE

DISTRO_FEATURES and shared SSTATE

[seth bollinger]

Hello All,

How does yocto know which package version to choose for an image if the 
package can be altered (compilation difference, or perhaps config 
alteration, etc.) by a DISTRO_FEATURE?

For instance, if I make a change to sysvinit-inittab/inittab based on a 
DISTRO_FEATURE, I can have multiple versions of sysvinit-inittab, but 
only one shipping package, right?  If I'm building two different images 
that have that DISTRO_FEATURE set differently, won't one of the builds 
have the incorrect sysvinit-inittab package installed?

I believe PAM support would be another good example.

Thanks,

Seth

Re: DISTRO_FEATURES and shared SSTATE

[Chris Larson]

[-- Attachment #1: Type: text/plain, Size: 822 bytes --]

On Sun, Oct 13, 2013 at 8:04 AM, seth bollinger <seth.boll@gmail.com> wrote:

> How does yocto know which package version to choose for an image if the
> package can be altered (compilation difference, or perhaps config
> alteration, etc.) by a DISTRO_FEATURE?
>
> For instance, if I make a change to sysvinit-inittab/inittab based on a
> DISTRO_FEATURE, I can have multiple versions of sysvinit-inittab, but only
> one shipping package, right?  If I'm building two different images that
> have that DISTRO_FEATURE set differently, won't one of the builds have the
> incorrect sysvinit-inittab package installed?
>

Changing such a variable will alter the checksum of the task, resulting in
re-execution of altered tasks if appropriate, or pulling from a different
sstate archive.
-- 
Christopher Larson

[-- Attachment #2: Type: text/html, Size: 1163 bytes --]