I've made some progress! In my command line, I was still using the -k argument: ROOT=/sysroot emerge -avk sys-power/nut It seems like the eclass is inside the binary package and thus ignoring the system eclass. (which make sense to me) Now I can test my modifications and propose something ;)
thank you -------------------------------------------- En date de : Mer 4.5.16, Ian Stakenvicius <[email protected]> a écrit : Objet: Re: [gentoo-dev] Re : Cannot see my eclass modifications À: [email protected] 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.
