emerge.1: clarify docs for package arguments

This will fix bug #354137.

diff --git a/man/emerge.1 b/man/emerge.1
index 297ac15975012d9280d9ffc04bad7a87d39a2d4f..34dfe83c366fad1c6644d390e9b661074307065f 100644 (file)
--- a/man/emerge.1
+++ b/man/emerge.1
@@ -28,8 +28,9 @@ and binary packages, and it can be used to create binary packages for
 distribution.
 .SH "EBUILDS, TBZ2S, SETS AND ATOMS"
 \fBemerge\fR primarily installs packages.  You can specify
-packages to install in one of four main ways: an \fIebuild\fR,
-a \fItbz2file\fR, a \fIset\fR, or an \fIatom\fR.
+packages to install in five possible ways: an \fIatom\fR,
+a \fIset\fR, an installed \fIfile\fR, an \fIebuild\fR, or
+a \fItbz2file\fR.
 .LP
 .TP
 .BR ebuild
@@ -52,8 +53,9 @@ A \fItbz2file\fR must be a valid .tbz2 created with \fBebuild
 .TP
 .BR file
 A \fIfile\fR must be a file or directory that has been installed by one or
-more packages. For directories that are owned by multiple packages, all
-owning packages to be selected. See the portageq(1) owners command if you
+more packages. If an absolute path is not used, then it must begin with
+either "./" or "../". For directories that are owned by multiple packages, all
+owning packages will be selected. See the portageq(1) owners command if you
 would like to query the owners of one or more files or directories.
 .TP
 .BR set