Bug 11169 - prelink recipe checks USER_CLASSES for image-prelink
Summary: prelink recipe checks USER_CLASSES for image-prelink
Status: RESOLVED FIXED
Alias: None
Product: Cross-prelink
Classification: Yocto Project Subprojects
Component: poky integration (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 2.4
Assignee: Mark Hatle
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-03-16 04:13 UTC by Paul Eggleton
Modified: 2017-08-24 12:04 UTC (History)
5 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2017-03-16 04:13:20 UTC
The prelink recipe is checking if image-prelink is in USER_CLASSES. This is the convention for enabling this, but it doesn't have to be enabled that way - it could even be inherited in an image recipe rather than at the configuration level and it would still work, but this check wouldn't get the correct answer.

Given that this check is done in a postinstall and it's when it's on the host that we want to do the check, I wonder, would it be possible to export another variable during do_rootfs that would make it into the environment such that the script could check it?