From bc672bf650da58e57c5a6e58b60ca94c8706eb89 Mon Sep 17 00:00:00 2001 From: Alexander Berntsen Date: Wed, 31 Jul 2013 17:25:14 +0200 Subject: [PATCH] Fix imprecise paragraph, bug #339446 --- man/ebuild.1 | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/man/ebuild.1 b/man/ebuild.1 index 4bde66e..29f88b0 100644 --- a/man/ebuild.1 +++ b/man/ebuild.1 @@ -19,11 +19,15 @@ This must be a valid ebuild script. For further information read \fBebuild\fR(5). .SH "COMMANDS" By default, portage will execute all the functions in order up to the -one actually specified. For example, simply issuing the command \fBcompile\fR -will trigger the functions before it to also be run (such as \fBsetup\fR -and \fBunpack\fR). If you wish to only have the specified command run, then -you should use the \fInoauto\fR option in the \fBFEATURES\fR environment -variable. See the \fBmake.conf\fR(5) man page for more information. +one actually specified, except for the functions that have already been +executed in a previous invocation of ebuild. For example, simply issuing the +command \fBcompile\fR will trigger the functions before it to also be run (such +as \fBsetup\fR and \fBunpack\fR), unless they were run in a previous invocation +of ebuild. If you want to make sure they are all run, you need to use +the command \fBclean\fR first. If you wish to only have the specified command +run, then you should use the \fInoauto\fR option in the \fBFEATURES\fR +environment variable. See the \fBmake.conf\fR(5) man page for more +information. .TP .BR help -- 1.8.1.5