1 |
On Mon, Sep 10, 2012 at 6:49 PM, Pandu Poluan <pandu@××××××.info> wrote: |
2 |
> |
3 |
> On Sep 11, 2012 5:19 AM, "Mark Knecht" <markknecht@×××××.com> wrote: |
4 |
>> |
5 |
>> On Mon, Sep 10, 2012 at 11:13 AM, Chris Stankevitz |
6 |
>> <chrisstankevitz@×××××.com> wrote: |
7 |
>> > On Sun, Sep 9, 2012 at 6:41 PM, Mark Knecht <markknecht@×××××.com> |
8 |
>> > wrote: |
9 |
>> >> That's a very new change just announced globally today and only for |
10 |
>> >> new installs. Take a look at eselect news for more info. |
11 |
>> > |
12 |
>> > What a coincidence! I went with the older stage3 approach. |
13 |
>> > |
14 |
>> > Thank you, |
15 |
>> > |
16 |
>> > Chris |
17 |
>> > |
18 |
>> |
19 |
>> I just switched 3 machines over to the new way. It works fine. eselect |
20 |
>> profile set will create the new link in /etc/portage. I figure the |
21 |
>> biggest issue for me is that I won't be able to mindlessly type vi |
22 |
>> /etc/make.conf anymore. ;-) |
23 |
>> |
24 |
> |
25 |
> Ahh... the curse of muscle memory... I bet I'll experience some dumbfounded |
26 |
> moments for at least one week, staring at an empty vi screen due to muscle |
27 |
> memory typing /etc/make.conf instead of /etc/portage/make.conf ... :-P |
28 |
> |
29 |
> Rgds, |
30 |
|
31 |
Someone else suggested (or I think they suggested) putting a link at |
32 |
/etc/make.conf pointing at the new location. That might help with that |
33 |
problem. I'm just gonna force myself to learn the new location but |
34 |
like you're worried about I've already done it a couple of times |
35 |
today! |
36 |
|
37 |
- Mark |