aboutsummaryrefslogtreecommitdiff
path: root/locale/eo/LC_MESSAGES/_articles/2020-08-10-guix-inside-sourcehut-builds-sr-ht-ci.po
blob: 64bc4176ab2eb19006f27be06711c14fbc0b9331 (about) (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
#
msgid ""
msgstr ""

msgid ""
"title: Guix inside sourcehut builds.sr.ht CI\n"
"date: 2020-08-10\n"
"updated_at: 2020-08-19\n"
"layout: post\n"
"lang: en\n"
"ref: guix-inside-sourcehut-builds-sr-ht-ci"
msgstr ""

msgid ""
"After the release of the [NixOS images in "
"builds.sr.ht](https://man.sr.ht/builds.sr.ht/compatibility.md#nixos) and "
"much usage of it, I also started looking at [Guix](https://guix.gnu.org/) "
"and wondered if I could get it on the awesome builds.sr.ht service."
msgstr ""

msgid ""
"The Guix manual section on the [binary "
"installation](https://guix.gnu.org/manual/en/guix.html#Binary-Installation) "
"is very thorough, and even a [shell installer "
"script](https://git.savannah.gnu.org/cgit/guix.git/plain/etc/guix-"
"install.sh) is provided, but it is built towards someone installing Guix on "
"their personal computer, and relies heavily on interactive input."
msgstr ""

msgid ""
"I developed the following set of scripts that I have been using for some "
"time to run Guix tasks inside builds.sr.ht jobs. First, `install-guix.sh`:"
msgstr ""

msgid ""
"Almost all of it is taken directly from the [binary "
"installation](https://guix.gnu.org/manual/en/guix.html#Binary-Installation) "
"section from the manual, with the interactive bits stripped out: after "
"downloading and extracting the Guix tarball, we create some symlinks, add "
"guixbuild users and authorize the `ci.guix.gnu.org.pub` signing key."
msgstr ""

msgid ""
"After installing Guix, we perform a `guix pull` to update Guix inside "
"`start-guix.sh`:"
msgstr ""

msgid ""
"Then we can put it all together in a sample `.build.yml` configuration file "
"I'm using myself:"
msgstr ""

msgid ""
"We have to add the `guix-daemon` to `~/.buildenv` so it can be started on "
"every following task run. Also, since we used `wget` inside `install-"
"guix.sh`, we had to add it to the images package list."
msgstr ""

msgid ""
"After the `install-guix` task, you can use Guix to build and test your "
"project, or run any `guix environment --ad-hoc my-package -- my script` :)"
msgstr ""

msgid "Improvements"
msgstr ""

msgid ""
"When I originally created this code I had a reason why to have both a `sudo`"
" call for `sudo ./scripts/install-guix.sh` and `sudo` usages inside "
"`install-guix.sh` itself. I couldn't figure out why (it feels like my past "
"self was a bit smarter 😬), but it feels ugly now. If it is truly required I "
"could add an explanation for it, or remove this entirely in favor of a more "
"elegant solution."
msgstr ""

msgid ""
"I could also contribute the Guix image upstream to builds.sr.ht, but there "
"wasn't any build or smoke tests in the original "
"[repository](https://git.sr.ht/~sircmpwn/builds.sr.ht), so I wasn't inclined"
" to make something that just \"works on my machine\" or add a maintainence "
"burden to the author. I didn't look at it again recently, though."
msgstr ""