Skip to contentSkip to conversation

DISTRO_FEATURES and shared SSTATE

DISCUSSION seth bollinger 2 participants 2 messages Oct 13, 2013

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw
Quoted 10 lines · seth bollinger

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.

Signature · 1 line
Christopher Larson