[Reproducible-commits] [source-date-epoch-spec] 01/01: Incorporate changes suggested by Milz Dechnik <dechmilznik at gmail.com>
Chris Lamb
lamby at moszumanska.debian.org
Thu Aug 27 14:11:32 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 48c4ffa40304ac3a79475e133836dcb5ce28ce60
Author: Chris Lamb <lamby at debian.org>
Date: Thu Aug 27 16:08:43 2015 +0200
Incorporate changes suggested by Milz Dechnik <dechmilznik at gmail.com>
---
source-date-epoch-spec.xml | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/source-date-epoch-spec.xml b/source-date-epoch-spec.xml
index f4b3b96..807d268 100644
--- a/source-date-epoch-spec.xml
+++ b/source-date-epoch-spec.xml
@@ -63,8 +63,7 @@
<sect2>
<title>Technical advantages</title>
<para>
- There are other, technical, reasons for adopting
- reproducible builds:
+ A reproducible build has other, technical, advantages:
</para>
<itemizedlist>
<listitem><para>
@@ -80,7 +79,7 @@
<listitem><para>
Removes many configuration-specific issues (eg. locale
or timezone-related changes to behaviour) eliminating
- hard to debug problem that can be specific to a user's
+ hard to debug problems that can be specific to a user's
particular environment.
</para></listitem>
<listitem><para>
@@ -89,15 +88,16 @@
no impact on generated binaries.
</para></listitem>
<listitem><para>
- Reduces the detection time of a build host compromise
- as their results can be externally validated.
+ Reduces the time-to-detection of a build host
+ compromise as its results can be externally validated.
</para></listitem>
<listitem><para>
Provides an audit trail from a binary back to its
source.
</para></listitem>
<listitem><para>
- Validation of packages built on foreign architectures.
+ Packages built on foreign architectures can be
+ trivially validated.
</para></listitem>
</itemizedlist>
</sect2>
@@ -106,7 +106,7 @@
<para>
Whilst there are a large number of obstacles to a fully
reproducible GNU/Linux or BSD distribution, many
- software packages are only unreprodubible because they
+ software packages are only unreproducible because they
embed a build-time timestamp into generated files.
</para>
<para>
@@ -125,12 +125,12 @@
</para>
<itemizedlist>
<listitem><para>
- It provides the age of the software.
+ Provides the age of the software.
</para></listitem>
<listitem><para>
- It suggests the environment that was used based on the
- availability of the build-dependencies available at the
- specified time.
+ Provides some indication of the environment that was
+ used for the build based on the availability of the
+ build-dependencies available at that particular moment.
</para></listitem>
</itemizedlist>
<para>
@@ -165,7 +165,7 @@
time is not a property of upstream source itself but
rather of a distributions' packaging that encapsulates
it. Ensuring this outer timestamp is used by the
- underling build system often requires cumbersome and
+ underlying build system often requires cumbersome and
distribution-specific changes.
</para>
<para>
--
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