ok, thank you.I will try the chroot stuff as soon as I have some time.

As for what I'm trying to do: making portage able to add user/groups when using 
--root option.
This is a known limitation since a long time. I'm currently also discussing 
this point with the "shadow" upstream team (I have some patches for useradd and 
groupadd)

So for now I'm trying to make portage to just echo some traces when calling 
enewgroup for example, when I emerge sys-power/nut as a test package (that 
package is creating a nut user and group)
I tried to put some einfo at the begining of the  enewgroup function, but I do 
not see them. I also tryed echo "test" > /tmp/test.txt, and I do no see the 
file too...

And I see the traces from the nut ebuild (package_setup if I remember 
properly). And if I remove the nut group from my /etc/group, I do see the 
enewgroup original traces, but not mine.
It's as if portage is using a different enewgroup function, or a cached one...

I tried the irc last time, but nobody was there (most likely because of the 
time. I will try tomorrow late afternoon)

--------------------------------------------
En date de : Mer 4.5.16, Ian Stakenvicius <a...@gentoo.org> a écrit :

 Objet: Re: [gentoo-dev] Re : Cannot see my eclass modifications
 À: gentoo-dev@lists.gentoo.org
 Date: Mercredi 4 mai 2016, 20h28
 
 On 04/05/16 02:30 PM,
 Farid BENAMROUCHE wrote:
 > hum... yes I've
 setup all the relevant settings in my /etc/portage...
 > I've also read the man, and still not
 understanding why.
 > 
 > But At least you are confirming me that
 directly modifying the user.eclass in /usr/portage/eclass
 should work!
 > 
 > The
 exact command line I've used was ROOT=/sysroot emerge
 -av sys-power/nut, where sysroot is a working x86 rootfs
 (ie, I can chroot in it) with no portage inside...
 > 
 >
 PORTAGE_ECLASS_WARNING_ENABLE="1" in the make.conf
 seems to not work too...
 
 
 ..ok so if you've got a
 full chroot, you might want to use 'emerge
 --config-root=/path/to/chroot [stuff]' and
 make sure that the
 /etc/portage/repos.conf
 changes you made are in the chroot too.
 
 Barring that, though, the issue may very well
 be the type of changes
 you're trying to
 make to user.eclass just not working (or being
 called) as expected.
 
 A bunch of us hang out on irc.freenode.org in
 #gentoo-dev-help , and
 stuff like this may
 be easier to help with in a more interactive
 environment like that.
 

Reply via email to