Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 126196 Details for
Bug 186639
man portage doesn't make clear that changes belong in make.conf and /etc/portage
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
[patch]
clarify the relationship between /etc/make.profile/ and /etc/portage/profile/
profile_override.patch (text/plain), 1.04 KB, created by
Zac Medico
on 2007-07-27 23:35:54 UTC
(
hide
)
Description:
clarify the relationship between /etc/make.profile/ and /etc/portage/profile/
Filename:
MIME Type:
Creator:
Zac Medico
Created:
2007-07-27 23:35:54 UTC
Size:
1.04 KB
patch
obsolete
>Index: man/portage.5 >=================================================================== >--- man/portage.5 (revision 7411) >+++ man/portage.5 (revision 7414) >@@ -22,11 +22,13 @@ > .fi > .TP > .BR /etc/make.profile/ >+site\-specific overrides go in \fB/etc/portage/profile/\fR > .nf > deprecated > make.defaults > packages > packages.build >+package.mask > package.provided > package.use > package.use.force >@@ -127,9 +129,10 @@ > what a profile is (usually arch specific stuff). If you need a custom > profile, then you should make your own \fB/etc/make.profile/\fR > directory and populate it. However, if you just wish to override some >-settings, do NOT edit these files because they WILL be lost with the >-next `emerge \-\-sync`. See the section below on \fB/etc/portage/\fR for >-overriding. >+settings, use \fB/etc/portage/profile/\fR (it supports all of the same file >+types that \fB/etc/make.profile/\fR does, except parent). Do NOT edit the >+settings in \fB/etc/make.profile/\fR because they WILL be lost with the next >+`emerge \-\-sync`. > .RS > .TP > .BR deprecated
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 186639
: 126196