1 |
I've made some progress! |
2 |
|
3 |
In my command line, I was still using the -k argument: ROOT=/sysroot emerge -avk sys-power/nut |
4 |
It seems like the eclass is inside the binary package and thus ignoring the system eclass. (which make sense to me) |
5 |
Now I can test my modifications and propose something ;) |
6 |
|
7 |
thank you |
8 |
|
9 |
-------------------------------------------- |
10 |
En date de : Mer 4.5.16, Ian Stakenvicius <axs@g.o> a écrit : |
11 |
|
12 |
Objet: Re: [gentoo-dev] Re : Cannot see my eclass modifications |
13 |
À: gentoo-dev@l.g.o |
14 |
Date: Mercredi 4 mai 2016, 20h28 |
15 |
|
16 |
On 04/05/16 02:30 PM, |
17 |
Farid BENAMROUCHE wrote: |
18 |
> hum... yes I've |
19 |
setup all the relevant settings in my /etc/portage... |
20 |
> I've also read the man, and still not |
21 |
understanding why. |
22 |
> |
23 |
> But At least you are confirming me that |
24 |
directly modifying the user.eclass in /usr/portage/eclass |
25 |
should work! |
26 |
> |
27 |
> The |
28 |
exact command line I've used was ROOT=/sysroot emerge |
29 |
-av sys-power/nut, where sysroot is a working x86 rootfs |
30 |
(ie, I can chroot in it) with no portage inside... |
31 |
> |
32 |
> |
33 |
PORTAGE_ECLASS_WARNING_ENABLE="1" in the make.conf |
34 |
seems to not work too... |
35 |
|
36 |
|
37 |
..ok so if you've got a |
38 |
full chroot, you might want to use 'emerge |
39 |
--config-root=/path/to/chroot [stuff]' and |
40 |
make sure that the |
41 |
/etc/portage/repos.conf |
42 |
changes you made are in the chroot too. |
43 |
|
44 |
Barring that, though, the issue may very well |
45 |
be the type of changes |
46 |
you're trying to |
47 |
make to user.eclass just not working (or being |
48 |
called) as expected. |
49 |
|
50 |
A bunch of us hang out on irc.freenode.org in |
51 |
#gentoo-dev-help , and |
52 |
stuff like this may |
53 |
be easier to help with in a more interactive |
54 |
environment like that. |