[OE-core] [PATCH 3/3] wic: add fakeroot to the populate-extfs step

[Richard Purdie]

On Wed, 2013-10-16 at 08:10 -0700, Darren Hart wrote:
> On Wed, 2013-10-16 at 13:09 +0100, Richard Purdie wrote:
> > On Wed, 2013-10-16 at 00:14 -0500, Tom Zanussi wrote:
> > > Without this, files in the generated filesystem pick up the wrong
> > > ownership.
> > > 
> > > Signed-off-by: Tom Zanussi <tom.zanussi at linux.intel.com>
> > > ---
> > >  scripts/lib/mic/kickstart/custom_commands/partition.py | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/scripts/lib/mic/kickstart/custom_commands/partition.py b/scripts/lib/mic/kickstart/custom_commands/partition.py
> > > index 302cace..309abee 100644
> > > --- a/scripts/lib/mic/kickstart/custom_commands/partition.py
> > > +++ b/scripts/lib/mic/kickstart/custom_commands/partition.py
> > > @@ -216,7 +216,7 @@ class Wic_PartData(Mic_PartData):
> > >          """
> > >          Prepare content for an ext2/3/4 rootfs partition.
> > >          """
> > > -        populate_script = "%s/usr/bin/populate-extfs.sh" % native_sysroot
> > > +        populate_script = "fakeroot %s/usr/bin/populate-extfs.sh" % native_sysroot
> > >          image_extra_space = 10240
> > >  
> > >          image_rootfs = rootfs_dir
> > 
> > We don't use fakeroot, please use pseudo. If pseudo doesn't work, we
> > need to figure out why and fix it.
> > 
> 
> Ultimately this needs to work independently from bitbake. Is that
> practical if we use pseudo here?

pseudo is an independent project and you can build and use it outside of
bitbake no problems at all. My worry is we didn't adopt fakeroot for
many good reasons. I don't want "fixing fakeroot" to suddenly appear on
the agenda. We did that and its called pseudo.

Cheers,

Richard