From fb0caf19c365cf89523e2725599781b05698a59f Mon Sep 17 00:00:00 2001 From: Zac Medico Date: Thu, 9 Jul 2009 07:35:22 +0000 Subject: Allow --deep to take an optional integer parameter, to specify how deep it should go. Also make --update so it no longer implies the equivalent of --deep=1. To get the old --update behavior, use --update --deep=1. svn path=/main/trunk/; revision=13812 --- man/emerge.1 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'man') diff --git a/man/emerge.1 b/man/emerge.1 index 4cb0c7ff2..07f511fa4 100644 --- a/man/emerge.1 +++ b/man/emerge.1 @@ -225,8 +225,8 @@ use \fB\-\-depclean\fR or \fB\-\-prune\fR. .TP .BR "\-\-update " (\fB\-u\fR) Updates packages to the best version available, which may not always be the -highest version number due to masking for testing and development. This will -also update direct dependencies which may not be what you want. Package atoms +highest version number due to masking for testing and development. +Package atoms specified on the command line are greedy, meaning that unspecific atoms may match multiple installed versions of slotted packages. .TP @@ -301,7 +301,7 @@ mode the bash build environment will run with the \-x option, causing it to output verbose debugging information to stdout. This also enables a plethora of other output (mostly dependency resolution messages). .TP -.BR "\-\-deep " (\fB\-D\fR) +.BR "\-\-deep [DEPTH] " (\fB\-D\fR) This flag forces \fBemerge\fR to consider the entire dependency tree of packages, instead of checking only the immediate dependencies of the packages. -- cgit v1.2.3-1-g7c22