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... -------------------------------------------- En date de : Mar 3.5.16, Mike Gilbert <[email protected]> a écrit : Objet: Re: [gentoo-dev] Re : Cannot see my eclass modifications À: "Gentoo Dev" <[email protected]>, [email protected] Date: Mardi 3 mai 2016, 23h39 On Tue, May 3, 2016 at 5:42 PM, Farid BENAMROUCHE <[email protected]> wrote: > Hi, > > I'm still searching for the reason why I'm not seeing my eclass modifications... no luck so far. > > What can I do to debug portage's behavior? > > Thank you > > -------------------------------------------- > En date de : Sam 30.4.16, Farid BENAMROUCHE <[email protected]> a écrit : > > Objet: Re : Cannot see my eclass modifications > À: [email protected] > Date: Samedi 30 avril 2016, 20h03 > > Hi all, > > I'm currently developping a patch for user.eclass, but I'm > banging my head against a wall... > > So for testing first, I've setup an overlay, and I now > that > it is taken in account by portage (If I rename portage's > user.eclass, emerge is still working. If I remove my > overlay, emerge complains about missing user eclass. So my > overlay is actually working) > I've modified enewgroup and egetent for example and put > some > einfo and also modified some other stuffs to be sure that > I'm entering the function.... > > Then emerge sys-power/nut, I can see the pkg-setup traces, > just after the call to enewgroup... but still cannot see > my > eclass modifications! > I tried to modify directly the > /usr/portage/eclass/user.eclass file, but still the same > issue... > I'm totally puzzled about this point! I'm most likely > missing a stupid point somewhere... > > Anyone knows what could be the problem? Please let me know > what traces/info you need and I will post them. > > Thank you! > > Portage will only use eclasses from your overlay for ebuilds in your overlay, at least by default. You can force it to use your overlay by setting eclass-overrides in repos.conf. I have no idea why you would experience this problem if you are modifying /usr/portage/eclass directly.
