5301 2013-10-02 10:13:40 +0000 Ability to track DISTRO_FEATURE use 2013-11-27 14:35:35 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 1.5 All Multiple RESOLVED FIXED Medium enhancement 1.6 1 ross.burton richard.purdie jessica.zhang mark.hatle meta.mr.watcher meta.watcher --- --- No (bug/feature does not impact docs) oldest_to_newest 37459 0 ross.burton 2013-10-02 10:13:40 +0000 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. 37495 1 mark.hatle 2013-10-02 16:39:23 +0000 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?) 39083 2 richard.purdie 2013-11-25 22:49:25 +0000 I've posted a proof of concept on this... 39111 3 richard.purdie 2013-11-27 14:35:35 +0000 Fixed in master http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=a10301f6a90567c2d2eca9306a4b7b752f58a9c2