Lines 22-32
Link Here
|
22 |
.fi |
22 |
.fi |
23 |
.TP |
23 |
.TP |
24 |
.BR /etc/make.profile/ |
24 |
.BR /etc/make.profile/ |
|
|
25 |
site\-specific overrides go in \fB/etc/portage/profile/\fR |
25 |
.nf |
26 |
.nf |
26 |
deprecated |
27 |
deprecated |
27 |
make.defaults |
28 |
make.defaults |
28 |
packages |
29 |
packages |
29 |
packages.build |
30 |
packages.build |
|
|
31 |
package.mask |
30 |
package.provided |
32 |
package.provided |
31 |
package.use |
33 |
package.use |
32 |
package.use.force |
34 |
package.use.force |
Lines 127-135
Link Here
|
127 |
what a profile is (usually arch specific stuff). If you need a custom |
129 |
what a profile is (usually arch specific stuff). If you need a custom |
128 |
profile, then you should make your own \fB/etc/make.profile/\fR |
130 |
profile, then you should make your own \fB/etc/make.profile/\fR |
129 |
directory and populate it. However, if you just wish to override some |
131 |
directory and populate it. However, if you just wish to override some |
130 |
settings, do NOT edit these files because they WILL be lost with the |
132 |
settings, use \fB/etc/portage/profile/\fR (it supports all of the same file |
131 |
next `emerge \-\-sync`. See the section below on \fB/etc/portage/\fR for |
133 |
types that \fB/etc/make.profile/\fR does, except parent). Do NOT edit the |
132 |
overriding. |
134 |
settings in \fB/etc/make.profile/\fR because they WILL be lost with the next |
|
|
135 |
`emerge \-\-sync`. |
133 |
.RS |
136 |
.RS |
134 |
.TP |
137 |
.TP |
135 |
.BR deprecated |
138 |
.BR deprecated |