Gentoo Archives: gentoo-dev

From: Mike Gilbert <floppym@g.o>
To: Gentoo Dev <gentoo-dev@l.g.o>, fariouche@×××××.fr
Subject: Re: [gentoo-dev] Re : Cannot see my eclass modifications
Date: Tue, 03 May 2016 22:40:14
Message-Id: CAJ0EP42OZmARxkMvAPhuPpYirt3LNSKT1uxBmy9rKdLo5sgFRA@mail.gmail.com
In Reply to: [gentoo-dev] Re : Cannot see my eclass modifications by Farid BENAMROUCHE
1 On Tue, May 3, 2016 at 5:42 PM, Farid BENAMROUCHE <fariouche@×××××.fr> wrote:
2 > Hi,
3 >
4 > I'm still searching for the reason why I'm not seeing my eclass modifications... no luck so far.
5 >
6 > What can I do to debug portage's behavior?
7 >
8 > Thank you
9 >
10 > --------------------------------------------
11 > En date de : Sam 30.4.16, Farid BENAMROUCHE <fariouche@×××××.fr> a écrit :
12 >
13 > Objet: Re : Cannot see my eclass modifications
14 > À: gentoo-dev@l.g.o
15 > Date: Samedi 30 avril 2016, 20h03
16 >
17 > Hi all,
18 >
19 > I'm currently developping a patch for user.eclass, but I'm
20 > banging my head against a wall...
21 >
22 > So for testing first, I've setup an overlay, and I now
23 > that
24 > it is taken in account by portage (If I rename portage's
25 > user.eclass, emerge is still working. If I remove my
26 > overlay, emerge complains about missing user eclass. So my
27 > overlay is actually working)
28 > I've modified enewgroup and egetent for example and put
29 > some
30 > einfo and also modified some other stuffs to be sure that
31 > I'm entering the function....
32 >
33 > Then emerge sys-power/nut, I can see the pkg-setup traces,
34 > just after the call to enewgroup... but still cannot see
35 > my
36 > eclass modifications!
37 > I tried to modify directly the
38 > /usr/portage/eclass/user.eclass file, but still the same
39 > issue...
40 > I'm totally puzzled about this point! I'm most likely
41 > missing a stupid point somewhere...
42 >
43 > Anyone knows what could be the problem? Please let me know
44 > what traces/info you need and I will post them.
45 >
46 > Thank you!
47 >
48 >
49
50 Portage will only use eclasses from your overlay for ebuilds in your
51 overlay, at least by default. You can force it to use your overlay by
52 setting eclass-overrides in repos.conf.
53
54 I have no idea why you would experience this problem if you are
55 modifying /usr/portage/eclass directly.