[Reproducible-commits] [reproducible-website] 02/55: Fix links for Liquid versions who can't cope with line breaks
Chris Lamb
chris at chris-lamb.co.uk
Tue Aug 23 13:39:50 UTC 2016
This is an automated email from the git hooks/post-receive script.
lamby pushed a commit to branch master
in repository reproducible-website.
commit 7d698a20398277b0c4b84bb6d18eab3337027ee9
Author: Jérémy Bobbio <lunar at debian.org>
Date: Sat Oct 31 18:40:31 2015 +0000
Fix links for Liquid versions who can't cope with line breaks
---
_docs/archives.md | 7 +++----
_docs/build_path.md | 3 +--
_docs/build_toolchain_from_source.md | 9 ++++-----
_docs/definition_strategies.md | 6 +++---
_docs/perimeter.md | 3 +--
_docs/recording.md | 8 ++++----
_docs/timestamps.md | 10 +++++-----
_docs/timezones.md | 6 +++---
8 files changed, 24 insertions(+), 28 deletions(-)
diff --git a/_docs/archives.md b/_docs/archives.md
index 91959f4..c6a1fb4 100644
--- a/_docs/archives.md
+++ b/_docs/archives.md
@@ -27,8 +27,8 @@ $ tar --mtime='2015-10-21 00:00Z' -cf product.tar build
[timezone]({{ "/docs/timezones/" | prepend: site.baseurl }}).)
For other achive formats, it is always possible to use `touch` to reset
-the modification times to a [predefined value]({{ "/docs/timestamps/" |
-prepend: site.baseurl }}) before creating the archive:
+the modification times to a [predefined value]({{ "/docs/timestamps/" | prepend: site.baseurl }})
+before creating the archive:
{% highlight sh %}
$ find build -print0 |
@@ -65,8 +65,7 @@ File ordering
When asked to record directories, most archive formats will read their
content in the order returned by the filesystem which is [likely to be
-different on every run]({{ "/docs/stable-inputs/" | prepend:
-site.baseurl }}).
+different on every run]({{ "/docs/stable-inputs/" | prepend: site.baseurl }}).
With version 1.28, GNU Tar has gained `--sort=name` option which will
sort filenames in a locale independent manner:
diff --git a/_docs/build_path.md b/_docs/build_path.md
index 5a64564..1e94049 100644
--- a/_docs/build_path.md
+++ b/_docs/build_path.md
@@ -20,8 +20,7 @@ For the specific case of [DWARF
symbols](https://en.wikipedia.org/wiki/DWARF), there is currently no good
tool to
change them after a build to a pre-determined value[^debugedit]. A work-around is to
-[define the build path as part of the build environment]({{
-"/docs/perimeter/" | prepend: site.baseurl }}).
+[define the build path as part of the build environment]({{ "/docs/perimeter/" | prepend: site.baseurl }}).
[^debugedit]: [debugedit](https://fedoraproject.org/wiki/Releases/FeatureBuildId) can replace the path used at build time by a predefined one but it will do it by rewriting bytes in place. As this does not reorder the hash table of strings, the resulting bytes will still be different depending on the original build path.
diff --git a/_docs/build_toolchain_from_source.md b/_docs/build_toolchain_from_source.md
index 92aa95d..6ba6dae 100644
--- a/_docs/build_toolchain_from_source.md
+++ b/_docs/build_toolchain_from_source.md
@@ -19,11 +19,10 @@ Building using external resources
The source for the different components can be retrieved from online
repository. Using release tarballs might be preferable as they are
-easier to cache, [mirror, checksum and verify]({{
-"/docs/volatile-inputs/" | prepend: site.baseurl }}). When retrieving
-the source from a version control system repository, it's best to have a
-precise reference to the code version. With Git, using a tag with a
-verified signature or a commit hash will work best.
+easier to cache, [mirror, checksum and verify]({{ "/docs/volatile-inputs/" | prepend: site.baseurl }}).
+When retrieving the source from a version control system repository,
+it's best to have a precise reference to the code version. With Git,
+using a tag with a verified signature or a commit hash will work best.
The compilation itself can be driven by shell scripts or an extra target
in the project `Makefile`.
diff --git a/_docs/definition_strategies.md b/_docs/definition_strategies.md
index a5461e1..a418581 100644
--- a/_docs/definition_strategies.md
+++ b/_docs/definition_strategies.md
@@ -29,9 +29,9 @@ tools from source.
Using `make` or any other compilation driver, the required tools will be
downloaded, built, and locally installed before compiling the software.
-Like any other [inputs from the network]({{ "/docs/volatile-inputs/" |
-prepend: site.baseurl }}), the content of the archive should be backed
-up and verified using cryptographic checksums.
+Like any other [inputs from the network]({{ "/docs/volatile-inputs/" | prepend: site.baseurl }}),
+the content of the archive should be backed up and verified using
+cryptographic checksums.
Reference distribution
----------------------
diff --git a/_docs/perimeter.md b/_docs/perimeter.md
index 041e700..09b9e66 100644
--- a/_docs/perimeter.md
+++ b/_docs/perimeter.md
@@ -41,8 +41,7 @@ XXX: Not really happy with this section. Please help!
What is exactly defined as the build environment needs to be properly
specified as this will determine how much of the build system will need
-to be [made deterministic]({{ "/docs/deterministic-build-systems/" |
-prepend: site.baseurl }}).
+to be [made deterministic]({{ "/docs/deterministic-build-systems/" | prepend: site.baseurl }}).
The defined environment will have the list of the tools used by the
build process and versions that must be used.
diff --git a/_docs/recording.md b/_docs/recording.md
index e6c54c9..9bb85ad 100644
--- a/_docs/recording.md
+++ b/_docs/recording.md
@@ -14,10 +14,10 @@ of the build environment irrelevant to the build output, or ensure they
are mandatory to rebuild the software exactly as it distributed.
Any irrelevant information should not be recorded. This depends on what
-has been made [part of the build environment]({{ "/docs/perimeter/" |
-prepend: site.baseurl }}), but likely includes information such as date
-and time of the build, build system hostname, path, network
-configuration, CPU type, memory size, environment variables…
+has been made [part of the build environment]({{ "/docs/perimeter/" | prepend: site.baseurl }}),
+but likely includes information such as date and time of the build,
+build system hostname, path, network configuration, CPU type, memory
+size, environment variables…
The rest of the build environment should either be defined as part of
the development process or recorded during the build process.
diff --git a/_docs/timestamps.md b/_docs/timestamps.md
index d6f7de0..3d0d583 100644
--- a/_docs/timestamps.md
+++ b/_docs/timestamps.md
@@ -6,8 +6,8 @@ permalink: /docs/timestamps/
Timestamps make the biggest source of reproducibility issues. Many build
tools fancy recording the current date and time. The filesystem does,
-and [most archive formats]({{ "/docs/archives/" | prepend: site.baseurl
-}}) will happily record modification times on top of their own
+and [most archive formats]({{ "/docs/archives/" | prepend: site.baseurl }})
+will happily record modification times on top of their own
timestamps. It is also customary to record the date of the build in the
software itself…
@@ -24,9 +24,9 @@ needs to be defined or extensively recorded.
If a date is required to give users an idea on when the software was
made, it is better to use a date that is relevant to the source code
instead of the build: old software can always be built later. Like
-[version information]({{ "/docs/version-information/" | prepend:
-site.baseurl }}), it's best to extract such a date from the revision
-control system or from a *changelog*.
+[version information]({{ "/docs/version-information/" | prepend: site.baseurl }}),
+it's best to extract such a date from the revision control system or
+from a *changelog*.
External tools
--------------
diff --git a/_docs/timezones.md b/_docs/timezones.md
index aa4b815..94e6279 100644
--- a/_docs/timezones.md
+++ b/_docs/timezones.md
@@ -4,9 +4,9 @@ layout: docs
permalink: /docs/timezones/
---
-Unless the build timezone is [made part of the build environment]({{
-"/docs/perimeter/" | prepend: site.baseurl }}), care must be taken to
-get the build output when the build is run in two different timezones.
+Unless the build timezone is [made part of the build environment]({{ "/docs/perimeter/" | prepend: site.baseurl }}),
+care must be taken to get the build output when the build is run in two
+different timezones.
Avoid writing the current timezone
----------------------------------
--
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