From 926c83c21804f90922154edfdafc5d9f64c9bb44 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sat, 29 Mar 2014 15:20:55 -0400 Subject: Added required content configuration. This includes checking when dropping files that any required content configuration is satisfied. However, it does not yet include an active check on the required content; the location log is trusted when checking the required content expression. --- doc/todo/required_content.mdwn | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'doc/todo') diff --git a/doc/todo/required_content.mdwn b/doc/todo/required_content.mdwn index 851e652ae..6afeee5c9 100644 --- a/doc/todo/required_content.mdwn +++ b/doc/todo/required_content.mdwn @@ -5,3 +5,19 @@ like preferred content, which is enforced. So, required content. For example, I might want a repository that is required to contain `*.jpeg`. This would make get --auto get it (it's implicitly part of the preferred content), and would make drop refuse to drop it. + +> I've implemented the basic required content. Currently only configurable +> via `vicfg`, because I don't think a lot of people are going to want to +> use it. +> +> Note that I did not yet add the active verification discussed below. +> So if required content is set to `not inallgroup=backup`, or +> `not copies=10`, trying to drop a file will not go off and prove +> that there are 10 copies or that the file is in every repository in +> the backup group. It will assume that the location log is accurate +> and go by that. +> +> I think this is enough to cover Richard's case, at least. +> In his example, A B and C are in group anchor and have required +> content set to `include=*`, and D E F have it set to +> `not inallgroup=anchor`. --[[Joey]] -- cgit v1.2.3