Bug 5301 - Ability to track DISTRO_FEATURE use
Summary: Ability to track DISTRO_FEATURE use
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.5
Hardware: All Multiple
: Medium enhancement
Target Milestone: 1.6
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-10-02 10:13 UTC by Ross Burton
Modified: 2013-11-27 14:35 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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...