At Tue, 24 Jul 2007 09:07:10 +0100 Neil Bothwick <[EMAIL PROTECTED]> wrote:
> On Mon, 23 Jul 2007 14:38:50 -0400, Allan Gottlieb wrote:
>
>> Note that users should place their customized local changes in the
>> /etc/portage directory, creating any needed files listed below that
>> do not exist.
>
> Local changes go in /etc/make.conf, per-package changes go
> in /etc/portage/.
Correct. How about (4 blank indent is from man portage; 2 blank
indent is new).
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 in make.conf local changes that are to
apply to all emerges; per-package changes belong 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
