[reproducible-website] 01/01: docs/buy_in: Document easier build sys refactoring
Eduard Sanou
dhole-guest at moszumanska.debian.org
Thu Dec 15 14:58:52 UTC 2016
This is an automated email from the git hooks/post-receive script.
dhole-guest pushed a commit to branch master
in repository reproducible-website.
commit 5f299177ce3b8fd73497e20d9ae526f5efa30323
Author: Clemens Lang <neverpanic at gmail.com>
Date: Thu Dec 15 13:13:58 2016 +0100
docs/buy_in: Document easier build sys refactoring
If your output did not change after a build system change, you can be
reasonably confident that your software will still work. That's better
than re-running all tests, so clearly an advantage of reproducible
builds.
---
_docs/buy_in.md | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/_docs/buy_in.md b/_docs/buy_in.md
index 3bf2d9c..393849a 100644
--- a/_docs/buy_in.md
+++ b/_docs/buy_in.md
@@ -93,6 +93,10 @@ With similar artifacts, testing can focus on parts that changed while
still preserving confidence about unchanged code. This can speed up
quality assurance and development speed.
+Changes to the build system can be tested easily with reproducible
+builds: If the output artifacts are identical, the changes will not
+affect runtime behavior.
+
“But how can I trust my compiler?”
----------------------------------
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/reproducible-website.git
More information about the Reproducible-commits
mailing list