1 |
On 11/08/2013 18:48, Tanstaafl wrote: |
2 |
> On 2013-08-11 12:03 PM, Marc Joliet <marcec@×××.de> wrote: |
3 |
>> When in doubt, read the man page (make.conf(5)): |
4 |
>> |
5 |
>> "[...] |
6 |
>> DESCRIPTION |
7 |
>> This file contains various variables that are used by |
8 |
>> Portage. Portage will check |
9 |
>> the currently-defined environment variables first for any |
10 |
>> settings. If no environ‐ |
11 |
>> ment settings are found, Portage then checks the |
12 |
>> make.conf files. Both |
13 |
>> /etc/make.conf and /etc/portage/make.conf are checked (if |
14 |
>> present), and settings |
15 |
>> from /etc/portage/make.conf will override settings from |
16 |
>> /etc/make.conf. [...]" |
17 |
> |
18 |
> Thanks... my point was more that the news item didn't explain this - |
19 |
> also, this answers as to make.conf, but what about make.profile? |
20 |
> |
21 |
> I just don't like being forced to assume, or 'test for myself', when it |
22 |
> could be made crystal clear in the news item/docs. |
23 |
> |
24 |
> Also, would |
25 |
> |
26 |
> ~ cd /etc/portage |
27 |
> ~ ln -s make.profile ../usr/portage/profiles/default/linux/amd64/13.0 |
28 |
|
29 |
No. That links a file in /etc/portage to something that doesn't exist |
30 |
(arguments wrong way round), and the .. parent directory doesn't belong |
31 |
there at all: |
32 |
|
33 |
cd /etc/portage |
34 |
ln -s $POSTDIR/profiles/path/to/profile/you/want profile.conf |
35 |
|
36 |
|
37 |
> |
38 |
> Be the right way to create the make.profile symlink in the new location? |
39 |
> |
40 |
> Not sure why the two preceeding dots are there in the current one in |
41 |
> /etc, but they are... |
42 |
> |
43 |
> On 2013-08-11 12:16 PM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
44 |
>> My question is why do you have files in both locations? |
45 |
> |
46 |
> I don't... I was getting ready to change these, and was just asking the |
47 |
> question... ;) |
48 |
|
49 |
|
50 |
new overrides old in this case |
51 |
|
52 |
|
53 |
-- |
54 |
Alan McKinnon |
55 |
alan.mckinnon@×××××.com |