Bug 5301

Summary: Ability to track DISTRO_FEATURE use
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Ross Burton <ross.burton>
Component: coreAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium CC: jessica.zhang, mark.hatle, meta.mr.watcher, meta.watcher
Version: 1.5   
Target Milestone: 1.6   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Ross Burton 2013-10-02 10:13:40 UTC 
When changing DISTRO_FEATURE (say, adding "x11") the entire distro is rebuild, including gcc-cross and so on.  It would be great if the recipe checksums somehow incorporated the distro features the recipe actually examines, so only recipes that would change are rebuild.
Comment 1 Mark Hatle 2013-10-02 16:39:23 UTC 
Note, that some -native packages also appear to inspect DISTRO_FEATURES and that causes them to rebuild as well.

For example, python-native inspects it looking for the existence of ipv6.

What is probably needed is to either sanitize the -native items, or clearly label the ones that do change behavior based on the target DISTRO_FEATURES.

(Another option is to use DISTRO_FEATURES_class-native to set it to a default that will work in all configurations?)
Comment 2 Richard Purdie 2013-11-25 22:49:25 UTC 
I've posted a proof of concept on this...