Am Sonntag, den 19.02.2012, 07:29 +0000 schrieb McClintock Matthew-B29882: > On Wed, Nov 9, 2011 at 4:03 PM, Richard Purdie wrote: > > Without this rootfs generation fails as an RDEPENDS is added > > but the package might not have bneen built.
s/bneen/been/ > > Signed-off-by: Richard Purdie <[email protected]> > > --- > > diff --git a/meta/classes/useradd.bbclass b/meta/classes/useradd.bbclass > > index 8cd7f4f..7faf1a7 100644 > > --- a/meta/classes/useradd.bbclass > > +++ b/meta/classes/useradd.bbclass > > @@ -2,7 +2,7 @@ > > # target sysroot, and shadow -native and -sysroot provide the utilities > > # and support files needed to add and modify user and group accounts > > DEPENDS_append = "${USERADDDEPENDS}" > > -USERADDDEPENDS = " base-passwd shadow-native shadow-sysroot" > > +USERADDDEPENDS = " base-passwd shadow-native shadow-sysroot shadow" > > The shadow recipe is a 'PACKAGE_ARCH = "${MACHINE_ARCH}"' recipe. This > makes all recipes that inherit useradd depend on shadow which will > depend on the MACHINE being built for. Ideally, we just need a way to > ensure these packages are deployed - we don't want them to effect > signatures. > > Can you suggest a better fix here? Some > bb.exec_func("shadow:do_populate_sysroot") or something equivalent? You raise a good point, but I have no solution. Thanks, Paul
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
