[build-path-prefix-map-spec] 48/50: Merge pull request #1 from danielshahaf/patch-1
Ximin Luo
infinity0 at debian.org
Fri Mar 10 15:17:23 UTC 2017
This is an automated email from the git hooks/post-receive script.
infinity0 pushed a commit to branch master
in repository build-path-prefix-map-spec.
commit 7934d5da5c30db510ab1128db1b0b68d07ced155
Merge: 14dbe98 8428b3c
Author: Ximin Luo <infinity0 at debian.org>
Date: Fri Mar 10 15:58:52 2017 +0100
Merge pull request #1 from danielshahaf/patch-1
spec-main.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --cc spec-main.rst
index c0201ae,eeed84f..156e115
--- a/spec-main.rst
+++ b/spec-main.rst
@@@ -113,10 -108,10 +113,10 @@@ Setting the encoded valu
Producers SHOULD NOT overwrite existing values; instead they should append
their new mappings onto the right of any existing value.
-Producers who build *general software* that uses this envvar, MUST NOT expect
+Producers who build *general software* that uses this variable, MUST NOT expect
any special contracts on the output emitted by *general consumers* based on
- this variable - only that their output be reproducible when the build path
+ this variable ― only that their output be reproducible when the build path
-changes and the value of this envvar is changed to match the new paths.
+changes and the value of this variable is changed to match the new paths.
On the other hand, if you know you will only support a limited set of
consumers, you may expect that they apply these mappings in specific ways.
@@@ -171,10 -167,10 +171,10 @@@ Notes and link
The test vectors from this document's appendix are also available there.
.. [3] This is to make it easier for producers to append values, e.g. as in
- ``envvar += ":" + encoded_pair`` which would be valid even if envvar is
- originally empty.
+ ``old_value += ":" + encoded_pair`` which would be valid even if the value
+ is originally empty.
- .. [4] This is to "fail early" in the cases that a naive producer does not
+ .. [4] This is to "fail early" in case a naive producer does not
encode characters like ``=`` but the build path or target path does
actually contain them.
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/build-path-prefix-map-spec.git
More information about the Reproducible-commits
mailing list