From: Zac Medico Date: Mon, 12 Aug 2013 22:19:56 +0000 (-0700) Subject: man/portage.5: fix environment spelling X-Git-Tag: v2.2.0~5 X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=698c9301fa33908cd6b9bf1c0a3ce6adcdd597f3;p=portage.git man/portage.5: fix environment spelling --- diff --git a/man/make.conf.5 b/man/make.conf.5 index 6c4710a74..acab65c4e 100644 --- a/man/make.conf.5 +++ b/man/make.conf.5 @@ -6,7 +6,7 @@ make.conf \- custom settings for Portage .SH "DESCRIPTION" This file contains various variables that are used by Portage. The file has a -newline-delimited list of \fI=\fR pairs (see the default file for +newline\-delimited list of \fI=\fR pairs (see the default file for examples) which are accessible from the environment of ebuilds. It supports simple shell\-like expansion of the form \fIvar="${var}"\fR, the source keyword and variable substituton, but not some of the more advanced BASH diff --git a/man/portage.5 b/man/portage.5 index dbc14bfe3..a57eaf0a1 100644 --- a/man/portage.5 +++ b/man/portage.5 @@ -1,4 +1,4 @@ -.TH "PORTAGE" "5" "Jul 2013" "Portage VERSION" "Portage" +.TH "PORTAGE" "5" "Aug 2013" "Portage VERSION" "Portage" .SH NAME portage \- the heart of Gentoo .SH "DESCRIPTION" @@ -941,7 +941,7 @@ bashrc approach that is described here. Also note that special variables such as \fBFEATURES\fR and \fBINSTALL_MASK\fR will not produce the intended results if they are set in bashrc, and therefore \fB/etc/portage/package.env\fR should be used instead. Lastly, note that these -files are interpreted much later than the portage enviroment file +files are interpreted much later than the portage environment file \fBpackage.env\fR. Portage will source all of these bashrc files after \fB/etc/portage/bashrc\fR