[gentoo-embedded] Re: emerge --root : users not created

["P. Levine" <plevine457@verizon.net>]

On 06/14/2010 04:09 AM, Sven Rebhan wrote:
> 2010/6/11 Marcus Priesch <marcus@priesch.priv.at>:
>> Hi sven,
>>
>> wouldnt it be enough to have the patch included in gentoo's shadow
>> ebuild - as i think its mainly relevant for gentoo folks - at least in
>> the meantime, until the patch gets accepted upstream ?!
> 
> Well, talk to the Gentoo maintainer of the shadow suite. :-) IIRC, it was
> clearly said, that the patch has to go through mainstream, but you can
> try nevertheless. IMHO the patch really _should_ go upstream and be
> reviewed there as it might be relevant for security stuff.
> 
>> as i assume this patch alone is not enough - as it needs tweaking the
>> eclass providing the eadduser & co functions also ... and therefore it's
>> hard to put in an overlay ... or ?!?!
> 
> The procedure would be:
> 1. Get the patch accepted either upstream or in the portage tree.
> 2. Find a good check to distinguish --chroot enabled and disabled shadow
> 3. Modify the eclass accordingly.
> 
> So, start with 1. and the rest will happen automatically... ;-)
> 
> Sven
> 
> 

I'm currently trying to upgrade the patch to the latest shadow svn head.

I'm having a problem that I might have to post on gentoo bugs, but I'd
like to post it here to make sure I'm not overlooking anything.  I
started a new cross-build of armv4l-softfloat-linux-gnueabi with
crossdev.  After installing the toolchain, using emerge-wrapper --init,
modifying make.conf, etc..., all emerges with
ROOT=/usr/armv4l-softfloat-linux-gnueabi/ in the environment cause
portage to use the --quiet flag.  I don't have the flag in
PORTAGE_RSYNC_EXTRA_OPTS.  I've tried deleting /var/cache/edb and
${ROOT}var/cache/edb, to no avail.  I can't use FEATURES="python-trace"
to debug because the --quiet flag seems to override it.  All thats
visible is "myopts {'--quiet': True, '--buildpkg': True, '--verbose':
True, '--oneshot': True, '--debug': True, '--root-deps':'rdeps'}".  I
already searched gentoo bugs.  Does anyone know if there was a change in
portage that would cause this, or am I overlooking something?

-P. Levine