diff options
-rw-r--r-- | general-concepts/use-flags/text.xml | 9 | ||||
-rw-r--r-- | general-concepts/user-environment/text.xml | 14 | ||||
-rw-r--r-- | profiles/make.defaults/text.xml | 11 |
3 files changed, 19 insertions, 15 deletions
diff --git a/general-concepts/use-flags/text.xml b/general-concepts/use-flags/text.xml index c591aaa..321a509 100644 --- a/general-concepts/use-flags/text.xml +++ b/general-concepts/use-flags/text.xml @@ -206,8 +206,9 @@ it on or off by default. <important> Adding <c>-</c> before a flag in <c>IUSE</c> is pretty much useless, as it will neither override the user configuration (<c>make.conf</c>) nor the profile -default (<c>make.defaults</c> and <c>package.use</c>). See make.conf(5) for -details on USE-ordering in Portage. +default (<c>make.defaults</c> and <c>package.use</c>). +See <uri link="::eclass-reference/make.conf/">make.conf(5)</uri> for details +on USE-ordering in Portage. </important> <codesample lang="ebuild"> @@ -348,8 +349,8 @@ needs. The <c>VIDEO_CARDS</c>, <c>INPUT_DEVICES</c> and <c>L10N</c> variables are automatically expanded into USE flags. These are known as <c>USE_EXPAND</c> variables. If the user has <c>L10N="en fr"</c> in -<c>make.conf</c>, for example, then <c>USE="l10n_en l10n_fr"</c> will -automatically be set by Portage. +<c><uri link="::eclass-reference/make.conf/"/></c>, for example, then +<c>USE="l10n_en l10n_fr"</c> will automatically be set by Portage. </p> <p> diff --git a/general-concepts/user-environment/text.xml b/general-concepts/user-environment/text.xml index d28b844..c2c02e7 100644 --- a/general-concepts/user-environment/text.xml +++ b/general-concepts/user-environment/text.xml @@ -2,15 +2,17 @@ <guide self="general-concepts/user-environment/"> <chapter> <title>User Environment</title> - <body> + <p> -User environment variables and <c>make.conf</c> settings get passed on to ebuilds. -This can be useful <d/> it's how <c>CFLAGS</c> and friends work, for example <d/> but -it can also result in nasty build-breaking variables like <c>LANG</c> and -<c>LC_ALL</c> getting through. Currently no sanitisation is performed upon the -environment. +User environment variables and +<c><uri link="::eclass-reference/make.conf/"/></c> settings get passed on +to ebuilds. This can be useful <d/> it's how <c>CFLAGS</c> and friends work, +for example <d/> but it can also result in nasty build-breaking variables like +<c>LANG</c> and <c>LC_ALL</c> getting through. Currently no sanitisation is +performed upon the environment. </p> + </body> <section> diff --git a/profiles/make.defaults/text.xml b/profiles/make.defaults/text.xml index 15ea2c6..03aa8db 100644 --- a/profiles/make.defaults/text.xml +++ b/profiles/make.defaults/text.xml @@ -5,11 +5,12 @@ <body> <p> -The <c>make.defaults</c> file in <c>profiles/</c> provides a minimal set of defaults -for the kinds of values which may be set in <c>make.conf</c> (<c>CFLAGS</c>, <c>USE</c>, -<c>FEATURES</c> etc) along with certain control variables (eg <c>USE_EXPAND</c>). -These values can further be refined by additional <c>make.defaults</c> files in -subprofiles. +The <c>make.defaults</c> file in <c>profiles/</c> provides a minimal set +of defaults for the kinds of values which may be set in +<c><uri link="::eclass-reference/make.conf/"/></c> (<c>CFLAGS</c>, +<c>USE</c>, <c>FEATURES</c> etc.) along with certain control variables +(e.g. <c>USE_EXPAND</c>). These values can further be refined by additional +<c>make.defaults</c> files in subprofiles. </p> <p> |