[Reproducible-commits] [source-date-epoch-spec] 01/01: Add proposed text for FORCE_SOURCE_DATE

[Ximin Luo]

This is an automated email from the git hooks/post-receive script.

infinity0 pushed a commit to branch force-source-date
in repository source-date-epoch-spec.

commit 4b9da6b7f1aae38b82eaf29deb51bbe150204c76
Author: Ximin Luo <infinity0 at debian.org>
Date:   Sat Jun 11 16:40:02 2016 +0200

    Add proposed text for FORCE_SOURCE_DATE
---
 source-date-epoch-spec.xml | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/source-date-epoch-spec.xml b/source-date-epoch-spec.xml
index 054acf7..28fbd57 100644
--- a/source-date-epoch-spec.xml
+++ b/source-date-epoch-spec.xml
@@ -153,6 +153,28 @@
 			exit with a non-zero error code.
 		</para>
 	</sect2>
+	<sect2>
+		<title>Special exceptions</title>
+		<para>
+			Background: embedded timestamps may be categorised into
+			several cases. For example, (a) implicit timestamps placed
+			into every output document, independently of the input
+			document, vs (b) explicit calls to "get-current-time"
+			procedures of the document input language, that may occur
+			in different positions in each input document.
+		</para>
+		<para>
+			Build processes STRONGLY SHOULD obey SOURCE_DATE_EPOCH for
+			all cases unconditionally. If (and only if) there are very
+			good reasons to go against this, it may choose to support
+			the environment variable FORCE_SOURCE_DATE. When this is 1,
+			it means "all cases that might obey SOURCE_DATE_EPOCH, will
+			obey it". For other values, including the empty or unset
+			values, the build process may choose which cases will obey
+			SOURCE_DATE_EPOCH - but this MUST be a subset of (or same
+			as) the cases that obey it when the value is 1.
+		</para>
+	</sect2>
 </sect1>
 
 <sect1>

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/source-date-epoch-spec.git