[Reproducible-commits] [reproducible-builds-howto] 03/03: Rephrase section about recording the build environment

[Jérémy Bobbio]

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

lunar pushed a commit to branch master
in repository reproducible-builds-howto.

commit 02983eed760d55572fcd35463ec6de6e8afc4b9f
Author: Jérémy Bobbio <lunar at debian.org>
Date:   Sun Aug 2 00:28:20 2015 +0200

    Rephrase section about recording the build environment
---
 reproducible-builds-howto.mdwn | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/reproducible-builds-howto.mdwn b/reproducible-builds-howto.mdwn
index e2e09ef..c3c4ba1 100644
--- a/reproducible-builds-howto.mdwn
+++ b/reproducible-builds-howto.mdwn
@@ -128,14 +128,14 @@ Some environment variables might affect some tools output. A common example is t
 
 While someone building your software might want to see build error messages in their preferred language, it is better to have the output always be in the same format.
 
-Store compilation information separately
-----------------------------------------
+Don't record information about the build environment
+----------------------------------------------------
 
-Any information related to the compilation process should be store in files separate from the software binary distribution. This includes information such as date and time of the build, build system hostname, path, network configuration, CPU type, memory size, environment variables.
+Avoid recording any information related to the compilation process in the software being distributed. This includes information such as date and time of the build, build system hostname, path, network configuration, CPU type, memory size, environment variables. Instead make sure that variations in these parameters do not affect the build products or make them stable as part of your controlled build environment. XXX add link
 
-XXX: unclear
+If you really want to record it, it should be in a separate build product that can be easily ignored or distributed separately—eventualy as a way to reproduce the build environment. XXX: add link
 
-Sadly, build paths are often recorded in debug information by compilers in order to locate the associated source files. This is currently hard to sanitize.
+One caveat though: build paths are often recorded in debug information by compilers in order to locate the associated source files. For the specific case of DWARF files, there is currently no good tool to change them after a build to a pre-determined value. A work-around is to define the build path as part of the build environment.
 
 Reproducible build environment
 ==============================

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/reproducible-builds-howto.git