[Reproducible-commits] [source-date-epoch-spec] 03/04: add some restrictions if upstream want to set this variable themselves

[Ximin Luo]

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

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

commit a1409cbad5d437c30cbaca098cba681b4c494635
Author: Ximin Luo <infinity0 at debian.org>
Date:   Thu Aug 27 16:52:13 2015 +0200

    add some restrictions if upstream want to set this variable themselves
---
 source-date-epoch-spec.xml | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/source-date-epoch-spec.xml b/source-date-epoch-spec.xml
index 39da80a..57ee6c2 100644
--- a/source-date-epoch-spec.xml
+++ b/source-date-epoch-spec.xml
@@ -218,10 +218,19 @@
 			this variable for any embedded timestamps, in place of
 			the "current" date and time of when the process is run.
 		</para>
+		<para>
+			Upstream build processes MAY attempt to set this variable
+			for child processes to consume, for example by reading
+			the time of the latest VCS commit or filesystem entry if
+			there are uncommitted changes. However, they MUST NOT do
+			this if the variable is already set (e.g. by a parent
+			process such as a distribution-specific build scripts, or
+			by the user themselves).
+		</para>
 
 		<warning>
 			<para>
-				Code should not require the presence of the
+				Code SHOULD NOT require the presence of the
 				variable so that it can be built outside of a
 				context where it is provided. Falling back to
 				the "current" time may be acceptable behaviour

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