]> code.ossystems Code Review - openembedded-core.git/commit
staging.bbclass: handle postinst-useradd-* fixmes
authorMikko Ylinen <mikko.ylinen@linux.intel.com>
Tue, 3 Oct 2017 07:09:26 +0000 (10:09 +0300)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Fri, 6 Oct 2017 11:03:34 +0000 (12:03 +0100)
commitb28374cfad37db161b5ac5953b4a4638912f3f27
tree22746e12abf53212d8427d886a43ec712c473d29
parent6ce87fdadab73e8a928864515495bc4ab3401577
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>
meta/classes/staging.bbclass
meta/classes/useradd.bbclass