Commit | Line | Data |
---|---|---|
8c01b9d0 ML |
1 | @node Contributing |
2 | @chapter Contributing | |
3 | ||
4 | This project is a cooperative effort, and we need your help to make it | |
5 | grow! Please get in touch with us on @email{guix-devel@@gnu.org} and | |
c0087d33 | 6 | @code{#guix} on the Libera Chat IRC network. We welcome ideas, bug |
8c01b9d0 ML |
7 | reports, patches, and anything that may be helpful to the project. We |
8 | particularly welcome help on packaging (@pxref{Packaging Guidelines}). | |
9 | ||
e15fcdd1 LC |
10 | @cindex code of conduct, of contributors |
11 | @cindex contributor covenant | |
dcb7119a AS |
12 | We want to provide a warm, friendly, and harassment-free environment, so |
13 | that anyone can contribute to the best of their abilities. To this end | |
14 | our project uses a ``Contributor Covenant'', which was adapted from | |
478af028 | 15 | @url{https://contributor-covenant.org/}. You can find a local version in |
dcb7119a | 16 | the @file{CODE-OF-CONDUCT} file in the source tree. |
e15fcdd1 | 17 | |
dfcdd9c2 LC |
18 | Contributors are not required to use their legal name in patches and |
19 | on-line communication; they can use any name or pseudonym of their | |
20 | choice. | |
21 | ||
8c01b9d0 ML |
22 | @menu |
23 | * Building from Git:: The latest and greatest. | |
24 | * Running Guix Before It Is Installed:: Hacker tricks. | |
25 | * The Perfect Setup:: The right tools. | |
afe7408e | 26 | * Packaging Guidelines:: Growing the distribution. |
8c01b9d0 ML |
27 | * Coding Style:: Hygiene of the contributor. |
28 | * Submitting Patches:: Share your work. | |
3c86372e | 29 | * Tracking Bugs and Patches:: Keeping it all organized. |
2d315cd4 | 30 | * Commit Access:: Pushing to the official repository. |
5800d2aa | 31 | * Updating the Guix Package:: Updating the Guix package definition. |
1897a6ef | 32 | * Translating Guix:: Make Guix speak your native language. |
8c01b9d0 ML |
33 | @end menu |
34 | ||
35 | @node Building from Git | |
36 | @section Building from Git | |
37 | ||
38 | If you want to hack Guix itself, it is recommended to use the latest | |
dbfcadfc LC |
39 | version from the Git repository: |
40 | ||
41 | @example | |
42 | git clone https://git.savannah.gnu.org/git/guix.git | |
43 | @end example | |
44 | ||
b3011dbb LC |
45 | @cindex authentication, of a Guix checkout |
46 | How do you ensure that you obtained a genuine copy of the repository? | |
3e9c6ee1 | 47 | To do that, run @command{guix git authenticate}, passing it the commit |
63c799c1 LC |
48 | and OpenPGP fingerprint of the @dfn{channel introduction} |
49 | (@pxref{Invoking guix git authenticate}): | |
b3011dbb | 50 | |
63c799c1 LC |
51 | @c The commit and fingerprint below must match those of the channel |
52 | @c introduction in '%default-channels'. | |
b3011dbb | 53 | @example |
3e9c6ee1 | 54 | git fetch origin keyring:keyring |
63c799c1 LC |
55 | guix git authenticate 9edb3f66fd807b096b48283debdcddccfea34bad \ |
56 | "BBB0 2DDF 2CEA F6A8 0D1D E643 A2A0 6DF2 A33A 54FA" | |
b3011dbb LC |
57 | @end example |
58 | ||
59 | @noindent | |
63c799c1 LC |
60 | This command completes with exit code zero on success; it prints an |
61 | error message and exits with a non-zero code otherwise. | |
62 | ||
63 | As you can see, there is a chicken-and-egg problem: you first need to | |
64 | have Guix installed. Typically you would install Guix System | |
65 | (@pxref{System Installation}) or Guix on top of another distro | |
66 | (@pxref{Binary Installation}); in either case, you would verify the | |
67 | OpenPGP signature on the installation medium. This ``bootstraps'' the | |
68 | trust chain. | |
b3011dbb | 69 | |
5fb95cc5 LC |
70 | The easiest way to set up a development environment for Guix is, of |
71 | course, by using Guix! The following command starts a new shell where | |
72 | all the dependencies and appropriate environment variables are set up to | |
73 | hack on Guix: | |
8c01b9d0 | 74 | |
5fb95cc5 | 75 | @example |
80edb7df | 76 | guix shell -D guix --pure |
5fb95cc5 LC |
77 | @end example |
78 | ||
80edb7df | 79 | @xref{Invoking guix shell}, for more information on that command. |
0636742b FP |
80 | |
81 | If you are unable to use Guix when building Guix from a checkout, the | |
82 | following are the required packages in addition to those mentioned in the | |
83 | installation instructions (@pxref{Requirements}). | |
84 | ||
85 | @itemize | |
21656ffa VS |
86 | @item @url{https://gnu.org/software/autoconf/, GNU Autoconf}; |
87 | @item @url{https://gnu.org/software/automake/, GNU Automake}; | |
88 | @item @url{https://gnu.org/software/gettext/, GNU Gettext}; | |
89 | @item @url{https://gnu.org/software/texinfo/, GNU Texinfo}; | |
90 | @item @url{https://www.graphviz.org/, Graphviz}; | |
91 | @item @url{https://www.gnu.org/software/help2man/, GNU Help2man (optional)}. | |
0636742b FP |
92 | @end itemize |
93 | ||
94 | On Guix, extra dependencies can be added by instead running @command{guix | |
80edb7df | 95 | shell}: |
5fb95cc5 LC |
96 | |
97 | @example | |
80edb7df | 98 | guix shell -D guix help2man git strace --pure |
5fb95cc5 LC |
99 | @end example |
100 | ||
101 | Run @command{./bootstrap} to generate the build system infrastructure | |
102 | using Autoconf and Automake. If you get an error like this one: | |
8c01b9d0 ML |
103 | |
104 | @example | |
105 | configure.ac:46: error: possibly undefined macro: PKG_CHECK_MODULES | |
106 | @end example | |
107 | ||
5fb95cc5 | 108 | @noindent |
8c01b9d0 | 109 | it probably means that Autoconf couldn’t find @file{pkg.m4}, which is |
5fb95cc5 LC |
110 | provided by pkg-config. Make sure that @file{pkg.m4} is available. The |
111 | same holds for the @file{guile.m4} set of macros provided by Guile. For | |
112 | instance, if you installed Automake in @file{/usr/local}, it wouldn’t | |
113 | look for @file{.m4} files in @file{/usr/share}. In that case, you have | |
114 | to invoke the following command: | |
8c01b9d0 ML |
115 | |
116 | @example | |
117 | export ACLOCAL_PATH=/usr/share/aclocal | |
118 | @end example | |
119 | ||
aabe6d38 | 120 | @xref{Macro Search Path,,, automake, The GNU Automake Manual}, for |
8c01b9d0 ML |
121 | more information. |
122 | ||
fa67d6ee RS |
123 | Then, run @command{./configure --localstatedir=@var{directory}}, where |
124 | @var{directory} is the @code{localstatedir} value used by your current | |
125 | installation (@pxref{The Store}, for information about this), usually | |
126 | @file{/var}. Note that you will probably not run @command{make install} | |
127 | at the end (you don't have to) but it's still important to pass the | |
128 | right @code{localstatedir}. | |
8c01b9d0 | 129 | |
5b97804e LF |
130 | Finally, you have to invoke @code{make && make check} to build Guix and |
131 | run the tests (@pxref{Running the Test Suite}). If anything fails, take | |
132 | a look at installation instructions (@pxref{Installation}) or send a | |
133 | message to the @email{guix-devel@@gnu.org, mailing list}. | |
8c01b9d0 | 134 | |
33391ee5 LC |
135 | From there on, you can authenticate all the commits included in your |
136 | checkout by running: | |
137 | ||
138 | @example | |
139 | make authenticate | |
140 | @end example | |
141 | ||
142 | The first run takes a couple of minutes, but subsequent runs are faster. | |
143 | ||
ef6596a2 MÁAV |
144 | Or, when your configuration for your local Git repository doesn't match |
145 | the default one, you can provide the reference for the @code{keyring} | |
146 | branch through the variable @code{GUIX_GIT_KEYRING}. The following | |
147 | example assumes that you have a Git remote called @samp{myremote} | |
148 | pointing to the official repository: | |
149 | ||
150 | @example | |
151 | make authenticate GUIX_GIT_KEYRING=myremote/keyring | |
152 | @end example | |
153 | ||
33391ee5 LC |
154 | @quotation Note |
155 | You are advised to run @command{make authenticate} after every | |
156 | @command{git pull} invocation. This ensures you keep receiving valid | |
157 | changes to the repository. | |
158 | @end quotation | |
159 | ||
8c01b9d0 ML |
160 | |
161 | @node Running Guix Before It Is Installed | |
162 | @section Running Guix Before It Is Installed | |
163 | ||
164 | In order to keep a sane working environment, you will find it useful to | |
165 | test the changes made in your local source tree checkout without | |
166 | actually installing them. So that you can distinguish between your | |
167 | ``end-user'' hat and your ``motley'' costume. | |
168 | ||
169 | To that end, all the command-line tools can be used even if you have not | |
ad911c83 RL |
170 | run @code{make install}. To do that, you first need to have an |
171 | environment with all the dependencies available (@pxref{Building from | |
172 | Git}), and then simply prefix each command with @command{./pre-inst-env} | |
173 | (the @file{pre-inst-env} script lives in the top build tree of Guix; it | |
174 | is generated by running @command{./bootstrap} followed by | |
175 | @command{./configure}). As an example, here is how you would build the | |
176 | @code{hello} package as defined in your working tree (this assumes | |
177 | @command{guix-daemon} is already running on your system; it's OK if it's | |
178 | a different version): | |
8c01b9d0 ML |
179 | |
180 | @example | |
8c01b9d0 ML |
181 | $ ./pre-inst-env guix build hello |
182 | @end example | |
183 | ||
184 | @noindent | |
0636742b | 185 | Similarly, an example for a Guile session using the Guix modules: |
8c01b9d0 ML |
186 | |
187 | @example | |
188 | $ ./pre-inst-env guile -c '(use-modules (guix utils)) (pk (%current-system))' | |
96856613 LC |
189 | |
190 | ;;; ("x86_64-linux") | |
191 | @end example | |
192 | ||
193 | @noindent | |
194 | @cindex REPL | |
195 | @cindex read-eval-print loop | |
196 | @dots{} and for a REPL (@pxref{Using Guile Interactively,,, guile, Guile | |
197 | Reference Manual}): | |
198 | ||
199 | @example | |
200 | $ ./pre-inst-env guile | |
201 | scheme@@(guile-user)> ,use(guix) | |
202 | scheme@@(guile-user)> ,use(gnu) | |
203 | scheme@@(guile-user)> (define snakes | |
204 | (fold-packages | |
205 | (lambda (package lst) | |
206 | (if (string-prefix? "python" | |
207 | (package-name package)) | |
208 | (cons package lst) | |
209 | lst)) | |
210 | '())) | |
211 | scheme@@(guile-user)> (length snakes) | |
212 | $1 = 361 | |
8c01b9d0 ML |
213 | @end example |
214 | ||
9022861d LC |
215 | If you are hacking on the daemon and its supporting code or if |
216 | @command{guix-daemon} is not already running on your system, you can | |
217 | launch it straight from the build tree@footnote{The @option{-E} flag to | |
218 | @command{sudo} guarantees that @code{GUILE_LOAD_PATH} is correctly set | |
219 | such that @command{guix-daemon} and the tools it uses can find the Guile | |
220 | modules they need.}: | |
221 | ||
222 | @example | |
223 | $ sudo -E ./pre-inst-env guix-daemon --build-users-group=guixbuild | |
224 | @end example | |
225 | ||
8c01b9d0 ML |
226 | The @command{pre-inst-env} script sets up all the environment variables |
227 | necessary to support this, including @env{PATH} and @env{GUILE_LOAD_PATH}. | |
228 | ||
ef54b61d | 229 | Note that @command{./pre-inst-env guix pull} does @emph{not} upgrade the |
75e24d7b | 230 | local source tree; it simply updates the @file{~/.config/guix/current} |
ef54b61d | 231 | symlink (@pxref{Invoking guix pull}). Run @command{git pull} instead if |
75e24d7b | 232 | you want to upgrade your local source tree. |
ef54b61d | 233 | |
8c01b9d0 ML |
234 | |
235 | @node The Perfect Setup | |
236 | @section The Perfect Setup | |
237 | ||
238 | The Perfect Setup to hack on Guix is basically the perfect setup used | |
239 | for Guile hacking (@pxref{Using Guile in Emacs,,, guile, Guile Reference | |
240 | Manual}). First, you need more than an editor, you need | |
21656ffa VS |
241 | @url{https://www.gnu.org/software/emacs, Emacs}, empowered by the |
242 | wonderful @url{https://nongnu.org/geiser/, Geiser}. To set that up, run: | |
f73ab814 LC |
243 | |
244 | @example | |
bcdb8e98 | 245 | guix package -i emacs guile emacs-geiser emacs-geiser-guile |
f73ab814 | 246 | @end example |
8c01b9d0 ML |
247 | |
248 | Geiser allows for interactive and incremental development from within | |
249 | Emacs: code compilation and evaluation from within buffers, access to | |
250 | on-line documentation (docstrings), context-sensitive completion, | |
251 | @kbd{M-.} to jump to an object definition, a REPL to try out your code, | |
252 | and more (@pxref{Introduction,,, geiser, Geiser User Manual}). For | |
253 | convenient Guix development, make sure to augment Guile’s load path so | |
254 | that it finds source files from your checkout: | |
255 | ||
256 | @lisp | |
257 | ;; @r{Assuming the Guix checkout is in ~/src/guix.} | |
bb38ece4 AK |
258 | (with-eval-after-load 'geiser-guile |
259 | (add-to-list 'geiser-guile-load-path "~/src/guix")) | |
8c01b9d0 ML |
260 | @end lisp |
261 | ||
262 | To actually edit the code, Emacs already has a neat Scheme mode. But in | |
263 | addition to that, you must not miss | |
c2c73f58 | 264 | @url{https://www.emacswiki.org/emacs/ParEdit, Paredit}. It provides |
8c01b9d0 ML |
265 | facilities to directly operate on the syntax tree, such as raising an |
266 | s-expression or wrapping it, swallowing or rejecting the following | |
267 | s-expression, etc. | |
268 | ||
42cdcdff RW |
269 | @cindex code snippets |
270 | @cindex templates | |
271 | @cindex reducing boilerplate | |
272 | We also provide templates for common git commit messages and package | |
273 | definitions in the @file{etc/snippets} directory. These templates can | |
21656ffa | 274 | be used with @url{https://joaotavora.github.io/yasnippet/, YASnippet} to |
42cdcdff RW |
275 | expand short trigger strings to interactive text snippets. You may want |
276 | to add the snippets directory to the @var{yas-snippet-dirs} variable in | |
277 | Emacs. | |
278 | ||
279 | @lisp | |
280 | ;; @r{Assuming the Guix checkout is in ~/src/guix.} | |
281 | (with-eval-after-load 'yasnippet | |
282 | (add-to-list 'yas-snippet-dirs "~/src/guix/etc/snippets")) | |
283 | @end lisp | |
284 | ||
285 | The commit message snippets depend on @url{https://magit.vc/, Magit} to | |
286 | display staged files. When editing a commit message type @code{add} | |
287 | followed by @kbd{TAB} to insert a commit message template for adding a | |
288 | package; type @code{update} followed by @kbd{TAB} to insert a template | |
9286c295 AI |
289 | for updating a package; type @code{https} followed by @kbd{TAB} to |
290 | insert a template for changing the home page URI of a package to HTTPS. | |
42cdcdff RW |
291 | |
292 | The main snippet for @code{scheme-mode} is triggered by typing | |
293 | @code{package...} followed by @kbd{TAB}. This snippet also inserts the | |
294 | trigger string @code{origin...}, which can be expanded further. The | |
295 | @code{origin} snippet in turn may insert other trigger strings ending on | |
296 | @code{...}, which also can be expanded further. | |
297 | ||
9a397114 OP |
298 | @cindex insert or update copyright |
299 | @cindex @code{M-x guix-copyright} | |
300 | @cindex @code{M-x copyright-update} | |
4f4fb215 | 301 | We additionally provide insertion and automatic update of a copyright in |
9a397114 OP |
302 | @file{etc/copyright.el}. You may want to set your full name, mail, and |
303 | load a file. | |
304 | ||
305 | @lisp | |
306 | (setq user-full-name "Alice Doe") | |
307 | (setq user-mail-address "alice@@mail.org") | |
308 | ;; @r{Assuming the Guix checkout is in ~/src/guix.} | |
309 | (load-file "~/src/guix/etc/copyright.el") | |
310 | @end lisp | |
311 | ||
312 | To insert a copyright at the current line invoke @code{M-x guix-copyright}. | |
313 | ||
314 | To update a copyright you need to specify a @code{copyright-names-regexp}. | |
315 | ||
316 | @lisp | |
317 | (setq copyright-names-regexp | |
318 | (format "%s <%s>" user-full-name user-mail-address)) | |
319 | @end lisp | |
320 | ||
321 | You can check if your copyright is up to date by evaluating @code{M-x | |
322 | copyright-update}. If you want to do it automatically after each buffer | |
323 | save then add @code{(add-hook 'after-save-hook 'copyright-update)} in | |
324 | Emacs. | |
8c01b9d0 | 325 | |
afe7408e LC |
326 | @node Packaging Guidelines |
327 | @section Packaging Guidelines | |
328 | ||
329 | @cindex packages, creating | |
330 | The GNU distribution is nascent and may well lack some of your favorite | |
331 | packages. This section describes how you can help make the distribution | |
332 | grow. | |
333 | ||
334 | Free software packages are usually distributed in the form of | |
335 | @dfn{source code tarballs}---typically @file{tar.gz} files that contain | |
336 | all the source files. Adding a package to the distribution means | |
337 | essentially two things: adding a @dfn{recipe} that describes how to | |
338 | build the package, including a list of other packages required to build | |
339 | it, and adding @dfn{package metadata} along with that recipe, such as a | |
340 | description and licensing information. | |
341 | ||
342 | In Guix all this information is embodied in @dfn{package definitions}. | |
343 | Package definitions provide a high-level view of the package. They are | |
344 | written using the syntax of the Scheme programming language; in fact, | |
345 | for each package we define a variable bound to the package definition, | |
346 | and export that variable from a module (@pxref{Package Modules}). | |
347 | However, in-depth Scheme knowledge is @emph{not} a prerequisite for | |
348 | creating packages. For more information on package definitions, | |
349 | @pxref{Defining Packages}. | |
350 | ||
351 | Once a package definition is in place, stored in a file in the Guix | |
352 | source tree, it can be tested using the @command{guix build} command | |
353 | (@pxref{Invoking guix build}). For example, assuming the new package is | |
354 | called @code{gnew}, you may run this command from the Guix build tree | |
355 | (@pxref{Running Guix Before It Is Installed}): | |
356 | ||
357 | @example | |
358 | ./pre-inst-env guix build gnew --keep-failed | |
359 | @end example | |
360 | ||
361 | Using @code{--keep-failed} makes it easier to debug build failures since | |
362 | it provides access to the failed build tree. Another useful | |
363 | command-line option when debugging is @code{--log-file}, to access the | |
364 | build log. | |
365 | ||
366 | If the package is unknown to the @command{guix} command, it may be that | |
367 | the source file contains a syntax error, or lacks a @code{define-public} | |
368 | clause to export the package variable. To figure it out, you may load | |
369 | the module from Guile to get more information about the actual error: | |
370 | ||
371 | @example | |
372 | ./pre-inst-env guile -c '(use-modules (gnu packages gnew))' | |
373 | @end example | |
374 | ||
375 | Once your package builds correctly, please send us a patch | |
376 | (@pxref{Submitting Patches}). Well, if you need help, we will be happy to | |
377 | help you too. Once the patch is committed in the Guix repository, the | |
378 | new package automatically gets built on the supported platforms by | |
4985a427 | 379 | @url{https://@value{SUBSTITUTE-SERVER-1}, our continuous integration system}. |
afe7408e LC |
380 | |
381 | @cindex substituter | |
382 | Users can obtain the new package definition simply by running | |
383 | @command{guix pull} (@pxref{Invoking guix pull}). When | |
4985a427 | 384 | @code{@value{SUBSTITUTE-SERVER-1}} is done building the package, installing the |
afe7408e LC |
385 | package automatically downloads binaries from there |
386 | (@pxref{Substitutes}). The only place where human intervention is | |
387 | needed is to review and apply the patch. | |
388 | ||
389 | ||
390 | @menu | |
391 | * Software Freedom:: What may go into the distribution. | |
392 | * Package Naming:: What's in a name? | |
393 | * Version Numbers:: When the name is not enough. | |
394 | * Synopses and Descriptions:: Helping users find the right package. | |
71e746cc | 395 | * Snippets versus Phases:: Whether to use a snippet, or a build phase. |
15fba3b1 | 396 | * Emacs Packages:: Your Elisp fix. |
afe7408e LC |
397 | * Python Modules:: A touch of British comedy. |
398 | * Perl Modules:: Little pearls. | |
399 | * Java Packages:: Coffee break. | |
8d1b22b2 | 400 | * Rust Crates:: Beware of oxidation. |
afe7408e LC |
401 | * Fonts:: Fond of fonts. |
402 | @end menu | |
403 | ||
404 | @node Software Freedom | |
405 | @subsection Software Freedom | |
406 | ||
407 | @c Adapted from http://www.gnu.org/philosophy/philosophy.html. | |
408 | @cindex free software | |
409 | The GNU operating system has been developed so that users can have | |
410 | freedom in their computing. GNU is @dfn{free software}, meaning that | |
21656ffa | 411 | users have the @url{https://www.gnu.org/philosophy/free-sw.html,four |
afe7408e LC |
412 | essential freedoms}: to run the program, to study and change the program |
413 | in source code form, to redistribute exact copies, and to distribute | |
414 | modified versions. Packages found in the GNU distribution provide only | |
415 | software that conveys these four freedoms. | |
416 | ||
417 | In addition, the GNU distribution follow the | |
21656ffa | 418 | @url{https://www.gnu.org/distros/free-system-distribution-guidelines.html,free |
afe7408e LC |
419 | software distribution guidelines}. Among other things, these guidelines |
420 | reject non-free firmware, recommendations of non-free software, and | |
421 | discuss ways to deal with trademarks and patents. | |
422 | ||
423 | Some otherwise free upstream package sources contain a small and optional | |
424 | subset that violates the above guidelines, for instance because this subset | |
425 | is itself non-free code. When that happens, the offending items are removed | |
426 | with appropriate patches or code snippets in the @code{origin} form of the | |
427 | package (@pxref{Defining Packages}). This way, @code{guix | |
428 | build --source} returns the ``freed'' source rather than the unmodified | |
429 | upstream source. | |
430 | ||
431 | ||
432 | @node Package Naming | |
433 | @subsection Package Naming | |
434 | ||
435 | @cindex package name | |
1dfc08f7 | 436 | A package actually has two names associated with it. |
afe7408e LC |
437 | First, there is the name of the @emph{Scheme variable}, the one following |
438 | @code{define-public}. By this name, the package can be made known in the | |
439 | Scheme code, for instance as input to another package. Second, there is | |
440 | the string in the @code{name} field of a package definition. This name | |
441 | is used by package management commands such as | |
442 | @command{guix package} and @command{guix build}. | |
443 | ||
444 | Both are usually the same and correspond to the lowercase conversion of | |
445 | the project name chosen upstream, with underscores replaced with | |
446 | hyphens. For instance, GNUnet is available as @code{gnunet}, and | |
447 | SDL_net as @code{sdl-net}. | |
448 | ||
1b1a61f8 TGRBGG |
449 | A noteworthy exception to this rule is when the project name is only a |
450 | single character, or if an older maintained project with the same name | |
451 | already exists---regardless of whether it has already been packaged for | |
452 | Guix. Use common sense to make such names unambiguous and meaningful. | |
453 | For example, Guix's package for the shell called ``s'' upstream is | |
454 | @code{s-shell} and @emph{not} @code{s}. Feel free to ask your fellow | |
455 | hackers for inspiration. | |
456 | ||
afe7408e LC |
457 | We do not add @code{lib} prefixes for library packages, unless these are |
458 | already part of the official project name. But @pxref{Python | |
459 | Modules} and @ref{Perl Modules} for special rules concerning modules for | |
460 | the Python and Perl languages. | |
461 | ||
462 | Font package names are handled differently, @pxref{Fonts}. | |
463 | ||
464 | ||
465 | @node Version Numbers | |
466 | @subsection Version Numbers | |
467 | ||
468 | @cindex package version | |
469 | We usually package only the latest version of a given free software | |
470 | project. But sometimes, for instance for incompatible library versions, | |
471 | two (or more) versions of the same package are needed. These require | |
472 | different Scheme variable names. We use the name as defined | |
473 | in @ref{Package Naming} | |
474 | for the most recent version; previous versions use the same name, suffixed | |
475 | by @code{-} and the smallest prefix of the version number that may | |
476 | distinguish the two versions. | |
477 | ||
478 | The name inside the package definition is the same for all versions of a | |
479 | package and does not contain any version number. | |
480 | ||
481 | For instance, the versions 2.24.20 and 3.9.12 of GTK+ may be packaged as follows: | |
482 | ||
8ba31e8b | 483 | @lisp |
afe7408e LC |
484 | (define-public gtk+ |
485 | (package | |
486 | (name "gtk+") | |
487 | (version "3.9.12") | |
488 | ...)) | |
489 | (define-public gtk+-2 | |
490 | (package | |
491 | (name "gtk+") | |
492 | (version "2.24.20") | |
493 | ...)) | |
8ba31e8b | 494 | @end lisp |
afe7408e | 495 | If we also wanted GTK+ 3.8.2, this would be packaged as |
8ba31e8b | 496 | @lisp |
afe7408e LC |
497 | (define-public gtk+-3.8 |
498 | (package | |
499 | (name "gtk+") | |
500 | (version "3.8.2") | |
501 | ...)) | |
8ba31e8b | 502 | @end lisp |
afe7408e LC |
503 | |
504 | @c See <https://lists.gnu.org/archive/html/guix-devel/2016-01/msg00425.html>, | |
505 | @c for a discussion of what follows. | |
506 | @cindex version number, for VCS snapshots | |
507 | Occasionally, we package snapshots of upstream's version control system | |
508 | (VCS) instead of formal releases. This should remain exceptional, | |
509 | because it is up to upstream developers to clarify what the stable | |
510 | release is. Yet, it is sometimes necessary. So, what should we put in | |
511 | the @code{version} field? | |
512 | ||
513 | Clearly, we need to make the commit identifier of the VCS snapshot | |
514 | visible in the version string, but we also need to make sure that the | |
515 | version string is monotonically increasing so that @command{guix package | |
516 | --upgrade} can determine which version is newer. Since commit | |
517 | identifiers, notably with Git, are not monotonically increasing, we add | |
518 | a revision number that we increase each time we upgrade to a newer | |
519 | snapshot. The resulting version string looks like this: | |
520 | ||
521 | @example | |
522 | 2.0.11-3.cabba9e | |
523 | ^ ^ ^ | |
524 | | | `-- upstream commit ID | |
525 | | | | |
526 | | `--- Guix package revision | |
527 | | | |
528 | latest upstream version | |
529 | @end example | |
530 | ||
531 | It is a good idea to strip commit identifiers in the @code{version} | |
532 | field to, say, 7 digits. It avoids an aesthetic annoyance (assuming | |
533 | aesthetics have a role to play here) as well as problems related to OS | |
534 | limits such as the maximum shebang length (127 bytes for the Linux | |
b8baebae XC |
535 | kernel). There are helper functions for doing this for packages using |
536 | @code{git-fetch} or @code{hg-fetch} (see below). It is best to use the | |
537 | full commit identifiers in @code{origin}s, though, to avoid ambiguities. | |
538 | A typical package definition may look like this: | |
539 | ||
afe7408e | 540 | |
8ba31e8b | 541 | @lisp |
afe7408e LC |
542 | (define my-package |
543 | (let ((commit "c3f29bc928d5900971f65965feaae59e1272a3f7") | |
544 | (revision "1")) ;Guix package revision | |
545 | (package | |
546 | (version (git-version "0.9" revision commit)) | |
547 | (source (origin | |
548 | (method git-fetch) | |
549 | (uri (git-reference | |
550 | (url "git://example.org/my-package.git") | |
551 | (commit commit))) | |
552 | (sha256 (base32 "1mbikn@dots{}")) | |
553 | (file-name (git-file-name name version)))) | |
554 | ;; @dots{} | |
555 | ))) | |
8ba31e8b | 556 | @end lisp |
afe7408e | 557 | |
b8baebae XC |
558 | @deffn {Scheme Procedure} git-version @var{VERSION} @var{REVISION} @var{COMMIT} |
559 | Return the version string for packages using @code{git-fetch}. | |
560 | ||
561 | @lisp | |
562 | (git-version "0.2.3" "0" "93818c936ee7e2f1ba1b315578bde363a7d43d05") | |
563 | @result{} "0.2.3-0.93818c9" | |
564 | @end lisp | |
565 | @end deffn | |
566 | ||
567 | @deffn {Scheme Procedure} hg-version @var{VERSION} @var{REVISION} @var{CHANGESET} | |
568 | Return the version string for packages using @code{hg-fetch}. It works | |
569 | in the same way as @code{git-version}. | |
570 | @end deffn | |
571 | ||
afe7408e LC |
572 | @node Synopses and Descriptions |
573 | @subsection Synopses and Descriptions | |
574 | ||
575 | @cindex package description | |
576 | @cindex package synopsis | |
577 | As we have seen before, each package in GNU@tie{}Guix includes a | |
578 | synopsis and a description (@pxref{Defining Packages}). Synopses and | |
579 | descriptions are important: They are what @command{guix package | |
580 | --search} searches, and a crucial piece of information to help users | |
581 | determine whether a given package suits their needs. Consequently, | |
582 | packagers should pay attention to what goes into them. | |
583 | ||
584 | Synopses must start with a capital letter and must not end with a | |
585 | period. They must not start with ``a'' or ``the'', which usually does | |
586 | not bring anything; for instance, prefer ``File-frobbing tool'' over ``A | |
587 | tool that frobs files''. The synopsis should say what the package | |
588 | is---e.g., ``Core GNU utilities (file, text, shell)''---or what it is | |
589 | used for---e.g., the synopsis for GNU@tie{}grep is ``Print lines | |
590 | matching a pattern''. | |
591 | ||
592 | Keep in mind that the synopsis must be meaningful for a very wide | |
593 | audience. For example, ``Manipulate alignments in the SAM format'' | |
594 | might make sense for a seasoned bioinformatics researcher, but might be | |
595 | fairly unhelpful or even misleading to a non-specialized audience. It | |
596 | is a good idea to come up with a synopsis that gives an idea of the | |
597 | application domain of the package. In this example, this might give | |
598 | something like ``Manipulate nucleotide sequence alignments'', which | |
599 | hopefully gives the user a better idea of whether this is what they are | |
600 | looking for. | |
601 | ||
602 | Descriptions should take between five and ten lines. Use full | |
603 | sentences, and avoid using acronyms without first introducing them. | |
604 | Please avoid marketing phrases such as ``world-leading'', | |
605 | ``industrial-strength'', and ``next-generation'', and avoid superlatives | |
606 | like ``the most advanced''---they are not helpful to users looking for a | |
607 | package and may even sound suspicious. Instead, try to be factual, | |
608 | mentioning use cases and features. | |
609 | ||
610 | @cindex Texinfo markup, in package descriptions | |
611 | Descriptions can include Texinfo markup, which is useful to introduce | |
612 | ornaments such as @code{@@code} or @code{@@dfn}, bullet lists, or | |
613 | hyperlinks (@pxref{Overview,,, texinfo, GNU Texinfo}). However you | |
614 | should be careful when using some characters for example @samp{@@} and | |
615 | curly braces which are the basic special characters in Texinfo | |
616 | (@pxref{Special Characters,,, texinfo, GNU Texinfo}). User interfaces | |
617 | such as @command{guix package --show} take care of rendering it | |
618 | appropriately. | |
619 | ||
620 | Synopses and descriptions are translated by volunteers | |
2a9784ff JL |
621 | @uref{https://translate.fedoraproject.org/projects/guix/packages, at |
622 | Weblate} so that as many users as possible can read them in | |
afe7408e LC |
623 | their native language. User interfaces search them and display them in |
624 | the language specified by the current locale. | |
625 | ||
626 | To allow @command{xgettext} to extract them as translatable strings, | |
627 | synopses and descriptions @emph{must be literal strings}. This means | |
628 | that you cannot use @code{string-append} or @code{format} to construct | |
629 | these strings: | |
630 | ||
631 | @lisp | |
632 | (package | |
633 | ;; @dots{} | |
634 | (synopsis "This is translatable") | |
635 | (description (string-append "This is " "*not*" " translatable."))) | |
636 | @end lisp | |
637 | ||
638 | Translation is a lot of work so, as a packager, please pay even more | |
639 | attention to your synopses and descriptions as every change may entail | |
640 | additional work for translators. In order to help them, it is possible | |
641 | to make recommendations or instructions visible to them by inserting | |
642 | special comments like this (@pxref{xgettext Invocation,,, gettext, GNU | |
643 | Gettext}): | |
644 | ||
93c25181 | 645 | @lisp |
afe7408e LC |
646 | ;; TRANSLATORS: "X11 resize-and-rotate" should not be translated. |
647 | (description "ARandR is designed to provide a simple visual front end | |
648 | for the X11 resize-and-rotate (RandR) extension. @dots{}") | |
93c25181 | 649 | @end lisp |
afe7408e | 650 | |
71e746cc MC |
651 | @node Snippets versus Phases |
652 | @subsection Snippets versus Phases | |
653 | ||
654 | @cindex snippets, when to use | |
655 | The boundary between using an origin snippet versus a build phase to | |
656 | modify the sources of a package can be elusive. Origin snippets are | |
657 | typically used to remove unwanted files such as bundled libraries, | |
658 | nonfree sources, or to apply simple substitutions. The source derived | |
659 | from an origin should produce a source that can be used to build the | |
660 | package on any system that the upstream package supports (i.e., act as | |
661 | the corresponding source). In particular, origin snippets must not | |
662 | embed store items in the sources; such patching should rather be done | |
663 | using build phases. Refer to the @code{origin} record documentation for | |
664 | more information (@pxref{origin Reference}). | |
afe7408e | 665 | |
15fba3b1 MC |
666 | @node Emacs Packages |
667 | @subsection Emacs Packages | |
668 | ||
669 | @cindex emacs, packaging | |
670 | @cindex elisp, packaging | |
671 | Emacs packages should preferably use the Emacs build system | |
672 | (@pxref{emacs-build-system}), for uniformity and the benefits provided | |
673 | by its build phases, such as the auto-generation of the autoloads file | |
eea7cc31 | 674 | and the byte compilation of the sources. Because there is no |
15fba3b1 MC |
675 | standardized way to run a test suite for Emacs packages, tests are |
676 | disabled by default. When a test suite is available, it should be | |
eea7cc31 | 677 | enabled by setting the @code{#:tests?} argument to @code{#true}. By |
15fba3b1 MC |
678 | default, the command to run the test is @command{make check}, but any |
679 | command can be specified via the @code{#:test-command} argument. The | |
680 | @code{#:test-command} argument expects a list containing a command and | |
eea7cc31 | 681 | its arguments, to be invoked during the @code{check} phase. |
15fba3b1 MC |
682 | |
683 | The Elisp dependencies of Emacs packages are typically provided as | |
684 | @code{propagated-inputs} when required at run time. As for other | |
685 | packages, build or test dependencies should be specified as | |
686 | @code{native-inputs}. | |
687 | ||
688 | Emacs packages sometimes depend on resources directories that should be | |
689 | installed along the Elisp files. The @code{#:include} argument can be | |
690 | used for that purpose, by specifying a list of regexps to match. The | |
691 | best practice when using the @code{#:include} argument is to extend | |
692 | rather than override its default value (accessible via the | |
693 | @code{%default-include} variable). As an example, a yasnippet extension | |
694 | package typically include a @file{snippets} directory, which could be | |
695 | copied to the installation directory using: | |
696 | ||
697 | @lisp | |
2c469f04 | 698 | #:include (cons "^snippets/" %default-include) |
15fba3b1 MC |
699 | @end lisp |
700 | ||
701 | When encountering problems, it is wise to check for the presence of the | |
702 | @code{Package-Requires} extension header in the package main source | |
703 | file, and whether any dependencies and their versions listed therein are | |
704 | satisfied. | |
705 | ||
afe7408e LC |
706 | @node Python Modules |
707 | @subsection Python Modules | |
708 | ||
709 | @cindex python | |
710 | We currently package Python 2 and Python 3, under the Scheme variable names | |
711 | @code{python-2} and @code{python} as explained in @ref{Version Numbers}. | |
712 | To avoid confusion and naming clashes with other programming languages, it | |
713 | seems desirable that the name of a package for a Python module contains | |
714 | the word @code{python}. | |
715 | ||
39356057 LF |
716 | Some modules are compatible with only one version of Python, others with |
717 | both. If the package Foo is compiled with Python 3, we name it | |
718 | @code{python-foo}. If it is compiled with Python 2, we name it | |
719 | @code{python2-foo}. Packages should be added when they are necessary; | |
720 | we don't add Python 2 variants of the package unless we are going to use | |
721 | them. | |
afe7408e LC |
722 | |
723 | If a project already contains the word @code{python}, we drop this; | |
724 | for instance, the module python-dateutil is packaged under the names | |
725 | @code{python-dateutil} and @code{python2-dateutil}. If the project name | |
726 | starts with @code{py} (e.g.@: @code{pytz}), we keep it and prefix it as | |
727 | described above. | |
728 | ||
729 | @subsubsection Specifying Dependencies | |
730 | @cindex inputs, for Python packages | |
731 | ||
732 | Dependency information for Python packages is usually available in the | |
733 | package source tree, with varying degrees of accuracy: in the | |
734 | @file{setup.py} file, in @file{requirements.txt}, or in @file{tox.ini}. | |
735 | ||
736 | Your mission, when writing a recipe for a Python package, is to map | |
737 | these dependencies to the appropriate type of ``input'' (@pxref{package | |
738 | Reference, inputs}). Although the @code{pypi} importer normally does a | |
739 | good job (@pxref{Invoking guix import}), you may want to check the | |
740 | following check list to determine which dependency goes where. | |
741 | ||
742 | @itemize | |
743 | ||
744 | @item | |
745 | We currently package Python 2 with @code{setuptools} and @code{pip} | |
746 | installed like Python 3.4 has per default. Thus you don't need to | |
747 | specify either of these as an input. @command{guix lint} will warn you | |
748 | if you do. | |
749 | ||
750 | @item | |
751 | Python dependencies required at run time go into | |
752 | @code{propagated-inputs}. They are typically defined with the | |
753 | @code{install_requires} keyword in @file{setup.py}, or in the | |
754 | @file{requirements.txt} file. | |
755 | ||
756 | @item | |
757 | Python packages required only at build time---e.g., those listed with | |
758 | the @code{setup_requires} keyword in @file{setup.py}---or only for | |
759 | testing---e.g., those in @code{tests_require}---go into | |
760 | @code{native-inputs}. The rationale is that (1) they do not need to be | |
761 | propagated because they are not needed at run time, and (2) in a | |
762 | cross-compilation context, it's the ``native'' input that we'd want. | |
763 | ||
764 | Examples are the @code{pytest}, @code{mock}, and @code{nose} test | |
765 | frameworks. Of course if any of these packages is also required at | |
766 | run-time, it needs to go to @code{propagated-inputs}. | |
767 | ||
768 | @item | |
769 | Anything that does not fall in the previous categories goes to | |
770 | @code{inputs}, for example programs or C libraries required for building | |
771 | Python packages containing C extensions. | |
772 | ||
773 | @item | |
774 | If a Python package has optional dependencies (@code{extras_require}), | |
775 | it is up to you to decide whether to add them or not, based on their | |
776 | usefulness/overhead ratio (@pxref{Submitting Patches, @command{guix | |
777 | size}}). | |
778 | ||
779 | @end itemize | |
780 | ||
781 | ||
782 | @node Perl Modules | |
783 | @subsection Perl Modules | |
784 | ||
785 | @cindex perl | |
786 | Perl programs standing for themselves are named as any other package, | |
787 | using the lowercase upstream name. | |
788 | For Perl packages containing a single class, we use the lowercase class name, | |
789 | replace all occurrences of @code{::} by dashes and prepend the prefix | |
790 | @code{perl-}. | |
791 | So the class @code{XML::Parser} becomes @code{perl-xml-parser}. | |
792 | Modules containing several classes keep their lowercase upstream name and | |
793 | are also prepended by @code{perl-}. Such modules tend to have the word | |
794 | @code{perl} somewhere in their name, which gets dropped in favor of the | |
795 | prefix. For instance, @code{libwww-perl} becomes @code{perl-libwww}. | |
796 | ||
797 | ||
798 | @node Java Packages | |
799 | @subsection Java Packages | |
800 | ||
801 | @cindex java | |
802 | Java programs standing for themselves are named as any other package, | |
803 | using the lowercase upstream name. | |
804 | ||
805 | To avoid confusion and naming clashes with other programming languages, | |
806 | it is desirable that the name of a package for a Java package is | |
807 | prefixed with @code{java-}. If a project already contains the word | |
808 | @code{java}, we drop this; for instance, the package @code{ngsjava} is | |
809 | packaged under the name @code{java-ngs}. | |
810 | ||
811 | For Java packages containing a single class or a small class hierarchy, | |
812 | we use the lowercase class name, replace all occurrences of @code{.} by | |
813 | dashes and prepend the prefix @code{java-}. So the class | |
814 | @code{apache.commons.cli} becomes package | |
815 | @code{java-apache-commons-cli}. | |
816 | ||
817 | ||
8d1b22b2 EF |
818 | @node Rust Crates |
819 | @subsection Rust Crates | |
820 | ||
821 | @cindex rust | |
822 | Rust programs standing for themselves are named as any other package, using the | |
823 | lowercase upstream name. | |
824 | ||
825 | To prevent namespace collisions we prefix all other Rust packages with the | |
826 | @code{rust-} prefix. The name should be changed to lowercase as appropriate and | |
827 | dashes should remain in place. | |
828 | ||
829 | In the rust ecosystem it is common for multiple incompatible versions of a | |
784048c2 HG |
830 | package to be used at any given time, so all package definitions should have a |
831 | versioned suffix. The versioned suffix is the left-most non-zero digit (and | |
832 | any leading zeros, of course). This follows the ``caret'' version scheme | |
833 | intended by Cargo. Examples@: @code{rust-clap-2}, @code{rust-rand-0.6}. | |
8d1b22b2 EF |
834 | |
835 | Because of the difficulty in reusing rust packages as pre-compiled inputs for | |
836 | other packages the Cargo build system (@pxref{Build Systems, | |
837 | @code{cargo-build-system}}) presents the @code{#:cargo-inputs} and | |
838 | @code{cargo-development-inputs} keywords as build system arguments. It would be | |
839 | helpful to think of these as similar to @code{propagated-inputs} and | |
840 | @code{native-inputs}. Rust @code{dependencies} and @code{build-dependencies} | |
841 | should go in @code{#:cargo-inputs}, and @code{dev-dependencies} should go in | |
842 | @code{#:cargo-development-inputs}. If a Rust package links to other libraries | |
843 | then the standard placement in @code{inputs} and the like should be used. | |
844 | ||
845 | Care should be taken to ensure the correct version of dependencies are used; to | |
846 | this end we try to refrain from skipping the tests or using @code{#:skip-build?} | |
847 | when possible. Of course this is not always possible, as the package may be | |
848 | developed for a different Operating System, depend on features from the Nightly | |
849 | Rust compiler, or the test suite may have atrophied since it was released. | |
850 | ||
851 | ||
afe7408e LC |
852 | @node Fonts |
853 | @subsection Fonts | |
854 | ||
855 | @cindex fonts | |
856 | For fonts that are in general not installed by a user for typesetting | |
857 | purposes, or that are distributed as part of a larger software package, | |
858 | we rely on the general packaging rules for software; for instance, this | |
859 | applies to the fonts delivered as part of the X.Org system or fonts that | |
860 | are part of TeX Live. | |
861 | ||
862 | To make it easier for a user to search for fonts, names for other packages | |
863 | containing only fonts are constructed as follows, independently of the | |
864 | upstream package name. | |
865 | ||
866 | The name of a package containing only one font family starts with | |
867 | @code{font-}; it is followed by the foundry name and a dash @code{-} | |
868 | if the foundry is known, and the font family name, in which spaces are | |
869 | replaced by dashes (and as usual, all upper case letters are transformed | |
870 | to lower case). | |
871 | For example, the Gentium font family by SIL is packaged under the name | |
872 | @code{font-sil-gentium}. | |
873 | ||
874 | For a package containing several font families, the name of the collection | |
875 | is used in the place of the font family name. | |
876 | For instance, the Liberation fonts consist of three families, | |
877 | Liberation Sans, Liberation Serif and Liberation Mono. | |
878 | These could be packaged separately under the names | |
879 | @code{font-liberation-sans} and so on; but as they are distributed together | |
880 | under a common name, we prefer to package them together as | |
881 | @code{font-liberation}. | |
882 | ||
883 | In the case where several formats of the same font family or font collection | |
884 | are packaged separately, a short form of the format, prepended by a dash, | |
885 | is added to the package name. We use @code{-ttf} for TrueType fonts, | |
886 | @code{-otf} for OpenType fonts and @code{-type1} for PostScript Type 1 | |
887 | fonts. | |
888 | ||
889 | ||
8c01b9d0 ML |
890 | @node Coding Style |
891 | @section Coding Style | |
892 | ||
893 | In general our code follows the GNU Coding Standards (@pxref{Top,,, | |
894 | standards, GNU Coding Standards}). However, they do not say much about | |
895 | Scheme, so here are some additional rules. | |
896 | ||
897 | @menu | |
898 | * Programming Paradigm:: How to compose your elements. | |
899 | * Modules:: Where to store your code? | |
900 | * Data Types and Pattern Matching:: Implementing data structures. | |
901 | * Formatting Code:: Writing conventions. | |
902 | @end menu | |
903 | ||
904 | @node Programming Paradigm | |
905 | @subsection Programming Paradigm | |
906 | ||
907 | Scheme code in Guix is written in a purely functional style. One | |
908 | exception is code that involves input/output, and procedures that | |
909 | implement low-level concepts, such as the @code{memoize} procedure. | |
910 | ||
911 | @node Modules | |
912 | @subsection Modules | |
913 | ||
914 | Guile modules that are meant to be used on the builder side must live in | |
915 | the @code{(guix build @dots{})} name space. They must not refer to | |
916 | other Guix or GNU modules. However, it is OK for a ``host-side'' module | |
917 | to use a build-side module. | |
918 | ||
919 | Modules that deal with the broader GNU system should be in the | |
920 | @code{(gnu @dots{})} name space rather than @code{(guix @dots{})}. | |
921 | ||
922 | @node Data Types and Pattern Matching | |
923 | @subsection Data Types and Pattern Matching | |
924 | ||
925 | The tendency in classical Lisp is to use lists to represent everything, | |
926 | and then to browse them ``by hand'' using @code{car}, @code{cdr}, | |
927 | @code{cadr}, and co. There are several problems with that style, | |
928 | notably the fact that it is hard to read, error-prone, and a hindrance | |
929 | to proper type error reports. | |
930 | ||
931 | Guix code should define appropriate data types (for instance, using | |
932 | @code{define-record-type*}) rather than abuse lists. In addition, it | |
933 | should use pattern matching, via Guile’s @code{(ice-9 match)} module, | |
f06f569a LC |
934 | especially when matching lists (@pxref{Pattern Matching,,, guile, GNU |
935 | Guile Reference Manual}). | |
8c01b9d0 ML |
936 | |
937 | @node Formatting Code | |
938 | @subsection Formatting Code | |
939 | ||
7bb2b10c LC |
940 | @cindex formatting code |
941 | @cindex coding style | |
8c01b9d0 ML |
942 | When writing Scheme code, we follow common wisdom among Scheme |
943 | programmers. In general, we follow the | |
21656ffa | 944 | @url{https://mumble.net/~campbell/scheme/style.txt, Riastradh's Lisp |
8c01b9d0 ML |
945 | Style Rules}. This document happens to describe the conventions mostly |
946 | used in Guile’s code too. It is very thoughtful and well written, so | |
947 | please do read it. | |
948 | ||
949 | Some special forms introduced in Guix, such as the @code{substitute*} | |
950 | macro, have special indentation rules. These are defined in the | |
8ca0c88a AK |
951 | @file{.dir-locals.el} file, which Emacs automatically uses. Also note |
952 | that Emacs-Guix provides @code{guix-devel-mode} mode that indents and | |
953 | highlights Guix code properly (@pxref{Development,,, emacs-guix, The | |
954 | Emacs-Guix Reference Manual}). | |
7bb2b10c LC |
955 | |
956 | @cindex indentation, of code | |
957 | @cindex formatting, of code | |
958 | If you do not use Emacs, please make sure to let your editor knows these | |
959 | rules. To automatically indent a package definition, you can also run: | |
960 | ||
961 | @example | |
c4fe13c2 | 962 | ./pre-inst-env guix style @var{package} |
7bb2b10c LC |
963 | @end example |
964 | ||
965 | @noindent | |
c4fe13c2 | 966 | @xref{Invoking guix style}, for more information. |
8c01b9d0 | 967 | |
60912a88 LC |
968 | @cindex Vim, Scheme code editing |
969 | If you are editing code with Vim, we recommend that you run @code{:set | |
970 | autoindent} so that your code is automatically indented as you type. | |
971 | Additionally, | |
972 | @uref{https://www.vim.org/scripts/script.php?script_id=3998, | |
973 | @code{paredit.vim}} may help you deal with all these parentheses. | |
974 | ||
8c01b9d0 ML |
975 | We require all top-level procedures to carry a docstring. This |
976 | requirement can be relaxed for simple private procedures in the | |
977 | @code{(guix build @dots{})} name space, though. | |
978 | ||
979 | Procedures should not have more than four positional parameters. Use | |
980 | keyword parameters for procedures that take more than four parameters. | |
981 | ||
982 | ||
983 | @node Submitting Patches | |
984 | @section Submitting Patches | |
985 | ||
986 | Development is done using the Git distributed version control system. | |
987 | Thus, access to the repository is not strictly necessary. We welcome | |
988 | contributions in the form of patches as produced by @code{git | |
9fc8ae41 SM |
989 | format-patch} sent to the @email{guix-patches@@gnu.org} mailing list |
990 | (@pxref{submitting patches,, Submitting patches to a project, git, Git | |
991 | User Manual}). Contributors are encouraged to take a moment to set some | |
992 | Git repository options (@pxref{Configuring Git}) first, which can | |
993 | improve the readability of patches. Seasoned Guix developers may also | |
994 | want to look at the section on commit access (@pxref{Commit Access}). | |
230efa87 | 995 | |
a7bde77d LC |
996 | This mailing list is backed by a Debbugs instance, which allows us to |
997 | keep track of submissions (@pxref{Tracking Bugs and Patches}). Each | |
998 | message sent to that mailing list gets a new tracking number assigned; | |
999 | people can then follow up on the submission by sending email to | |
1000 | @code{@var{NNN}@@debbugs.gnu.org}, where @var{NNN} is the tracking | |
1001 | number (@pxref{Sending a Patch Series}). | |
230efa87 | 1002 | |
8c01b9d0 ML |
1003 | Please write commit logs in the ChangeLog format (@pxref{Change Logs,,, |
1004 | standards, GNU Coding Standards}); you can check the commit history for | |
1005 | examples. | |
1006 | ||
1007 | Before submitting a patch that adds or modifies a package definition, | |
fcc58db6 LC |
1008 | please run through this check list: |
1009 | ||
1010 | @enumerate | |
d18b787d | 1011 | @cindex @code{git format-patch} |
1012 | @cindex @code{git-format-patch} | |
1013 | @item | |
f697fc26 LF |
1014 | When generating your patches with @code{git format-patch} or @code{git |
1015 | send-email}, we recommend using the option @code{--base=}, perhaps with | |
1016 | the value @code{auto}. This option adds a note to the patch stating | |
1017 | which commit the patch is based on. This helps reviewers understand how | |
1018 | to apply and review your patches. | |
d18b787d | 1019 | |
308c08d3 RW |
1020 | @item |
1021 | If the authors of the packaged software provide a cryptographic | |
1022 | signature for the release tarball, make an effort to verify the | |
1023 | authenticity of the archive. For a detached GPG signature file this | |
1024 | would be done with the @code{gpg --verify} command. | |
1025 | ||
cbd02397 LC |
1026 | @item |
1027 | Take some time to provide an adequate synopsis and description for the | |
1028 | package. @xref{Synopses and Descriptions}, for some guidelines. | |
1029 | ||
fcc58db6 LC |
1030 | @item |
1031 | Run @code{guix lint @var{package}}, where @var{package} is the | |
8c01b9d0 | 1032 | name of the new or modified package, and fix any errors it reports |
fcc58db6 LC |
1033 | (@pxref{Invoking guix lint}). |
1034 | ||
c4fe13c2 LC |
1035 | @item |
1036 | Run @code{guix style @var{package}} to format the new package definition | |
1037 | according to the project's conventions (@pxref{Invoking guix style}). | |
1038 | ||
fcc58db6 LC |
1039 | @item |
1040 | Make sure the package builds on your platform, using @code{guix build | |
1041 | @var{package}}. | |
1042 | ||
89339a35 DM |
1043 | @item |
1044 | We recommend you also try building the package on other supported | |
1045 | platforms. As you may not have access to actual hardware platforms, we | |
1046 | recommend using the @code{qemu-binfmt-service-type} to emulate them. In | |
a9afff4b SR |
1047 | order to enable it, add the @code{virtualization} service module and the |
1048 | following service to the list of services in your @code{operating-system} | |
1049 | configuration: | |
89339a35 | 1050 | |
8ba31e8b | 1051 | @lisp |
89339a35 DM |
1052 | (service qemu-binfmt-service-type |
1053 | (qemu-binfmt-configuration | |
a9afff4b | 1054 | (platforms (lookup-qemu-platforms "arm" "aarch64")))) |
8ba31e8b | 1055 | @end lisp |
89339a35 DM |
1056 | |
1057 | Then reconfigure your system. | |
1058 | ||
1059 | You can then build packages for different platforms by specifying the | |
1060 | @code{--system} option. For example, to build the "hello" package for | |
de393bd0 | 1061 | the armhf or aarch64 architectures, you would run the following |
b28e4e3c | 1062 | commands, respectively: |
89339a35 DM |
1063 | @example |
1064 | guix build --system=armhf-linux --rounds=2 hello | |
1065 | guix build --system=aarch64-linux --rounds=2 hello | |
89339a35 DM |
1066 | @end example |
1067 | ||
d222522e LC |
1068 | @item |
1069 | @cindex bundling | |
1070 | Make sure the package does not use bundled copies of software already | |
1071 | available as separate packages. | |
1072 | ||
1073 | Sometimes, packages include copies of the source code of their | |
1074 | dependencies as a convenience for users. However, as a distribution, we | |
1075 | want to make sure that such packages end up using the copy we already | |
1076 | have in the distribution, if there is one. This improves resource usage | |
1077 | (the dependency is built and stored only once), and allows the | |
1078 | distribution to make transverse changes such as applying security | |
1079 | updates for a given software package in a single place and have them | |
1080 | affect the whole system---something that bundled copies prevent. | |
1081 | ||
fcc58db6 LC |
1082 | @item |
1083 | Take a look at the profile reported by @command{guix size} | |
1084 | (@pxref{Invoking guix size}). This will allow you to notice references | |
1085 | to other packages unwillingly retained. It may also help determine | |
1086 | whether to split the package (@pxref{Packages with Multiple Outputs}), | |
024e358c | 1087 | and which optional dependencies should be used. In particular, avoid adding |
0afeb746 | 1088 | @code{texlive} as a dependency: because of its extreme size, use |
48cccf06 | 1089 | the @code{texlive-tiny} package or @code{texlive-union} procedure instead. |
fcc58db6 LC |
1090 | |
1091 | @item | |
f7331f06 | 1092 | For important changes, check that dependent packages (if applicable) are |
fcc58db6 | 1093 | not affected by the change; @code{guix refresh --list-dependent |
8c01b9d0 ML |
1094 | @var{package}} will help you do that (@pxref{Invoking guix refresh}). |
1095 | ||
916b5eba LC |
1096 | @c See <https://lists.gnu.org/archive/html/guix-devel/2016-10/msg00933.html>. |
1097 | @cindex branching strategy | |
1098 | @cindex rebuild scheduling strategy | |
1099 | Depending on the number of dependent packages and thus the amount of | |
1100 | rebuilding induced, commits go to different branches, along these lines: | |
1101 | ||
1102 | @table @asis | |
1103 | @item 300 dependent packages or less | |
1104 | @code{master} branch (non-disruptive changes). | |
1105 | ||
bb9a99e6 | 1106 | @item between 300 and 1,800 dependent packages |
916b5eba | 1107 | @code{staging} branch (non-disruptive changes). This branch is intended |
bb9a99e6 | 1108 | to be merged in @code{master} every 6 weeks or so. Topical changes |
916b5eba | 1109 | (e.g., an update of the GNOME stack) can instead go to a specific branch |
4de68873 LF |
1110 | (say, @code{gnome-updates}). This branch is not expected to be |
1111 | buildable or usable until late in its development process. | |
916b5eba | 1112 | |
bb9a99e6 | 1113 | @item more than 1,800 dependent packages |
916b5eba LC |
1114 | @code{core-updates} branch (may include major and potentially disruptive |
1115 | changes). This branch is intended to be merged in @code{master} every | |
4de68873 LF |
1116 | 6 months or so. This branch is not expected to be buildable or usable |
1117 | until late in its development process. | |
916b5eba LC |
1118 | @end table |
1119 | ||
4985a427 | 1120 | All these branches are @uref{https://@value{SUBSTITUTE-SERVER-1}, |
38ab778f | 1121 | tracked by our build farm} and merged into @code{master} once |
189b1543 LC |
1122 | everything has been successfully built. This allows us to fix issues |
1123 | before they hit users, and to reduce the window during which pre-built | |
1124 | binaries are not available. | |
1125 | ||
175bea0c | 1126 | When we decide to start building the @code{staging} or |
58853df8 LF |
1127 | @code{core-updates} branches, they will be forked and renamed with the |
1128 | suffix @code{-frozen}, at which time only bug fixes may be pushed to the | |
1129 | frozen branches. The @code{core-updates} and @code{staging} branches | |
1130 | will remain open to accept patches for the next cycle. Please ask on | |
1131 | the mailing list or IRC if unsure where to place a patch. | |
38ab778f MB |
1132 | @c TODO: It would be good with badges on the website that tracks these |
1133 | @c branches. Or maybe even a status page. | |
1134 | ||
d23c20f1 | 1135 | @item |
5b74fe06 LC |
1136 | @cindex determinism, of build processes |
1137 | @cindex reproducible builds, checking | |
d23c20f1 LC |
1138 | Check whether the package's build process is deterministic. This |
1139 | typically means checking whether an independent build of the package | |
1140 | yields the exact same result that you obtained, bit for bit. | |
1141 | ||
5b74fe06 LC |
1142 | A simple way to do that is by building the same package several times in |
1143 | a row on your machine (@pxref{Invoking guix build}): | |
1144 | ||
1145 | @example | |
1146 | guix build --rounds=2 my-package | |
1147 | @end example | |
1148 | ||
1149 | This is enough to catch a class of common non-determinism issues, such | |
1150 | as timestamps or randomly-generated output in the build result. | |
1151 | ||
1152 | Another option is to use @command{guix challenge} (@pxref{Invoking guix | |
1153 | challenge}). You may run it once the package has been committed and | |
4985a427 | 1154 | built by @code{@value{SUBSTITUTE-SERVER-1}} to check whether it obtains the same |
5b74fe06 LC |
1155 | result as you did. Better yet: Find another machine that can build it |
1156 | and run @command{guix publish}. Since the remote build machine is | |
1157 | likely different from yours, this can catch non-determinism issues | |
1158 | related to the hardware---e.g., use of different instruction set | |
1159 | extensions---or to the operating system kernel---e.g., reliance on | |
1160 | @code{uname} or @file{/proc} files. | |
d23c20f1 | 1161 | |
3c2d03a2 LC |
1162 | @item |
1163 | When writing documentation, please use gender-neutral wording when | |
1164 | referring to people, such as | |
1165 | @uref{https://en.wikipedia.org/wiki/Singular_they, singular | |
1166 | ``they''@comma{} ``their''@comma{} ``them''}, and so forth. | |
1167 | ||
3a78fab8 | 1168 | @item |
1169 | Verify that your patch contains only one set of related changes. | |
1170 | Bundling unrelated changes together makes reviewing harder and slower. | |
1171 | ||
1172 | Examples of unrelated changes include the addition of several packages, | |
1173 | or a package update along with fixes to that package. | |
1174 | ||
7bb2b10c | 1175 | @item |
c4fe13c2 LC |
1176 | Please follow our code formatting rules, possibly running |
1177 | @command{guix style} script to do that automatically for you | |
7bb2b10c LC |
1178 | (@pxref{Formatting Code}). |
1179 | ||
4feb589b PN |
1180 | @item |
1181 | When possible, use mirrors in the source URL (@pxref{Invoking guix download}). | |
1182 | Use reliable URLs, not generated ones. For instance, GitHub archives are not | |
1183 | necessarily identical from one generation to the next, so in this case it's | |
1184 | often better to clone the repository. Don't use the @command{name} field in | |
1185 | the URL: it is not very useful and if the name changes, the URL will probably | |
1186 | be wrong. | |
1187 | ||
bf99d7e0 | 1188 | @item |
da31e7d9 PN |
1189 | Check if Guix builds (@pxref{Building from Git}) and address the |
1190 | warnings, especially those about use of undefined symbols. | |
bf99d7e0 | 1191 | |
9fcf2820 PN |
1192 | @item |
1193 | Make sure your changes do not break Guix and simulate a @code{guix pull} with: | |
1194 | @example | |
1195 | guix pull --url=/path/to/your/checkout --profile=/tmp/guix.master | |
1196 | @end example | |
1197 | ||
fcc58db6 LC |
1198 | @end enumerate |
1199 | ||
a40424bd | 1200 | When posting a patch to the mailing list, use @samp{[PATCH] @dots{}} as |
a1891cbf BW |
1201 | a subject, if your patch is to be applied on a branch other than |
1202 | @code{master}, say @code{core-updates}, specify it in the subject like | |
1203 | @samp{[PATCH core-updates] @dots{}}. You may use your email client or | |
1204 | the @command{git send-email} command (@pxref{Sending a Patch Series}). | |
1205 | We prefer to get patches in plain text messages, either inline or as | |
1206 | MIME attachments. You are advised to pay attention if your email client | |
1207 | changes anything like line breaks or indentation which could potentially | |
1208 | break the patches. | |
5a183a1e | 1209 | |
c8d6fa77 FL |
1210 | Expect some delay when you submit your very first patch to |
1211 | @email{guix-patches@@gnu.org}. You have to wait until you get an | |
4b08aad5 | 1212 | acknowledgement with the assigned tracking number. Future acknowledgements |
c8d6fa77 FL |
1213 | should not be delayed. |
1214 | ||
4619b59c JN |
1215 | When a bug is resolved, please close the thread by sending an email to |
1216 | @email{@var{NNN}-done@@debbugs.gnu.org}. | |
1217 | ||
9fc8ae41 SM |
1218 | @node Configuring Git |
1219 | @subsection Configuring Git | |
1220 | @cindex git configuration | |
1221 | @cindex @code{git format-patch} | |
1222 | @cindex @code{git send-email} | |
1223 | ||
1224 | If you have not done so already, you may wish to set a name and email | |
1225 | that will be associated with your commits (@pxref{telling git your name, | |
1226 | , Telling Git your name, git, Git User Manual}). If you wish to use a | |
5fafb6e7 | 1227 | different name or email just for commits in this repository, you can |
9fc8ae41 SM |
1228 | use @command{git config --local}, or edit @file{.git/config} in the |
1229 | repository instead of @file{~/.gitconfig}. | |
1230 | ||
1231 | We provide some default settings in @file{etc/git/gitconfig} which | |
1232 | modify how patches are generated, making them easier to read and apply. | |
1233 | These settings can be applied by manually copying them to | |
1234 | @file{.git/config} in your checkout, or by telling Git to include the | |
1235 | whole file: | |
1236 | ||
1237 | @example | |
1238 | git config --local include.path ../etc/git/gitconfig | |
1239 | @end example | |
1240 | ||
1241 | From then on, any changes to @file{etc/git/gitconfig} would | |
1242 | automatically take effect. | |
1243 | ||
1244 | Since the first patch in a series must be sent separately | |
1245 | (@pxref{Sending a Patch Series}), it can also be helpful to tell | |
1246 | @command{git format-patch} to handle the e-mail threading instead of | |
1247 | @command{git send-email}: | |
1248 | ||
1249 | @example | |
1250 | git config --local format.thread shallow | |
1251 | git config --local sendemail.thread no | |
1252 | @end example | |
1253 | ||
5a183a1e JN |
1254 | @unnumberedsubsec Sending a Patch Series |
1255 | @anchor{Sending a Patch Series} | |
1256 | @cindex patch series | |
1257 | @cindex @code{git send-email} | |
5a183a1e JN |
1258 | |
1259 | When sending a patch series (e.g., using @code{git send-email}), please | |
1260 | first send one message to @email{guix-patches@@gnu.org}, and then send | |
1261 | subsequent patches to @email{@var{NNN}@@debbugs.gnu.org} to make sure | |
1262 | they are kept together. See | |
1263 | @uref{https://debbugs.gnu.org/Advanced.html, the Debbugs documentation} | |
fb8b99a5 AB |
1264 | for more information. You can install @command{git send-email} with |
1265 | @command{guix install git:send-email}. | |
5a183a1e | 1266 | @c Debbugs bug: https://debbugs.gnu.org/db/15/15361.html |
a7bde77d LC |
1267 | |
1268 | @node Tracking Bugs and Patches | |
1269 | @section Tracking Bugs and Patches | |
1270 | ||
3c86372e CM |
1271 | This section describes how the Guix project tracks its bug reports and |
1272 | patch submissions. | |
1273 | ||
1274 | @menu | |
1275 | * The Issue Tracker:: The official bug and patch tracker. | |
1276 | * Debbugs User Interfaces:: Ways to interact with Debbugs. | |
1277 | * Debbugs Usertags:: Tag reports with custom labels. | |
1278 | @end menu | |
1279 | ||
1280 | @node The Issue Tracker | |
1281 | @subsection The Issue Tracker | |
1282 | ||
a7bde77d LC |
1283 | @cindex bug reports, tracking |
1284 | @cindex patch submissions, tracking | |
1285 | @cindex issue tracking | |
1286 | @cindex Debbugs, issue tracking system | |
1287 | Bug reports and patch submissions are currently tracked using the | |
1288 | Debbugs instance at @uref{https://bugs.gnu.org}. Bug reports are filed | |
1289 | against the @code{guix} ``package'' (in Debbugs parlance), by sending | |
1290 | email to @email{bug-guix@@gnu.org}, while patch submissions are filed | |
1291 | against the @code{guix-patches} package by sending email to | |
1292 | @email{guix-patches@@gnu.org} (@pxref{Submitting Patches}). | |
1293 | ||
3c86372e CM |
1294 | @node Debbugs User Interfaces |
1295 | @subsection Debbugs User Interfaces | |
1296 | ||
a7bde77d LC |
1297 | A web interface (actually @emph{two} web interfaces!) are available to |
1298 | browse issues: | |
1299 | ||
1300 | @itemize | |
1301 | @item | |
cdea5265 LC |
1302 | @url{https://issues.guix.gnu.org} provides a pleasant |
1303 | interface@footnote{The web interface at | |
1304 | @url{https://issues.guix.gnu.org} is powered by Mumi, a nice piece of | |
1305 | software written in Guile, and you can help! See | |
1306 | @url{https://git.elephly.net/gitweb.cgi?p=software/mumi.git}.} to browse | |
1307 | bug reports and patches, and to participate in discussions; | |
1308 | @item | |
a7bde77d LC |
1309 | @url{https://bugs.gnu.org/guix} lists bug reports; |
1310 | @item | |
1311 | @url{https://bugs.gnu.org/guix-patches} lists patch submissions. | |
1312 | @end itemize | |
1313 | ||
cdea5265 LC |
1314 | To view discussions related to issue number @var{n}, go to |
1315 | @indicateurl{https://issues.guix.gnu.org/@var{n}} or | |
a7bde77d LC |
1316 | @indicateurl{https://bugs.gnu.org/@var{n}}. |
1317 | ||
1318 | If you use Emacs, you may find it more convenient to interact with | |
1319 | issues using @file{debbugs.el}, which you can install with: | |
1320 | ||
1321 | @example | |
1322 | guix install emacs-debbugs | |
1323 | @end example | |
1324 | ||
1325 | For example, to list all open issues on @code{guix-patches}, hit: | |
1326 | ||
1327 | @example | |
1328 | @kbd{C-u} @kbd{M-x} debbugs-gnu @kbd{RET} @kbd{RET} guix-patches @kbd{RET} n y | |
1329 | @end example | |
1330 | ||
1331 | @xref{Top,,, debbugs-ug, Debbugs User Guide}, for more information on | |
1332 | this nifty tool! | |
2d315cd4 | 1333 | |
3c86372e CM |
1334 | @node Debbugs Usertags |
1335 | @subsection Debbugs Usertags | |
1336 | ||
1337 | @cindex usertags, for debbugs | |
1338 | @cindex Debbugs usertags | |
1339 | Debbugs provides a feature called @dfn{usertags} that allows any user to | |
1340 | tag any bug with an arbitrary label. Bugs can be searched by usertag, | |
1341 | so this is a handy way to organize bugs@footnote{The list of usertags is | |
1342 | public information, and anyone can modify any user's list of usertags, | |
1343 | so keep that in mind if you choose to use this feature.}. | |
1344 | ||
1345 | For example, to view all the bug reports (or patches, in the case of | |
1346 | @code{guix-patches}) tagged with the usertag @code{powerpc64le-linux} | |
586136d1 CM |
1347 | for the user @code{guix}, open a URL like the following in a web |
1348 | browser: | |
1349 | @url{https://debbugs.gnu.org/cgi-bin/pkgreport.cgi?tag=powerpc64le-linux;users=guix}. | |
3c86372e CM |
1350 | |
1351 | For more information on how to use usertags, please refer to the | |
1352 | documentation for Debbugs or the documentation for whatever tool you use | |
1353 | to interact with Debbugs. | |
1354 | ||
1355 | In Guix, we are experimenting with usertags to keep track of | |
1356 | architecture-specific issues. To facilitate collaboration, all our | |
586136d1 CM |
1357 | usertags are associated with the single user @code{guix}. The following |
1358 | usertags currently exist for that user: | |
3c86372e CM |
1359 | |
1360 | @table @code | |
1361 | ||
1362 | @item powerpc64le-linux | |
1363 | The purpose of this usertag is to make it easy to find the issues that | |
1364 | matter most for the @code{powerpc64le-linux} system type. Please assign | |
1365 | this usertag to bugs or patches that affect @code{powerpc64le-linux} but | |
1366 | not other system types. In addition, you may use it to identify issues | |
1367 | that for some reason are particularly important for the | |
1368 | @code{powerpc64le-linux} system type, even if the issue affects other | |
1369 | system types, too. | |
1370 | ||
1371 | @item reproducibility | |
1372 | For issues related to reproducibility. For example, it would be | |
1373 | appropriate to assign this usertag to a bug report for a package that | |
1374 | fails to build reproducibly. | |
1375 | ||
1376 | @end table | |
1377 | ||
1378 | If you're a committer and you want to add a usertag, just start using it | |
586136d1 CM |
1379 | with the @code{guix} user. If the usertag proves useful to you, |
1380 | consider updating this section of the manual so that others will know | |
1381 | what your usertag means. | |
3c86372e | 1382 | |
2d315cd4 LC |
1383 | @node Commit Access |
1384 | @section Commit Access | |
1385 | ||
1386 | @cindex commit access, for developers | |
aaf4a009 LC |
1387 | Everyone can contribute to Guix without having commit access |
1388 | (@pxref{Submitting Patches}). However, for frequent contributors, | |
1389 | having write access to the repository can be convenient. Commit access | |
1390 | should not be thought of as a ``badge of honor'' but rather as a | |
1391 | responsibility a contributor is willing to take to help the project. | |
1392 | ||
1393 | The following sections explain how to get commit access, how to be ready | |
1394 | to push commits, and the policies and community expectations for commits | |
1395 | pushed upstream. | |
1396 | ||
1397 | @subsection Applying for Commit Access | |
1398 | ||
1399 | When you deem it necessary, consider applying for commit | |
ef09cb86 LC |
1400 | access by following these steps: |
1401 | ||
1402 | @enumerate | |
1403 | @item | |
1404 | Find three committers who would vouch for you. You can view the list of | |
1405 | committers at | |
1406 | @url{https://savannah.gnu.org/project/memberlist.php?group=guix}. Each | |
1407 | of them should email a statement to @email{guix-maintainers@@gnu.org} (a | |
1408 | private alias for the collective of maintainers), signed with their | |
1409 | OpenPGP key. | |
1410 | ||
1411 | Committers are expected to have had some interactions with you as a | |
1412 | contributor and to be able to judge whether you are sufficiently | |
1413 | familiar with the project's practices. It is @emph{not} a judgment on | |
1414 | the value of your work, so a refusal should rather be interpreted as | |
1415 | ``let's try again later''. | |
1416 | ||
1417 | @item | |
1418 | Send @email{guix-maintainers@@gnu.org} a message stating your intent, | |
1419 | listing the three committers who support your application, signed with | |
1420 | the OpenPGP key you will use to sign commits, and giving its fingerprint | |
1421 | (see below). See @uref{https://emailselfdefense.fsf.org/en/}, for an | |
1422 | introduction to public-key cryptography with GnuPG. | |
1423 | ||
4a84deda LC |
1424 | @c See <https://sha-mbles.github.io/>. |
1425 | Set up GnuPG such that it never uses the SHA1 hash algorithm for digital | |
1426 | signatures, which is known to be unsafe since 2019, for instance by | |
1427 | adding the following line to @file{~/.gnupg/gpg.conf} (@pxref{GPG | |
1428 | Esoteric Options,,, gnupg, The GNU Privacy Guard Manual}): | |
1429 | ||
1430 | @example | |
1431 | digest-algo sha512 | |
1432 | @end example | |
1433 | ||
ef09cb86 LC |
1434 | @item |
1435 | Maintainers ultimately decide whether to grant you commit access, | |
1436 | usually following your referrals' recommendation. | |
1437 | ||
1438 | @item | |
84133320 | 1439 | @cindex OpenPGP, signed commits |
ef09cb86 LC |
1440 | If and once you've been given access, please send a message to |
1441 | @email{guix-devel@@gnu.org} to say so, again signed with the OpenPGP key | |
1442 | you will use to sign commits (do that before pushing your first commit). | |
1443 | That way, everyone can notice and ensure you control that OpenPGP key. | |
1444 | ||
84133320 LC |
1445 | @quotation Important |
1446 | Before you can push for the first time, maintainers must: | |
1447 | ||
1448 | @enumerate | |
1449 | @item | |
1450 | add your OpenPGP key to the @code{keyring} branch; | |
1451 | @item | |
1452 | add your OpenPGP fingerprint to the @file{.guix-authorizations} file of | |
1453 | the branch(es) you will commit to. | |
1454 | @end enumerate | |
1455 | @end quotation | |
ef09cb86 LC |
1456 | |
1457 | @item | |
1458 | Make sure to read the rest of this section and... profit! | |
1459 | @end enumerate | |
1460 | ||
1461 | @quotation Note | |
1462 | Maintainers are happy to give commit access to people who have been | |
1463 | contributing for some time and have a track record---don't be shy and | |
1464 | don't underestimate your work! | |
1465 | ||
1466 | However, note that the project is working towards a more automated patch | |
1467 | review and merging system, which, as a consequence, may lead us to have | |
1468 | fewer people with commit access to the main repository. Stay tuned! | |
1469 | @end quotation | |
1470 | ||
2d315cd4 LC |
1471 | All commits that are pushed to the central repository on Savannah must |
1472 | be signed with an OpenPGP key, and the public key should be uploaded to | |
1473 | your user account on Savannah and to public key servers, such as | |
1474 | @code{keys.openpgp.org}. To configure Git to automatically sign | |
1475 | commits, run: | |
1476 | ||
1477 | @example | |
1478 | git config commit.gpgsign true | |
b5b9266e LC |
1479 | |
1480 | # Substitute the fingerprint of your public PGP key. | |
2d315cd4 LC |
1481 | git config user.signingkey CABBA6EA1DC0FF33 |
1482 | @end example | |
1483 | ||
1484 | You can prevent yourself from accidentally pushing unsigned commits to | |
b5b9266e | 1485 | Savannah by using the pre-push Git hook located at |
2d315cd4 LC |
1486 | @file{etc/git/pre-push}: |
1487 | ||
1488 | @example | |
1489 | cp etc/git/pre-push .git/hooks/pre-push | |
1490 | @end example | |
1491 | ||
aaf4a009 LC |
1492 | @subsection Commit Policy |
1493 | ||
1494 | If you get commit access, please make sure to follow | |
1495 | the policy below (discussions of the policy can take place on | |
1496 | @email{guix-devel@@gnu.org}). | |
1497 | ||
1498 | Non-trivial patches should always be posted to | |
1499 | @email{guix-patches@@gnu.org} (trivial patches include fixing typos, | |
1500 | etc.). This mailing list fills the patch-tracking database | |
1501 | (@pxref{Tracking Bugs and Patches}). | |
1502 | ||
1503 | For patches that just add a new package, and a simple one, it's OK to | |
1504 | commit, if you're confident (which means you successfully built it in a | |
1505 | chroot setup, and have done a reasonable copyright and license | |
1506 | auditing). Likewise for package upgrades, except upgrades that trigger | |
1507 | a lot of rebuilds (for example, upgrading GnuTLS or GLib). We have a | |
1508 | mailing list for commit notifications (@email{guix-commits@@gnu.org}), | |
1509 | so people can notice. Before pushing your changes, make sure to run | |
1510 | @code{git pull --rebase}. | |
1511 | ||
2d315cd4 LC |
1512 | When pushing a commit on behalf of somebody else, please add a |
1513 | @code{Signed-off-by} line at the end of the commit log message---e.g., | |
1514 | with @command{git am --signoff}. This improves tracking of who did | |
1515 | what. | |
1516 | ||
1ad5209d LC |
1517 | When adding channel news entries (@pxref{Channels, Writing Channel |
1518 | News}), make sure they are well-formed by running the following command | |
1519 | right before pushing: | |
1520 | ||
1521 | @example | |
1522 | make check-channel-news | |
1523 | @end example | |
1524 | ||
2d315cd4 LC |
1525 | For anything else, please post to @email{guix-patches@@gnu.org} and |
1526 | leave time for a review, without committing anything (@pxref{Submitting | |
1527 | Patches}). If you didn’t receive any reply after two weeks, and if | |
1528 | you're confident, it's OK to commit. | |
1529 | ||
1530 | That last part is subject to being adjusted, allowing individuals to commit | |
1531 | directly on non-controversial changes on parts they’re familiar with. | |
98ebcf1c | 1532 | |
d4751342 LC |
1533 | @subsection Addressing Issues |
1534 | ||
1535 | Peer review (@pxref{Submitting Patches}) and tools such as | |
1536 | @command{guix lint} (@pxref{Invoking guix lint}) and the test suite | |
1537 | (@pxref{Running the Test Suite}) should catch issues before they are | |
1538 | pushed. Yet, commits that ``break'' functionality might occasionally | |
1539 | go through. When that happens, there are two priorities: mitigating | |
1540 | the impact, and understanding what happened to reduce the chance of | |
1541 | similar incidents in the future. The responsibility for both these | |
1542 | things primarily lies with those involved, but like everything this is | |
1543 | a group effort. | |
1544 | ||
1545 | Some issues can directly affect all users---for instance because they | |
1546 | make @command{guix pull} fail or break core functionality, because they | |
1547 | break major packages (at build time or run time), or because they | |
1548 | introduce known security vulnerabilities. | |
1549 | ||
1550 | @cindex reverting commits | |
1551 | The people involved in authoring, reviewing, and pushing such | |
1552 | commit(s) should be at the forefront to mitigate their impact in a | |
1553 | timely fashion: by pushing a followup commit to fix it (if possible), | |
1554 | or by reverting it to leave time to come up with a proper fix, and by | |
1555 | communicating with other developers about the problem. | |
1556 | ||
1557 | If these persons are unavailable to address the issue in time, other | |
1558 | committers are entitled to revert the commit(s), explaining in the | |
1559 | commit log and on the mailing list what the problem was, with the goal | |
1560 | of leaving time to the original committer, reviewer(s), and author(s) | |
1561 | to propose a way forward. | |
1562 | ||
1563 | Once the problem has been dealt with, it is the responsibility of | |
1564 | those involved to make sure the situation is understood. If you are | |
1565 | working to understand what happened, focus on gathering information | |
1566 | and avoid assigning any blame. Do ask those involved to describe what | |
1567 | happened, do not ask them to explain the situation---this would | |
1568 | implicitly blame them, which is unhelpful. Accountability comes from | |
1569 | a consensus about the problem, learning from it and improving | |
1570 | processes so that it's less likely to reoccur. | |
1571 | ||
aaf4a009 LC |
1572 | @subsection Commit Revocation |
1573 | ||
9ade2b72 LF |
1574 | In order to reduce the possibility of mistakes, committers will have |
1575 | their Savannah account removed from the Guix Savannah project and their | |
1576 | key removed from @file{.guix-authorizations} after 12 months of | |
1577 | inactivity; they can ask to regain commit access by emailing the | |
1578 | maintainers, without going through the vouching process. | |
1579 | ||
d3d6d1c6 LC |
1580 | Maintainers@footnote{See @uref{https://guix.gnu.org/en/about} for the |
1581 | current list of maintainers. You can email them privately at | |
1582 | @email{guix-maintainers@@gnu.org}.} may also revoke an individual's | |
1583 | commit rights, as a last resort, if cooperation with the rest of the | |
1584 | community has caused too much friction---even within the bounds of the | |
1585 | project's code of conduct (@pxref{Contributing}). They would only do so | |
1586 | after public or private discussion with the individual and a clear | |
1587 | notice. Examples of behavior that hinders cooperation and could lead to | |
1588 | such a decision include: | |
1589 | ||
1590 | @itemize | |
1591 | @item repeated violation of the commit policy stated above; | |
1592 | @item repeated failure to take peer criticism into account; | |
1593 | @item breaching trust through a series of grave incidents. | |
1594 | @end itemize | |
1595 | ||
1596 | When maintainers resort to such a decision, they notify developers on | |
1597 | @email{guix-devel@@gnu.org}; inquiries may be sent to | |
1598 | @email{guix-maintainers@@gnu.org}. Depending on the situation, the | |
1599 | individual may still be welcome to contribute. | |
1600 | ||
aaf4a009 LC |
1601 | @subsection Helping Out |
1602 | ||
98ebcf1c LC |
1603 | One last thing: the project keeps moving forward because committers not |
1604 | only push their own awesome changes, but also offer some of their time | |
1605 | @emph{reviewing} and pushing other people's changes. As a committer, | |
1606 | you're welcome to use your expertise and commit rights to help other | |
1607 | contributors, too! | |
5800d2aa MC |
1608 | |
1609 | @node Updating the Guix Package | |
1610 | @section Updating the Guix Package | |
1611 | ||
1612 | @cindex update-guix-package, updating the guix package | |
1613 | It is sometimes desirable to update the @code{guix} package itself (the | |
1614 | package defined in @code{(gnu packages package-management)}), for | |
1615 | example to make new daemon features available for use by the | |
1616 | @code{guix-service-type} service type. In order to simplify this task, | |
1617 | the following command can be used: | |
1618 | ||
1619 | @example | |
1620 | make update-guix-package | |
1621 | @end example | |
1622 | ||
1623 | The @code{update-guix-package} make target will use the last known | |
1624 | @emph{commit} corresponding to @code{HEAD} in your Guix checkout, | |
1625 | compute the hash of the Guix sources corresponding to that commit and | |
1626 | update the @code{commit}, @code{revision} and hash of the @code{guix} | |
1627 | package definition. | |
1628 | ||
1629 | To validate that the updated @code{guix} package hashes are correct and | |
1630 | that it can be built successfully, the following command can be run from | |
1631 | the directory of your Guix checkout: | |
1632 | ||
1633 | @example | |
1634 | ./pre-inst-env guix build guix | |
1635 | @end example | |
1636 | ||
1637 | To guard against accidentally updating the @code{guix} package to a | |
1638 | commit that others can't refer to, a check is made that the commit used | |
1639 | has already been pushed to the Savannah-hosted Guix git repository. | |
1640 | ||
1641 | This check can be disabled, @emph{at your own peril}, by setting the | |
3de898b4 MC |
1642 | @code{GUIX_ALLOW_ME_TO_USE_PRIVATE_COMMIT} environment variable. When |
1643 | this variable is set, the updated package source is also added to the | |
1644 | store. This is used as part of the release process of Guix. | |
1897a6ef JL |
1645 | |
1646 | @cindex translation | |
1647 | @cindex l10n | |
1648 | @cindex i18n | |
1649 | @cindex native language support | |
1650 | @node Translating Guix | |
1651 | @section Translating Guix | |
1652 | ||
1653 | Writing code and packages is not the only way to provide a meaningful | |
1654 | contribution to Guix. Translating to a language you speak is another | |
1655 | example of a valuable contribution you can make. This section is designed | |
1656 | to describe the translation process. It gives you advice on how you can | |
1657 | get involved, what can be translated, what mistakes you should avoid and | |
1658 | what we can do to help you! | |
1659 | ||
1660 | Guix is a big project that has multiple components that can be translated. | |
1661 | We coordinate the translation effort on a | |
1662 | @uref{https://translate.fedoraproject.org/projects/guix/,Weblate instance} | |
1663 | hosted by our friends at Fedora. You will need an account to submit | |
1664 | translations. | |
1665 | ||
1666 | Some of the software packaged in Guix also contain translations. We do not | |
1667 | host a translation platform for them. If you want to translate a package | |
ef7275cd | 1668 | provided by Guix, you should contact their developers or find the information |
1897a6ef JL |
1669 | on their website. As an example, you can find the homepage of the |
1670 | @code{hello} package by typing @code{guix show hello}. On the ``homepage'' | |
1671 | line, you will see @url{https://www.gnu.org/software/hello/} as the homepage. | |
1672 | ||
1673 | Many GNU and non-GNU packages can be translated on the | |
1674 | @uref{https://translationproject.org,Translation Project}. Some projects | |
1675 | with multiple components have their own platform. For instance, GNOME has | |
1676 | its own platform, @uref{https://l10n.gnome.org/,Damned Lies}. | |
1677 | ||
1678 | Guix has five components hosted on Weblate. | |
1679 | ||
1680 | @itemize | |
1681 | @item @code{guix} contains all the strings from the Guix software (the | |
1682 | guided system installer, the package manager, etc), excluding packages. | |
1683 | @item @code{packages} contains the synopsis (single-sentence description | |
1684 | of a package) and description (longer description) of packages in Guix. | |
1685 | @item @code{website} contains the official Guix website, except for | |
1686 | blog posts and multimedia content. | |
1687 | @item @code{documentation-manual} corresponds to this manual. | |
1688 | @item @code{documentation-cookbook} is the component for the cookbook. | |
1689 | @end itemize | |
1690 | ||
1691 | @subsubheading General Directions | |
1692 | ||
1693 | Once you get an account, you should be able to select a component from | |
1694 | @uref{https://translate.fedoraproject.org/projects/guix/,the guix project}, | |
1695 | and select a language. If your language does not appear in the list, go | |
1696 | to the bottom and click on the ``Start new translation'' button. Select | |
1697 | the language you want to translate to from the list, to start your new | |
1698 | translation. | |
1699 | ||
1700 | Like lots of other free software packages, Guix uses | |
1701 | @uref{https://www.gnu.org/software/gettext,GNU Gettext} for its translations, | |
1702 | with which translatable strings are extracted from the source code to so-called | |
1703 | PO files. | |
1704 | ||
1705 | Even though PO files are text files, changes should not be made with a text | |
1706 | editor but with PO editing software. Weblate integrates PO editing | |
1707 | functionality. Alternatively, translators can use any of various | |
1708 | free-software tools for filling in translations, of which | |
1709 | @uref{https://poedit.net/,Poedit} is one example, and (after logging in) | |
1710 | @uref{https://docs.weblate.org/en/latest/user/files.html,upload} the changed | |
1711 | file. There is also a special | |
1712 | @uref{https://www.emacswiki.org/emacs/PoMode,PO editing mode} for users of GNU | |
1713 | Emacs. Over time translators find out what software they are happy with and | |
1714 | what features they need. | |
1715 | ||
1716 | On Weblate, you will find various links to the editor, that will show various | |
1717 | subsets (or all) of the strings. Have a look around and at the | |
1718 | @uref{https://docs.weblate.org/en/latest/,documentation} to familiarize | |
1719 | yourself with the platform. | |
1720 | ||
1721 | @subsubheading Translation Components | |
1722 | ||
1723 | In this section, we provide more detailed guidance on the translation | |
1724 | process, as well as details on what you should or should not do. When in | |
1725 | doubt, please contact us, we will be happy to help! | |
1726 | ||
1727 | @table @asis | |
1728 | @item guix | |
1729 | Guix is written in the Guile programming language, and some strings contain | |
d127fdd0 | 1730 | special formatting that is interpreted by Guile. These special formatting |
1897a6ef JL |
1731 | should be highlighted by Weblate. They start with @code{~} followed by one |
1732 | or more characters. | |
1733 | ||
d127fdd0 | 1734 | When printing the string, Guile replaces the special formatting symbols with |
1897a6ef JL |
1735 | actual values. For instance, the string @samp{ambiguous package specification |
1736 | `~a'} would be substituted to contain said package specification instead of | |
d127fdd0 | 1737 | @code{~a}. To properly translate this string, you must keep the formatting |
1897a6ef JL |
1738 | code in your translation, although you can place it where it makes sense in |
1739 | your language. For instance, the French translation says @samp{spécification | |
1740 | du paquet « ~a » ambiguë} because the adjective needs to be placed in the | |
1741 | end of the sentence. | |
1742 | ||
d127fdd0 | 1743 | If there are multiple formatting symbols, make sure to respect the order. |
1897a6ef JL |
1744 | Guile does not know in which order you intended the string to be read, so it |
1745 | will substitute the symbols in the same order as the English sentence. | |
1746 | ||
1747 | As an example, you cannot translate @samp{package '~a' has been superseded by | |
1748 | '~a'} by @samp{'~a' superseeds package '~a'}, because the meaning would be | |
ef7275cd | 1749 | reversed. If @var{foo} is superseded by @var{bar}, the translation would read |
1897a6ef | 1750 | @samp{'foo' superseeds package 'bar'}. To work around this problem, it |
d127fdd0 | 1751 | is possible to use more advanced formatting to select a given piece of data, |
1897a6ef | 1752 | instead of following the default English order. @xref{Formatted Output,,, |
d127fdd0 | 1753 | guile, GNU Guile Reference Manual}, for more information on formatting in Guile. |
1897a6ef JL |
1754 | |
1755 | @item packages | |
1756 | ||
1757 | Package descriptions occasionally contain Texinfo markup (@pxref{Synopses | |
1758 | and Descriptions}). Texinfo markup looks like @samp{@@code@{rm -rf@}}, | |
1759 | @samp{@@emph@{important@}}, etc. When translating, please leave markup as is. | |
1760 | ||
1761 | The characters after ``@@'' form the name of the markup, and the text between | |
1762 | ``@{'' and ``@}'' is its content. In general, you should not translate the | |
1763 | content of markup like @code{@@code}, as it contains literal code that do not | |
d127fdd0 | 1764 | change with language. You can translate the content of formatting markup such |
1897a6ef JL |
1765 | as @code{@@emph}, @code{@@i}, @code{@@itemize}, @code{@@item}. However, do |
1766 | not translate the name of the markup, or it will not be recognized. Do | |
1767 | not translate the word after @code{@@end}, it is the name of the markup that | |
1768 | is closed at this position (e.g.@: @code{@@itemize ... @@end itemize}). | |
1769 | ||
1770 | @item documentation-manual and documentation-cookbook | |
1771 | ||
1772 | The first step to ensure a successful translation of the manual is to find | |
1773 | and translate the following strings @emph{first}: | |
1774 | ||
1775 | @itemize | |
1776 | @item @code{version.texi}: Translate this string as @code{version-xx.texi}, | |
1777 | where @code{xx} is your language code (the one shown in the URL on | |
1778 | weblate). | |
1779 | @item @code{contributing.texi}: Translate this string as | |
1780 | @code{contributing.xx.texi}, where @code{xx} is the same language code. | |
1781 | @item @code{Top}: Do not translate this string, it is important for Texinfo. | |
1782 | If you translate it, the document will be empty (missing a Top node). | |
1783 | Please look for it, and register @code{Top} as its translation. | |
1784 | @end itemize | |
1785 | ||
1786 | Translating these strings first ensure we can include your translation in | |
1787 | the guix repository without breaking the make process or the | |
1788 | @command{guix pull} machinery. | |
1789 | ||
1790 | The manual and the cookbook both use Texinfo. As for @code{packages}, please | |
1791 | keep Texinfo markup as is. There are more possible markup types in the manual | |
1792 | than in the package descriptions. In general, do not translate the content | |
1793 | of @code{@@code}, @code{@@file}, @code{@@var}, @code{@@value}, etc. You | |
d127fdd0 | 1794 | should translate the content of formatting markup such as @code{@@emph}, |
1897a6ef JL |
1795 | @code{@@i}, etc. |
1796 | ||
d127fdd0 | 1797 | The manual contains sections that can be referred to by name by @code{@@ref}, |
1897a6ef JL |
1798 | @code{@@xref} and @code{@@pxref}. We have a mechanism in place so you do |
1799 | not have to translate their content. If you keep the English title, we will | |
1800 | automatically replace it with your translation of that title. This ensures | |
1801 | that Texinfo will always be able to find the node. If you decide to change | |
1802 | the translation of the title, the references will automatically be updated | |
1803 | and you will not have to update them all yourself. | |
1804 | ||
1805 | When translating references from the cookbook to the manual, you need to | |
1806 | replace the name of the manual and the name of the section. For instance, | |
1807 | to translate @code{@@pxref@{Defining Packages,,, guix, GNU Guix Reference | |
1808 | Manual@}}, you would replace @code{Defining Packages} with the title of that | |
1809 | section in the translated manual @emph{only} if that title is translated. | |
1810 | If the title is not translated in your language yet, do not translate it here, | |
1811 | or the link will be broken. Replace @code{guix} with @code{guix.xx} where | |
1812 | @code{xx} is your language code. @code{GNU Guix Reference Manual} is the | |
1813 | text of the link. You can translate it however you wish. | |
1814 | ||
1815 | @item website | |
1816 | ||
1817 | The website pages are written using SXML, an s-expression version of HTML, | |
1818 | the basic language of the web. We have a process to extract translatable | |
1819 | strings from the source, and replace complex s-expressions with a more familiar | |
1820 | XML markup, where each markup is numbered. Translators can arbitrarily change | |
1821 | the ordering, as in the following example. | |
1822 | ||
1823 | @example | |
1824 | #. TRANSLATORS: Defining Packages is a section name | |
1825 | #. in the English (en) manual. | |
1826 | #: apps/base/templates/about.scm:64 | |
1827 | msgid "Packages are <1>defined<1.1>en</1.1><1.2>Defining-Packages.html</1.2></1> as native <2>Guile</2> modules." | |
1828 | msgstr "Pakete werden als reine <2>Guile</2>-Module <1>definiert<1.1>de</1.1><1.2>Pakete-definieren.html</1.2></1>." | |
1829 | @end example | |
1830 | ||
1831 | Note that you need to include the same markups. You cannot skip any. | |
1832 | @end table | |
1833 | ||
1834 | In case you make a mistake, the component might fail to build properly with your | |
1835 | language, or even make guix pull fail. To prevent that, we have a process | |
1836 | in place to check the content of the files before pushing to our repository. | |
1837 | We will not be able to update the translation for your language in Guix, so | |
1838 | we will notify you (through weblate and/or by email) so you get a chance to | |
1839 | fix the issue. | |
1840 | ||
1841 | @subsubheading Outside of Weblate | |
1842 | ||
1843 | Currently, some parts of Guix cannot be translated on Weblate, help wanted! | |
1844 | ||
1845 | @itemize | |
1846 | @item @command{guix pull} news can be translated in @file{news.scm}, but is not | |
1847 | available from Weblate. If you want to provide a translation, you | |
1848 | can prepare a patch as described above, or simply send us your | |
1849 | translation with the name of the news entry you translated and your | |
1850 | language. @xref{Writing Channel News}, for more information about | |
1851 | channel news. | |
1852 | @item Guix blog posts cannot currently be translated. | |
1853 | @item The installer script (for foreign distributions) is entirely in English. | |
1854 | @item Some of the libraries Guix uses cannot be translated or are translated | |
1855 | outside of the Guix project. Guile itself is not internationalized. | |
1856 | @item Other manuals linked from this manual or the cookbook might not be | |
1857 | translated. | |
1858 | @end itemize | |
1859 | ||
1860 | @subsubheading Translation Infrastructure | |
1861 | ||
1862 | Weblate is backed by a git repository from which it discovers new strings to | |
1863 | translate and pushes new and updated translations. Normally, it would be | |
1864 | enough to give it commit access to our repositories. However, we decided | |
1865 | to use a separate repository for two reasons. First, we would have to give | |
1866 | Weblate commit access and authorize its signing key, but we do not trust it | |
ef7275cd | 1867 | in the same way we trust guix developers, especially since we do not manage |
1897a6ef JL |
1868 | the instance ourselves. Second, if translators mess something up, it can |
1869 | break the generation of the website and/or guix pull for all our users, | |
1870 | independently of their language. | |
1871 | ||
1872 | For these reasons, we use a dedicated repository to host translations, and we | |
1873 | synchronize it with our guix and artworks repositories after checking no issue | |
1874 | was introduced in the translation. | |
1875 | ||
ef7275cd | 1876 | Developers can download the latest PO files from weblate in the Guix |
d127fdd0 | 1877 | repository by running the @command{make download-po} command. It will |
1897a6ef JL |
1878 | automatically download the latest files from weblate, reformat them to a |
1879 | canonical form, and check they do not contain issues. The manual needs to be | |
1880 | built again to check for additional issues that might crash Texinfo. | |
1881 | ||
ef7275cd | 1882 | Before pushing new translation files, developers should add them to the |
1897a6ef JL |
1883 | make machinery so the translations are actually available. The process |
1884 | differs for the various components. | |
1885 | ||
1886 | @itemize | |
1887 | @item New po files for the @code{guix} and @code{packages} components must | |
1888 | be registered by adding the new language to @file{po/guix/LINGUAS} or | |
1889 | @file{po/packages/LINGUAS}. | |
1890 | @item New po files for the @code{documentation-manual} component must be | |
1891 | registered by adding the file name to @code{DOC_PO_FILES} in | |
1892 | @file{po/doc/local.mk}, the generated @file{%D%/guix.xx.texi} manual to | |
1893 | @code{info_TEXINFOS} in @file{doc/local.mk} and the generated | |
1894 | @file{%D%/guix.xx.texi} and @file{%D%/contributing.xx.texi} to | |
1895 | @code{TRANSLATED_INFO} also in @file{doc/local.mk}. | |
1896 | @item New po files for the @code{documentation-cookbook} component must be | |
1897 | registered by adding the file name to @code{DOC_COOKBOOK_PO_FILES} in | |
1898 | @file{po/doc/local.mk}, the generated @file{%D%/guix-cookbook.xx.texi} | |
1899 | manual to @code{info_TEXINFOS} in @file{doc/local.mk} and the generated | |
1900 | @file{%D%/guix-cookbook.xx.texi} to @code{TRANSLATED_INFO} also | |
1901 | in @file{doc/local.mk}. | |
1902 | @item New po files for the @code{website} component must be added to the | |
1903 | @code{guix-artwork} repository, in @file{website/po/}. | |
1904 | @file{website/po/LINGUAS} and @file{website/po/ietf-tags.scm} must | |
1905 | be updated accordingly (see @file{website/i18n-howto.txt} for more | |
1906 | information on the process). | |
1907 | @end itemize |