Bug 4507 - Change to SSTATEPOSTINSTFUNCS function doesn't cause re-stage
Summary: Change to SSTATEPOSTINSTFUNCS function doesn't cause re-stage
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 1.4
Hardware: All Multiple
: Medium normal
Target Milestone: 1.6
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-05-17 08:54 UTC by Ross Burton
Modified: 2014-03-23 08:59 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-05-17 08:54:25 UTC 
I have a class that uses SSTATEPOSTINSTFUNCS:

SSTATEPOSTINSTFUNCS_append_class-native = " pixbufcache_sstate_postinst"

pixbufcache_sstate_postinst() {
...
}

If I change the contents of pixbufcache_sstate_postinst, the native recipes that use this class don't get re-written to the sysroot.
Comment 1 Richard Purdie 2014-02-12 11:23:05 UTC 
After http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=707cdcf9050397ce48c81a7225ca01f618b9a87a it does account for these.
Comment 2 Paul Eggleton 2014-03-03 14:50:18 UTC 
Unfortunately not; SSTATEPOSTINSTFUNCS aren't real postfuncs.