From cc2c9e5a50abd63f42aca05f1ace0b2af07e982f Mon Sep 17 00:00:00 2001 From: Zac Medico Date: Sat, 17 Mar 2012 14:31:55 -0700 Subject: repoman: add --digest= option, bug #406875 --- man/repoman.1 | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) (limited to 'man') diff --git a/man/repoman.1 b/man/repoman.1 index ddabbbb5b..37babcd4b 100644 --- a/man/repoman.1 +++ b/man/repoman.1 @@ -1,4 +1,4 @@ -.TH "REPOMAN" "1" "Feb 2012" "Portage VERSION" "Portage" +.TH "REPOMAN" "1" "Mar 2012" "Portage VERSION" "Portage" .SH NAME repoman \- Gentoo's program to enforce a minimal level of quality assurance in packages added to the portage tree .SH SYNOPSIS @@ -15,6 +15,21 @@ Note: \fBrepoman commit\fR only works \fIinside local\fR cvs, git, or subversion \fB-a\fR, \fB--ask\fR Request a confirmation before commiting .TP +\fB\-\-digest=\fR +Automatically update Manifest digests for modified files. This +option triggers a behavior that is very similar to that enabled +by FEATURES="digest" in \fBmake.conf\fR(5). In order to enable +this behavior by default for repoman alone, add +\fB\-\-digest=y\fR to the \fIREPOMAN_DEFAULT_OPTS\fR variable in +\fBmake.conf\fR(5). The \fBmanifest\-check\fR mode will +automatically ignore the \-\-digest option. + +\fBNOTE:\fR +This option does not trigger update of digests for Manifest DIST +entries that already exist. Replacement of existing Manifest +DIST entries can be forced by using the \fBmanifest\fR mode +together with the \fB\-\-force\fR option. +.TP \fB--force\fR Force commit to proceed, regardless of QA issues. For convenience, this option causes the most time consuming QA checks to be skipped. The commit message will -- cgit v1.2.3-1-g7c22