1 |
Zac Medico posted on Sun, 09 Sep 2012 14:57:30 -0700 as excerpted: |
2 |
|
3 |
> On 09/09/2012 02:42 PM, Doug Goldstein wrote: |
4 |
>> On Sun, Sep 9, 2012 at 3:13 PM, Jorge Manuel B. S. Vicetto |
5 |
>> <jmbsvicetto@g.o> wrote: |
6 |
>>> -----BEGIN PGP SIGNED MESSAGE----- |
7 |
>>> Hash: SHA1 |
8 |
>>> |
9 |
>>> This news item was committed. |
10 |
>>> |
11 |
>>> |
12 |
>> So the news item was a bit ambiguous on if I wanted to make the change |
13 |
>> myself to the new locations when I could actually make the change. |
14 |
>> Current portage supports it? Or is their a new version coming which I |
15 |
>> would need? |
16 |
> |
17 |
> It's been supported in stable portage since portage-2.1.9.24 stabilized |
18 |
> in November/December 2010: |
19 |
|
20 |
Zac, |
21 |
|
22 |
To your knowlege (IOW have you tested) having /etc/make.conf either a |
23 |
symlink to /etc/portage/make.conf or a simple one-line |
24 |
"source /etc/portage/make.conf"? |
25 |
|
26 |
Back when I first became aware of the movement toward |
27 |
/etc/portage/make.conf, I'd guess in late 2010 or early 2011 given your |
28 |
dates, I tried both setting only /etc/portage/make.conf, which failed due |
29 |
to some third party utility (which I'd hope has been fixed now but I've |
30 |
not tested it), and making /etc/make.conf a simple symlink/source, which |
31 |
caused portage some indigestion. |
32 |
|
33 |
So I'm wondering if the latter problem's now (tested) fixed, and people |
34 |
can use the new location but still put either a compatibility symlink or |
35 |
source at the old location to keep old scripts and the like working, |
36 |
without portage suffering the indigestion at the prospect that it did at |
37 |
least way back then. |
38 |
|
39 |
If you haven't tested it and want me to, then file a bug if necessary, |
40 |
just say so, but it'd be nice to know whether you believe it to be |
41 |
working now, before I go try it again. |
42 |
|
43 |
-- |
44 |
Duncan - List replies preferred. No HTML msgs. |
45 |
"Every nonfree program has a lord, a master -- |
46 |
and if you use the program, he is your master." Richard Stallman |