[Reproducible-commits] [source-date-epoch-spec] 02/05: Some intro

Chris Lamb lamby at moszumanska.debian.org
Sat Aug 22 12:08:42 UTC 2015


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

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

commit b858fcffd40b86c2d7f714cc286c5fd18a1c3978
Author: Chris Lamb <lamby at debian.org>
Date:   Sat Aug 22 14:00:54 2015 +0200

    Some intro
---
 source-date-epoch-spec.xml | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/source-date-epoch-spec.xml b/source-date-epoch-spec.xml
index f4e7c72..61f856a 100644
--- a/source-date-epoch-spec.xml
+++ b/source-date-epoch-spec.xml
@@ -21,8 +21,25 @@
 
 <sect1>
 	<title>Reproducible builds</title>
+	<para>
+		A "reproducible build" is the property of a software package
+		whereby two builds of the source produce byte-for-byte
+		identical binaries.
+	</para>
 	<sect2>
 		<title>Why they matter</title>
+		<para>
+			Projects like Coreboot, Tor and Bitcoin have a strong interest
+			in allowing their users to verify that the binaries they
+			distribute correspond to the published source code and have
+			achieved some success in this area. For Linux distributions,
+			doing the same for their repositories is a much bigger job as
+			thousands of packages need to be built in a reproducible way.
+		</para>
+		<para>
+			There are other, technical, reasons for adopting
+			reproducible builds:
+		</para>
 	</sect2>
 	<sect2>
 		<title>Technical issues</title>

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



More information about the Reproducible-commits mailing list