| 1 |
At Tue, 24 Jul 2007 09:07:10 +0100 Neil Bothwick <neil@××××××××××.uk> wrote: |
| 2 |
|
| 3 |
> On Mon, 23 Jul 2007 14:38:50 -0400, Allan Gottlieb wrote: |
| 4 |
> |
| 5 |
>> Note that users should place their customized local changes in the |
| 6 |
>> /etc/portage directory, creating any needed files listed below that |
| 7 |
>> do not exist. |
| 8 |
> |
| 9 |
> Local changes go in /etc/make.conf, per-package changes go |
| 10 |
> in /etc/portage/. |
| 11 |
|
| 12 |
Correct. How about (4 blank indent is from man portage; 2 blank |
| 13 |
indent is new). |
| 14 |
|
| 15 |
allan |
| 16 |
|
| 17 |
The current portage code uses many different configuration files, most |
| 18 |
of which are unknown to users and normal developers. Here we will try |
| 19 |
to collect all the odds and ends so as to help users more effectively |
| 20 |
utilize portage. This is a reference only for files which do not |
| 21 |
already have a man page. |
| 22 |
|
| 23 |
Note that users should place in make.conf local changes that are to |
| 24 |
apply to all emerges; per-package changes belong in the /etc/portage |
| 25 |
directory, creating any needed files listed below that do not exist. |
| 26 |
The files are listed in increasing order of priority. |
| 27 |
|
| 28 |
The make.profile directory, which is a symlink into the /usr/portage |
| 29 |
tree, is for system defaults. Like all of the /usr/portage tree, |
| 30 |
these files are overwritten when an emerge sync is performed. Hence |
| 31 |
users normally do *not* alter these files. |
| 32 |
|
| 33 |
All files in the make.profile directory may be tweaked via parent pro- |
| 34 |
files when using cascading profiles. For more info, please see |
| 35 |
http://www.gentoo.org/proj/en/releng/docs/cascading-profiles.xml |
| 36 |
-- |
| 37 |
gentoo-user@g.o mailing list |
Archives