1 |
At Mon, 23 Jul 2007 17:02:35 +0100 Neil Bothwick <neil@××××××××××.uk> wrote: |
2 |
|
3 |
> On Mon, 23 Jul 2007 17:43:01 +0200, Alan McKinnon wrote: |
4 |
> |
5 |
>> make.profile is for devs to make default system changes |
6 |
> |
7 |
> make.conf is for users to make customised system changes |
8 |
> |
9 |
>> /etc/portage/* is for users to make customized local changes |
10 |
> |
11 |
> In increasing order of priority. |
12 |
|
13 |
OK. Here are proposed words. The two paragraphs indented 4 spaces |
14 |
are the first two paragraphs of the existing man page; the middle |
15 |
paragraph is new. I did not know neil's comment on priority, but |
16 |
trust his memory and included the comment in the proposed addition. |
17 |
|
18 |
My proposal is to file an enhancement documentation bug. |
19 |
|
20 |
allan |
21 |
|
22 |
The current portage code uses many different configuration files, most |
23 |
of which are unknown to users and normal developers. Here we will try |
24 |
to collect all the odds and ends so as to help users more effectively |
25 |
utilize portage. This is a reference only for files which do not |
26 |
already have a man page. |
27 |
|
28 |
Note that users should place their customized local changes in the |
29 |
/etc/portage directory, creating any needed files listed below that |
30 |
do not exist. The files are listed in increasing order of |
31 |
priority. |
32 |
|
33 |
The make.profile directory, which is a symlink into the /usr/portage |
34 |
tree, is for system defaults. Like all of the /usr/portage tree, |
35 |
these files are overwritten when an emerge sync is performed. Hence |
36 |
users normally do *not* alter these files. |
37 |
|
38 |
All files in the make.profile directory may be tweaked via parent pro- |
39 |
files when using cascading profiles. For more info, please see |
40 |
http://www.gentoo.org/proj/en/releng/docs/cascading-profiles.xml |
41 |
|
42 |
-- |
43 |
gentoo-user@g.o mailing list |