summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZac Medico <zmedico@gentoo.org>2009-04-30 06:55:08 +0000
committerZac Medico <zmedico@gentoo.org>2009-04-30 06:55:08 +0000
commit4e0da23a946c5e87deef8a3da9aa50f7858a751c (patch)
tree24f6d53948ec2ebb83031042f8e77a406c171132
parentAllow --root-deps for ROOT=/, so people can do weird things like use it with (diff)
downloadportage-multirepo-4e0da23a946c5e87deef8a3da9aa50f7858a751c.tar.gz
portage-multirepo-4e0da23a946c5e87deef8a3da9aa50f7858a751c.tar.bz2
portage-multirepo-4e0da23a946c5e87deef8a3da9aa50f7858a751c.zip
Remove the ATOMS section and move --update to a new ACTIONS section.
(trunk r13272) svn path=/main/branches/2.1.6/; revision=13451
-rw-r--r--man/egencache.116
1 files changed, 7 insertions, 9 deletions
diff --git a/man/egencache.1 b/man/egencache.1
index 087ba2fd..c641f036 100644
--- a/man/egencache.1
+++ b/man/egencache.1
@@ -6,10 +6,12 @@ egencache \- generate metadata cache for ebuild repositories
.I [options] --update [ATOM]\fR...
.SH "DESCRIPTION"
The egencache program generates metadata cache for ebuild repositories.
-.SH "ATOMS"
-An optional list of specific package atoms to update. If no package atoms are
-specified then all will be updated. See ebuild(5) for the details on package
-atom syntax.
+.SH ACTIONS
+.TP
+.BR "\-\-update [ATOM] ... "
+Update the \fImetadata/cache/\fR directory (generate metadata as necessary).
+If no package atoms are specified then all will be updated. See ebuild(5)
+for the details on package atom syntax.
.SH OPTIONS
.TP
.BR "\-\-cache\-dir=CACHE_DIR"
@@ -33,7 +35,7 @@ Also see the related \fB\-\-load\-average\fR option.
Specifies that maximum load allowed when spawning multiple jobs.
.TP
.BR "\-\-rsync"
-When used together with the \fB\-\-update\fR options, this enables a workaround
+When used together with the \fB\-\-update\fR action, this enables a workaround
for cases in which the content of a cache entry changes and neither the file
mtime nor size changes, preventing rsync from detecting changes. Such cases are
handled by bumping the mtime on the ebuild (and the corresponding cache entry).
@@ -42,10 +44,6 @@ This option should only be needed for distribution via something like
(see \fBbug 139134\fR). It's not needed with \fBgit\fR(1) since that uses a
more thorough mechanism which allows it to detect changed inode numbers
(described in \fIracy-git.txt\fR in the git technical docs).
-.TP
-.BR "\-\-update [ATOM] ... "
-Update the \fImetadata/cache/\fR directory (generate metadata as necessary).
-If no package atoms are specified then all will be updated.
.SH "ENVIRONMENT OPTIONS"
.TP
\fBEGENCACHE_DEFAULT_OPTS\fR