From f3101b3adce6731790f80f83fafece54b7bd8a63 Mon Sep 17 00:00:00 2001 From: Brian Harring Date: Fri, 23 Sep 2011 16:43:28 -0700 Subject: manifest: controllable per repo This adds three states to layout.conf key use-manifest; false, true, and strict. false means "don't use manifests at all" true means "use and generate manifests, but allow them to be missing" strict means "manifests must be used everywhere in this repo" BUG=chromium-os:11308 TEST=repoman manifest usage. --- man/make.conf.5 | 4 ---- man/portage.5 | 3 +++ 2 files changed, 3 insertions(+), 4 deletions(-) (limited to 'man') diff --git a/man/make.conf.5 b/man/make.conf.5 index 3f3efae8b..6c64686c7 100644 --- a/man/make.conf.5 +++ b/man/make.conf.5 @@ -204,10 +204,6 @@ non-developers as well. The \fBsandbox\fR feature is very important and should not be disabled by default. .RS .TP -.B allow\-missing\-manifests -Allow missing manifest entries. This is primarily useful for temporary -trees or instances where manifests aren't used. -.TP .B assume\-digests When commiting work to cvs with \fBrepoman\fR(1), assume that all existing SRC_URI digests are correct. This feature also affects digest generation via diff --git a/man/portage.5 b/man/portage.5 index 2af667621..1d9545ab6 100644 --- a/man/portage.5 +++ b/man/portage.5 @@ -781,6 +781,9 @@ aliases = foo-overlay sign\-manifests = false # thin\-manifests only contain DIST entries thin\-manifests = true +# indicate that this repo requires manifests for each package, and is +# considered a failure if a manifest file is missing/incorrect +use\-manifests = strict .fi .RE .TP -- cgit v1.2.3-1-g7c22