]> code.ossystems Code Review - openembedded-core.git/commit
staging.bbclass: handle postinst-useradd-* fixmes
authorMikko Ylinen <mikko.ylinen@linux.intel.com>
Wed, 6 Dec 2017 22:53:18 +0000 (14:53 -0800)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Sun, 7 Jan 2018 17:06:35 +0000 (17:06 +0000)
commit764b93cac374a55c31c86627f13270db874cdbdb
treefa92b46c8d90dbdd9372bfab2d915adc32ab43ce
parent6a2bdae1c418374aee9b53abfc03cb506647c94e
staging.bbclass: handle postinst-useradd-* fixmes

After 02457ef7f600ce954874e2d11e74b1c6daaa3bfc, PSEUDO for
postinst-useradd-* scripts get to use only one PSEUDO_LOCALSTATEDIR
which is set under recipes ${WORKDIR}.

When the those scripts are run in a clean build environment that
is built from the sstate (populate_sysroot_setscene run for
postinst-useradd-* providers), pseudo fails to run because it cannot
access the PSEUDO_LOCALSTATEDIR (recipe ${WORKDIR}s do not exist).
This triggers a sysroot staging error.

Previously, the PSEUDO_LOCALSTATEDIR setting in useradd.bbclass
worked because the RSS sstate/staging logic automagically processed
${STAGING_DIR_TARGET} in postinst-useradd-* scripts to point under
the sysroot being built.

The fix uses the same fixme processing by adding PSEUDO_LOCALSTATEDIR
variable to it. Furthermore, LOGFIFO is added to be able to use
the logging fifo of the recipe that actually runs postinst-useradd-*.

Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
meta/classes/staging.bbclass
meta/classes/useradd.bbclass