[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
02/03: website: reproducibility-with-guix: Fix image links and table.
From: |
Ludovic Courtès |
Subject: |
02/03: website: reproducibility-with-guix: Fix image links and table. |
Date: |
Tue, 14 Jan 2020 10:22:45 -0500 (EST) |
civodul pushed a commit to branch master
in repository guix-artwork.
commit fc764d62d1904a296964679b67ba450b058f9f78
Author: Ludovic Courtès <address@hidden>
AuthorDate: Tue Jan 14 16:21:09 2020 +0100
website: reproducibility-with-guix: Fix image links and table.
* website/posts/reproducibility-with-guix.md: Fix image links; turn
table into a verbatim ASCII table.
---
website/posts/reproducibility-with-guix.md | 37 +++++++++++-------------------
1 file changed, 13 insertions(+), 24 deletions(-)
diff --git a/website/posts/reproducibility-with-guix.md
b/website/posts/reproducibility-with-guix.md
index 8c7ca54..5e8975c 100644
--- a/website/posts/reproducibility-with-guix.md
+++ b/website/posts/reproducibility-with-guix.md
@@ -394,31 +394,20 @@ unit.
The following figure illustrates how the various pieces of information
from a package are used in the build process (done explicitly by
`guix build`, or implicitly when installing or otherwise using a
-package): ![](guix-package.png)
+package): ![Diagram of a Guix
package.](https://guix.gnu.org/static/blog/img/guix-package.png)
It may help to translate the Guix jargon to the vocabulary of C
programming:
-<table>
- <tr>
- <th>Guix package</th> <th>C program</th>
- </tr>
- <tr>
- <td>source code</td> <td>source code</td>
- </tr>
- <tr>
- <td>inputs</td> <td>libraries</td>
- </tr>
- <tr>
- <td>arguments</td> <td>compiler options</td>
- </tr>
- <tr>
- <td>build system</td> <td>compiler</td>
- </tr>
- <tr>
- <td>output</td> <td>executable</td>
- </tr>
-</table>
+```
+| Guix package | C program |
+|--------------+------------------|
+| source code | source code |
+| inputs | libraries |
+| arguments | compiler options |
+| build system | compiler |
+| output | executable |
+```
Building a package can be considered a generalization of compiling a
program. We could in fact create a \"GCC build system\" for Guix that
@@ -569,9 +558,9 @@ fundamentally distinct from its inputs. You could define a
special-purpose build system for one package, and put all the source
code in there. At the level of the CPU and the computer\'s memory, a
build process (as in fact *any* computation) looks like
-![](computation.png) It is human interpretation that decomposes this
-into ![](data-code.png) and in a next step into
-![](data-program-environment.png) We can go on and divide the
+![Image of a
computation.](https://guix.gnu.org/static/blog/img/computation.png) It is human
interpretation that decomposes this
+into ![Code and data.](https://guix.gnu.org/static/blog/img/data-code.png) and
in a next step into
+![Data, program, and
environment.](https://guix.gnu.org/static/blog/img/data-program-environment.png)
We can go on and divide the
environment into operating system, development tools, and application
software, for example, but the further we go in decomposing the input to
a computation, the more arbitrary it gets.