At Mon, 23 Jul 2007 17:02:35 +0100 Neil Bothwick <[EMAIL PROTECTED]> wrote:
> On Mon, 23 Jul 2007 17:43:01 +0200, Alan McKinnon wrote:
>
>> make.profile is for devs to make default system changes
>
> make.conf is for users to make customised system changes
>
>> /etc/portage/* is for users to make customized local changes
>
> In increasing order of priority.
OK. Here are proposed words. The two paragraphs indented 4 spaces
are the first two paragraphs of the existing man page; the middle
paragraph is new. I did not know neil's comment on priority, but
trust his memory and included the comment in the proposed addition.
My proposal is to file an enhancement documentation bug.
allan
The current portage code uses many different configuration files, most
of which are unknown to users and normal developers. Here we will try
to collect all the odds and ends so as to help users more effectively
utilize portage. This is a reference only for files which do not
already have a man page.
Note that users should place their customized local changes in the
/etc/portage directory, creating any needed files listed below that
do not exist. The files are listed in increasing order of
priority.
The make.profile directory, which is a symlink into the /usr/portage
tree, is for system defaults. Like all of the /usr/portage tree,
these files are overwritten when an emerge sync is performed. Hence
users normally do *not* alter these files.
All files in the make.profile directory may be tweaked via parent pro-
files when using cascading profiles. For more info, please see
http://www.gentoo.org/proj/en/releng/docs/cascading-profiles.xml
--
[EMAIL PROTECTED] mailing list
