Commit | Line | Data |
---|---|---|
568717fd LC |
1 | \input texinfo |
2 | @c -*-texinfo-*- | |
3 | ||
4 | @c %**start of header | |
5 | @setfilename guix.info | |
6 | @documentencoding UTF-8 | |
f8348b91 | 7 | @settitle GNU Guix Reference Manual |
568717fd LC |
8 | @c %**end of header |
9 | ||
10 | @include version.texi | |
7df7a74e | 11 | |
debc6360 | 12 | @c Identifier of the OpenPGP key used to sign tarballs and such. |
5564c011 | 13 | @set OPENPGP-SIGNING-KEY-ID 3CE464558A84FDC69DB40CFB090B11993D9AEBB5 |
debc6360 | 14 | |
7df7a74e | 15 | @copying |
db5a9444 | 16 | Copyright @copyright{} 2012, 2013, 2014, 2015, 2016 Ludovic Courtès@* |
f97c9175 | 17 | Copyright @copyright{} 2013, 2014, 2016 Andreas Enge@* |
87eafdbd | 18 | Copyright @copyright{} 2013 Nikita Karetnikov@* |
1a3e6b15 | 19 | Copyright @copyright{} 2014, 2015, 2016 Alex Kost@* |
1b846da8 | 20 | Copyright @copyright{} 2015, 2016 Mathieu Lirzin@* |
8c01b9d0 | 21 | Copyright @copyright{} 2014 Pierre-Antoine Rault@* |
97d76250 | 22 | Copyright @copyright{} 2015 Taylan Ulrich Bayırlı/Kammer@* |
4d343a14 | 23 | Copyright @copyright{} 2015, 2016 Leo Famulari@* |
909147e4 | 24 | Copyright @copyright{} 2015, 2016 Ricardo Wurmus@* |
4d343a14 | 25 | Copyright @copyright{} 2016 Ben Woodcroft@* |
76192896 | 26 | Copyright @copyright{} 2016 Chris Marusich@* |
6e42660b | 27 | Copyright @copyright{} 2016 Efraim Flashner@* |
d6a07ee6 | 28 | Copyright @copyright{} 2016 John Darrington@* |
92c03a87 | 29 | Copyright @copyright{} 2016 ng0@* |
8c00b838 | 30 | Copyright @copyright{} 2016 Jan Nieuwenhuizen@* |
9747d189 AW |
31 | Copyright @copyright{} 2016 Julien Lepiller@* |
32 | Copyright @copyright{} 2016 Alex ter Weele | |
7df7a74e NK |
33 | |
34 | Permission is granted to copy, distribute and/or modify this document | |
35 | under the terms of the GNU Free Documentation License, Version 1.3 or | |
36 | any later version published by the Free Software Foundation; with no | |
37 | Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A | |
38 | copy of the license is included in the section entitled ``GNU Free | |
39 | Documentation License''. | |
40 | @end copying | |
568717fd | 41 | |
abd67856 | 42 | @dircategory System administration |
568717fd | 43 | @direntry |
abd67856 LC |
44 | * Guix: (guix). Manage installed software and system configuration. |
45 | * guix package: (guix)Invoking guix package. Installing, removing, and upgrading packages. | |
46 | * guix build: (guix)Invoking guix build. Building packages. | |
47 | * guix gc: (guix)Invoking guix gc. Reclaiming unused disk space. | |
48 | * guix pull: (guix)Invoking guix pull. Update the list of available packages. | |
49 | * guix system: (guix)Invoking guix system. Manage the operating system configuration. | |
568717fd | 50 | @end direntry |
568717fd | 51 | |
372c4bbc DT |
52 | @dircategory Software development |
53 | @direntry | |
abd67856 | 54 | * guix environment: (guix)Invoking guix environment. Building development environments with Guix. |
372c4bbc DT |
55 | @end direntry |
56 | ||
abd67856 LC |
57 | @dircategory Emacs |
58 | @direntry | |
59 | * Guix user interface: (guix)Emacs Interface. Package management from the comfort of Emacs. | |
60 | @end direntry | |
61 | ||
62 | ||
568717fd | 63 | @titlepage |
7730d112 LC |
64 | @title GNU Guix Reference Manual |
65 | @subtitle Using the GNU Guix Functional Package Manager | |
2cbed07e | 66 | @author The GNU Guix Developers |
568717fd LC |
67 | |
68 | @page | |
69 | @vskip 0pt plus 1filll | |
70 | Edition @value{EDITION} @* | |
71 | @value{UPDATED} @* | |
72 | ||
7df7a74e | 73 | @insertcopying |
568717fd LC |
74 | @end titlepage |
75 | ||
568717fd LC |
76 | @contents |
77 | ||
78 | @c ********************************************************************* | |
79 | @node Top | |
f8348b91 | 80 | @top GNU Guix |
568717fd | 81 | |
f8348b91 LC |
82 | This document describes GNU Guix version @value{VERSION}, a functional |
83 | package management tool written for the GNU system. | |
568717fd LC |
84 | |
85 | @menu | |
86 | * Introduction:: What is Guix about? | |
bd5e766b | 87 | * Installation:: Installing Guix. |
eeaf4427 | 88 | * Package Management:: Package installation, upgrade, etc. |
c554de89 | 89 | * Emacs Interface:: Using Guix from Emacs. |
568717fd LC |
90 | * Programming Interface:: Using Guix in Scheme. |
91 | * Utilities:: Package management commands. | |
a1ba8475 | 92 | * GNU Distribution:: Software for your friendly GNU system. |
9bf3c1a7 | 93 | * Contributing:: Your help needed! |
568717fd LC |
94 | |
95 | * Acknowledgments:: Thanks! | |
96 | * GNU Free Documentation License:: The license of this manual. | |
97 | * Concept Index:: Concepts. | |
a85b83d2 | 98 | * Programming Index:: Data types, functions, and variables. |
aaa3eaa9 LC |
99 | |
100 | @detailmenu | |
101 | --- The Detailed Node Listing --- | |
102 | ||
103 | Installation | |
104 | ||
1b2b8177 | 105 | * Binary Installation:: Getting Guix running in no time! |
aaa3eaa9 | 106 | * Requirements:: Software needed to build and run Guix. |
ec0339cd | 107 | * Running the Test Suite:: Testing Guix. |
aaa3eaa9 LC |
108 | * Setting Up the Daemon:: Preparing the build daemon's environment. |
109 | * Invoking guix-daemon:: Running the build daemon. | |
0e2d0213 | 110 | * Application Setup:: Application-specific setup. |
aaa3eaa9 LC |
111 | |
112 | Setting Up the Daemon | |
113 | ||
114 | * Build Environment Setup:: Preparing the isolated build environment. | |
115 | * Daemon Offload Setup:: Offloading builds to remote machines. | |
116 | ||
117 | Package Management | |
118 | ||
119 | * Features:: How Guix will make your life brighter. | |
120 | * Invoking guix package:: Package installation, removal, etc. | |
aaa3eaa9 LC |
121 | * Substitutes:: Downloading pre-built binaries. |
122 | * Packages with Multiple Outputs:: Single source package, multiple outputs. | |
123 | * Invoking guix gc:: Running the garbage collector. | |
124 | * Invoking guix pull:: Fetching the latest Guix and distribution. | |
125 | * Invoking guix archive:: Exporting and importing store files. | |
126 | ||
c554de89 AK |
127 | Emacs Interface |
128 | ||
129 | * Initial Setup: Emacs Initial Setup. Preparing @file{~/.emacs}. | |
130 | * Package Management: Emacs Package Management. Managing packages and generations. | |
687c9bc0 | 131 | * Licenses: Emacs Licenses. Interface for licenses of Guix packages. |
b5e3cbbb | 132 | * Package Source Locations: Emacs Package Locations. Interface for package location files. |
9b0afb0d | 133 | * Popup Interface: Emacs Popup Interface. Magit-like interface for guix commands. |
c554de89 | 134 | * Prettify Mode: Emacs Prettify. Abbreviating @file{/gnu/store/@dots{}} file names. |
34850cd5 | 135 | * Build Log Mode: Emacs Build Log. Highlighting Guix build logs. |
187f80c6 AK |
136 | * Completions: Emacs Completions. Completing @command{guix} shell command. |
137 | * Development: Emacs Development. Tools for Guix developers. | |
32950fc8 | 138 | * Hydra: Emacs Hydra. Interface for Guix build farm. |
c554de89 | 139 | |
aaa3eaa9 LC |
140 | Programming Interface |
141 | ||
142 | * Defining Packages:: Defining new packages. | |
143 | * Build Systems:: Specifying how packages are built. | |
144 | * The Store:: Manipulating the package store. | |
145 | * Derivations:: Low-level interface to package derivations. | |
146 | * The Store Monad:: Purely functional interface to the store. | |
147 | * G-Expressions:: Manipulating build expressions. | |
148 | ||
92492b23 LC |
149 | Defining Packages |
150 | ||
151 | * package Reference:: The package data type. | |
152 | * origin Reference:: The origin data type. | |
153 | ||
aaa3eaa9 LC |
154 | Utilities |
155 | ||
156 | * Invoking guix build:: Building packages from the command line. | |
fcc58db6 | 157 | * Invoking guix edit:: Editing package definitions. |
aaa3eaa9 LC |
158 | * Invoking guix download:: Downloading a file and printing its hash. |
159 | * Invoking guix hash:: Computing the cryptographic hash of a file. | |
160 | * Invoking guix import:: Importing package definitions. | |
161 | * Invoking guix refresh:: Updating package definitions. | |
162 | * Invoking guix lint:: Finding errors in package definitions. | |
fcc58db6 | 163 | * Invoking guix size:: Profiling disk usage. |
88856916 | 164 | * Invoking guix graph:: Visualizing the graph of packages. |
aaa3eaa9 | 165 | * Invoking guix environment:: Setting up development environments. |
aff8ce7c | 166 | * Invoking guix publish:: Sharing substitutes. |
d23c20f1 | 167 | * Invoking guix challenge:: Challenging substitute servers. |
32efa254 | 168 | * Invoking guix container:: Process isolation. |
aaa3eaa9 | 169 | |
e3009f60 LC |
170 | Invoking @command{guix build} |
171 | ||
172 | * Common Build Options:: Build options for most commands. | |
173 | * Package Transformation Options:: Creating variants of packages. | |
174 | * Additional Build Options:: Options specific to 'guix build'. | |
175 | ||
aaa3eaa9 LC |
176 | GNU Distribution |
177 | ||
178 | * System Installation:: Installing the whole operating system. | |
35ed9306 | 179 | * System Configuration:: Configuring the operating system. |
aaa3eaa9 LC |
180 | * Installing Debugging Files:: Feeding the debugger. |
181 | * Security Updates:: Deploying security fixes quickly. | |
182 | * Package Modules:: Packages from the programmer's viewpoint. | |
183 | * Packaging Guidelines:: Growing the distribution. | |
184 | * Bootstrapping:: GNU/Linux built from scratch. | |
185 | * Porting:: Targeting another platform or kernel. | |
186 | ||
e3009f60 LC |
187 | System Installation |
188 | ||
189 | * Limitations:: What you can expect. | |
190 | * Hardware Considerations:: Supported hardware. | |
191 | * USB Stick Installation:: Preparing the installation medium. | |
192 | * Preparing for Installation:: Networking, partitioning, etc. | |
193 | * Proceeding with the Installation:: The real thing. | |
c8b54374 | 194 | * Installing GuixSD in a VM:: GuixSD playground. |
e3009f60 LC |
195 | * Building the Installation Image:: How this comes to be. |
196 | ||
aaa3eaa9 LC |
197 | System Configuration |
198 | ||
199 | * Using the Configuration System:: Customizing your GNU system. | |
200 | * operating-system Reference:: Detail of operating-system declarations. | |
201 | * File Systems:: Configuring file system mounts. | |
202 | * Mapped Devices:: Block device extra processing. | |
203 | * User Accounts:: Specifying user accounts. | |
598e19dc | 204 | * Locales:: Language and cultural convention settings. |
aaa3eaa9 LC |
205 | * Services:: Specifying system services. |
206 | * Setuid Programs:: Programs running with root privileges. | |
1b2b8177 | 207 | * X.509 Certificates:: Authenticating HTTPS servers. |
996ed739 | 208 | * Name Service Switch:: Configuring libc's name service switch. |
aaa3eaa9 LC |
209 | * Initial RAM Disk:: Linux-Libre bootstrapping. |
210 | * GRUB Configuration:: Configuring the boot loader. | |
211 | * Invoking guix system:: Instantiating a system configuration. | |
97d76250 | 212 | * Running GuixSD in a VM:: How to run GuixSD in a virtual machine. |
aaa3eaa9 LC |
213 | * Defining Services:: Adding new service definitions. |
214 | ||
215 | Services | |
216 | ||
217 | * Base Services:: Essential system services. | |
c311089b | 218 | * Scheduled Job Execution:: The mcron service. |
92c03a87 | 219 | * Log Rotation:: The rottlog service. |
aaa3eaa9 LC |
220 | * Networking Services:: Network setup, SSH daemon, etc. |
221 | * X Window:: Graphical display. | |
1b2b8177 LC |
222 | * Desktop Services:: D-Bus and desktop services. |
223 | * Database Services:: SQL databases. | |
d8c18af8 | 224 | * Mail Services:: IMAP, POP3, SMTP, and all that. |
859e367d | 225 | * Kerberos Services:: Kerberos services. |
cbd02397 | 226 | * Web Services:: Web servers. |
eb419bc9 | 227 | * Network File System:: NFS related services. |
dbc6d370 | 228 | * Miscellaneous Services:: Other services. |
aaa3eaa9 | 229 | |
0adfe95a LC |
230 | Defining Services |
231 | ||
232 | * Service Composition:: The model for composing services. | |
233 | * Service Types and Services:: Types and services. | |
234 | * Service Reference:: API reference. | |
dd17bc38 | 235 | * Shepherd Services:: A particular type of service. |
0adfe95a | 236 | |
aaa3eaa9 LC |
237 | Packaging Guidelines |
238 | ||
ec0339cd LC |
239 | * Software Freedom:: What may go into the distribution. |
240 | * Package Naming:: What's in a name? | |
241 | * Version Numbers:: When the name is not enough. | |
cbd02397 | 242 | * Synopses and Descriptions:: Helping users find the right package. |
ec0339cd LC |
243 | * Python Modules:: Taming the snake. |
244 | * Perl Modules:: Little pearls. | |
e1c963bf | 245 | * Java Packages:: Coffee break. |
ec0339cd | 246 | * Fonts:: Fond of fonts. |
aaa3eaa9 | 247 | |
8c01b9d0 ML |
248 | Contributing |
249 | ||
250 | * Building from Git:: The latest and greatest. | |
251 | * Running Guix Before It Is Installed:: Hacker tricks. | |
252 | * The Perfect Setup:: The right tools. | |
253 | * Coding Style:: Hygiene of the contributor. | |
254 | * Submitting Patches:: Share your work. | |
255 | ||
256 | Coding Style | |
257 | ||
258 | * Programming Paradigm:: How to compose your elements. | |
259 | * Modules:: Where to store your code? | |
260 | * Data Types and Pattern Matching:: Implementing data structures. | |
261 | * Formatting Code:: Writing conventions. | |
262 | ||
aaa3eaa9 | 263 | @end detailmenu |
568717fd LC |
264 | @end menu |
265 | ||
266 | @c ********************************************************************* | |
267 | @node Introduction | |
268 | @chapter Introduction | |
269 | ||
6f773606 | 270 | @cindex purpose |
c80e7e55 | 271 | GNU Guix@footnote{``Guix'' is pronounced like ``geeks'', or ``ɡiːks'' |
6f773606 LC |
272 | using the international phonetic alphabet (IPA).} is a package |
273 | management tool for the GNU system. Guix makes it easy for unprivileged | |
274 | users to install, upgrade, or remove packages, to roll back to a | |
275 | previous package set, to build packages from source, and generally | |
276 | assists with the creation and maintenance of software environments. | |
277 | ||
278 | @cindex user interfaces | |
279 | Guix provides a command-line package management interface | |
280 | (@pxref{Invoking guix package}), a set of command-line utilities | |
281 | (@pxref{Utilities}), a visual user interface in Emacs (@pxref{Emacs | |
282 | Interface}), as well as Scheme programming interfaces | |
283 | (@pxref{Programming Interface}). | |
284 | @cindex build daemon | |
285 | Its @dfn{build daemon} is responsible for building packages on behalf of | |
286 | users (@pxref{Setting Up the Daemon}) and for downloading pre-built | |
287 | binaries from authorized sources (@pxref{Substitutes}). | |
288 | ||
289 | @cindex extensibility of the distribution | |
e32171ee | 290 | @cindex customization, of packages |
6f773606 LC |
291 | Guix includes package definitions for many GNU and non-GNU packages, all |
292 | of which @uref{https://www.gnu.org/philosophy/free-sw.html, respect the | |
293 | user's computing freedom}. It is @emph{extensible}: users can write | |
294 | their own package definitions (@pxref{Defining Packages}) and make them | |
295 | available as independent package modules (@pxref{Package Modules}). It | |
296 | is also @emph{customizable}: users can @emph{derive} specialized package | |
297 | definitions from existing ones, including from the command line | |
298 | (@pxref{Package Transformation Options}). | |
299 | ||
300 | @cindex Guix System Distribution | |
301 | @cindex GuixSD | |
302 | You can install GNU@tie{}Guix on top of an existing GNU/Linux system | |
303 | where it complements the available tools without interference | |
304 | (@pxref{Installation}), or you can use it as part of the standalone | |
305 | @dfn{Guix System Distribution} or GuixSD (@pxref{GNU Distribution}). | |
306 | With GNU@tie{}GuixSD, you @emph{declare} all aspects of the operating | |
307 | system configuration and Guix takes care of instantiating the | |
308 | configuration in a transactional, reproducible, and stateless fashion | |
309 | (@pxref{System Configuration}). | |
568717fd LC |
310 | |
311 | @cindex functional package management | |
6f773606 | 312 | Under the hood, Guix implements the @dfn{functional package management} |
136787cb LC |
313 | discipline pioneered by Nix (@pxref{Acknowledgments}). |
314 | In Guix, the package build and installation process is seen | |
6f773606 | 315 | as a @emph{function}, in the mathematical sense. That function takes inputs, |
4bfc4ea3 NK |
316 | such as build scripts, a compiler, and libraries, and |
317 | returns an installed package. As a pure function, its result depends | |
568717fd LC |
318 | solely on its inputs---for instance, it cannot refer to software or |
319 | scripts that were not explicitly passed as inputs. A build function | |
4bfc4ea3 | 320 | always produces the same result when passed a given set of inputs. It |
f97c9175 | 321 | cannot alter the environment of the running system in |
568717fd LC |
322 | any way; for instance, it cannot create, modify, or delete files outside |
323 | of its build and installation directories. This is achieved by running | |
e900c503 | 324 | build processes in isolated environments (or @dfn{containers}), where only their |
4bfc4ea3 | 325 | explicit inputs are visible. |
568717fd | 326 | |
e531ac2a | 327 | @cindex store |
568717fd | 328 | The result of package build functions is @dfn{cached} in the file |
e531ac2a | 329 | system, in a special directory called @dfn{the store} (@pxref{The |
f97c9175 | 330 | Store}). Each package is installed in a directory of its own in the |
834129e0 | 331 | store---by default under @file{/gnu/store}. The directory name contains |
568717fd LC |
332 | a hash of all the inputs used to build that package; thus, changing an |
333 | input yields a different directory name. | |
334 | ||
f97c9175 AE |
335 | This approach is the foundation for the salient features of Guix: support |
336 | for transactional package upgrade and rollback, per-user installation, and | |
eeaf4427 | 337 | garbage collection of packages (@pxref{Features}). |
568717fd | 338 | |
a1ba8475 | 339 | |
bd5e766b LC |
340 | @c ********************************************************************* |
341 | @node Installation | |
342 | @chapter Installation | |
343 | ||
e32171ee | 344 | @cindex installing Guix |
48febeb8 LC |
345 | GNU Guix is available for download from its website at |
346 | @url{http://www.gnu.org/software/guix/}. This section describes the | |
347 | software requirements of Guix, as well as how to install it and get | |
348 | ready to use it. | |
bd5e766b | 349 | |
5af6de3e LC |
350 | Note that this section is concerned with the installation of the package |
351 | manager, which can be done on top of a running GNU/Linux system. If, | |
352 | instead, you want to install the complete GNU operating system, | |
6621cdb6 | 353 | @pxref{System Installation}. |
5af6de3e | 354 | |
d23ef788 LC |
355 | @cindex foreign distro |
356 | When installed on a running GNU/Linux system---thereafter called a | |
357 | @dfn{foreign distro}---GNU@tie{}Guix complements the available tools | |
358 | without interference. Its data lives exclusively in two directories, | |
359 | usually @file{/gnu/store} and @file{/var/guix}; other files on your | |
360 | system, such as @file{/etc}, are left untouched. | |
361 | ||
bd5e766b | 362 | @menu |
09722b11 | 363 | * Binary Installation:: Getting Guix running in no time! |
bd5e766b | 364 | * Requirements:: Software needed to build and run Guix. |
ec0339cd | 365 | * Running the Test Suite:: Testing Guix. |
bd5e766b LC |
366 | * Setting Up the Daemon:: Preparing the build daemon's environment. |
367 | * Invoking guix-daemon:: Running the build daemon. | |
0e2d0213 | 368 | * Application Setup:: Application-specific setup. |
bd5e766b LC |
369 | @end menu |
370 | ||
09722b11 LC |
371 | @node Binary Installation |
372 | @section Binary Installation | |
373 | ||
e32171ee | 374 | @cindex installing Guix from binaries |
09722b11 LC |
375 | This section describes how to install Guix on an arbitrary system from a |
376 | self-contained tarball providing binaries for Guix and for all its | |
377 | dependencies. This is often quicker than installing from source, which | |
378 | is described in the next sections. The only requirement is to have | |
379 | GNU@tie{}tar and Xz. | |
380 | ||
381 | Installing goes along these lines: | |
382 | ||
383 | @enumerate | |
384 | @item | |
e32171ee | 385 | @cindex downloading Guix binary |
09722b11 | 386 | Download the binary tarball from |
daa8922a LC |
387 | @indicateurl{ftp://alpha.gnu.org/gnu/guix/guix-binary-@value{VERSION}.@var{system}.tar.xz}, |
388 | where @var{system} is @code{x86_64-linux} for an @code{x86_64} machine | |
389 | already running the kernel Linux, and so on. | |
390 | ||
debc6360 | 391 | @c The following is somewhat duplicated in ``System Installation''. |
daa8922a LC |
392 | Make sure to download the associated @file{.sig} file and to verify the |
393 | authenticity of the tarball against it, along these lines: | |
394 | ||
395 | @example | |
396 | $ wget ftp://alpha.gnu.org/gnu/guix/guix-binary-@value{VERSION}.@var{system}.tar.xz.sig | |
397 | $ gpg --verify guix-binary-@value{VERSION}.@var{system}.tar.xz.sig | |
398 | @end example | |
399 | ||
f97c9175 | 400 | If that command fails because you do not have the required public key, |
daa8922a LC |
401 | then run this command to import it: |
402 | ||
403 | @example | |
debc6360 | 404 | $ gpg --keyserver pgp.mit.edu --recv-keys @value{OPENPGP-SIGNING-KEY-ID} |
daa8922a LC |
405 | @end example |
406 | ||
407 | @noindent | |
408 | and rerun the @code{gpg --verify} command. | |
debc6360 | 409 | @c end authentication part |
09722b11 LC |
410 | |
411 | @item | |
412 | As @code{root}, run: | |
413 | ||
414 | @example | |
5dc42964 | 415 | # cd /tmp |
254b1c2e LC |
416 | # tar --warning=no-timestamp -xf \ |
417 | guix-binary-@value{VERSION}.@var{system}.tar.xz | |
5dc42964 | 418 | # mv var/guix /var/ && mv gnu / |
09722b11 LC |
419 | @end example |
420 | ||
7acd3439 LC |
421 | This creates @file{/gnu/store} (@pxref{The Store}) and @file{/var/guix}. |
422 | The latter contains a ready-to-use profile for @code{root} (see next | |
423 | step.) | |
09722b11 | 424 | |
5dc3ce5f LC |
425 | Do @emph{not} unpack the tarball on a working Guix system since that |
426 | would overwrite its own essential files. | |
427 | ||
254b1c2e | 428 | The @code{--warning=no-timestamp} option makes sure GNU@tie{}tar does |
e9ba6357 LC |
429 | not emit warnings about ``implausibly old time stamps'' (such |
430 | warnings were triggered by GNU@tie{}tar 1.26 and older; recent | |
431 | versions are fine.) | |
432 | They stem from the fact that all the | |
254b1c2e LC |
433 | files in the archive have their modification time set to zero (which |
434 | means January 1st, 1970.) This is done on purpose to make sure the | |
435 | archive content is independent of its creation time, thus making it | |
436 | reproducible. | |
437 | ||
7acd3439 LC |
438 | @item |
439 | Make @code{root}'s profile available under @file{~/.guix-profile}: | |
440 | ||
441 | @example | |
442 | # ln -sf /var/guix/profiles/per-user/root/guix-profile \ | |
443 | ~root/.guix-profile | |
444 | @end example | |
445 | ||
43c33047 LC |
446 | @item |
447 | Create the group and user accounts for build users as explained below | |
448 | (@pxref{Build Environment Setup}). | |
449 | ||
09722b11 | 450 | @item |
bf98aea9 | 451 | Run the daemon, and set it to automatically start on boot. |
c8e26887 | 452 | |
bf98aea9 LC |
453 | If your host distro uses the systemd init system, this can be achieved |
454 | with these commands: | |
c8e26887 GC |
455 | |
456 | @example | |
b7230de5 | 457 | # ln -s ~root/.guix-profile/lib/systemd/system/guix-daemon.service \ |
c8e26887 GC |
458 | /etc/systemd/system/ |
459 | # systemctl start guix-daemon && systemctl enable guix-daemon | |
460 | @end example | |
461 | ||
462 | If your host distro uses the Upstart init system: | |
09722b11 LC |
463 | |
464 | @example | |
b7230de5 | 465 | # ln -s ~root/.guix-profile/lib/upstart/system/guix-daemon.conf /etc/init/ |
bf98aea9 | 466 | # start guix-daemon |
09722b11 LC |
467 | @end example |
468 | ||
c8e26887 GC |
469 | Otherwise, you can still start the daemon manually with: |
470 | ||
471 | @example | |
472 | # ~root/.guix-profile/bin/guix-daemon --build-users-group=guixbuild | |
473 | @end example | |
d2825c96 | 474 | |
09722b11 LC |
475 | @item |
476 | Make the @command{guix} command available to other users on the machine, | |
477 | for instance with: | |
478 | ||
479 | @example | |
480 | # mkdir -p /usr/local/bin | |
481 | # cd /usr/local/bin | |
d72d05f9 | 482 | # ln -s /var/guix/profiles/per-user/root/guix-profile/bin/guix |
09722b11 | 483 | @end example |
39f8ed14 | 484 | |
aca738f3 LC |
485 | It is also a good idea to make the Info version of this manual available |
486 | there: | |
487 | ||
488 | @example | |
489 | # mkdir -p /usr/local/share/info | |
490 | # cd /usr/local/share/info | |
491 | # for i in /var/guix/profiles/per-user/root/guix-profile/share/info/* ; | |
492 | do ln -s $i ; done | |
493 | @end example | |
494 | ||
495 | That way, assuming @file{/usr/local/share/info} is in the search path, | |
496 | running @command{info guix} will open this manual (@pxref{Other Info | |
497 | Directories,,, texinfo, GNU Texinfo}, for more details on changing the | |
498 | Info search path.) | |
499 | ||
39f8ed14 | 500 | @item |
e32171ee | 501 | @cindex substitutes, authorization thereof |
df061d07 LC |
502 | To use substitutes from @code{hydra.gnu.org} or one of its mirrors |
503 | (@pxref{Substitutes}), authorize them: | |
39f8ed14 LC |
504 | |
505 | @example | |
7acd3439 | 506 | # guix archive --authorize < ~root/.guix-profile/share/guix/hydra.gnu.org.pub |
39f8ed14 | 507 | @end example |
09722b11 LC |
508 | @end enumerate |
509 | ||
bf98aea9 | 510 | This completes root-level install of Guix. Each user will need to |
7414de0a | 511 | perform additional steps to make their Guix environment ready for use, |
c8e26887 | 512 | @pxref{Application Setup}. |
09722b11 | 513 | |
c8e26887 GC |
514 | You can confirm that Guix is working by installing a sample package into |
515 | the root profile: | |
09722b11 LC |
516 | |
517 | @example | |
c8e26887 | 518 | # guix package -i hello |
09722b11 LC |
519 | @end example |
520 | ||
c8e26887 GC |
521 | The @code{guix} package must remain available in @code{root}'s profile, |
522 | or it would become subject to garbage collection---in which case you | |
523 | would find yourself badly handicapped by the lack of the @command{guix} | |
bf98aea9 LC |
524 | command. In other words, do not remove @code{guix} by running |
525 | @code{guix package -r guix}. | |
526 | ||
527 | The binary installation tarball can be (re)produced and verified simply | |
528 | by running the following command in the Guix source tree: | |
529 | ||
530 | @example | |
531 | make guix-binary.@var{system}.tar.xz | |
532 | @end example | |
c8e26887 | 533 | |
09722b11 | 534 | |
bd5e766b LC |
535 | @node Requirements |
536 | @section Requirements | |
537 | ||
09722b11 LC |
538 | This section lists requirements when building Guix from source. The |
539 | build procedure for Guix is the same as for other GNU software, and is | |
540 | not covered here. Please see the files @file{README} and @file{INSTALL} | |
541 | in the Guix source tree for additional details. | |
542 | ||
bd5e766b LC |
543 | GNU Guix depends on the following packages: |
544 | ||
545 | @itemize | |
47c66da0 | 546 | @item @url{http://gnu.org/software/guile/, GNU Guile}, version 2.0.7 or later; |
288dca55 | 547 | @item @url{http://gnupg.org/, GNU libgcrypt}; |
f0b98b84 | 548 | @item @url{http://www.gnu.org/software/make/, GNU Make}. |
8a96bd4b ID |
549 | @end itemize |
550 | ||
551 | The following dependencies are optional: | |
552 | ||
553 | @itemize | |
9b7bd1b1 LC |
554 | @item |
555 | Installing @uref{http://gnutls.org/, GnuTLS-Guile} will allow you to | |
556 | access @code{https} URLs for substitutes, which is highly recommended | |
557 | (@pxref{Substitutes}). It also allows you to access HTTPS URLs with the | |
558 | @command{guix download} command (@pxref{Invoking guix download}), the | |
559 | @command{guix import pypi} command, and the @command{guix import cpan} | |
560 | command. @xref{Guile Preparations, how to install the GnuTLS bindings | |
561 | for Guile,, gnutls-guile, GnuTLS-Guile}. | |
562 | ||
288dca55 | 563 | @item |
8a96bd4b | 564 | Installing |
288dca55 | 565 | @url{http://savannah.nongnu.org/projects/guile-json/, Guile-JSON} will |
2f7d2d91 LC |
566 | allow you to use the @command{guix import pypi} command (@pxref{Invoking |
567 | guix import}). It is of | |
288dca55 | 568 | interest primarily for developers and not for casual users. |
4591c02e | 569 | |
21531add LC |
570 | @item |
571 | @c Note: We need at least 0.10.2 for 'channel-send-eof'. | |
572 | Support for build offloading (@pxref{Daemon Offload Setup}) depends on | |
573 | @uref{https://github.com/artyom-poptsov/guile-ssh, Guile-SSH}, | |
574 | version 0.10.2 or later. | |
575 | ||
4591c02e LC |
576 | @item |
577 | When @url{http://zlib.net, zlib} is available, @command{guix publish} | |
578 | can compress build byproducts (@pxref{Invoking guix publish}). | |
bd5e766b LC |
579 | @end itemize |
580 | ||
581 | Unless @code{--disable-daemon} was passed to @command{configure}, the | |
582 | following packages are also needed: | |
583 | ||
584 | @itemize | |
368d08f7 LC |
585 | @item @url{http://sqlite.org, SQLite 3}; |
586 | @item @url{http://www.bzip.org, libbz2}; | |
587 | @item @url{http://gcc.gnu.org, GCC's g++}, with support for the | |
588 | C++11 standard. | |
bd5e766b LC |
589 | @end itemize |
590 | ||
e32171ee | 591 | @cindex state directory |
ef5f5c86 LC |
592 | When configuring Guix on a system that already has a Guix installation, |
593 | be sure to specify the same state directory as the existing installation | |
594 | using the @code{--localstatedir} option of the @command{configure} | |
595 | script (@pxref{Directory Variables, @code{localstatedir},, standards, | |
596 | GNU Coding Standards}). The @command{configure} script protects against | |
597 | unintended misconfiguration of @var{localstatedir} so you do not | |
598 | inadvertently corrupt your store (@pxref{The Store}). | |
599 | ||
e32171ee | 600 | @cindex Nix, compatibility |
4bfc4ea3 NK |
601 | When a working installation of @url{http://nixos.org/nix/, the Nix package |
602 | manager} is available, you | |
bd5e766b | 603 | can instead configure Guix with @code{--disable-daemon}. In that case, |
4bfc4ea3 | 604 | Nix replaces the three dependencies above. |
bd5e766b | 605 | |
b22a12fd LC |
606 | Guix is compatible with Nix, so it is possible to share the same store |
607 | between both. To do so, you must pass @command{configure} not only the | |
608 | same @code{--with-store-dir} value, but also the same | |
4bfc4ea3 NK |
609 | @code{--localstatedir} value. The latter is essential because it |
610 | specifies where the database that stores metadata about the store is | |
834129e0 | 611 | located, among other things. The default values for Nix are |
b22a12fd | 612 | @code{--with-store-dir=/nix/store} and @code{--localstatedir=/nix/var}. |
4bfc4ea3 NK |
613 | Note that @code{--disable-daemon} is not required if |
614 | your goal is to share the store with Nix. | |
b22a12fd | 615 | |
ec0339cd LC |
616 | @node Running the Test Suite |
617 | @section Running the Test Suite | |
618 | ||
e32171ee | 619 | @cindex test suite |
ec0339cd LC |
620 | After a successful @command{configure} and @code{make} run, it is a good |
621 | idea to run the test suite. It can help catch issues with the setup or | |
622 | environment, or bugs in Guix itself---and really, reporting test | |
623 | failures is a good way to help improve the software. To run the test | |
624 | suite, type: | |
625 | ||
626 | @example | |
627 | make check | |
628 | @end example | |
629 | ||
630 | Test cases can run in parallel: you can use the @code{-j} option of | |
631 | GNU@tie{}make to speed things up. The first run may take a few minutes | |
632 | on a recent machine; subsequent runs will be faster because the store | |
633 | that is created for test purposes will already have various things in | |
634 | cache. | |
635 | ||
a887fd8d LC |
636 | It is also possible to run a subset of the tests by defining the |
637 | @code{TESTS} makefile variable as in this example: | |
638 | ||
639 | @example | |
640 | make check TESTS="tests/store.scm tests/cpio.scm" | |
641 | @end example | |
642 | ||
a9edb211 ML |
643 | By default, tests results are displayed at a file level. In order to |
644 | see the details of every individual test cases, it is possible to define | |
645 | the @code{SCM_LOG_DRIVER_FLAGS} makefile variable as in this example: | |
646 | ||
647 | @example | |
648 | make check TESTS="tests/base64.scm" SCM_LOG_DRIVER_FLAGS="--brief=no" | |
649 | @end example | |
650 | ||
ec0339cd | 651 | Upon failure, please email @email{bug-guix@@gnu.org} and attach the |
a9edb211 ML |
652 | @file{test-suite.log} file. Please specify the Guix version being used |
653 | as well as version numbers of the dependencies (@pxref{Requirements}) in | |
654 | your message. | |
ec0339cd | 655 | |
0a2f2848 LC |
656 | Guix also comes with a whole-system test suite that tests complete |
657 | GuixSD operating system instances. It can only run on systems where | |
658 | Guix is already installed, using: | |
659 | ||
660 | @example | |
661 | make check-system | |
662 | @end example | |
663 | ||
664 | @noindent | |
665 | or, again, by defining @code{TESTS} to select a subset of tests to run: | |
666 | ||
667 | @example | |
668 | make check-system TESTS="basic mcron" | |
669 | @end example | |
670 | ||
671 | These system tests are defined in the @code{(gnu tests @dots{})} | |
672 | modules. They work by running the operating systems under test with | |
673 | lightweight instrumentation in a virtual machine (VM). They can be | |
674 | computationally intensive or rather cheap, depending on whether | |
675 | substitutes are available for their dependencies (@pxref{Substitutes}). | |
676 | Some of them require a lot of storage space to hold VM images. | |
677 | ||
678 | Again in case of test failures, please send @email{bug-guix@@gnu.org} | |
679 | all the details. | |
680 | ||
bd5e766b LC |
681 | @node Setting Up the Daemon |
682 | @section Setting Up the Daemon | |
683 | ||
684 | @cindex daemon | |
685 | Operations such as building a package or running the garbage collector | |
49e6291a | 686 | are all performed by a specialized process, the @dfn{build daemon}, on |
bd5e766b LC |
687 | behalf of clients. Only the daemon may access the store and its |
688 | associated database. Thus, any operation that manipulates the store | |
689 | goes through the daemon. For instance, command-line tools such as | |
e49951eb | 690 | @command{guix package} and @command{guix build} communicate with the |
bd5e766b LC |
691 | daemon (@i{via} remote procedure calls) to instruct it what to do. |
692 | ||
49e6291a | 693 | The following sections explain how to prepare the build daemon's |
f97c9175 | 694 | environment. See also @ref{Substitutes}, for information on how to allow |
225dafde | 695 | the daemon to download pre-built binaries. |
49e6291a LC |
696 | |
697 | @menu | |
698 | * Build Environment Setup:: Preparing the isolated build environment. | |
699 | * Daemon Offload Setup:: Offloading builds to remote machines. | |
700 | @end menu | |
701 | ||
702 | @node Build Environment Setup | |
703 | @subsection Build Environment Setup | |
704 | ||
e32171ee | 705 | @cindex build environment |
bd5e766b LC |
706 | In a standard multi-user setup, Guix and its daemon---the |
707 | @command{guix-daemon} program---are installed by the system | |
834129e0 | 708 | administrator; @file{/gnu/store} is owned by @code{root} and |
bd5e766b LC |
709 | @command{guix-daemon} runs as @code{root}. Unprivileged users may use |
710 | Guix tools to build packages or otherwise access the store, and the | |
711 | daemon will do it on their behalf, ensuring that the store is kept in a | |
712 | consistent state, and allowing built packages to be shared among users. | |
713 | ||
714 | @cindex build users | |
715 | When @command{guix-daemon} runs as @code{root}, you may not want package | |
716 | build processes themselves to run as @code{root} too, for obvious | |
717 | security reasons. To avoid that, a special pool of @dfn{build users} | |
718 | should be created for use by build processes started by the daemon. | |
719 | These build users need not have a shell and a home directory: they will | |
720 | just be used when the daemon drops @code{root} privileges in build | |
721 | processes. Having several such users allows the daemon to launch | |
722 | distinct build processes under separate UIDs, which guarantees that they | |
723 | do not interfere with each other---an essential feature since builds are | |
724 | regarded as pure functions (@pxref{Introduction}). | |
725 | ||
726 | On a GNU/Linux system, a build user pool may be created like this (using | |
727 | Bash syntax and the @code{shadow} commands): | |
728 | ||
091196b3 LC |
729 | @c See http://lists.gnu.org/archive/html/bug-guix/2013-01/msg00239.html |
730 | @c for why `-G' is needed. | |
bd5e766b | 731 | @example |
cfc149dc LC |
732 | # groupadd --system guixbuild |
733 | # for i in `seq -w 1 10`; | |
bd5e766b | 734 | do |
cfc149dc LC |
735 | useradd -g guixbuild -G guixbuild \ |
736 | -d /var/empty -s `which nologin` \ | |
737 | -c "Guix build user $i" --system \ | |
738 | guixbuilder$i; | |
bd5e766b LC |
739 | done |
740 | @end example | |
741 | ||
742 | @noindent | |
54eb03ab LC |
743 | The number of build users determines how many build jobs may run in |
744 | parallel, as specified by the @option{--max-jobs} option | |
eca69fc0 LC |
745 | (@pxref{Invoking guix-daemon, @option{--max-jobs}}). To use |
746 | @command{guix system vm} and related commands, you may need to add the | |
747 | build users to the @code{kvm} group so they can access @file{/dev/kvm}, | |
748 | using @code{-G guixbuild,kvm} instead of @code{-G guixbuild} | |
749 | (@pxref{Invoking guix system}). | |
750 | ||
751 | The @code{guix-daemon} program may then be run as @code{root} with the | |
d2825c96 LC |
752 | following command@footnote{If your machine uses the systemd init system, |
753 | dropping the @file{@var{prefix}/lib/systemd/system/guix-daemon.service} | |
754 | file in @file{/etc/systemd/system} will ensure that | |
ad227484 MDRS |
755 | @command{guix-daemon} is automatically started. Similarly, if your |
756 | machine uses the Upstart init system, drop the | |
757 | @file{@var{prefix}/lib/upstart/system/guix-daemon.conf} | |
758 | file in @file{/etc/init}.}: | |
bd5e766b LC |
759 | |
760 | @example | |
cfc149dc | 761 | # guix-daemon --build-users-group=guixbuild |
bd5e766b LC |
762 | @end example |
763 | ||
e900c503 | 764 | @cindex chroot |
b095792f LC |
765 | @noindent |
766 | This way, the daemon starts build processes in a chroot, under one of | |
cfc149dc | 767 | the @code{guixbuilder} users. On GNU/Linux, by default, the chroot |
6dc99317 LC |
768 | environment contains nothing but: |
769 | ||
770 | @c Keep this list in sync with libstore/build.cc! ----------------------- | |
771 | @itemize | |
772 | @item | |
4743a4da LC |
773 | a minimal @code{/dev} directory, created mostly independently from the |
774 | host @code{/dev}@footnote{``Mostly'', because while the set of files | |
775 | that appear in the chroot's @code{/dev} is fixed, most of these files | |
776 | can only be created if the host has them.}; | |
777 | ||
778 | @item | |
f97c9175 | 779 | the @code{/proc} directory; it only shows the processes of the container |
4743a4da | 780 | since a separate PID name space is used; |
6dc99317 LC |
781 | |
782 | @item | |
783 | @file{/etc/passwd} with an entry for the current user and an entry for | |
784 | user @file{nobody}; | |
785 | ||
786 | @item | |
787 | @file{/etc/group} with an entry for the user's group; | |
788 | ||
789 | @item | |
790 | @file{/etc/hosts} with an entry that maps @code{localhost} to | |
791 | @code{127.0.0.1}; | |
792 | ||
793 | @item | |
794 | a writable @file{/tmp} directory. | |
795 | @end itemize | |
b095792f | 796 | |
cb960102 ED |
797 | You can influence the directory where the daemon stores build trees |
798 | @i{via} the @code{TMPDIR} environment variable. However, the build tree | |
f97c9175 | 799 | within the chroot is always called @file{/tmp/guix-build-@var{name}.drv-0}, |
cb960102 ED |
800 | where @var{name} is the derivation name---e.g., @code{coreutils-8.24}. |
801 | This way, the value of @code{TMPDIR} does not leak inside build | |
802 | environments, which avoids discrepancies in cases where build processes | |
803 | capture the name of their build tree. | |
804 | ||
e0c941fe LC |
805 | @vindex http_proxy |
806 | The daemon also honors the @code{http_proxy} environment variable for | |
807 | HTTP downloads it performs, be it for fixed-output derivations | |
808 | (@pxref{Derivations}) or for substitutes (@pxref{Substitutes}). | |
809 | ||
1e2644bb LC |
810 | If you are installing Guix as an unprivileged user, it is still possible |
811 | to run @command{guix-daemon} provided you pass @code{--disable-chroot}. | |
812 | However, build processes will not be isolated from one another, and not | |
813 | from the rest of the system. Thus, build processes may interfere with | |
814 | each other, and may access programs, libraries, and other files | |
815 | available on the system---making it much harder to view them as | |
816 | @emph{pure} functions. | |
bd5e766b | 817 | |
49e6291a LC |
818 | |
819 | @node Daemon Offload Setup | |
820 | @subsection Using the Offload Facility | |
821 | ||
822 | @cindex offloading | |
4ec2e92d | 823 | @cindex build hook |
21531add LC |
824 | When desired, the build daemon can @dfn{offload} derivation builds to |
825 | other machines running Guix, using the @code{offload} @dfn{build | |
826 | hook}@footnote{This feature is available only when | |
827 | @uref{https://github.com/artyom-poptsov/guile-ssh, Guile-SSH} is | |
828 | present.}. When that | |
49e6291a | 829 | feature is enabled, a list of user-specified build machines is read from |
f97c9175 | 830 | @file{/etc/guix/machines.scm}; every time a build is requested, for |
49e6291a | 831 | instance via @code{guix build}, the daemon attempts to offload it to one |
f97c9175 | 832 | of the machines that satisfy the constraints of the derivation, in |
49e6291a LC |
833 | particular its system type---e.g., @file{x86_64-linux}. Missing |
834 | prerequisites for the build are copied over SSH to the target machine, | |
835 | which then proceeds with the build; upon success the output(s) of the | |
836 | build are copied back to the initial machine. | |
837 | ||
4ec2e92d | 838 | The @file{/etc/guix/machines.scm} file typically looks like this: |
49e6291a LC |
839 | |
840 | @example | |
841 | (list (build-machine | |
842 | (name "eightysix.example.org") | |
843 | (system "x86_64-linux") | |
21531add | 844 | (host-key "ssh-ed25519 AAAAC3Nza@dots{}") |
49e6291a | 845 | (user "bob") |
21531add | 846 | (speed 2.)) ;incredibly fast! |
49e6291a LC |
847 | |
848 | (build-machine | |
849 | (name "meeps.example.org") | |
850 | (system "mips64el-linux") | |
21531add | 851 | (host-key "ssh-rsa AAAAB3Nza@dots{}") |
49e6291a LC |
852 | (user "alice") |
853 | (private-key | |
854 | (string-append (getenv "HOME") | |
21531add | 855 | "/.ssh/identity-for-guix")))) |
49e6291a LC |
856 | @end example |
857 | ||
858 | @noindent | |
859 | In the example above we specify a list of two build machines, one for | |
860 | the @code{x86_64} architecture and one for the @code{mips64el} | |
4ec2e92d LC |
861 | architecture. |
862 | ||
863 | In fact, this file is---not surprisingly!---a Scheme file that is | |
864 | evaluated when the @code{offload} hook is started. Its return value | |
865 | must be a list of @code{build-machine} objects. While this example | |
866 | shows a fixed list of build machines, one could imagine, say, using | |
867 | DNS-SD to return a list of potential build machines discovered in the | |
868 | local network (@pxref{Introduction, Guile-Avahi,, guile-avahi, Using | |
c678a4ee LC |
869 | Avahi in Guile Scheme Programs}). The @code{build-machine} data type is |
870 | detailed below. | |
4ec2e92d | 871 | |
c678a4ee | 872 | @deftp {Data Type} build-machine |
f97c9175 AE |
873 | This data type represents build machines to which the daemon may offload |
874 | builds. The important fields are: | |
49e6291a LC |
875 | |
876 | @table @code | |
877 | ||
878 | @item name | |
f97c9175 | 879 | The host name of the remote machine. |
49e6291a LC |
880 | |
881 | @item system | |
f97c9175 | 882 | The system type of the remote machine---e.g., @code{"x86_64-linux"}. |
49e6291a LC |
883 | |
884 | @item user | |
885 | The user account to use when connecting to the remote machine over SSH. | |
886 | Note that the SSH key pair must @emph{not} be passphrase-protected, to | |
887 | allow non-interactive logins. | |
888 | ||
21531add LC |
889 | @item host-key |
890 | This must be the machine's SSH @dfn{public host key} in OpenSSH format. | |
891 | This is used to authenticate the machine when we connect to it. It is a | |
892 | long string that looks like this: | |
893 | ||
894 | @example | |
895 | ssh-ed25519 AAAAC3NzaC@dots{}mde+UhL hint@@example.org | |
896 | @end example | |
897 | ||
898 | If the machine is running the OpenSSH daemon, @command{sshd}, the host | |
899 | key can be found in a file such as | |
900 | @file{/etc/ssh/ssh_host_ed25519_key.pub}. | |
901 | ||
902 | If the machine is running the SSH daemon of GNU@tie{}lsh, | |
903 | @command{lshd}, the host key is in @file{/etc/lsh/host-key.pub} or a | |
904 | similar file. It can be converted to the OpenSSH format using | |
905 | @command{lsh-export-key} (@pxref{Converting keys,,, lsh, LSH Manual}): | |
906 | ||
907 | @example | |
908 | $ lsh-export-key --openssh < /etc/lsh/host-key.pub | |
909 | ssh-rsa AAAAB3NzaC1yc2EAAAAEOp8FoQAAAQEAs1eB46LV@dots{} | |
910 | @end example | |
911 | ||
49e6291a LC |
912 | @end table |
913 | ||
4ec2e92d | 914 | A number of optional fields may be specified: |
49e6291a | 915 | |
21531add | 916 | @table @asis |
49e6291a | 917 | |
21531add LC |
918 | @item @code{port} (default: @code{22}) |
919 | Port number of SSH server on the machine. | |
cecd72d5 | 920 | |
21531add LC |
921 | @item @code{private-key} (default: @file{~/.ssh/id_rsa}) |
922 | The SSH private key file to use when connecting to the machine, in | |
923 | OpenSSH format. | |
49e6291a | 924 | |
1d48cf94 LC |
925 | @item @code{compression} (default: @code{"zlib@@openssh.com,zlib"}) |
926 | @itemx @code{compression-level} (default: @code{3}) | |
927 | The SSH-level compression methods and compression level requested. | |
928 | ||
929 | Note that offloading relies on SSH compression to reduce bandwidth usage | |
930 | when transferring files to and from build machines. | |
931 | ||
cf283dd9 LC |
932 | @item @code{daemon-socket} (default: @code{"/var/guix/daemon-socket/socket"}) |
933 | File name of the Unix-domain socket @command{guix-daemon} is listening | |
934 | to on that machine. | |
c4fdfd6f | 935 | |
21531add LC |
936 | @item @code{parallel-builds} (default: @code{1}) |
937 | The number of builds that may run in parallel on the machine. | |
49e6291a | 938 | |
21531add | 939 | @item @code{speed} (default: @code{1.0}) |
49e6291a LC |
940 | A ``relative speed factor''. The offload scheduler will tend to prefer |
941 | machines with a higher speed factor. | |
942 | ||
21531add | 943 | @item @code{features} (default: @code{'()}) |
49e6291a LC |
944 | A list of strings denoting specific features supported by the machine. |
945 | An example is @code{"kvm"} for machines that have the KVM Linux modules | |
946 | and corresponding hardware support. Derivations can request features by | |
947 | name, and they will be scheduled on matching build machines. | |
948 | ||
949 | @end table | |
c678a4ee | 950 | @end deftp |
49e6291a | 951 | |
aebaee95 LC |
952 | The @code{guile} command must be in the search path on the build |
953 | machines. In addition, the Guix modules must be in | |
c4fdfd6f LC |
954 | @code{$GUILE_LOAD_PATH} on the build machine---you can check whether |
955 | this is the case by running: | |
956 | ||
957 | @example | |
21531add | 958 | ssh build-machine guile -c "'(use-modules (guix config))'" |
c4fdfd6f | 959 | @end example |
49e6291a | 960 | |
f97c9175 | 961 | There is one last thing to do once @file{machines.scm} is in place. As |
49e6291a | 962 | explained above, when offloading, files are transferred back and forth |
c4fdfd6f LC |
963 | between the machine stores. For this to work, you first need to |
964 | generate a key pair on each machine to allow the daemon to export signed | |
965 | archives of files from the store (@pxref{Invoking guix archive}): | |
49e6291a LC |
966 | |
967 | @example | |
968 | # guix archive --generate-key | |
969 | @end example | |
970 | ||
971 | @noindent | |
c4fdfd6f LC |
972 | Each build machine must authorize the key of the master machine so that |
973 | it accepts store items it receives from the master: | |
974 | ||
975 | @example | |
976 | # guix archive --authorize < master-public-key.txt | |
977 | @end example | |
978 | ||
979 | @noindent | |
980 | Likewise, the master machine must authorize the key of each build machine. | |
981 | ||
982 | All the fuss with keys is here to express pairwise mutual trust | |
983 | relations between the master and the build machines. Concretely, when | |
984 | the master receives files from a build machine (and @i{vice versa}), its | |
985 | build daemon can make sure they are genuine, have not been tampered | |
986 | with, and that they are signed by an authorized key. | |
49e6291a | 987 | |
aebaee95 LC |
988 | @cindex offload test |
989 | To test whether your setup is operational, run this command on the | |
990 | master node: | |
991 | ||
992 | @example | |
993 | # guix offload test | |
994 | @end example | |
995 | ||
996 | This will attempt to connect to each of the build machines specified in | |
997 | @file{/etc/guix/machines.scm}, make sure Guile and the Guix modules are | |
998 | available on each machine, attempt to export to the machine and import | |
999 | from it, and report any error in the process. | |
1000 | ||
1001 | If you want to test a different machine file, just specify it on the | |
1002 | command line: | |
1003 | ||
1004 | @example | |
1005 | # guix offload test machines-qualif.scm | |
1006 | @end example | |
1007 | ||
27991c97 LC |
1008 | Last, you can test the subset of the machines whose name matches a |
1009 | regular expression like this: | |
1010 | ||
1011 | @example | |
1012 | # guix offload test machines.scm '\.gnu\.org$' | |
1013 | @end example | |
49e6291a | 1014 | |
bd5e766b LC |
1015 | @node Invoking guix-daemon |
1016 | @section Invoking @command{guix-daemon} | |
1017 | ||
1018 | The @command{guix-daemon} program implements all the functionality to | |
1019 | access the store. This includes launching build processes, running the | |
1020 | garbage collector, querying the availability of a build result, etc. It | |
1021 | is normally run as @code{root} like this: | |
1022 | ||
1023 | @example | |
cfc149dc | 1024 | # guix-daemon --build-users-group=guixbuild |
bd5e766b LC |
1025 | @end example |
1026 | ||
1027 | @noindent | |
081145cf | 1028 | For details on how to set it up, @pxref{Setting Up the Daemon}. |
bd5e766b | 1029 | |
e900c503 LC |
1030 | @cindex chroot |
1031 | @cindex container, build environment | |
1032 | @cindex build environment | |
1033 | @cindex reproducible builds | |
bd5e766b LC |
1034 | By default, @command{guix-daemon} launches build processes under |
1035 | different UIDs, taken from the build group specified with | |
1036 | @code{--build-users-group}. In addition, each build process is run in a | |
1037 | chroot environment that only contains the subset of the store that the | |
1038 | build process depends on, as specified by its derivation | |
1039 | (@pxref{Programming Interface, derivation}), plus a set of specific | |
1040 | system directories. By default, the latter contains @file{/dev} and | |
e900c503 LC |
1041 | @file{/dev/pts}. Furthermore, on GNU/Linux, the build environment is a |
1042 | @dfn{container}: in addition to having its own file system tree, it has | |
1043 | a separate mount name space, its own PID name space, network name space, | |
1044 | etc. This helps achieve reproducible builds (@pxref{Features}). | |
bd5e766b | 1045 | |
cbc538fe LC |
1046 | When the daemon performs a build on behalf of the user, it creates a |
1047 | build directory under @file{/tmp} or under the directory specified by | |
1048 | its @code{TMPDIR} environment variable; this directory is shared with | |
1049 | the container for the duration of the build. Be aware that using a | |
1050 | directory other than @file{/tmp} can affect build results---for example, | |
1051 | with a longer directory name, a build process that uses Unix-domain | |
1052 | sockets might hit the name length limitation for @code{sun_path}, which | |
1053 | it would otherwise not hit. | |
1054 | ||
1055 | The build directory is automatically deleted upon completion, unless the | |
1056 | build failed and the client specified @option{--keep-failed} | |
1057 | (@pxref{Invoking guix build, @option{--keep-failed}}). | |
1058 | ||
bd5e766b LC |
1059 | The following command-line options are supported: |
1060 | ||
1061 | @table @code | |
1062 | @item --build-users-group=@var{group} | |
1063 | Take users from @var{group} to run build processes (@pxref{Setting Up | |
1064 | the Daemon, build users}). | |
1065 | ||
6858f9d1 | 1066 | @item --no-substitutes |
b5385b52 | 1067 | @cindex substitutes |
6858f9d1 | 1068 | Do not use substitutes for build products. That is, always build things |
c4202d60 LC |
1069 | locally instead of allowing downloads of pre-built binaries |
1070 | (@pxref{Substitutes}). | |
6858f9d1 | 1071 | |
b5385b52 LC |
1072 | By default substitutes are used, unless the client---such as the |
1073 | @command{guix package} command---is explicitly invoked with | |
1074 | @code{--no-substitutes}. | |
1075 | ||
1076 | When the daemon runs with @code{--no-substitutes}, clients can still | |
1077 | explicitly enable substitution @i{via} the @code{set-build-options} | |
1078 | remote procedure call (@pxref{The Store}). | |
1079 | ||
9176607e | 1080 | @item --substitute-urls=@var{urls} |
f8a8e0fe | 1081 | @anchor{daemon-substitute-urls} |
9176607e | 1082 | Consider @var{urls} the default whitespace-separated list of substitute |
df061d07 LC |
1083 | source URLs. When this option is omitted, |
1084 | @indicateurl{https://mirror.hydra.gnu.org https://hydra.gnu.org} is used | |
1085 | (@code{mirror.hydra.gnu.org} is a mirror of @code{hydra.gnu.org}). | |
9176607e LC |
1086 | |
1087 | This means that substitutes may be downloaded from @var{urls}, as long | |
1088 | as they are signed by a trusted signature (@pxref{Substitutes}). | |
1089 | ||
4ec2e92d LC |
1090 | @cindex build hook |
1091 | @item --no-build-hook | |
1092 | Do not use the @dfn{build hook}. | |
1093 | ||
1094 | The build hook is a helper program that the daemon can start and to | |
1095 | which it submits build requests. This mechanism is used to offload | |
1096 | builds to other machines (@pxref{Daemon Offload Setup}). | |
1097 | ||
bd5e766b LC |
1098 | @item --cache-failures |
1099 | Cache build failures. By default, only successful builds are cached. | |
1100 | ||
30d9aa54 LC |
1101 | When this option is used, @command{guix gc --list-failures} can be used |
1102 | to query the set of store items marked as failed; @command{guix gc | |
1103 | --clear-failures} removes store items from the set of cached failures. | |
1104 | @xref{Invoking guix gc}. | |
1105 | ||
bd5e766b LC |
1106 | @item --cores=@var{n} |
1107 | @itemx -c @var{n} | |
1108 | Use @var{n} CPU cores to build each derivation; @code{0} means as many | |
1109 | as available. | |
1110 | ||
6efc160e | 1111 | The default value is @code{0}, but it may be overridden by clients, such |
e49951eb MW |
1112 | as the @code{--cores} option of @command{guix build} (@pxref{Invoking |
1113 | guix build}). | |
bd5e766b LC |
1114 | |
1115 | The effect is to define the @code{NIX_BUILD_CORES} environment variable | |
1116 | in the build process, which can then use it to exploit internal | |
1117 | parallelism---for instance, by running @code{make -j$NIX_BUILD_CORES}. | |
1118 | ||
1119 | @item --max-jobs=@var{n} | |
1120 | @itemx -M @var{n} | |
1121 | Allow at most @var{n} build jobs in parallel. The default value is | |
f6526eb3 LC |
1122 | @code{1}. Setting it to @code{0} means that no builds will be performed |
1123 | locally; instead, the daemon will offload builds (@pxref{Daemon Offload | |
1124 | Setup}), or simply fail. | |
bd5e766b | 1125 | |
ecf84b7c LC |
1126 | @item --rounds=@var{N} |
1127 | Build each derivation @var{n} times in a row, and raise an error if | |
1128 | consecutive build results are not bit-for-bit identical. Note that this | |
1129 | setting can be overridden by clients such as @command{guix build} | |
1130 | (@pxref{Invoking guix build}). | |
1131 | ||
b4528110 ED |
1132 | When used in conjunction with @option{--keep-failed}, the differing |
1133 | output is kept in the store, under @file{/gnu/store/@dots{}-check}. | |
1134 | This makes it easy to look for differences between the two results. | |
1135 | ||
bd5e766b LC |
1136 | @item --debug |
1137 | Produce debugging output. | |
1138 | ||
1139 | This is useful to debug daemon start-up issues, but then it may be | |
1140 | overridden by clients, for example the @code{--verbosity} option of | |
e49951eb | 1141 | @command{guix build} (@pxref{Invoking guix build}). |
bd5e766b LC |
1142 | |
1143 | @item --chroot-directory=@var{dir} | |
1144 | Add @var{dir} to the build chroot. | |
1145 | ||
1146 | Doing this may change the result of build processes---for instance if | |
1147 | they use optional dependencies found in @var{dir} when it is available, | |
1148 | and not otherwise. For that reason, it is not recommended to do so. | |
1149 | Instead, make sure that each derivation declares all the inputs that it | |
1150 | needs. | |
1151 | ||
1152 | @item --disable-chroot | |
1153 | Disable chroot builds. | |
1154 | ||
1155 | Using this option is not recommended since, again, it would allow build | |
1e2644bb LC |
1156 | processes to gain access to undeclared dependencies. It is necessary, |
1157 | though, when @command{guix-daemon} is running under an unprivileged user | |
1158 | account. | |
bd5e766b LC |
1159 | |
1160 | @item --disable-log-compression | |
1161 | Disable compression of the build logs. | |
1162 | ||
1da983b9 LC |
1163 | Unless @code{--lose-logs} is used, all the build logs are kept in the |
1164 | @var{localstatedir}. To save space, the daemon automatically compresses | |
1165 | them with bzip2 by default. This option disables that. | |
1166 | ||
ab3893d7 LC |
1167 | @item --disable-deduplication |
1168 | @cindex deduplication | |
bd5e766b LC |
1169 | Disable automatic file ``deduplication'' in the store. |
1170 | ||
1da983b9 | 1171 | By default, files added to the store are automatically ``deduplicated'': |
ab3893d7 LC |
1172 | if a newly added file is identical to another one found in the store, |
1173 | the daemon makes the new file a hard link to the other file. This can | |
4988dd40 | 1174 | noticeably reduce disk usage, at the expense of slightly increased |
ab3893d7 LC |
1175 | input/output load at the end of a build process. This option disables |
1176 | this optimization. | |
1da983b9 | 1177 | |
6e37066e LC |
1178 | @item --gc-keep-outputs[=yes|no] |
1179 | Tell whether the garbage collector (GC) must keep outputs of live | |
1180 | derivations. | |
1181 | ||
1182 | When set to ``yes'', the GC will keep the outputs of any live derivation | |
1183 | available in the store---the @code{.drv} files. The default is ``no'', | |
1184 | meaning that derivation outputs are kept only if they are GC roots. | |
1185 | ||
1186 | @item --gc-keep-derivations[=yes|no] | |
1187 | Tell whether the garbage collector (GC) must keep derivations | |
1188 | corresponding to live outputs. | |
1189 | ||
1190 | When set to ``yes'', as is the case by default, the GC keeps | |
1191 | derivations---i.e., @code{.drv} files---as long as at least one of their | |
1192 | outputs is live. This allows users to keep track of the origins of | |
1193 | items in their store. Setting it to ``no'' saves a bit of disk space. | |
1194 | ||
1195 | Note that when both @code{--gc-keep-derivations} and | |
1196 | @code{--gc-keep-outputs} are used, the effect is to keep all the build | |
1197 | prerequisites (the sources, compiler, libraries, and other build-time | |
1198 | tools) of live objects in the store, regardless of whether these | |
1199 | prerequisites are live. This is convenient for developers since it | |
1200 | saves rebuilds or downloads. | |
1201 | ||
bd5e766b LC |
1202 | @item --impersonate-linux-2.6 |
1203 | On Linux-based systems, impersonate Linux 2.6. This means that the | |
1204 | kernel's @code{uname} system call will report 2.6 as the release number. | |
1205 | ||
1206 | This might be helpful to build programs that (usually wrongfully) depend | |
1207 | on the kernel version number. | |
1208 | ||
1209 | @item --lose-logs | |
1210 | Do not keep build logs. By default they are kept under | |
ce33631f | 1211 | @code{@var{localstatedir}/guix/log}. |
bd5e766b LC |
1212 | |
1213 | @item --system=@var{system} | |
1214 | Assume @var{system} as the current system type. By default it is the | |
1215 | architecture/kernel pair found at configure time, such as | |
1216 | @code{x86_64-linux}. | |
b8d2aa26 LC |
1217 | |
1218 | @item --listen=@var{socket} | |
1219 | Listen for connections on @var{socket}, the file name of a Unix-domain | |
1220 | socket. The default socket is | |
1221 | @file{@var{localstatedir}/daemon-socket/socket}. This option is only | |
1222 | useful in exceptional circumstances, such as if you need to run several | |
1223 | daemons on the same machine. | |
bd5e766b LC |
1224 | @end table |
1225 | ||
1226 | ||
0e2d0213 LC |
1227 | @node Application Setup |
1228 | @section Application Setup | |
1229 | ||
d23ef788 | 1230 | @cindex foreign distro |
85e57214 LC |
1231 | When using Guix on top of GNU/Linux distribution other than GuixSD---a |
1232 | so-called @dfn{foreign distro}---a few additional steps are needed to | |
1233 | get everything in place. Here are some of them. | |
0e2d0213 LC |
1234 | |
1235 | @subsection Locales | |
1236 | ||
5c3c1427 | 1237 | @anchor{locales-and-locpath} |
0e2d0213 | 1238 | @cindex locales, when not on GuixSD |
5c3c1427 | 1239 | @vindex LOCPATH |
85e57214 | 1240 | @vindex GUIX_LOCPATH |
f97c9175 AE |
1241 | Packages installed @i{via} Guix will not use the locale data of the |
1242 | host system. Instead, you must first install one of the locale packages | |
85e57214 LC |
1243 | available with Guix and then define the @code{GUIX_LOCPATH} environment |
1244 | variable: | |
0e2d0213 LC |
1245 | |
1246 | @example | |
1247 | $ guix package -i glibc-locales | |
85e57214 | 1248 | $ export GUIX_LOCPATH=$HOME/.guix-profile/lib/locale |
0e2d0213 LC |
1249 | @end example |
1250 | ||
1251 | Note that the @code{glibc-locales} package contains data for all the | |
1252 | locales supported by the GNU@tie{}libc and weighs in at around | |
f97c9175 | 1253 | 110@tie{}MiB. Alternatively, the @code{glibc-utf8-locales} is smaller but |
0e2d0213 LC |
1254 | limited to a few UTF-8 locales. |
1255 | ||
85e57214 LC |
1256 | The @code{GUIX_LOCPATH} variable plays a role similar to @code{LOCPATH} |
1257 | (@pxref{Locale Names, @code{LOCPATH},, libc, The GNU C Library Reference | |
1258 | Manual}). There are two important differences though: | |
1259 | ||
1260 | @enumerate | |
1261 | @item | |
f97c9175 | 1262 | @code{GUIX_LOCPATH} is honored only by the libc in Guix, and not by the libc |
85e57214 | 1263 | provided by foreign distros. Thus, using @code{GUIX_LOCPATH} allows you |
f97c9175 | 1264 | to make sure the programs of the foreign distro will not end up loading |
85e57214 LC |
1265 | incompatible locale data. |
1266 | ||
1267 | @item | |
1268 | libc suffixes each entry of @code{GUIX_LOCPATH} with @code{/X.Y}, where | |
1269 | @code{X.Y} is the libc version---e.g., @code{2.22}. This means that, | |
1270 | should your Guix profile contain a mixture of programs linked against | |
1271 | different libc version, each libc version will only try to load locale | |
1272 | data in the right format. | |
1273 | @end enumerate | |
1274 | ||
1275 | This is important because the locale data format used by different libc | |
1276 | versions may be incompatible. | |
1277 | ||
9a5187b6 LC |
1278 | @subsection Name Service Switch |
1279 | ||
1280 | @cindex name service switch, glibc | |
1281 | @cindex NSS (name service switch), glibc | |
1282 | @cindex nscd (name service caching daemon) | |
1283 | @cindex name service caching daemon (nscd) | |
1284 | When using Guix on a foreign distro, we @emph{strongly recommend} that | |
1285 | the system run the GNU C library's @dfn{name service cache daemon}, | |
1286 | @command{nscd}, which should be listening on the | |
1287 | @file{/var/run/nscd/socket} socket. Failing to do that, applications | |
1288 | installed with Guix may fail to look up host names or user accounts, or | |
1289 | may even crash. The next paragraphs explain why. | |
1290 | ||
1291 | @cindex @file{nsswitch.conf} | |
1292 | The GNU C library implements a @dfn{name service switch} (NSS), which is | |
1293 | an extensible mechanism for ``name lookups'' in general: host name | |
1294 | resolution, user accounts, and more (@pxref{Name Service Switch,,, libc, | |
1295 | The GNU C Library Reference Manual}). | |
1296 | ||
1297 | @cindex Network information service (NIS) | |
1298 | @cindex NIS (Network information service) | |
1299 | Being extensible, the NSS supports @dfn{plugins}, which provide new name | |
1300 | lookup implementations: for example, the @code{nss-mdns} plugin allow | |
1301 | resolution of @code{.local} host names, the @code{nis} plugin allows | |
1302 | user account lookup using the Network information service (NIS), and so | |
1303 | on. These extra ``lookup services'' are configured system-wide in | |
1304 | @file{/etc/nsswitch.conf}, and all the programs running on the system | |
1305 | honor those settings (@pxref{NSS Configuration File,,, libc, The GNU C | |
1306 | Reference Manual}). | |
1307 | ||
1308 | When they perform a name lookup---for instance by calling the | |
1309 | @code{getaddrinfo} function in C---applications first try to connect to | |
1310 | the nscd; on success, nscd performs name lookups on their behalf. If | |
1311 | the nscd is not running, then they perform the name lookup by | |
1312 | themselves, by loading the name lookup services into their own address | |
1313 | space and running it. These name lookup services---the | |
1314 | @file{libnss_*.so} files---are @code{dlopen}'d, but they may come from | |
1315 | the host system's C library, rather than from the C library the | |
1316 | application is linked against (the C library coming from Guix). | |
1317 | ||
1318 | And this is where the problem is: if your application is linked against | |
1319 | Guix's C library (say, glibc 2.24) and tries to load NSS plugins from | |
1320 | another C library (say, @code{libnss_mdns.so} for glibc 2.22), it will | |
1321 | likely crash or have its name lookups fail unexpectedly. | |
1322 | ||
1323 | Running @command{nscd} on the system, among other advantages, eliminates | |
1324 | this binary incompatibility problem because those @code{libnss_*.so} | |
1325 | files are loaded in the @command{nscd} process, not in applications | |
1326 | themselves. | |
1327 | ||
0e2d0213 LC |
1328 | @subsection X11 Fonts |
1329 | ||
e32171ee | 1330 | @cindex fonts |
4988dd40 | 1331 | The majority of graphical applications use Fontconfig to locate and |
f97c9175 AE |
1332 | load fonts and perform X11-client-side rendering. The @code{fontconfig} |
1333 | package in Guix looks for fonts in @file{$HOME/.guix-profile} | |
0e2d0213 | 1334 | by default. Thus, to allow graphical applications installed with Guix |
f97c9175 | 1335 | to display fonts, you have to install fonts with Guix as well. |
0e2d0213 | 1336 | Essential font packages include @code{gs-fonts}, @code{font-dejavu}, and |
8fe5b1d1 | 1337 | @code{font-gnu-freefont-ttf}. |
0e2d0213 | 1338 | |
5c36edc8 LC |
1339 | To display text written in Chinese languages, Japanese, or Korean in |
1340 | graphical applications, consider installing | |
1341 | @code{font-adobe-source-han-sans} or @code{font-wqy-zenhei}. The former | |
1342 | has multiple outputs, one per language family (@pxref{Packages with | |
1343 | Multiple Outputs}). For instance, the following command installs fonts | |
1344 | for Chinese languages: | |
1345 | ||
1346 | @example | |
1347 | guix package -i font-adobe-source-han-sans:cn | |
1348 | @end example | |
1349 | ||
e32171ee | 1350 | @cindex @code{xterm} |
1a3e6b15 AK |
1351 | Older programs such as @command{xterm} do not use Fontconfig and instead |
1352 | rely on server-side font rendering. Such programs require to specify a | |
1353 | full name of a font using XLFD (X Logical Font Description), like this: | |
1354 | ||
1355 | @example | |
1356 | -*-dejavu sans-medium-r-normal-*-*-100-*-*-*-*-*-1 | |
1357 | @end example | |
1358 | ||
1359 | To be able to use such full names for the TrueType fonts installed in | |
1360 | your Guix profile, you need to extend the font path of the X server: | |
1361 | ||
1362 | @example | |
1363 | xset +fp ~/.guix-profile/share/fonts/truetype | |
1364 | @end example | |
1365 | ||
e32171ee | 1366 | @cindex @code{xlsfonts} |
1a3e6b15 AK |
1367 | After that, you can run @code{xlsfonts} (from @code{xlsfonts} package) |
1368 | to make sure your TrueType fonts are listed there. | |
1369 | ||
b3129f2b LC |
1370 | @subsection X.509 Certificates |
1371 | ||
e32171ee | 1372 | @cindex @code{nss-certs} |
b3129f2b LC |
1373 | The @code{nss-certs} package provides X.509 certificates, which allow |
1374 | programs to authenticate Web servers accessed over HTTPS. | |
1375 | ||
1376 | When using Guix on a foreign distro, you can install this package and | |
1377 | define the relevant environment variables so that packages know where to | |
80d944b7 | 1378 | look for certificates. @xref{X.509 Certificates}, for detailed |
b3129f2b LC |
1379 | information. |
1380 | ||
6d97319c AK |
1381 | @subsection Emacs Packages |
1382 | ||
e32171ee | 1383 | @cindex @code{emacs} |
6d97319c AK |
1384 | When you install Emacs packages with Guix, the elisp files may be placed |
1385 | either in @file{$HOME/.guix-profile/share/emacs/site-lisp/} or in | |
1386 | sub-directories of | |
1387 | @file{$HOME/.guix-profile/share/emacs/site-lisp/guix.d/}. The latter | |
1388 | directory exists because potentially there may exist thousands of Emacs | |
1389 | packages and storing all their files in a single directory may be not | |
1390 | reliable (because of name conflicts). So we think using a separate | |
1391 | directory for each package is a good idea. It is very similar to how | |
1392 | the Emacs package system organizes the file structure (@pxref{Package | |
1393 | Files,,, emacs, The GNU Emacs Manual}). | |
1394 | ||
1395 | By default, Emacs (installed with Guix) ``knows'' where these packages | |
f97c9175 | 1396 | are placed, so you do not need to perform any configuration. If, for |
6d97319c | 1397 | some reason, you want to avoid auto-loading Emacs packages installed |
f97c9175 | 1398 | with Guix, you can do so by running Emacs with @code{--no-site-file} |
6d97319c AK |
1399 | option (@pxref{Init File,,, emacs, The GNU Emacs Manual}). |
1400 | ||
0e2d0213 LC |
1401 | @c TODO What else? |
1402 | ||
eeaf4427 LC |
1403 | @c ********************************************************************* |
1404 | @node Package Management | |
1405 | @chapter Package Management | |
1406 | ||
e32171ee | 1407 | @cindex packages |
f8348b91 | 1408 | The purpose of GNU Guix is to allow users to easily install, upgrade, and |
eeaf4427 | 1409 | remove software packages, without having to know about their build |
f97c9175 | 1410 | procedures or dependencies. Guix also goes beyond this obvious set of |
eeaf4427 LC |
1411 | features. |
1412 | ||
1413 | This chapter describes the main features of Guix, as well as the package | |
c1941588 | 1414 | management tools it provides. Two user interfaces are provided for |
c554de89 AK |
1415 | routine package management tasks: A command-line interface described below |
1416 | (@pxref{Invoking guix package, @code{guix package}}), as well as a visual user | |
1417 | interface in Emacs described in a subsequent chapter (@pxref{Emacs Interface}). | |
eeaf4427 LC |
1418 | |
1419 | @menu | |
1420 | * Features:: How Guix will make your life brighter. | |
e49951eb | 1421 | * Invoking guix package:: Package installation, removal, etc. |
c4202d60 | 1422 | * Substitutes:: Downloading pre-built binaries. |
760c60d6 | 1423 | * Packages with Multiple Outputs:: Single source package, multiple outputs. |
e49951eb | 1424 | * Invoking guix gc:: Running the garbage collector. |
f651b477 | 1425 | * Invoking guix pull:: Fetching the latest Guix and distribution. |
760c60d6 | 1426 | * Invoking guix archive:: Exporting and importing store files. |
eeaf4427 LC |
1427 | @end menu |
1428 | ||
1429 | @node Features | |
1430 | @section Features | |
1431 | ||
1432 | When using Guix, each package ends up in the @dfn{package store}, in its | |
1433 | own directory---something that resembles | |
9a130e19 AK |
1434 | @file{/gnu/store/xxx-package-1.2}, where @code{xxx} is a base32 string |
1435 | (note that Guix comes with an Emacs extension to shorten those file | |
081145cf | 1436 | names, @pxref{Emacs Prettify}.) |
eeaf4427 LC |
1437 | |
1438 | Instead of referring to these directories, users have their own | |
1439 | @dfn{profile}, which points to the packages that they actually want to | |
821b0015 LC |
1440 | use. These profiles are stored within each user's home directory, at |
1441 | @code{$HOME/.guix-profile}. | |
eeaf4427 | 1442 | |
821b0015 | 1443 | For example, @code{alice} installs GCC 4.7.2. As a result, |
eeaf4427 | 1444 | @file{/home/alice/.guix-profile/bin/gcc} points to |
834129e0 | 1445 | @file{/gnu/store/@dots{}-gcc-4.7.2/bin/gcc}. Now, on the same machine, |
821b0015 LC |
1446 | @code{bob} had already installed GCC 4.8.0. The profile of @code{bob} |
1447 | simply continues to point to | |
834129e0 | 1448 | @file{/gnu/store/@dots{}-gcc-4.8.0/bin/gcc}---i.e., both versions of GCC |
821b0015 | 1449 | coexist on the same system without any interference. |
eeaf4427 | 1450 | |
e49951eb | 1451 | The @command{guix package} command is the central tool to manage |
f97c9175 | 1452 | packages (@pxref{Invoking guix package}). It operates on the per-user |
821b0015 | 1453 | profiles, and can be used @emph{with normal user privileges}. |
eeaf4427 | 1454 | |
e32171ee | 1455 | @cindex transactions |
eeaf4427 LC |
1456 | The command provides the obvious install, remove, and upgrade |
1457 | operations. Each invocation is actually a @emph{transaction}: either | |
ba55b1cb | 1458 | the specified operation succeeds, or nothing happens. Thus, if the |
e49951eb | 1459 | @command{guix package} process is terminated during the transaction, |
eeaf4427 LC |
1460 | or if a power outage occurs during the transaction, then the user's |
1461 | profile remains in its previous state, and remains usable. | |
1462 | ||
1463 | In addition, any package transaction may be @emph{rolled back}. So, if, | |
1464 | for example, an upgrade installs a new version of a package that turns | |
1465 | out to have a serious bug, users may roll back to the previous instance | |
4af2447e | 1466 | of their profile, which was known to work well. Similarly, the global |
6f773606 LC |
1467 | system configuration on GuixSD is subject to |
1468 | transactional upgrades and roll-back | |
4af2447e | 1469 | (@pxref{Using the Configuration System}). |
eeaf4427 | 1470 | |
f97c9175 AE |
1471 | All packages in the package store may be @emph{garbage-collected}. |
1472 | Guix can determine which packages are still referenced by user | |
fe8ff028 | 1473 | profiles, and remove those that are provably no longer referenced |
e49951eb | 1474 | (@pxref{Invoking guix gc}). Users may also explicitly remove old |
fe8ff028 LC |
1475 | generations of their profile so that the packages they refer to can be |
1476 | collected. | |
eeaf4427 | 1477 | |
e900c503 LC |
1478 | @cindex reproducibility |
1479 | @cindex reproducible builds | |
eeaf4427 LC |
1480 | Finally, Guix takes a @dfn{purely functional} approach to package |
1481 | management, as described in the introduction (@pxref{Introduction}). | |
834129e0 | 1482 | Each @file{/gnu/store} package directory name contains a hash of all the |
eeaf4427 LC |
1483 | inputs that were used to build that package---compiler, libraries, build |
1484 | scripts, etc. This direct correspondence allows users to make sure a | |
1485 | given package installation matches the current state of their | |
e900c503 LC |
1486 | distribution. It also helps maximize @dfn{build reproducibility}: |
1487 | thanks to the isolated build environments that are used, a given build | |
1488 | is likely to yield bit-identical files when performed on different | |
1489 | machines (@pxref{Invoking guix-daemon, container}). | |
eeaf4427 | 1490 | |
c4202d60 | 1491 | @cindex substitutes |
eeaf4427 | 1492 | This foundation allows Guix to support @dfn{transparent binary/source |
c4202d60 | 1493 | deployment}. When a pre-built binary for a @file{/gnu/store} item is |
18f2887b | 1494 | available from an external source---a @dfn{substitute}, Guix just |
c4202d60 LC |
1495 | downloads it and unpacks it; |
1496 | otherwise, it builds the package from source, locally | |
bf9eacd2 LC |
1497 | (@pxref{Substitutes}). Because build results are usually bit-for-bit |
1498 | reproducible, users do not have to trust servers that provide | |
1499 | substitutes: they can force a local build and @emph{challenge} providers | |
1500 | (@pxref{Invoking guix challenge}). | |
eeaf4427 | 1501 | |
f5fd4fd2 LC |
1502 | Control over the build environment is a feature that is also useful for |
1503 | developers. The @command{guix environment} command allows developers of | |
1504 | a package to quickly set up the right development environment for their | |
f97c9175 AE |
1505 | package, without having to manually install the dependencies of the |
1506 | package into their profile (@pxref{Invoking guix environment}). | |
f5fd4fd2 | 1507 | |
e49951eb MW |
1508 | @node Invoking guix package |
1509 | @section Invoking @command{guix package} | |
eeaf4427 | 1510 | |
e32171ee JD |
1511 | @cindex installing packages |
1512 | @cindex removing packages | |
1513 | @cindex package installation | |
1514 | @cindex package removal | |
e49951eb | 1515 | The @command{guix package} command is the tool that allows users to |
eeaf4427 LC |
1516 | install, upgrade, and remove packages, as well as rolling back to |
1517 | previous configurations. It operates only on the user's own profile, | |
1518 | and works with normal user privileges (@pxref{Features}). Its syntax | |
1519 | is: | |
1520 | ||
1521 | @example | |
e49951eb | 1522 | guix package @var{options} |
eeaf4427 | 1523 | @end example |
e32171ee | 1524 | @cindex transactions |
ba55b1cb | 1525 | Primarily, @var{options} specifies the operations to be performed during |
eeaf4427 | 1526 | the transaction. Upon completion, a new profile is created, but |
99bd74d5 | 1527 | previous @dfn{generations} of the profile remain available, should the user |
eeaf4427 LC |
1528 | want to roll back. |
1529 | ||
6447738c MW |
1530 | For example, to remove @code{lua} and install @code{guile} and |
1531 | @code{guile-cairo} in a single transaction: | |
1532 | ||
1533 | @example | |
1534 | guix package -r lua -i guile guile-cairo | |
1535 | @end example | |
1536 | ||
99bd74d5 LC |
1537 | @command{guix package} also supports a @dfn{declarative approach} |
1538 | whereby the user specifies the exact set of packages to be available and | |
1539 | passes it @i{via} the @option{--manifest} option | |
1540 | (@pxref{profile-manifest, @option{--manifest}}). | |
1541 | ||
e32171ee | 1542 | @cindex profile |
b9e5c0a9 | 1543 | For each user, a symlink to the user's default profile is automatically |
0ec1af59 | 1544 | created in @file{$HOME/.guix-profile}. This symlink always points to the |
b9e5c0a9 LC |
1545 | current generation of the user's default profile. Thus, users can add |
1546 | @file{$HOME/.guix-profile/bin} to their @code{PATH} environment | |
1547 | variable, and so on. | |
d664f1b4 LC |
1548 | @cindex search paths |
1549 | If you are not using the Guix System Distribution, consider adding the | |
1550 | following lines to your @file{~/.bash_profile} (@pxref{Bash Startup | |
1551 | Files,,, bash, The GNU Bash Reference Manual}) so that newly-spawned | |
1552 | shells get all the right environment variable definitions: | |
1553 | ||
1554 | @example | |
1555 | GUIX_PROFILE="$HOME/.guix-profile" \ | |
1556 | source "$HOME/.guix-profile/etc/profile" | |
1557 | @end example | |
b9e5c0a9 | 1558 | |
4379c35b LC |
1559 | In a multi-user setup, user profiles are stored in a place registered as |
1560 | a @dfn{garbage-collector root}, which @file{$HOME/.guix-profile} points | |
1561 | to (@pxref{Invoking guix gc}). That directory is normally | |
0ec1af59 LC |
1562 | @code{@var{localstatedir}/profiles/per-user/@var{user}}, where |
1563 | @var{localstatedir} is the value passed to @code{configure} as | |
4379c35b LC |
1564 | @code{--localstatedir}, and @var{user} is the user name. The |
1565 | @file{per-user} directory is created when @command{guix-daemon} is | |
1566 | started, and the @var{user} sub-directory is created by @command{guix | |
1567 | package}. | |
0ec1af59 LC |
1568 | |
1569 | The @var{options} can be among the following: | |
1570 | ||
eeaf4427 LC |
1571 | @table @code |
1572 | ||
6447738c MW |
1573 | @item --install=@var{package} @dots{} |
1574 | @itemx -i @var{package} @dots{} | |
1575 | Install the specified @var{package}s. | |
eeaf4427 | 1576 | |
6447738c | 1577 | Each @var{package} may specify either a simple package name, such as |
1b846da8 ML |
1578 | @code{guile}, or a package name followed by an at-sign and version number, |
1579 | such as @code{guile@@1.8.8} or simply @code{guile@@1.8} (in the latter | |
724311a2 LC |
1580 | case, the newest version prefixed by @code{1.8} is selected.) |
1581 | ||
1582 | If no version number is specified, the | |
dc5669cd MW |
1583 | newest available version will be selected. In addition, @var{package} |
1584 | may contain a colon, followed by the name of one of the outputs of the | |
1b846da8 | 1585 | package, as in @code{gcc:doc} or @code{binutils@@2.22:lib} |
e7f34eb0 LC |
1586 | (@pxref{Packages with Multiple Outputs}). Packages with a corresponding |
1587 | name (and optionally version) are searched for among the GNU | |
1588 | distribution modules (@pxref{Package Modules}). | |
eeaf4427 | 1589 | |
461572cc LC |
1590 | @cindex propagated inputs |
1591 | Sometimes packages have @dfn{propagated inputs}: these are dependencies | |
21461f27 LC |
1592 | that automatically get installed along with the required package |
1593 | (@pxref{package-propagated-inputs, @code{propagated-inputs} in | |
1594 | @code{package} objects}, for information about propagated inputs in | |
1595 | package definitions). | |
461572cc | 1596 | |
21461f27 | 1597 | @anchor{package-cmd-propagated-inputs} |
461572cc LC |
1598 | An example is the GNU MPC library: its C header files refer to those of |
1599 | the GNU MPFR library, which in turn refer to those of the GMP library. | |
1600 | Thus, when installing MPC, the MPFR and GMP libraries also get installed | |
1601 | in the profile; removing MPC also removes MPFR and GMP---unless they had | |
f97c9175 | 1602 | also been explicitly installed by the user. |
461572cc | 1603 | |
ba7ea5ce | 1604 | Besides, packages sometimes rely on the definition of environment |
5924080d | 1605 | variables for their search paths (see explanation of |
ba7ea5ce | 1606 | @code{--search-paths} below). Any missing or possibly incorrect |
5924080d LC |
1607 | environment variable definitions are reported here. |
1608 | ||
5d4b411f LC |
1609 | @item --install-from-expression=@var{exp} |
1610 | @itemx -e @var{exp} | |
1611 | Install the package @var{exp} evaluates to. | |
1612 | ||
1613 | @var{exp} must be a Scheme expression that evaluates to a | |
1614 | @code{<package>} object. This option is notably useful to disambiguate | |
1615 | between same-named variants of a package, with expressions such as | |
1616 | @code{(@@ (gnu packages base) guile-final)}. | |
1617 | ||
1618 | Note that this option installs the first output of the specified | |
1619 | package, which may be insufficient when needing a specific output of a | |
1620 | multiple-output package. | |
1621 | ||
0d279400 DT |
1622 | @item --install-from-file=@var{file} |
1623 | @itemx -f @var{file} | |
1624 | Install the package that the code within @var{file} evaluates to. | |
1625 | ||
1626 | As an example, @var{file} might contain a definition like this | |
1627 | (@pxref{Defining Packages}): | |
1628 | ||
1629 | @example | |
1630 | @verbatiminclude package-hello.scm | |
1631 | @end example | |
1632 | ||
baacf042 | 1633 | Developers may find it useful to include such a @file{guix.scm} file |
f97c9175 | 1634 | in the root of their project source tree that can be used to test |
0d279400 DT |
1635 | development snapshots and create reproducible development environments |
1636 | (@pxref{Invoking guix environment}). | |
1637 | ||
6447738c MW |
1638 | @item --remove=@var{package} @dots{} |
1639 | @itemx -r @var{package} @dots{} | |
1640 | Remove the specified @var{package}s. | |
eeaf4427 | 1641 | |
6447738c | 1642 | As for @code{--install}, each @var{package} may specify a version number |
13ed095c LC |
1643 | and/or output name in addition to the package name. For instance, |
1644 | @code{-r glibc:debug} would remove the @code{debug} output of | |
1645 | @code{glibc}. | |
1646 | ||
6447738c MW |
1647 | @item --upgrade[=@var{regexp} @dots{}] |
1648 | @itemx -u [@var{regexp} @dots{}] | |
e32171ee | 1649 | @cindex upgrading packages |
6447738c MW |
1650 | Upgrade all the installed packages. If one or more @var{regexp}s are |
1651 | specified, upgrade only installed packages whose name matches a | |
d5f01e48 | 1652 | @var{regexp}. Also see the @code{--do-not-upgrade} option below. |
eeaf4427 | 1653 | |
f651b477 LC |
1654 | Note that this upgrades package to the latest version of packages found |
1655 | in the distribution currently installed. To update your distribution, | |
1656 | you should regularly run @command{guix pull} (@pxref{Invoking guix | |
1657 | pull}). | |
1658 | ||
d5f01e48 MW |
1659 | @item --do-not-upgrade[=@var{regexp} @dots{}] |
1660 | When used together with the @code{--upgrade} option, do @emph{not} | |
1661 | upgrade any packages whose name matches a @var{regexp}. For example, to | |
1662 | upgrade all packages in the current profile except those containing the | |
1663 | substring ``emacs'': | |
1664 | ||
1665 | @example | |
1666 | $ guix package --upgrade . --do-not-upgrade emacs | |
1667 | @end example | |
1668 | ||
99bd74d5 | 1669 | @item @anchor{profile-manifest}--manifest=@var{file} |
1b676447 | 1670 | @itemx -m @var{file} |
99bd74d5 LC |
1671 | @cindex profile declaration |
1672 | @cindex profile manifest | |
1673 | Create a new generation of the profile from the manifest object | |
1b676447 DT |
1674 | returned by the Scheme code in @var{file}. |
1675 | ||
99bd74d5 LC |
1676 | This allows you to @emph{declare} the profile's contents rather than |
1677 | constructing it through a sequence of @code{--install} and similar | |
1678 | commands. The advantage is that @var{file} can be put under version | |
1679 | control, copied to different machines to reproduce the same profile, and | |
1680 | so on. | |
1681 | ||
1682 | @c FIXME: Add reference to (guix profile) documentation when available. | |
1683 | @var{file} must return a @dfn{manifest} object, which is roughly a list | |
1684 | of packages: | |
1b676447 | 1685 | |
99bd74d5 | 1686 | @findex packages->manifest |
1b676447 | 1687 | @example |
99bd74d5 | 1688 | (use-package-modules guile emacs) |
1b676447 DT |
1689 | |
1690 | (packages->manifest | |
99bd74d5 LC |
1691 | (list emacs |
1692 | guile-2.0 | |
1b676447 | 1693 | ;; Use a specific package output. |
99bd74d5 | 1694 | (list guile-2.0 "debug"))) |
1b676447 DT |
1695 | @end example |
1696 | ||
24e262f0 | 1697 | @item --roll-back |
e32171ee JD |
1698 | @cindex rolling back |
1699 | @cindex undoing transactions | |
1700 | @cindex transactions, undoing | |
24e262f0 LC |
1701 | Roll back to the previous @dfn{generation} of the profile---i.e., undo |
1702 | the last transaction. | |
1703 | ||
1704 | When combined with options such as @code{--install}, roll back occurs | |
1705 | before any other actions. | |
1706 | ||
d9307267 | 1707 | When rolling back from the first generation that actually contains |
4b2bc804 | 1708 | installed packages, the profile is made to point to the @dfn{zeroth |
f97c9175 | 1709 | generation}, which contains no files apart from its own metadata. |
d9307267 | 1710 | |
f97c9175 AE |
1711 | After having rolled back, installing, removing, or upgrading packages |
1712 | overwrites previous future generations. Thus, the history of the | |
1713 | generations in a profile is always linear. | |
82fe08ed | 1714 | |
b3bb82f1 AK |
1715 | @item --switch-generation=@var{pattern} |
1716 | @itemx -S @var{pattern} | |
e32171ee | 1717 | @cindex generations |
b3bb82f1 AK |
1718 | Switch to a particular generation defined by @var{pattern}. |
1719 | ||
1720 | @var{pattern} may be either a generation number or a number prefixed | |
1721 | with ``+'' or ``-''. The latter means: move forward/backward by a | |
1722 | specified number of generations. For example, if you want to return to | |
1723 | the latest generation after @code{--roll-back}, use | |
1724 | @code{--switch-generation=+1}. | |
1725 | ||
1726 | The difference between @code{--roll-back} and | |
1727 | @code{--switch-generation=-1} is that @code{--switch-generation} will | |
1728 | not make a zeroth generation, so if a specified generation does not | |
1729 | exist, the current generation will not be changed. | |
1730 | ||
dbc31ab2 | 1731 | @item --search-paths[=@var{kind}] |
5924080d LC |
1732 | @cindex search paths |
1733 | Report environment variable definitions, in Bash syntax, that may be | |
1734 | needed in order to use the set of installed packages. These environment | |
1735 | variables are used to specify @dfn{search paths} for files used by some | |
1736 | of the installed packages. | |
1737 | ||
1738 | For example, GCC needs the @code{CPATH} and @code{LIBRARY_PATH} | |
1739 | environment variables to be defined so it can look for headers and | |
1740 | libraries in the user's profile (@pxref{Environment Variables,,, gcc, | |
1741 | Using the GNU Compiler Collection (GCC)}). If GCC and, say, the C | |
1742 | library are installed in the profile, then @code{--search-paths} will | |
1743 | suggest setting these variables to @code{@var{profile}/include} and | |
1744 | @code{@var{profile}/lib}, respectively. | |
1745 | ||
dbc31ab2 LC |
1746 | The typical use case is to define these environment variables in the |
1747 | shell: | |
1748 | ||
1749 | @example | |
1750 | $ eval `guix package --search-paths` | |
1751 | @end example | |
1752 | ||
1753 | @var{kind} may be one of @code{exact}, @code{prefix}, or @code{suffix}, | |
1754 | meaning that the returned environment variable definitions will either | |
1755 | be exact settings, or prefixes or suffixes of the current value of these | |
1756 | variables. When omitted, @var{kind} defaults to @code{exact}. | |
1757 | ||
fc2d2339 LC |
1758 | This option can also be used to compute the @emph{combined} search paths |
1759 | of several profiles. Consider this example: | |
1760 | ||
1761 | @example | |
1762 | $ guix package -p foo -i guile | |
1763 | $ guix package -p bar -i guile-json | |
1764 | $ guix package -p foo -p bar --search-paths | |
1765 | @end example | |
1766 | ||
1767 | The last command above reports about the @code{GUILE_LOAD_PATH} | |
1768 | variable, even though, taken individually, neither @file{foo} nor | |
1769 | @file{bar} would lead to that recommendation. | |
1770 | ||
1771 | ||
eeaf4427 LC |
1772 | @item --profile=@var{profile} |
1773 | @itemx -p @var{profile} | |
1774 | Use @var{profile} instead of the user's default profile. | |
1775 | ||
70915c1a | 1776 | @item --verbose |
f97c9175 AE |
1777 | Produce verbose output. In particular, emit the build log of the |
1778 | environment on the standard error port. | |
70915c1a | 1779 | |
eeaf4427 LC |
1780 | @item --bootstrap |
1781 | Use the bootstrap Guile to build the profile. This option is only | |
1782 | useful to distribution developers. | |
1783 | ||
1784 | @end table | |
1785 | ||
f97c9175 | 1786 | In addition to these actions, @command{guix package} supports the |
733b4130 LC |
1787 | following options to query the current state of a profile, or the |
1788 | availability of packages: | |
eeaf4427 | 1789 | |
733b4130 LC |
1790 | @table @option |
1791 | ||
acc08466 NK |
1792 | @item --search=@var{regexp} |
1793 | @itemx -s @var{regexp} | |
b110869d | 1794 | @cindex searching for packages |
5763ad92 | 1795 | List the available packages whose name, synopsis, or description matches |
f97c9175 | 1796 | @var{regexp}. Print all the metadata of matching packages in |
299112d3 LC |
1797 | @code{recutils} format (@pxref{Top, GNU recutils databases,, recutils, |
1798 | GNU recutils manual}). | |
acc08466 | 1799 | |
299112d3 LC |
1800 | This allows specific fields to be extracted using the @command{recsel} |
1801 | command, for instance: | |
1802 | ||
1803 | @example | |
e49951eb | 1804 | $ guix package -s malloc | recsel -p name,version |
299112d3 LC |
1805 | name: glibc |
1806 | version: 2.17 | |
1807 | ||
1808 | name: libgc | |
1809 | version: 7.2alpha6 | |
1810 | @end example | |
acc08466 | 1811 | |
a12d92f5 LC |
1812 | Similarly, to show the name of all the packages available under the |
1813 | terms of the GNU@tie{}LGPL version 3: | |
1814 | ||
1815 | @example | |
1816 | $ guix package -s "" | recsel -p name -e 'license ~ "LGPL 3"' | |
1817 | name: elfutils | |
1818 | ||
1819 | name: gmp | |
1820 | @dots{} | |
1821 | @end example | |
1822 | ||
db5a9444 LC |
1823 | It is also possible to refine search results using several @code{-s} |
1824 | flags. For example, the following command returns a list of board | |
1825 | games: | |
1826 | ||
1827 | @example | |
1828 | $ guix package -s '\<board\>' -s game | recsel -p name | |
1829 | name: gnubg | |
1830 | @dots{} | |
1831 | @end example | |
1832 | ||
1833 | If we were to omit @code{-s game}, we would also get software packages | |
1834 | that deal with printed circuit boards; removing the angle brackets | |
1835 | around @code{board} would further add packages that have to do with | |
1836 | keyboards. | |
1837 | ||
b110869d LC |
1838 | And now for a more elaborate example. The following command searches |
1839 | for cryptographic libraries, filters out Haskell, Perl, Python, and Ruby | |
1840 | libraries, and prints the name and synopsis of the matching packages: | |
1841 | ||
1842 | @example | |
1843 | $ guix package -s crypto -s library | \ | |
1844 | recsel -e '! (name ~ "^(ghc|perl|python|ruby)")' -p name,synopsis | |
1845 | @end example | |
1846 | ||
1847 | @noindent | |
1848 | @xref{Selection Expressions,,, recutils, GNU recutils manual}, for more | |
1849 | information on @dfn{selection expressions} for @code{recsel -e}. | |
1850 | ||
2aa6efb0 CR |
1851 | @item --show=@var{package} |
1852 | Show details about @var{package}, taken from the list of available packages, in | |
1853 | @code{recutils} format (@pxref{Top, GNU recutils databases,, recutils, GNU | |
1854 | recutils manual}). | |
1855 | ||
1856 | @example | |
1857 | $ guix package --show=python | recsel -p name,version | |
1858 | name: python | |
1859 | version: 2.7.6 | |
1860 | ||
1861 | name: python | |
1862 | version: 3.3.5 | |
1863 | @end example | |
1864 | ||
1865 | You may also specify the full name of a package to only get details about a | |
1866 | specific version of it: | |
1867 | @example | |
ea206df4 | 1868 | $ guix package --show=python@@3.4 | recsel -p name,version |
2aa6efb0 | 1869 | name: python |
ea206df4 | 1870 | version: 3.4.3 |
2aa6efb0 CR |
1871 | @end example |
1872 | ||
1873 | ||
1874 | ||
733b4130 LC |
1875 | @item --list-installed[=@var{regexp}] |
1876 | @itemx -I [@var{regexp}] | |
bd9bde1c LC |
1877 | List the currently installed packages in the specified profile, with the |
1878 | most recently installed packages shown last. When @var{regexp} is | |
1879 | specified, list only installed packages whose name matches @var{regexp}. | |
733b4130 LC |
1880 | |
1881 | For each installed package, print the following items, separated by | |
1882 | tabs: the package name, its version string, the part of the package that | |
1883 | is installed (for instance, @code{out} for the default output, | |
1884 | @code{include} for its headers, etc.), and the path of this package in | |
1885 | the store. | |
1886 | ||
64fc89b6 LC |
1887 | @item --list-available[=@var{regexp}] |
1888 | @itemx -A [@var{regexp}] | |
5763ad92 | 1889 | List packages currently available in the distribution for this system |
a1ba8475 LC |
1890 | (@pxref{GNU Distribution}). When @var{regexp} is specified, list only |
1891 | installed packages whose name matches @var{regexp}. | |
64fc89b6 LC |
1892 | |
1893 | For each package, print the following items separated by tabs: its name, | |
6e721c4d LC |
1894 | its version string, the parts of the package (@pxref{Packages with |
1895 | Multiple Outputs}), and the source location of its definition. | |
64fc89b6 | 1896 | |
f566d765 LC |
1897 | @item --list-generations[=@var{pattern}] |
1898 | @itemx -l [@var{pattern}] | |
e32171ee | 1899 | @cindex generations |
f566d765 LC |
1900 | Return a list of generations along with their creation dates; for each |
1901 | generation, show the installed packages, with the most recently | |
4b2bc804 NK |
1902 | installed packages shown last. Note that the zeroth generation is never |
1903 | shown. | |
f566d765 LC |
1904 | |
1905 | For each installed package, print the following items, separated by | |
1906 | tabs: the name of a package, its version string, the part of the package | |
1907 | that is installed (@pxref{Packages with Multiple Outputs}), and the | |
1908 | location of this package in the store. | |
1909 | ||
1910 | When @var{pattern} is used, the command returns only matching | |
1911 | generations. Valid patterns include: | |
1912 | ||
1913 | @itemize | |
1914 | @item @emph{Integers and comma-separated integers}. Both patterns denote | |
1915 | generation numbers. For instance, @code{--list-generations=1} returns | |
1916 | the first one. | |
1917 | ||
1918 | And @code{--list-generations=1,8,2} outputs three generations in the | |
1919 | specified order. Neither spaces nor trailing commas are allowed. | |
1920 | ||
1921 | @item @emph{Ranges}. @code{--list-generations=2..9} prints the | |
1922 | specified generations and everything in between. Note that the start of | |
f97c9175 | 1923 | a range must be smaller than its end. |
f566d765 LC |
1924 | |
1925 | It is also possible to omit the endpoint. For example, | |
1926 | @code{--list-generations=2..}, returns all generations starting from the | |
1927 | second one. | |
1928 | ||
1929 | @item @emph{Durations}. You can also get the last @emph{N}@tie{}days, weeks, | |
1930 | or months by passing an integer along with the first letter of the | |
d7ddb257 LC |
1931 | duration. For example, @code{--list-generations=20d} lists generations |
1932 | that are up to 20 days old. | |
f566d765 LC |
1933 | @end itemize |
1934 | ||
b7884ca3 NK |
1935 | @item --delete-generations[=@var{pattern}] |
1936 | @itemx -d [@var{pattern}] | |
d7ddb257 LC |
1937 | When @var{pattern} is omitted, delete all generations except the current |
1938 | one. | |
b7884ca3 NK |
1939 | |
1940 | This command accepts the same patterns as @option{--list-generations}. | |
d7ddb257 LC |
1941 | When @var{pattern} is specified, delete the matching generations. When |
1942 | @var{pattern} specifies a duration, generations @emph{older} than the | |
1943 | specified duration match. For instance, @code{--delete-generations=1m} | |
1944 | deletes generations that are more than one month old. | |
1945 | ||
391bdd8f LC |
1946 | If the current generation matches, it is @emph{not} deleted. Also, the |
1947 | zeroth generation is never deleted. | |
b7884ca3 | 1948 | |
f97c9175 | 1949 | Note that deleting generations prevents rolling back to them. |
1bb9900a LC |
1950 | Consequently, this command must be used with care. |
1951 | ||
733b4130 | 1952 | @end table |
eeaf4427 | 1953 | |
70ee5642 | 1954 | Finally, since @command{guix package} may actually start build |
ccd7158d | 1955 | processes, it supports all the common build options (@pxref{Common Build |
f97c9175 | 1956 | Options}). It also supports package transformation options, such as |
b8638f03 LC |
1957 | @option{--with-source} (@pxref{Package Transformation Options}). |
1958 | However, note that package transformations are lost when upgrading; to | |
f97c9175 | 1959 | preserve transformations across upgrades, you should define your own |
b8638f03 LC |
1960 | package variant in a Guile module and add it to @code{GUIX_PACKAGE_PATH} |
1961 | (@pxref{Defining Packages}). | |
1962 | ||
70ee5642 | 1963 | |
c4202d60 LC |
1964 | @node Substitutes |
1965 | @section Substitutes | |
1966 | ||
1967 | @cindex substitutes | |
1968 | @cindex pre-built binaries | |
1969 | Guix supports transparent source/binary deployment, which means that it | |
1970 | can either build things locally, or download pre-built items from a | |
1971 | server. We call these pre-built items @dfn{substitutes}---they are | |
1972 | substitutes for local build results. In many cases, downloading a | |
1973 | substitute is much faster than building things locally. | |
1974 | ||
1975 | Substitutes can be anything resulting from a derivation build | |
1976 | (@pxref{Derivations}). Of course, in the common case, they are | |
1977 | pre-built package binaries, but source tarballs, for instance, which | |
1978 | also result from derivation builds, can be available as substitutes. | |
1979 | ||
1980 | The @code{hydra.gnu.org} server is a front-end to a build farm that | |
1981 | builds packages from the GNU distribution continuously for some | |
32950fc8 AK |
1982 | architectures, and makes them available as substitutes (@pxref{Emacs |
1983 | Hydra}, for information on how to query the continuous integration | |
1984 | server). This is the | |
f8a8e0fe LC |
1985 | default source of substitutes; it can be overridden by passing the |
1986 | @option{--substitute-urls} option either to @command{guix-daemon} | |
1987 | (@pxref{daemon-substitute-urls,, @code{guix-daemon --substitute-urls}}) | |
1988 | or to client tools such as @command{guix package} | |
1989 | (@pxref{client-substitute-urls,, client @option{--substitute-urls} | |
1990 | option}). | |
c4202d60 | 1991 | |
9b7bd1b1 LC |
1992 | Substitute URLs can be either HTTP or HTTPS@footnote{For HTTPS access, |
1993 | the Guile bindings of GnuTLS must be installed. @xref{Requirements}.} | |
1994 | HTTPS is recommended because communications are encrypted; conversely, | |
1995 | using HTTP makes all communications visible to an eavesdropper, who | |
1996 | could use the information gathered to determine, for instance, whether | |
1997 | your system has unpatched security vulnerabilities. | |
1998 | ||
c4202d60 LC |
1999 | @cindex security |
2000 | @cindex digital signatures | |
e32171ee | 2001 | @cindex substitutes, authorization thereof |
df061d07 LC |
2002 | To allow Guix to download substitutes from @code{hydra.gnu.org} or a |
2003 | mirror thereof, you | |
c4202d60 LC |
2004 | must add its public key to the access control list (ACL) of archive |
2005 | imports, using the @command{guix archive} command (@pxref{Invoking guix | |
2006 | archive}). Doing so implies that you trust @code{hydra.gnu.org} to not | |
2007 | be compromised and to serve genuine substitutes. | |
2008 | ||
2009 | This public key is installed along with Guix, in | |
2010 | @code{@var{prefix}/share/guix/hydra.gnu.org.pub}, where @var{prefix} is | |
2011 | the installation prefix of Guix. If you installed Guix from source, | |
2012 | make sure you checked the GPG signature of | |
2013 | @file{guix-@value{VERSION}.tar.gz}, which contains this public key file. | |
2014 | Then, you can run something like this: | |
2015 | ||
2016 | @example | |
2017 | # guix archive --authorize < hydra.gnu.org.pub | |
2018 | @end example | |
2019 | ||
2020 | Once this is in place, the output of a command like @code{guix build} | |
2021 | should change from something like: | |
2022 | ||
2023 | @example | |
2024 | $ guix build emacs --dry-run | |
2025 | The following derivations would be built: | |
2026 | /gnu/store/yr7bnx8xwcayd6j95r2clmkdl1qh688w-emacs-24.3.drv | |
2027 | /gnu/store/x8qsh1hlhgjx6cwsjyvybnfv2i37z23w-dbus-1.6.4.tar.gz.drv | |
2028 | /gnu/store/1ixwp12fl950d15h2cj11c73733jay0z-alsa-lib-1.0.27.1.tar.bz2.drv | |
2029 | /gnu/store/nlma1pw0p603fpfiqy7kn4zm105r5dmw-util-linux-2.21.drv | |
2030 | @dots{} | |
2031 | @end example | |
2032 | ||
2033 | @noindent | |
2034 | to something like: | |
2035 | ||
2036 | @example | |
2037 | $ guix build emacs --dry-run | |
2038 | The following files would be downloaded: | |
2039 | /gnu/store/pk3n22lbq6ydamyymqkkz7i69wiwjiwi-emacs-24.3 | |
2040 | /gnu/store/2ygn4ncnhrpr61rssa6z0d9x22si0va3-libjpeg-8d | |
2041 | /gnu/store/71yz6lgx4dazma9dwn2mcjxaah9w77jq-cairo-1.12.16 | |
2042 | /gnu/store/7zdhgp0n1518lvfn8mb96sxqfmvqrl7v-libxrender-0.9.7 | |
2043 | @dots{} | |
2044 | @end example | |
2045 | ||
2046 | @noindent | |
2047 | This indicates that substitutes from @code{hydra.gnu.org} are usable and | |
2048 | will be downloaded, when possible, for future builds. | |
2049 | ||
2050 | Guix ignores substitutes that are not signed, or that are not signed by | |
ef27aa9c | 2051 | one of the keys listed in the ACL. It also detects and raises an error |
c4202d60 LC |
2052 | when attempting to use a substitute that has been tampered with. |
2053 | ||
e0c941fe | 2054 | @vindex http_proxy |
9b7bd1b1 LC |
2055 | Substitutes are downloaded over HTTP or HTTPS. |
2056 | The @code{http_proxy} environment | |
e0c941fe LC |
2057 | variable can be set in the environment of @command{guix-daemon} and is |
2058 | honored for downloads of substitutes. Note that the value of | |
2059 | @code{http_proxy} in the environment where @command{guix build}, | |
2060 | @command{guix package}, and other client commands are run has | |
2061 | @emph{absolutely no effect}. | |
2062 | ||
9b7bd1b1 LC |
2063 | When using HTTPS, the server's X.509 certificate is @emph{not} validated |
2064 | (in other words, the server is not authenticated), contrary to what | |
2065 | HTTPS clients such as Web browsers usually do. This is because Guix | |
2066 | authenticates substitute information itself, as explained above, which | |
2067 | is what we care about (whereas X.509 certificates are about | |
2068 | authenticating bindings between domain names and public keys.) | |
2069 | ||
c4202d60 LC |
2070 | The substitute mechanism can be disabled globally by running |
2071 | @code{guix-daemon} with @code{--no-substitutes} (@pxref{Invoking | |
2072 | guix-daemon}). It can also be disabled temporarily by passing the | |
2073 | @code{--no-substitutes} option to @command{guix package}, @command{guix | |
2074 | build}, and other command-line tools. | |
2075 | ||
2076 | ||
9b7bd1b1 LC |
2077 | @unnumberedsubsec On Trusting Binaries |
2078 | ||
c4202d60 LC |
2079 | Today, each individual's control over their own computing is at the |
2080 | mercy of institutions, corporations, and groups with enough power and | |
2081 | determination to subvert the computing infrastructure and exploit its | |
2082 | weaknesses. While using @code{hydra.gnu.org} substitutes can be | |
2083 | convenient, we encourage users to also build on their own, or even run | |
2084 | their own build farm, such that @code{hydra.gnu.org} is less of an | |
8ce229fc LC |
2085 | interesting target. One way to help is by publishing the software you |
2086 | build using @command{guix publish} so that others have one more choice | |
2087 | of server to download substitutes from (@pxref{Invoking guix publish}). | |
c4202d60 LC |
2088 | |
2089 | Guix has the foundations to maximize build reproducibility | |
2090 | (@pxref{Features}). In most cases, independent builds of a given | |
2091 | package or derivation should yield bit-identical results. Thus, through | |
2092 | a diverse set of independent package builds, we can strengthen the | |
d23c20f1 LC |
2093 | integrity of our systems. The @command{guix challenge} command aims to |
2094 | help users assess substitute servers, and to assist developers in | |
2095 | finding out about non-deterministic package builds (@pxref{Invoking guix | |
a8d65643 LC |
2096 | challenge}). Similarly, the @option{--check} option of @command{guix |
2097 | build} allows users to check whether previously-installed substitutes | |
2098 | are genuine by rebuilding them locally (@pxref{build-check, | |
2099 | @command{guix build --check}}). | |
c4202d60 LC |
2100 | |
2101 | In the future, we want Guix to have support to publish and retrieve | |
2102 | binaries to/from other users, in a peer-to-peer fashion. If you would | |
2103 | like to discuss this project, join us on @email{guix-devel@@gnu.org}. | |
2104 | ||
2105 | ||
6e721c4d LC |
2106 | @node Packages with Multiple Outputs |
2107 | @section Packages with Multiple Outputs | |
2108 | ||
2109 | @cindex multiple-output packages | |
2110 | @cindex package outputs | |
e32171ee | 2111 | @cindex outputs |
6e721c4d LC |
2112 | |
2113 | Often, packages defined in Guix have a single @dfn{output}---i.e., the | |
f97c9175 | 2114 | source package leads to exactly one directory in the store. When running |
6e721c4d LC |
2115 | @command{guix package -i glibc}, one installs the default output of the |
2116 | GNU libc package; the default output is called @code{out}, but its name | |
2117 | can be omitted as shown in this command. In this particular case, the | |
2118 | default output of @code{glibc} contains all the C header files, shared | |
2119 | libraries, static libraries, Info documentation, and other supporting | |
2120 | files. | |
2121 | ||
2122 | Sometimes it is more appropriate to separate the various types of files | |
2123 | produced from a single source package into separate outputs. For | |
2124 | instance, the GLib C library (used by GTK+ and related packages) | |
2125 | installs more than 20 MiB of reference documentation as HTML pages. | |
2126 | To save space for users who do not need it, the documentation goes to a | |
2127 | separate output, called @code{doc}. To install the main GLib output, | |
2128 | which contains everything but the documentation, one would run: | |
2129 | ||
2130 | @example | |
2131 | guix package -i glib | |
2132 | @end example | |
2133 | ||
e32171ee | 2134 | @cindex documentation |
6e721c4d LC |
2135 | The command to install its documentation is: |
2136 | ||
2137 | @example | |
2138 | guix package -i glib:doc | |
2139 | @end example | |
2140 | ||
2141 | Some packages install programs with different ``dependency footprints''. | |
f97c9175 | 2142 | For instance, the WordNet package installs both command-line tools and |
6e721c4d LC |
2143 | graphical user interfaces (GUIs). The former depend solely on the C |
2144 | library, whereas the latter depend on Tcl/Tk and the underlying X | |
2145 | libraries. In this case, we leave the command-line tools in the default | |
2146 | output, whereas the GUIs are in a separate output. This allows users | |
fcc58db6 LC |
2147 | who do not need the GUIs to save space. The @command{guix size} command |
2148 | can help find out about such situations (@pxref{Invoking guix size}). | |
88856916 | 2149 | @command{guix graph} can also be helpful (@pxref{Invoking guix graph}). |
6e721c4d LC |
2150 | |
2151 | There are several such multiple-output packages in the GNU distribution. | |
91ef73d4 LC |
2152 | Other conventional output names include @code{lib} for libraries and |
2153 | possibly header files, @code{bin} for stand-alone programs, and | |
2154 | @code{debug} for debugging information (@pxref{Installing Debugging | |
2155 | Files}). The outputs of a packages are listed in the third column of | |
2156 | the output of @command{guix package --list-available} (@pxref{Invoking | |
2157 | guix package}). | |
6e721c4d | 2158 | |
eeaf4427 | 2159 | |
e49951eb MW |
2160 | @node Invoking guix gc |
2161 | @section Invoking @command{guix gc} | |
fe8ff028 LC |
2162 | |
2163 | @cindex garbage collector | |
e32171ee | 2164 | @cindex disk space |
f97c9175 | 2165 | Packages that are installed, but not used, may be @dfn{garbage-collected}. |
e49951eb | 2166 | The @command{guix gc} command allows users to explicitly run the garbage |
c22eb992 LC |
2167 | collector to reclaim space from the @file{/gnu/store} directory. It is |
2168 | the @emph{only} way to remove files from @file{/gnu/store}---removing | |
2169 | files or directories manually may break it beyond repair! | |
fe8ff028 LC |
2170 | |
2171 | The garbage collector has a set of known @dfn{roots}: any file under | |
834129e0 | 2172 | @file{/gnu/store} reachable from a root is considered @dfn{live} and |
fe8ff028 LC |
2173 | cannot be deleted; any other file is considered @dfn{dead} and may be |
2174 | deleted. The set of garbage collector roots includes default user | |
e49951eb MW |
2175 | profiles, and may be augmented with @command{guix build --root}, for |
2176 | example (@pxref{Invoking guix build}). | |
fe8ff028 | 2177 | |
1bb9900a LC |
2178 | Prior to running @code{guix gc --collect-garbage} to make space, it is |
2179 | often useful to remove old generations from user profiles; that way, old | |
2180 | package builds referenced by those generations can be reclaimed. This | |
2181 | is achieved by running @code{guix package --delete-generations} | |
2182 | (@pxref{Invoking guix package}). | |
2183 | ||
e49951eb | 2184 | The @command{guix gc} command has three modes of operation: it can be |
fe8ff028 | 2185 | used to garbage-collect any dead files (the default), to delete specific |
7770aafc LC |
2186 | files (the @code{--delete} option), to print garbage-collector |
2187 | information, or for more advanced queries. The garbage collection | |
2188 | options are as follows: | |
fe8ff028 LC |
2189 | |
2190 | @table @code | |
2191 | @item --collect-garbage[=@var{min}] | |
2192 | @itemx -C [@var{min}] | |
834129e0 | 2193 | Collect garbage---i.e., unreachable @file{/gnu/store} files and |
fe8ff028 LC |
2194 | sub-directories. This is the default operation when no option is |
2195 | specified. | |
2196 | ||
2197 | When @var{min} is given, stop once @var{min} bytes have been collected. | |
2198 | @var{min} may be a number of bytes, or it may include a unit as a | |
4a44d7bb LC |
2199 | suffix, such as @code{MiB} for mebibytes and @code{GB} for gigabytes |
2200 | (@pxref{Block size, size specifications,, coreutils, GNU Coreutils}). | |
fe8ff028 LC |
2201 | |
2202 | When @var{min} is omitted, collect all the garbage. | |
2203 | ||
0054e470 LC |
2204 | @item --free-space=@var{free} |
2205 | @itemx -F @var{free} | |
2206 | Collect garbage until @var{free} space is available under | |
2207 | @file{/gnu/store}, if possible; @var{free} denotes storage space, such | |
2208 | as @code{500MiB}, as described above. | |
2209 | ||
2210 | When @var{free} or more is already available in @file{/gnu/store}, do | |
2211 | nothing and exit immediately. | |
2212 | ||
fe8ff028 LC |
2213 | @item --delete |
2214 | @itemx -d | |
2215 | Attempt to delete all the store files and directories specified as | |
2216 | arguments. This fails if some of the files are not in the store, or if | |
2217 | they are still live. | |
2218 | ||
30d9aa54 LC |
2219 | @item --list-failures |
2220 | List store items corresponding to cached build failures. | |
2221 | ||
2222 | This prints nothing unless the daemon was started with | |
2223 | @option{--cache-failures} (@pxref{Invoking guix-daemon, | |
2224 | @option{--cache-failures}}). | |
2225 | ||
2226 | @item --clear-failures | |
2227 | Remove the specified store items from the failed-build cache. | |
2228 | ||
2229 | Again, this option only makes sense when the daemon is started with | |
2230 | @option{--cache-failures}. Otherwise, it does nothing. | |
2231 | ||
fe8ff028 LC |
2232 | @item --list-dead |
2233 | Show the list of dead files and directories still present in the | |
2234 | store---i.e., files and directories no longer reachable from any root. | |
2235 | ||
2236 | @item --list-live | |
2237 | Show the list of live store files and directories. | |
ba8b732d LC |
2238 | |
2239 | @end table | |
2240 | ||
2241 | In addition, the references among existing store files can be queried: | |
2242 | ||
2243 | @table @code | |
2244 | ||
2245 | @item --references | |
2246 | @itemx --referrers | |
e32171ee | 2247 | @cindex package dependencies |
ba8b732d LC |
2248 | List the references (respectively, the referrers) of store files given |
2249 | as arguments. | |
2250 | ||
8e59fdd5 LC |
2251 | @item --requisites |
2252 | @itemx -R | |
fcc58db6 | 2253 | @cindex closure |
8e59fdd5 LC |
2254 | List the requisites of the store files passed as arguments. Requisites |
2255 | include the store files themselves, their references, and the references | |
2256 | of these, recursively. In other words, the returned list is the | |
2257 | @dfn{transitive closure} of the store files. | |
2258 | ||
f97c9175 AE |
2259 | @xref{Invoking guix size}, for a tool to profile the size of the closure |
2260 | of an element. @xref{Invoking guix graph}, for a tool to visualize | |
88856916 | 2261 | the graph of references. |
fcc58db6 | 2262 | |
fe8ff028 LC |
2263 | @end table |
2264 | ||
7770aafc LC |
2265 | Lastly, the following options allow you to check the integrity of the |
2266 | store and to control disk usage. | |
2267 | ||
2268 | @table @option | |
2269 | ||
2270 | @item --verify[=@var{options}] | |
2271 | @cindex integrity, of the store | |
2272 | @cindex integrity checking | |
2273 | Verify the integrity of the store. | |
2274 | ||
2275 | By default, make sure that all the store items marked as valid in the | |
f97c9175 | 2276 | database of the daemon actually exist in @file{/gnu/store}. |
7770aafc | 2277 | |
f97c9175 | 2278 | When provided, @var{options} must be a comma-separated list containing one |
7770aafc LC |
2279 | or more of @code{contents} and @code{repair}. |
2280 | ||
7414de0a | 2281 | When passing @option{--verify=contents}, the daemon computes the |
f97c9175 | 2282 | content hash of each store item and compares it against its hash in the |
7770aafc LC |
2283 | database. Hash mismatches are reported as data corruptions. Because it |
2284 | traverses @emph{all the files in the store}, this command can take a | |
2285 | long time, especially on systems with a slow disk drive. | |
2286 | ||
2287 | @cindex repairing the store | |
2288 | Using @option{--verify=repair} or @option{--verify=contents,repair} | |
2289 | causes the daemon to try to repair corrupt store items by fetching | |
2290 | substitutes for them (@pxref{Substitutes}). Because repairing is not | |
2291 | atomic, and thus potentially dangerous, it is available only to the | |
2292 | system administrator. | |
2293 | ||
2294 | @item --optimize | |
2295 | @cindex deduplication | |
2296 | Optimize the store by hard-linking identical files---this is | |
2297 | @dfn{deduplication}. | |
2298 | ||
2299 | The daemon performs deduplication after each successful build or archive | |
2300 | import, unless it was started with @code{--disable-deduplication} | |
2301 | (@pxref{Invoking guix-daemon, @code{--disable-deduplication}}). Thus, | |
2302 | this option is primarily useful when the daemon was running with | |
2303 | @code{--disable-deduplication}. | |
2304 | ||
2305 | @end table | |
eeaf4427 | 2306 | |
f651b477 LC |
2307 | @node Invoking guix pull |
2308 | @section Invoking @command{guix pull} | |
2309 | ||
e32171ee JD |
2310 | @cindex upgrading Guix |
2311 | @cindex @command{guix pull} | |
2312 | @cindex pull | |
f651b477 LC |
2313 | Packages are installed or upgraded to the latest version available in |
2314 | the distribution currently available on your local machine. To update | |
2315 | that distribution, along with the Guix tools, you must run @command{guix | |
2316 | pull}: the command downloads the latest Guix source code and package | |
2317 | descriptions, and deploys it. | |
2318 | ||
2319 | On completion, @command{guix package} will use packages and package | |
2320 | versions from this just-retrieved copy of Guix. Not only that, but all | |
2321 | the Guix commands and Scheme modules will also be taken from that latest | |
2322 | version. New @command{guix} sub-commands added by the update also | |
cb05108a LC |
2323 | become available. |
2324 | ||
2325 | Any user can update their Guix copy using @command{guix pull}, and the | |
2326 | effect is limited to the user who run @command{guix pull}. For | |
2327 | instance, when user @code{root} runs @command{guix pull}, this has no | |
2328 | effect on the version of Guix that user @code{alice} sees, and vice | |
2329 | versa@footnote{Under the hood, @command{guix pull} updates the | |
2330 | @file{~/.config/guix/latest} symbolic link to point to the latest Guix, | |
2331 | and the @command{guix} command loads code from there.}. | |
f651b477 LC |
2332 | |
2333 | The @command{guix pull} command is usually invoked with no arguments, | |
2334 | but it supports the following options: | |
2335 | ||
2336 | @table @code | |
2337 | @item --verbose | |
2338 | Produce verbose output, writing build logs to the standard error output. | |
2339 | ||
ab5d72ad LC |
2340 | @item --url=@var{url} |
2341 | Download the source tarball of Guix from @var{url}. | |
2342 | ||
2343 | By default, the tarball is taken from its canonical address at | |
2344 | @code{gnu.org}, for the stable branch of Guix. | |
2345 | ||
f651b477 LC |
2346 | @item --bootstrap |
2347 | Use the bootstrap Guile to build the latest Guix. This option is only | |
2348 | useful to Guix developers. | |
2349 | @end table | |
2350 | ||
760c60d6 LC |
2351 | |
2352 | @node Invoking guix archive | |
2353 | @section Invoking @command{guix archive} | |
2354 | ||
e32171ee JD |
2355 | @cindex @command{guix archive} |
2356 | @cindex archive | |
760c60d6 LC |
2357 | The @command{guix archive} command allows users to @dfn{export} files |
2358 | from the store into a single archive, and to later @dfn{import} them. | |
2359 | In particular, it allows store files to be transferred from one machine | |
4d4c4816 AE |
2360 | to the store on another machine. |
2361 | ||
e32171ee | 2362 | @cindex exporting store items |
4d4c4816 AE |
2363 | To export store files as an archive to standard output, run: |
2364 | ||
2365 | @example | |
2366 | guix archive --export @var{options} @var{specifications}... | |
2367 | @end example | |
2368 | ||
2369 | @var{specifications} may be either store file names or package | |
2370 | specifications, as for @command{guix package} (@pxref{Invoking guix | |
2371 | package}). For instance, the following command creates an archive | |
2372 | containing the @code{gui} output of the @code{git} package and the main | |
2373 | output of @code{emacs}: | |
2374 | ||
2375 | @example | |
2376 | guix archive --export git:gui /gnu/store/...-emacs-24.3 > great.nar | |
2377 | @end example | |
2378 | ||
2379 | If the specified packages are not built yet, @command{guix archive} | |
2380 | automatically builds them. The build process may be controlled with the | |
2381 | common build options (@pxref{Common Build Options}). | |
2382 | ||
2383 | To transfer the @code{emacs} package to a machine connected over SSH, | |
2384 | one would run: | |
760c60d6 LC |
2385 | |
2386 | @example | |
56607088 | 2387 | guix archive --export -r emacs | ssh the-machine guix archive --import |
760c60d6 LC |
2388 | @end example |
2389 | ||
87236aed | 2390 | @noindent |
56607088 LC |
2391 | Similarly, a complete user profile may be transferred from one machine |
2392 | to another like this: | |
2393 | ||
2394 | @example | |
2395 | guix archive --export -r $(readlink -f ~/.guix-profile) | \ | |
2396 | ssh the-machine guix-archive --import | |
2397 | @end example | |
2398 | ||
2399 | @noindent | |
2400 | However, note that, in both examples, all of @code{emacs} and the | |
2401 | profile as well as all of their dependencies are transferred (due to | |
f97c9175 AE |
2402 | @code{-r}), regardless of what is already available in the store on the |
2403 | target machine. The @code{--missing} option can help figure out which | |
2404 | items are missing from the target store. | |
87236aed | 2405 | |
760c60d6 | 2406 | Archives are stored in the ``Nix archive'' or ``Nar'' format, which is |
0dbd88db LC |
2407 | comparable in spirit to `tar', but with a few noteworthy differences |
2408 | that make it more appropriate for our purposes. First, rather than | |
f97c9175 | 2409 | recording all Unix metadata for each file, the Nar format only mentions |
0dbd88db LC |
2410 | the file type (regular, directory, or symbolic link); Unix permissions |
2411 | and owner/group are dismissed. Second, the order in which directory | |
2412 | entries are stored always follows the order of file names according to | |
2413 | the C locale collation order. This makes archive production fully | |
2414 | deterministic. | |
2415 | ||
2416 | When exporting, the daemon digitally signs the contents of the archive, | |
2417 | and that digital signature is appended. When importing, the daemon | |
2418 | verifies the signature and rejects the import in case of an invalid | |
2419 | signature or if the signing key is not authorized. | |
760c60d6 LC |
2420 | @c FIXME: Add xref to daemon doc about signatures. |
2421 | ||
2422 | The main options are: | |
2423 | ||
2424 | @table @code | |
2425 | @item --export | |
2426 | Export the specified store files or packages (see below.) Write the | |
2427 | resulting archive to the standard output. | |
2428 | ||
56607088 LC |
2429 | Dependencies are @emph{not} included in the output, unless |
2430 | @code{--recursive} is passed. | |
2431 | ||
2432 | @item -r | |
2433 | @itemx --recursive | |
2434 | When combined with @code{--export}, this instructs @command{guix | |
2435 | archive} to include dependencies of the given items in the archive. | |
2436 | Thus, the resulting archive is self-contained: it contains the closure | |
2437 | of the exported store items. | |
2438 | ||
760c60d6 LC |
2439 | @item --import |
2440 | Read an archive from the standard input, and import the files listed | |
2441 | therein into the store. Abort if the archive has an invalid digital | |
f82cc5fd LC |
2442 | signature, or if it is signed by a public key not among the authorized |
2443 | keys (see @code{--authorize} below.) | |
554f26ec | 2444 | |
87236aed LC |
2445 | @item --missing |
2446 | Read a list of store file names from the standard input, one per line, | |
2447 | and write on the standard output the subset of these files missing from | |
2448 | the store. | |
2449 | ||
554f26ec | 2450 | @item --generate-key[=@var{parameters}] |
f82cc5fd | 2451 | @cindex signing, archives |
f97c9175 | 2452 | Generate a new key pair for the daemon. This is a prerequisite before |
554f26ec LC |
2453 | archives can be exported with @code{--export}. Note that this operation |
2454 | usually takes time, because it needs to gather enough entropy to | |
2455 | generate the key pair. | |
2456 | ||
2457 | The generated key pair is typically stored under @file{/etc/guix}, in | |
2458 | @file{signing-key.pub} (public key) and @file{signing-key.sec} (private | |
867d8473 LC |
2459 | key, which must be kept secret.) When @var{parameters} is omitted, |
2460 | an ECDSA key using the Ed25519 curve is generated, or, for Libgcrypt | |
2461 | versions before 1.6.0, it is a 4096-bit RSA key. | |
f97c9175 | 2462 | Alternatively, @var{parameters} can specify |
554f26ec LC |
2463 | @code{genkey} parameters suitable for Libgcrypt (@pxref{General |
2464 | public-key related Functions, @code{gcry_pk_genkey},, gcrypt, The | |
2465 | Libgcrypt Reference Manual}). | |
f82cc5fd LC |
2466 | |
2467 | @item --authorize | |
2468 | @cindex authorizing, archives | |
2469 | Authorize imports signed by the public key passed on standard input. | |
2470 | The public key must be in ``s-expression advanced format''---i.e., the | |
2471 | same format as the @file{signing-key.pub} file. | |
2472 | ||
2473 | The list of authorized keys is kept in the human-editable file | |
2474 | @file{/etc/guix/acl}. The file contains | |
2475 | @url{http://people.csail.mit.edu/rivest/Sexp.txt, ``advanced-format | |
2476 | s-expressions''} and is structured as an access-control list in the | |
2477 | @url{http://theworld.com/~cme/spki.txt, Simple Public-Key Infrastructure | |
2478 | (SPKI)}. | |
c6f8e9dd LC |
2479 | |
2480 | @item --extract=@var{directory} | |
2481 | @itemx -x @var{directory} | |
2482 | Read a single-item archive as served by substitute servers | |
2483 | (@pxref{Substitutes}) and extract it to @var{directory}. This is a | |
2484 | low-level operation needed in only very narrow use cases; see below. | |
2485 | ||
2486 | For example, the following command extracts the substitute for Emacs | |
2487 | served by @code{hydra.gnu.org} to @file{/tmp/emacs}: | |
2488 | ||
2489 | @example | |
2490 | $ wget -O - \ | |
df061d07 | 2491 | https://hydra.gnu.org/nar/@dots{}-emacs-24.5 \ |
c6f8e9dd LC |
2492 | | bunzip2 | guix archive -x /tmp/emacs |
2493 | @end example | |
2494 | ||
2495 | Single-item archives are different from multiple-item archives produced | |
2496 | by @command{guix archive --export}; they contain a single store item, | |
2497 | and they do @emph{not} embed a signature. Thus this operation does | |
2498 | @emph{no} signature verification and its output should be considered | |
2499 | unsafe. | |
2500 | ||
2501 | The primary purpose of this operation is to facilitate inspection of | |
2502 | archive contents coming from possibly untrusted substitute servers. | |
2503 | ||
760c60d6 LC |
2504 | @end table |
2505 | ||
c554de89 AK |
2506 | @c ********************************************************************* |
2507 | @include emacs.texi | |
760c60d6 | 2508 | |
568717fd LC |
2509 | @c ********************************************************************* |
2510 | @node Programming Interface | |
2511 | @chapter Programming Interface | |
2512 | ||
3dc1970d LC |
2513 | GNU Guix provides several Scheme programming interfaces (APIs) to |
2514 | define, build, and query packages. The first interface allows users to | |
2515 | write high-level package definitions. These definitions refer to | |
2516 | familiar packaging concepts, such as the name and version of a package, | |
2517 | its build system, and its dependencies. These definitions can then be | |
2518 | turned into concrete build actions. | |
2519 | ||
ba55b1cb | 2520 | Build actions are performed by the Guix daemon, on behalf of users. In a |
3dc1970d | 2521 | standard setup, the daemon has write access to the store---the |
834129e0 | 2522 | @file{/gnu/store} directory---whereas users do not. The recommended |
3dc1970d LC |
2523 | setup also has the daemon perform builds in chroots, under a specific |
2524 | build users, to minimize interference with the rest of the system. | |
2525 | ||
2526 | @cindex derivation | |
2527 | Lower-level APIs are available to interact with the daemon and the | |
2528 | store. To instruct the daemon to perform a build action, users actually | |
2529 | provide it with a @dfn{derivation}. A derivation is a low-level | |
2530 | representation of the build actions to be taken, and the environment in | |
2531 | which they should occur---derivations are to package definitions what | |
49ad317a LC |
2532 | assembly is to C programs. The term ``derivation'' comes from the fact |
2533 | that build results @emph{derive} from them. | |
3dc1970d LC |
2534 | |
2535 | This chapter describes all these APIs in turn, starting from high-level | |
2536 | package definitions. | |
2537 | ||
568717fd | 2538 | @menu |
b860f382 | 2539 | * Defining Packages:: Defining new packages. |
7458bd0a | 2540 | * Build Systems:: Specifying how packages are built. |
b860f382 LC |
2541 | * The Store:: Manipulating the package store. |
2542 | * Derivations:: Low-level interface to package derivations. | |
2543 | * The Store Monad:: Purely functional interface to the store. | |
21b679f6 | 2544 | * G-Expressions:: Manipulating build expressions. |
568717fd LC |
2545 | @end menu |
2546 | ||
2547 | @node Defining Packages | |
2548 | @section Defining Packages | |
2549 | ||
3dc1970d LC |
2550 | The high-level interface to package definitions is implemented in the |
2551 | @code{(guix packages)} and @code{(guix build-system)} modules. As an | |
2552 | example, the package definition, or @dfn{recipe}, for the GNU Hello | |
2553 | package looks like this: | |
2554 | ||
2555 | @example | |
e7f34eb0 LC |
2556 | (define-module (gnu packages hello) |
2557 | #:use-module (guix packages) | |
2558 | #:use-module (guix download) | |
2559 | #:use-module (guix build-system gnu) | |
a6dcdcac SB |
2560 | #:use-module (guix licenses) |
2561 | #:use-module (gnu packages gawk)) | |
b22a12fd | 2562 | |
79f5dd59 | 2563 | (define-public hello |
3dc1970d LC |
2564 | (package |
2565 | (name "hello") | |
17d8e33f | 2566 | (version "2.10") |
3dc1970d | 2567 | (source (origin |
17d8e33f ML |
2568 | (method url-fetch) |
2569 | (uri (string-append "mirror://gnu/hello/hello-" version | |
2570 | ".tar.gz")) | |
2571 | (sha256 | |
2572 | (base32 | |
2573 | "0ssi1wpaf7plaswqqjwigppsg5fyh99vdlb9kzl7c9lng89ndq1i")))) | |
3dc1970d | 2574 | (build-system gnu-build-system) |
654c0d97 | 2575 | (arguments '(#:configure-flags '("--enable-silent-rules"))) |
3dc1970d | 2576 | (inputs `(("gawk" ,gawk))) |
7458bd0a LC |
2577 | (synopsis "Hello, GNU world: An example GNU package") |
2578 | (description "Guess what GNU Hello prints!") | |
3dc1970d | 2579 | (home-page "http://www.gnu.org/software/hello/") |
b22a12fd | 2580 | (license gpl3+))) |
3dc1970d LC |
2581 | @end example |
2582 | ||
2583 | @noindent | |
2584 | Without being a Scheme expert, the reader may have guessed the meaning | |
f97c9175 AE |
2585 | of the various fields here. This expression binds the variable |
2586 | @code{hello} to a @code{<package>} object, which is essentially a record | |
3dc1970d LC |
2587 | (@pxref{SRFI-9, Scheme records,, guile, GNU Guile Reference Manual}). |
2588 | This package object can be inspected using procedures found in the | |
2589 | @code{(guix packages)} module; for instance, @code{(package-name hello)} | |
2590 | returns---surprise!---@code{"hello"}. | |
2591 | ||
2f7d2d91 LC |
2592 | With luck, you may be able to import part or all of the definition of |
2593 | the package you are interested in from another repository, using the | |
2594 | @code{guix import} command (@pxref{Invoking guix import}). | |
2595 | ||
f97c9175 | 2596 | In the example above, @var{hello} is defined in a module of its own, |
e7f34eb0 LC |
2597 | @code{(gnu packages hello)}. Technically, this is not strictly |
2598 | necessary, but it is convenient to do so: all the packages defined in | |
2599 | modules under @code{(gnu packages @dots{})} are automatically known to | |
2600 | the command-line tools (@pxref{Package Modules}). | |
2601 | ||
3dc1970d LC |
2602 | There are a few points worth noting in the above package definition: |
2603 | ||
2604 | @itemize | |
2605 | @item | |
a2bf4907 LC |
2606 | The @code{source} field of the package is an @code{<origin>} object |
2607 | (@pxref{origin Reference}, for the complete reference). | |
3dc1970d LC |
2608 | Here, the @code{url-fetch} method from @code{(guix download)} is used, |
2609 | meaning that the source is a file to be downloaded over FTP or HTTP. | |
2610 | ||
2611 | The @code{mirror://gnu} prefix instructs @code{url-fetch} to use one of | |
2612 | the GNU mirrors defined in @code{(guix download)}. | |
2613 | ||
2614 | The @code{sha256} field specifies the expected SHA256 hash of the file | |
2615 | being downloaded. It is mandatory, and allows Guix to check the | |
2616 | integrity of the file. The @code{(base32 @dots{})} form introduces the | |
6c365eca | 2617 | base32 representation of the hash. You can obtain this information with |
210cc920 LC |
2618 | @code{guix download} (@pxref{Invoking guix download}) and @code{guix |
2619 | hash} (@pxref{Invoking guix hash}). | |
3dc1970d | 2620 | |
f9cc8971 LC |
2621 | @cindex patches |
2622 | When needed, the @code{origin} form can also have a @code{patches} field | |
2623 | listing patches to be applied, and a @code{snippet} field giving a | |
2624 | Scheme expression to modify the source code. | |
2625 | ||
3dc1970d LC |
2626 | @item |
2627 | @cindex GNU Build System | |
7458bd0a LC |
2628 | The @code{build-system} field specifies the procedure to build the |
2629 | package (@pxref{Build Systems}). Here, @var{gnu-build-system} | |
2630 | represents the familiar GNU Build System, where packages may be | |
2631 | configured, built, and installed with the usual @code{./configure && | |
2632 | make && make check && make install} command sequence. | |
2633 | ||
2634 | @item | |
2635 | The @code{arguments} field specifies options for the build system | |
2636 | (@pxref{Build Systems}). Here it is interpreted by | |
2637 | @var{gnu-build-system} as a request run @file{configure} with the | |
2638 | @code{--enable-silent-rules} flag. | |
3dc1970d | 2639 | |
654c0d97 LC |
2640 | @cindex quote |
2641 | @cindex quoting | |
2642 | @findex ' | |
2643 | @findex quote | |
2644 | What about these quote (@code{'}) characters? They are Scheme syntax to | |
2645 | introduce a literal list; @code{'} is synonymous with @code{quote}. | |
2646 | @xref{Expression Syntax, quoting,, guile, GNU Guile Reference Manual}, | |
2647 | for details. Here the value of the @code{arguments} field is a list of | |
2648 | arguments passed to the build system down the road, as with @code{apply} | |
2649 | (@pxref{Fly Evaluation, @code{apply},, guile, GNU Guile Reference | |
2650 | Manual}). | |
2651 | ||
2652 | The hash-colon (@code{#:}) sequence defines a Scheme @dfn{keyword} | |
2653 | (@pxref{Keywords,,, guile, GNU Guile Reference Manual}), and | |
2654 | @code{#:configure-flags} is a keyword used to pass a keyword argument | |
2655 | to the build system (@pxref{Coding With Keywords,,, guile, GNU Guile | |
2656 | Reference Manual}). | |
2657 | ||
3dc1970d LC |
2658 | @item |
2659 | The @code{inputs} field specifies inputs to the build process---i.e., | |
2660 | build-time or run-time dependencies of the package. Here, we define an | |
2661 | input called @code{"gawk"} whose value is that of the @var{gawk} | |
2662 | variable; @var{gawk} is itself bound to a @code{<package>} object. | |
2663 | ||
654c0d97 LC |
2664 | @cindex backquote (quasiquote) |
2665 | @findex ` | |
2666 | @findex quasiquote | |
2667 | @cindex comma (unquote) | |
2668 | @findex , | |
2669 | @findex unquote | |
2670 | @findex ,@@ | |
2671 | @findex unquote-splicing | |
2672 | Again, @code{`} (a backquote, synonymous with @code{quasiquote}) allows | |
2673 | us to introduce a literal list in the @code{inputs} field, while | |
2674 | @code{,} (a comma, synonymous with @code{unquote}) allows us to insert a | |
2675 | value in that list (@pxref{Expression Syntax, unquote,, guile, GNU Guile | |
2676 | Reference Manual}). | |
2677 | ||
3dc1970d LC |
2678 | Note that GCC, Coreutils, Bash, and other essential tools do not need to |
2679 | be specified as inputs here. Instead, @var{gnu-build-system} takes care | |
7458bd0a | 2680 | of ensuring that they are present (@pxref{Build Systems}). |
3dc1970d LC |
2681 | |
2682 | However, any other dependencies need to be specified in the | |
2683 | @code{inputs} field. Any dependency not specified here will simply be | |
2684 | unavailable to the build process, possibly leading to a build failure. | |
2685 | @end itemize | |
2686 | ||
87eafdbd TUBK |
2687 | @xref{package Reference}, for a full description of possible fields. |
2688 | ||
2f7d2d91 | 2689 | Once a package definition is in place, the |
e49951eb | 2690 | package may actually be built using the @code{guix build} command-line |
39bee8a2 LC |
2691 | tool (@pxref{Invoking guix build}). You can easily jump back to the |
2692 | package definition using the @command{guix edit} command | |
2693 | (@pxref{Invoking guix edit}). | |
2694 | @xref{Packaging Guidelines}, for | |
b4f5e0e8 CR |
2695 | more information on how to test package definitions, and |
2696 | @ref{Invoking guix lint}, for information on how to check a definition | |
2697 | for style conformance. | |
2698 | ||
f97c9175 | 2699 | Finally, updating the package definition to a new upstream version |
7458bd0a LC |
2700 | can be partly automated by the @command{guix refresh} command |
2701 | (@pxref{Invoking guix refresh}). | |
3dc1970d LC |
2702 | |
2703 | Behind the scenes, a derivation corresponding to the @code{<package>} | |
2704 | object is first computed by the @code{package-derivation} procedure. | |
834129e0 | 2705 | That derivation is stored in a @code{.drv} file under @file{/gnu/store}. |
ba55b1cb | 2706 | The build actions it prescribes may then be realized by using the |
3dc1970d LC |
2707 | @code{build-derivations} procedure (@pxref{The Store}). |
2708 | ||
2709 | @deffn {Scheme Procedure} package-derivation @var{store} @var{package} [@var{system}] | |
59688fc4 LC |
2710 | Return the @code{<derivation>} object of @var{package} for @var{system} |
2711 | (@pxref{Derivations}). | |
3dc1970d LC |
2712 | |
2713 | @var{package} must be a valid @code{<package>} object, and @var{system} | |
2714 | must be a string denoting the target system type---e.g., | |
2715 | @code{"x86_64-linux"} for an x86_64 Linux-based GNU system. @var{store} | |
2716 | must be a connection to the daemon, which operates on the store | |
2717 | (@pxref{The Store}). | |
2718 | @end deffn | |
568717fd | 2719 | |
9c1edabd LC |
2720 | @noindent |
2721 | @cindex cross-compilation | |
2722 | Similarly, it is possible to compute a derivation that cross-builds a | |
2723 | package for some other system: | |
2724 | ||
2725 | @deffn {Scheme Procedure} package-cross-derivation @var{store} @ | |
2726 | @var{package} @var{target} [@var{system}] | |
59688fc4 LC |
2727 | Return the @code{<derivation>} object of @var{package} cross-built from |
2728 | @var{system} to @var{target}. | |
9c1edabd LC |
2729 | |
2730 | @var{target} must be a valid GNU triplet denoting the target hardware | |
2731 | and operating system, such as @code{"mips64el-linux-gnu"} | |
2732 | (@pxref{Configuration Names, GNU configuration triplets,, configure, GNU | |
2733 | Configure and Build System}). | |
2734 | @end deffn | |
2735 | ||
2a75b0b6 LC |
2736 | @cindex package transformations |
2737 | @cindex input rewriting | |
2738 | @cindex dependency tree rewriting | |
2739 | Packages can be manipulated in arbitrary ways. An example of a useful | |
2740 | transformation is @dfn{input rewriting}, whereby the dependency tree of | |
2741 | a package is rewritten by replacing specific inputs by others: | |
2742 | ||
2743 | @deffn {Scheme Procedure} package-input-rewriting @var{replacements} @ | |
2744 | [@var{rewrite-name}] | |
2745 | Return a procedure that, when passed a package, replaces its direct and | |
2746 | indirect dependencies (but not its implicit inputs) according to | |
2747 | @var{replacements}. @var{replacements} is a list of package pairs; the | |
2748 | first element of each pair is the package to replace, and the second one | |
2749 | is the replacement. | |
2750 | ||
2751 | Optionally, @var{rewrite-name} is a one-argument procedure that takes | |
2752 | the name of a package and returns its new name after rewrite. | |
2753 | @end deffn | |
2754 | ||
2755 | @noindent | |
2756 | Consider this example: | |
2757 | ||
2758 | @example | |
2759 | (define libressl-instead-of-openssl | |
2760 | ;; This is a procedure to replace OPENSSL by LIBRESSL, | |
2761 | ;; recursively. | |
2762 | (package-input-rewriting `((,openssl . ,libressl)))) | |
2763 | ||
2764 | (define git-with-libressl | |
2765 | (libressl-instead-of-openssl git)) | |
2766 | @end example | |
2767 | ||
2768 | @noindent | |
2769 | Here we first define a rewriting procedure that replaces @var{openssl} | |
2770 | with @var{libressl}. Then we use it to define a @dfn{variant} of the | |
2771 | @var{git} package that uses @var{libressl} instead of @var{openssl}. | |
2772 | This is exactly what the @option{--with-input} command-line option does | |
2773 | (@pxref{Package Transformation Options, @option{--with-input}}). | |
2774 | ||
87eafdbd TUBK |
2775 | @menu |
2776 | * package Reference :: The package data type. | |
2777 | * origin Reference:: The origin data type. | |
2778 | @end menu | |
2779 | ||
2780 | ||
2781 | @node package Reference | |
2782 | @subsection @code{package} Reference | |
2783 | ||
2784 | This section summarizes all the options available in @code{package} | |
2785 | declarations (@pxref{Defining Packages}). | |
2786 | ||
2787 | @deftp {Data Type} package | |
2788 | This is the data type representing a package recipe. | |
2789 | ||
2790 | @table @asis | |
2791 | @item @code{name} | |
2792 | The name of the package, as a string. | |
2793 | ||
2794 | @item @code{version} | |
2795 | The version of the package, as a string. | |
2796 | ||
2797 | @item @code{source} | |
da675305 LC |
2798 | An object telling how the source code for the package should be |
2799 | acquired. Most of the time, this is an @code{origin} object, which | |
2800 | denotes a file fetched from the Internet (@pxref{origin Reference}). It | |
2801 | can also be any other ``file-like'' object such as a @code{local-file}, | |
2802 | which denotes a file from the local file system (@pxref{G-Expressions, | |
2803 | @code{local-file}}). | |
87eafdbd TUBK |
2804 | |
2805 | @item @code{build-system} | |
2806 | The build system that should be used to build the package (@pxref{Build | |
2807 | Systems}). | |
2808 | ||
2809 | @item @code{arguments} (default: @code{'()}) | |
2810 | The arguments that should be passed to the build system. This is a | |
2811 | list, typically containing sequential keyword-value pairs. | |
2812 | ||
2813 | @item @code{inputs} (default: @code{'()}) | |
70650c68 LC |
2814 | @itemx @code{native-inputs} (default: @code{'()}) |
2815 | @itemx @code{propagated-inputs} (default: @code{'()}) | |
2816 | @cindex inputs, of packages | |
2817 | These fields list dependencies of the package. Each one is a list of | |
2818 | tuples, where each tuple has a label for the input (a string) as its | |
2819 | first element, a package, origin, or derivation as its second element, | |
2820 | and optionally the name of the output thereof that should be used, which | |
2821 | defaults to @code{"out"} (@pxref{Packages with Multiple Outputs}, for | |
f97c9175 | 2822 | more on package outputs). For example, the list below specifies three |
70650c68 | 2823 | inputs: |
87eafdbd | 2824 | |
70650c68 LC |
2825 | @example |
2826 | `(("libffi" ,libffi) | |
2827 | ("libunistring" ,libunistring) | |
2828 | ("glib:bin" ,glib "bin")) ;the "bin" output of Glib | |
2829 | @end example | |
2830 | ||
2831 | @cindex cross compilation, package dependencies | |
2832 | The distinction between @code{native-inputs} and @code{inputs} is | |
2833 | necessary when considering cross-compilation. When cross-compiling, | |
2834 | dependencies listed in @code{inputs} are built for the @emph{target} | |
2835 | architecture; conversely, dependencies listed in @code{native-inputs} | |
2836 | are built for the architecture of the @emph{build} machine. | |
2837 | ||
f97c9175 AE |
2838 | @code{native-inputs} is typically used to list tools needed at |
2839 | build time, but not at run time, such as Autoconf, Automake, pkg-config, | |
70650c68 LC |
2840 | Gettext, or Bison. @command{guix lint} can report likely mistakes in |
2841 | this area (@pxref{Invoking guix lint}). | |
2842 | ||
2843 | @anchor{package-propagated-inputs} | |
2844 | Lastly, @code{propagated-inputs} is similar to @code{inputs}, but the | |
f97c9175 AE |
2845 | specified packages will be automatically installed alongside the package |
2846 | they belong to (@pxref{package-cmd-propagated-inputs, @command{guix | |
70650c68 LC |
2847 | package}}, for information on how @command{guix package} deals with |
2848 | propagated inputs.) | |
21461f27 | 2849 | |
e0508b6b LC |
2850 | For example this is necessary when a C/C++ library needs headers of |
2851 | another library to compile, or when a pkg-config file refers to another | |
2852 | one @i{via} its @code{Requires} field. | |
2853 | ||
f97c9175 AE |
2854 | Another example where @code{propagated-inputs} is useful is for languages |
2855 | that lack a facility to record the run-time search path akin to the | |
c8ebb4c4 | 2856 | @code{RUNPATH} of ELF files; this includes Guile, Python, Perl, and |
e0508b6b LC |
2857 | more. To ensure that libraries written in those languages can find |
2858 | library code they depend on at run time, run-time dependencies must be | |
2859 | listed in @code{propagated-inputs} rather than @code{inputs}. | |
87eafdbd | 2860 | |
87eafdbd TUBK |
2861 | @item @code{self-native-input?} (default: @code{#f}) |
2862 | This is a Boolean field telling whether the package should use itself as | |
2863 | a native input when cross-compiling. | |
2864 | ||
2865 | @item @code{outputs} (default: @code{'("out")}) | |
2866 | The list of output names of the package. @xref{Packages with Multiple | |
2867 | Outputs}, for typical uses of additional outputs. | |
2868 | ||
2869 | @item @code{native-search-paths} (default: @code{'()}) | |
2870 | @itemx @code{search-paths} (default: @code{'()}) | |
2871 | A list of @code{search-path-specification} objects describing | |
2872 | search-path environment variables honored by the package. | |
2873 | ||
2874 | @item @code{replacement} (default: @code{#f}) | |
f97c9175 | 2875 | This must be either @code{#f} or a package object that will be used as a |
87eafdbd TUBK |
2876 | @dfn{replacement} for this package. @xref{Security Updates, grafts}, |
2877 | for details. | |
2878 | ||
2879 | @item @code{synopsis} | |
2880 | A one-line description of the package. | |
2881 | ||
2882 | @item @code{description} | |
2883 | A more elaborate description of the package. | |
2884 | ||
2885 | @item @code{license} | |
e32171ee | 2886 | @cindex license, of packages |
f97c9175 AE |
2887 | The license of the package; a value from @code{(guix licenses)}, |
2888 | or a list of such values. | |
87eafdbd TUBK |
2889 | |
2890 | @item @code{home-page} | |
2891 | The URL to the home-page of the package, as a string. | |
2892 | ||
2893 | @item @code{supported-systems} (default: @var{%supported-systems}) | |
2894 | The list of systems supported by the package, as strings of the form | |
2895 | @code{architecture-kernel}, for example @code{"x86_64-linux"}. | |
2896 | ||
2897 | @item @code{maintainers} (default: @code{'()}) | |
2898 | The list of maintainers of the package, as @code{maintainer} objects. | |
2899 | ||
2900 | @item @code{location} (default: source location of the @code{package} form) | |
f97c9175 | 2901 | The source location of the package. It is useful to override this when |
87eafdbd TUBK |
2902 | inheriting from another package, in which case this field is not |
2903 | automatically corrected. | |
2904 | @end table | |
2905 | @end deftp | |
2906 | ||
2907 | ||
2908 | @node origin Reference | |
2909 | @subsection @code{origin} Reference | |
2910 | ||
2911 | This section summarizes all the options available in @code{origin} | |
2912 | declarations (@pxref{Defining Packages}). | |
2913 | ||
2914 | @deftp {Data Type} origin | |
2915 | This is the data type representing a source code origin. | |
2916 | ||
2917 | @table @asis | |
2918 | @item @code{uri} | |
2919 | An object containing the URI of the source. The object type depends on | |
2920 | the @code{method} (see below). For example, when using the | |
2921 | @var{url-fetch} method of @code{(guix download)}, the valid @code{uri} | |
2922 | values are: a URL represented as a string, or a list thereof. | |
2923 | ||
2924 | @item @code{method} | |
f97c9175 | 2925 | A procedure that handles the URI. |
87eafdbd TUBK |
2926 | |
2927 | Examples include: | |
2928 | ||
2929 | @table @asis | |
2930 | @item @var{url-fetch} from @code{(guix download)} | |
f97c9175 | 2931 | download a file from the HTTP, HTTPS, or FTP URL specified in the |
87eafdbd TUBK |
2932 | @code{uri} field; |
2933 | ||
db97a03a | 2934 | @vindex git-fetch |
87eafdbd TUBK |
2935 | @item @var{git-fetch} from @code{(guix git-download)} |
2936 | clone the Git version control repository, and check out the revision | |
2937 | specified in the @code{uri} field as a @code{git-reference} object; a | |
2938 | @code{git-reference} looks like this: | |
2939 | ||
2940 | @example | |
2941 | (git-reference | |
2942 | (url "git://git.debian.org/git/pkg-shadow/shadow") | |
2943 | (commit "v4.1.5.1")) | |
2944 | @end example | |
2945 | @end table | |
2946 | ||
2947 | @item @code{sha256} | |
2948 | A bytevector containing the SHA-256 hash of the source. Typically the | |
2949 | @code{base32} form is used here to generate the bytevector from a | |
2950 | base-32 string. | |
2951 | ||
db97a03a LC |
2952 | You can obtain this information using @code{guix download} |
2953 | (@pxref{Invoking guix download}) or @code{guix hash} (@pxref{Invoking | |
2954 | guix hash}). | |
2955 | ||
87eafdbd TUBK |
2956 | @item @code{file-name} (default: @code{#f}) |
2957 | The file name under which the source code should be saved. When this is | |
2958 | @code{#f}, a sensible default value will be used in most cases. In case | |
2959 | the source is fetched from a URL, the file name from the URL will be | |
f97c9175 | 2960 | used. For version control checkouts, it is recommended to provide the |
87eafdbd TUBK |
2961 | file name explicitly because the default is not very descriptive. |
2962 | ||
2963 | @item @code{patches} (default: @code{'()}) | |
2964 | A list of file names containing patches to be applied to the source. | |
2965 | ||
0dfebdaa LC |
2966 | This list of patches must be unconditional. In particular, it cannot |
2967 | depend on the value of @code{%current-system} or | |
2968 | @code{%current-target-system}. | |
2969 | ||
87eafdbd | 2970 | @item @code{snippet} (default: @code{#f}) |
1929fdba LC |
2971 | A G-expression (@pxref{G-Expressions}) or S-expression that will be run |
2972 | in the source directory. This is a convenient way to modify the source, | |
2973 | sometimes more convenient than a patch. | |
87eafdbd TUBK |
2974 | |
2975 | @item @code{patch-flags} (default: @code{'("-p1")}) | |
2976 | A list of command-line flags that should be passed to the @code{patch} | |
2977 | command. | |
2978 | ||
2979 | @item @code{patch-inputs} (default: @code{#f}) | |
2980 | Input packages or derivations to the patching process. When this is | |
2981 | @code{#f}, the usual set of inputs necessary for patching are provided, | |
2982 | such as GNU@tie{}Patch. | |
2983 | ||
2984 | @item @code{modules} (default: @code{'()}) | |
2985 | A list of Guile modules that should be loaded during the patching | |
2986 | process and while running the code in the @code{snippet} field. | |
2987 | ||
87eafdbd TUBK |
2988 | @item @code{patch-guile} (default: @code{#f}) |
2989 | The Guile package that should be used in the patching process. When | |
2990 | this is @code{#f}, a sensible default is used. | |
2991 | @end table | |
2992 | @end deftp | |
2993 | ||
9c1edabd | 2994 | |
7458bd0a LC |
2995 | @node Build Systems |
2996 | @section Build Systems | |
2997 | ||
2998 | @cindex build system | |
2999 | Each package definition specifies a @dfn{build system} and arguments for | |
3000 | that build system (@pxref{Defining Packages}). This @code{build-system} | |
f97c9175 | 3001 | field represents the build procedure of the package, as well as implicit |
7458bd0a LC |
3002 | dependencies of that build procedure. |
3003 | ||
3004 | Build systems are @code{<build-system>} objects. The interface to | |
3005 | create and manipulate them is provided by the @code{(guix build-system)} | |
3006 | module, and actual build systems are exported by specific modules. | |
3007 | ||
f5fd4fd2 | 3008 | @cindex bag (low-level package representation) |
0d5a559f LC |
3009 | Under the hood, build systems first compile package objects to |
3010 | @dfn{bags}. A @dfn{bag} is like a package, but with less | |
3011 | ornamentation---in other words, a bag is a lower-level representation of | |
3012 | a package, which includes all the inputs of that package, including some | |
3013 | that were implicitly added by the build system. This intermediate | |
3014 | representation is then compiled to a derivation (@pxref{Derivations}). | |
3015 | ||
7458bd0a LC |
3016 | Build systems accept an optional list of @dfn{arguments}. In package |
3017 | definitions, these are passed @i{via} the @code{arguments} field | |
3018 | (@pxref{Defining Packages}). They are typically keyword arguments | |
3019 | (@pxref{Optional Arguments, keyword arguments in Guile,, guile, GNU | |
3020 | Guile Reference Manual}). The value of these arguments is usually | |
3021 | evaluated in the @dfn{build stratum}---i.e., by a Guile process launched | |
3022 | by the daemon (@pxref{Derivations}). | |
3023 | ||
3024 | The main build system is @var{gnu-build-system}, which implements the | |
f97c9175 | 3025 | standard build procedure for GNU and many other packages. It |
7458bd0a LC |
3026 | is provided by the @code{(guix build-system gnu)} module. |
3027 | ||
3028 | @defvr {Scheme Variable} gnu-build-system | |
3029 | @var{gnu-build-system} represents the GNU Build System, and variants | |
3030 | thereof (@pxref{Configuration, configuration and makefile conventions,, | |
3031 | standards, GNU Coding Standards}). | |
3032 | ||
3033 | @cindex build phases | |
f97c9175 | 3034 | In a nutshell, packages using it are configured, built, and installed with |
7458bd0a LC |
3035 | the usual @code{./configure && make && make check && make install} |
3036 | command sequence. In practice, a few additional steps are often needed. | |
3037 | All these steps are split up in separate @dfn{phases}, | |
3038 | notably@footnote{Please see the @code{(guix build gnu-build-system)} | |
3039 | modules for more details about the build phases.}: | |
3040 | ||
3041 | @table @code | |
3042 | @item unpack | |
3043 | Unpack the source tarball, and change the current directory to the | |
3044 | extracted source tree. If the source is actually a directory, copy it | |
3045 | to the build tree, and enter that directory. | |
3046 | ||
3047 | @item patch-source-shebangs | |
3048 | Patch shebangs encountered in source files so they refer to the right | |
3049 | store file names. For instance, this changes @code{#!/bin/sh} to | |
3050 | @code{#!/gnu/store/@dots{}-bash-4.3/bin/sh}. | |
3051 | ||
3052 | @item configure | |
3053 | Run the @file{configure} script with a number of default options, such | |
3054 | as @code{--prefix=/gnu/store/@dots{}}, as well as the options specified | |
3055 | by the @code{#:configure-flags} argument. | |
3056 | ||
3057 | @item build | |
3058 | Run @code{make} with the list of flags specified with | |
0917e80e | 3059 | @code{#:make-flags}. If the @code{#:parallel-build?} argument is true |
7458bd0a LC |
3060 | (the default), build with @code{make -j}. |
3061 | ||
3062 | @item check | |
3063 | Run @code{make check}, or some other target specified with | |
3064 | @code{#:test-target}, unless @code{#:tests? #f} is passed. If the | |
3065 | @code{#:parallel-tests?} argument is true (the default), run @code{make | |
3066 | check -j}. | |
3067 | ||
3068 | @item install | |
3069 | Run @code{make install} with the flags listed in @code{#:make-flags}. | |
3070 | ||
3071 | @item patch-shebangs | |
3072 | Patch shebangs on the installed executable files. | |
3073 | ||
3074 | @item strip | |
3075 | Strip debugging symbols from ELF files (unless @code{#:strip-binaries?} | |
3076 | is false), copying them to the @code{debug} output when available | |
3077 | (@pxref{Installing Debugging Files}). | |
3078 | @end table | |
3079 | ||
3080 | @vindex %standard-phases | |
3081 | The build-side module @code{(guix build gnu-build-system)} defines | |
3082 | @var{%standard-phases} as the default list of build phases. | |
3083 | @var{%standard-phases} is a list of symbol/procedure pairs, where the | |
3084 | procedure implements the actual phase. | |
3085 | ||
3086 | The list of phases used for a particular package can be changed with the | |
3087 | @code{#:phases} parameter. For instance, passing: | |
3088 | ||
3089 | @example | |
c2c5dc79 | 3090 | #:phases (modify-phases %standard-phases (delete 'configure)) |
7458bd0a LC |
3091 | @end example |
3092 | ||
9bf404e9 | 3093 | means that all the phases described above will be used, except the |
7458bd0a LC |
3094 | @code{configure} phase. |
3095 | ||
3096 | In addition, this build system ensures that the ``standard'' environment | |
3097 | for GNU packages is available. This includes tools such as GCC, libc, | |
3098 | Coreutils, Bash, Make, Diffutils, grep, and sed (see the @code{(guix | |
f97c9175 AE |
3099 | build-system gnu)} module for a complete list). We call these the |
3100 | @dfn{implicit inputs} of a package, because package definitions do not | |
7458bd0a LC |
3101 | have to mention them. |
3102 | @end defvr | |
3103 | ||
3104 | Other @code{<build-system>} objects are defined to support other | |
3105 | conventions and tools used by free software packages. They inherit most | |
3106 | of @var{gnu-build-system}, and differ mainly in the set of inputs | |
3107 | implicitly added to the build process, and in the list of phases | |
3108 | executed. Some of these build systems are listed below. | |
3109 | ||
5f7a1a4d RW |
3110 | @defvr {Scheme Variable} ant-build-system |
3111 | This variable is exported by @code{(guix build-system ant)}. It | |
3112 | implements the build procedure for Java packages that can be built with | |
3113 | @url{http://ant.apache.org/, Ant build tool}. | |
3114 | ||
3115 | It adds both @code{ant} and the @dfn{Java Development Kit} (JDK) as | |
3116 | provided by the @code{icedtea} package to the set of inputs. Different | |
3117 | packages can be specified with the @code{#:ant} and @code{#:jdk} | |
3118 | parameters, respectively. | |
3119 | ||
3120 | When the original package does not provide a suitable Ant build file, | |
3121 | the parameter @code{#:jar-name} can be used to generate a minimal Ant | |
3122 | build file @file{build.xml} with tasks to build the specified jar | |
3123 | archive. | |
3124 | ||
3125 | The parameter @code{#:build-target} can be used to specify the Ant task | |
3126 | that should be run during the @code{build} phase. By default the | |
3127 | ``jar'' task will be run. | |
3128 | ||
3129 | @end defvr | |
3130 | ||
a1b30f99 AP |
3131 | @defvr {Scheme Variable} asdf-build-system/source |
3132 | @defvrx {Scheme Variable} asdf-build-system/sbcl | |
3133 | @defvrx {Scheme Variable} asdf-build-system/ecl | |
3134 | ||
3135 | These variables, exported by @code{(guix build-system asdf)}, implement | |
3136 | build procedures for Common Lisp packages using | |
3137 | @url{https://common-lisp.net/project/asdf/, ``ASDF''}. ASDF is a system | |
3138 | definition facility for Common Lisp programs and libraries. | |
3139 | ||
3140 | The @code{asdf-build-system/source} system installs the packages in | |
3141 | source form, and can be loaded using any common lisp implementation, via | |
3142 | ASDF. The others, such as @code{asdf-build-system/sbcl}, install binary | |
3143 | systems in the format which a particular implementation understands. | |
3144 | These build systems can also be used to produce executable programs, or | |
3145 | lisp images which contain a set of packages pre-loaded. | |
3146 | ||
3147 | The build system uses naming conventions. For binary packages, the | |
3148 | package itself as well as its run-time dependencies should begin their | |
3149 | name with the lisp implementation, such as @code{sbcl-} for | |
3150 | @code{asdf-build-system/sbcl}. Beginning the input name with this | |
3151 | prefix will allow the build system to encode its location into the | |
3152 | resulting library, so that the input can be found at run-time. | |
3153 | ||
3154 | If dependencies are used only for tests, it is convenient to use a | |
3155 | different prefix in order to avoid having a run-time dependency on such | |
3156 | systems. For example, | |
3157 | ||
3158 | @example | |
3159 | (define-public sbcl-bordeaux-threads | |
3160 | (package | |
3161 | ... | |
3162 | (native-inputs `(("tests:cl-fiveam" ,sbcl-fiveam))) | |
3163 | ...)) | |
3164 | @end example | |
3165 | ||
3166 | Additionally, the corresponding source package should be labeled using | |
3167 | the same convention as python packages (see @ref{Python Modules}), using | |
3168 | the @code{cl-} prefix. | |
3169 | ||
3170 | For binary packages, each system should be defined as a Guix package. | |
3171 | If one package @code{origin} contains several systems, package variants | |
3172 | can be created in order to build all the systems. Source packages, | |
3173 | which use @code{asdf-build-system/source}, may contain several systems. | |
3174 | ||
3175 | In order to create executable programs and images, the build-side | |
3176 | procedures @code{build-program} and @code{build-image} can be used. | |
3177 | They should be called in a build phase after the @code{create-symlinks} | |
3178 | phase, so that the system which was just built can be used within the | |
3179 | resulting image. @code{build-program} requires a list of Common Lisp | |
3180 | expressions to be passed as the @code{#:entry-program} argument. | |
3181 | ||
3182 | If the system is not defined within its own @code{.asd} file of the same | |
3183 | name, then the @code{#:asd-file} parameter should be used to specify | |
3184 | which file the system is defined in. | |
3185 | ||
3186 | @end defvr | |
3187 | ||
7458bd0a LC |
3188 | @defvr {Scheme Variable} cmake-build-system |
3189 | This variable is exported by @code{(guix build-system cmake)}. It | |
3190 | implements the build procedure for packages using the | |
3191 | @url{http://www.cmake.org, CMake build tool}. | |
3192 | ||
3193 | It automatically adds the @code{cmake} package to the set of inputs. | |
3194 | Which package is used can be specified with the @code{#:cmake} | |
3195 | parameter. | |
9849cfc1 LC |
3196 | |
3197 | The @code{#:configure-flags} parameter is taken as a list of flags | |
3198 | passed to the @command{cmake} command. The @code{#:build-type} | |
3199 | parameter specifies in abstract terms the flags passed to the compiler; | |
3200 | it defaults to @code{"RelWithDebInfo"} (short for ``release mode with | |
3201 | debugging information''), which roughly means that code is compiled with | |
3202 | @code{-O2 -g}, as is the case for Autoconf-based packages by default. | |
7458bd0a LC |
3203 | @end defvr |
3204 | ||
3afcf52b FB |
3205 | @defvr {Scheme Variable} glib-or-gtk-build-system |
3206 | This variable is exported by @code{(guix build-system glib-or-gtk)}. It | |
3207 | is intended for use with packages making use of GLib or GTK+. | |
3208 | ||
3209 | This build system adds the following two phases to the ones defined by | |
3210 | @var{gnu-build-system}: | |
3211 | ||
3212 | @table @code | |
3213 | @item glib-or-gtk-wrap | |
f97c9175 AE |
3214 | The phase @code{glib-or-gtk-wrap} ensures that programs in |
3215 | @file{bin/} are able to find GLib ``schemas'' and | |
3afcf52b FB |
3216 | @uref{https://developer.gnome.org/gtk3/stable/gtk-running.html, GTK+ |
3217 | modules}. This is achieved by wrapping the programs in launch scripts | |
3218 | that appropriately set the @code{XDG_DATA_DIRS} and @code{GTK_PATH} | |
3219 | environment variables. | |
3220 | ||
73aa8ddb LC |
3221 | It is possible to exclude specific package outputs from that wrapping |
3222 | process by listing their names in the | |
3223 | @code{#:glib-or-gtk-wrap-excluded-outputs} parameter. This is useful | |
3224 | when an output is known not to contain any GLib or GTK+ binaries, and | |
3225 | where wrapping would gratuitously add a dependency of that output on | |
3226 | GLib and GTK+. | |
3227 | ||
3afcf52b | 3228 | @item glib-or-gtk-compile-schemas |
f97c9175 | 3229 | The phase @code{glib-or-gtk-compile-schemas} makes sure that all |
3afcf52b | 3230 | @uref{https://developer.gnome.org/gio/stable/glib-compile-schemas.html, |
f97c9175 | 3231 | GSettings schemas} of GLib are compiled. Compilation is performed by the |
3afcf52b FB |
3232 | @command{glib-compile-schemas} program. It is provided by the package |
3233 | @code{glib:bin} which is automatically imported by the build system. | |
3234 | The @code{glib} package providing @command{glib-compile-schemas} can be | |
3235 | specified with the @code{#:glib} parameter. | |
3236 | @end table | |
3237 | ||
3238 | Both phases are executed after the @code{install} phase. | |
3239 | @end defvr | |
3240 | ||
7458bd0a LC |
3241 | @defvr {Scheme Variable} python-build-system |
3242 | This variable is exported by @code{(guix build-system python)}. It | |
3243 | implements the more or less standard build procedure used by Python | |
3244 | packages, which consists in running @code{python setup.py build} and | |
3245 | then @code{python setup.py install --prefix=/gnu/store/@dots{}}. | |
3246 | ||
3247 | For packages that install stand-alone Python programs under @code{bin/}, | |
f97c9175 | 3248 | it takes care of wrapping these programs so that their @code{PYTHONPATH} |
7458bd0a LC |
3249 | environment variable points to all the Python libraries they depend on. |
3250 | ||
8a46205b CM |
3251 | Which Python package is used to perform the build can be specified with |
3252 | the @code{#:python} parameter. This is a useful way to force a package | |
3253 | to be built for a specific version of the Python interpreter, which | |
3254 | might be necessary if the package is only compatible with a single | |
3255 | interpreter version. | |
5f7565d1 HG |
3256 | |
3257 | By default guix calls @code{setup.py} under control of | |
3258 | @code{setuptools}, much like @command{pip} does. Some packages are not | |
3259 | compatible with setuptools (and pip), thus you can disable this by | |
3260 | setting the @code{#:use-setuptools} parameter to @code{#f}. | |
7458bd0a LC |
3261 | @end defvr |
3262 | ||
3263 | @defvr {Scheme Variable} perl-build-system | |
3264 | This variable is exported by @code{(guix build-system perl)}. It | |
2d2a53fc EB |
3265 | implements the standard build procedure for Perl packages, which either |
3266 | consists in running @code{perl Build.PL --prefix=/gnu/store/@dots{}}, | |
3267 | followed by @code{Build} and @code{Build install}; or in running | |
3268 | @code{perl Makefile.PL PREFIX=/gnu/store/@dots{}}, followed by | |
f97c9175 | 3269 | @code{make} and @code{make install}, depending on which of |
2d2a53fc EB |
3270 | @code{Build.PL} or @code{Makefile.PL} is present in the package |
3271 | distribution. Preference is given to the former if both @code{Build.PL} | |
3272 | and @code{Makefile.PL} exist in the package distribution. This | |
3273 | preference can be reversed by specifying @code{#t} for the | |
3274 | @code{#:make-maker?} parameter. | |
3275 | ||
3276 | The initial @code{perl Makefile.PL} or @code{perl Build.PL} invocation | |
3277 | passes flags specified by the @code{#:make-maker-flags} or | |
3278 | @code{#:module-build-flags} parameter, respectively. | |
7458bd0a LC |
3279 | |
3280 | Which Perl package is used can be specified with @code{#:perl}. | |
3281 | @end defvr | |
3282 | ||
f8f3bef6 RW |
3283 | @defvr {Scheme Variable} r-build-system |
3284 | This variable is exported by @code{(guix build-system r)}. It | |
3285 | implements the build procedure used by @uref{http://r-project.org, R} | |
3286 | packages, which essentially is little more than running @code{R CMD | |
3287 | INSTALL --library=/gnu/store/@dots{}} in an environment where | |
3288 | @code{R_LIBS_SITE} contains the paths to all R package inputs. Tests | |
3289 | are run after installation using the R function | |
3290 | @code{tools::testInstalledPackage}. | |
3291 | @end defvr | |
3292 | ||
c08f9818 DT |
3293 | @defvr {Scheme Variable} ruby-build-system |
3294 | This variable is exported by @code{(guix build-system ruby)}. It | |
3295 | implements the RubyGems build procedure used by Ruby packages, which | |
3296 | involves running @code{gem build} followed by @code{gem install}. | |
3297 | ||
5dc87623 DT |
3298 | The @code{source} field of a package that uses this build system |
3299 | typically references a gem archive, since this is the format that Ruby | |
3300 | developers use when releasing their software. The build system unpacks | |
3301 | the gem archive, potentially patches the source, runs the test suite, | |
3302 | repackages the gem, and installs it. Additionally, directories and | |
3303 | tarballs may be referenced to allow building unreleased gems from Git or | |
3304 | a traditional source release tarball. | |
e83c6d00 | 3305 | |
c08f9818 | 3306 | Which Ruby package is used can be specified with the @code{#:ruby} |
6e9f2913 PP |
3307 | parameter. A list of additional flags to be passed to the @command{gem} |
3308 | command can be specified with the @code{#:gem-flags} parameter. | |
c08f9818 | 3309 | @end defvr |
7458bd0a | 3310 | |
a677c726 RW |
3311 | @defvr {Scheme Variable} waf-build-system |
3312 | This variable is exported by @code{(guix build-system waf)}. It | |
3313 | implements a build procedure around the @code{waf} script. The common | |
3314 | phases---@code{configure}, @code{build}, and @code{install}---are | |
3315 | implemented by passing their names as arguments to the @code{waf} | |
3316 | script. | |
3317 | ||
3318 | The @code{waf} script is executed by the Python interpreter. Which | |
3319 | Python package is used to run the script can be specified with the | |
3320 | @code{#:python} parameter. | |
3321 | @end defvr | |
3322 | ||
14dfdf2e FB |
3323 | @defvr {Scheme Variable} haskell-build-system |
3324 | This variable is exported by @code{(guix build-system haskell)}. It | |
3325 | implements the Cabal build procedure used by Haskell packages, which | |
3326 | involves running @code{runhaskell Setup.hs configure | |
3327 | --prefix=/gnu/store/@dots{}} and @code{runhaskell Setup.hs build}. | |
3328 | Instead of installing the package by running @code{runhaskell Setup.hs | |
3329 | install}, to avoid trying to register libraries in the read-only | |
3330 | compiler store directory, the build system uses @code{runhaskell | |
3331 | Setup.hs copy}, followed by @code{runhaskell Setup.hs register}. In | |
3332 | addition, the build system generates the package documentation by | |
3333 | running @code{runhaskell Setup.hs haddock}, unless @code{#:haddock? #f} | |
3334 | is passed. Optional Haddock parameters can be passed with the help of | |
3335 | the @code{#:haddock-flags} parameter. If the file @code{Setup.hs} is | |
3336 | not found, the build system looks for @code{Setup.lhs} instead. | |
3337 | ||
3338 | Which Haskell compiler is used can be specified with the @code{#:haskell} | |
a54bd6d7 | 3339 | parameter which defaults to @code{ghc}. |
14dfdf2e FB |
3340 | @end defvr |
3341 | ||
e9137a53 FB |
3342 | @defvr {Scheme Variable} emacs-build-system |
3343 | This variable is exported by @code{(guix build-system emacs)}. It | |
f97c9175 AE |
3344 | implements an installation procedure similar to the packaging system |
3345 | of Emacs itself (@pxref{Packages,,, emacs, The GNU Emacs Manual}). | |
e9137a53 FB |
3346 | |
3347 | It first creates the @code{@var{package}-autoloads.el} file, then it | |
3348 | byte compiles all Emacs Lisp files. Differently from the Emacs | |
3349 | packaging system, the Info documentation files are moved to the standard | |
3350 | documentation directory and the @file{dir} file is deleted. Each | |
3351 | package is installed in its own directory under | |
3352 | @file{share/emacs/site-lisp/guix.d}. | |
3353 | @end defvr | |
3354 | ||
7458bd0a LC |
3355 | Lastly, for packages that do not need anything as sophisticated, a |
3356 | ``trivial'' build system is provided. It is trivial in the sense that | |
3357 | it provides basically no support: it does not pull any implicit inputs, | |
3358 | and does not have a notion of build phases. | |
3359 | ||
3360 | @defvr {Scheme Variable} trivial-build-system | |
3361 | This variable is exported by @code{(guix build-system trivial)}. | |
3362 | ||
3363 | This build system requires a @code{#:builder} argument. This argument | |
f97c9175 | 3364 | must be a Scheme expression that builds the package output(s)---as |
7458bd0a LC |
3365 | with @code{build-expression->derivation} (@pxref{Derivations, |
3366 | @code{build-expression->derivation}}). | |
3367 | @end defvr | |
3368 | ||
568717fd LC |
3369 | @node The Store |
3370 | @section The Store | |
3371 | ||
e531ac2a | 3372 | @cindex store |
1ddee424 | 3373 | @cindex store items |
e531ac2a LC |
3374 | @cindex store paths |
3375 | ||
f97c9175 AE |
3376 | Conceptually, the @dfn{store} is the place where derivations that have |
3377 | been built successfully are stored---by default, @file{/gnu/store}. | |
1ddee424 LC |
3378 | Sub-directories in the store are referred to as @dfn{store items} or |
3379 | sometimes @dfn{store paths}. The store has an associated database that | |
3380 | contains information such as the store paths referred to by each store | |
3381 | path, and the list of @emph{valid} store items---results of successful | |
ef5f5c86 LC |
3382 | builds. This database resides in @file{@var{localstatedir}/guix/db}, |
3383 | where @var{localstatedir} is the state directory specified @i{via} | |
3384 | @option{--localstatedir} at configure time, usually @file{/var}. | |
1ddee424 LC |
3385 | |
3386 | The store is @emph{always} accessed by the daemon on behalf of its clients | |
e531ac2a | 3387 | (@pxref{Invoking guix-daemon}). To manipulate the store, clients |
f97c9175 AE |
3388 | connect to the daemon over a Unix-domain socket, send requests to it, |
3389 | and read the result---these are remote procedure calls, or RPCs. | |
e531ac2a | 3390 | |
1ddee424 LC |
3391 | @quotation Note |
3392 | Users must @emph{never} modify files under @file{/gnu/store} directly. | |
3393 | This would lead to inconsistencies and break the immutability | |
3394 | assumptions of Guix's functional model (@pxref{Introduction}). | |
3395 | ||
3396 | @xref{Invoking guix gc, @command{guix gc --verify}}, for information on | |
3397 | how to check the integrity of the store and attempt recovery from | |
3398 | accidental modifications. | |
3399 | @end quotation | |
3400 | ||
e531ac2a LC |
3401 | The @code{(guix store)} module provides procedures to connect to the |
3402 | daemon, and to perform RPCs. These are described below. | |
3403 | ||
3404 | @deffn {Scheme Procedure} open-connection [@var{file}] [#:reserve-space? #t] | |
3405 | Connect to the daemon over the Unix-domain socket at @var{file}. When | |
3406 | @var{reserve-space?} is true, instruct it to reserve a little bit of | |
3407 | extra space on the file system so that the garbage collector can still | |
f97c9175 | 3408 | operate should the disk become full. Return a server object. |
e531ac2a LC |
3409 | |
3410 | @var{file} defaults to @var{%default-socket-path}, which is the normal | |
3411 | location given the options that were passed to @command{configure}. | |
3412 | @end deffn | |
3413 | ||
3414 | @deffn {Scheme Procedure} close-connection @var{server} | |
3415 | Close the connection to @var{server}. | |
3416 | @end deffn | |
3417 | ||
3418 | @defvr {Scheme Variable} current-build-output-port | |
3419 | This variable is bound to a SRFI-39 parameter, which refers to the port | |
3420 | where build and error logs sent by the daemon should be written. | |
3421 | @end defvr | |
3422 | ||
3423 | Procedures that make RPCs all take a server object as their first | |
3424 | argument. | |
3425 | ||
3426 | @deffn {Scheme Procedure} valid-path? @var{server} @var{path} | |
06b76acc LC |
3427 | @cindex invalid store items |
3428 | Return @code{#t} when @var{path} designates a valid store item and | |
3429 | @code{#f} otherwise (an invalid item may exist on disk but still be | |
3430 | invalid, for instance because it is the result of an aborted or failed | |
3431 | build.) | |
3432 | ||
3433 | A @code{&nix-protocol-error} condition is raised if @var{path} is not | |
3434 | prefixed by the store directory (@file{/gnu/store}). | |
e531ac2a LC |
3435 | @end deffn |
3436 | ||
cfbf9160 | 3437 | @deffn {Scheme Procedure} add-text-to-store @var{server} @var{name} @var{text} [@var{references}] |
e531ac2a LC |
3438 | Add @var{text} under file @var{name} in the store, and return its store |
3439 | path. @var{references} is the list of store paths referred to by the | |
3440 | resulting store path. | |
3441 | @end deffn | |
3442 | ||
874e6874 | 3443 | @deffn {Scheme Procedure} build-derivations @var{server} @var{derivations} |
59688fc4 LC |
3444 | Build @var{derivations} (a list of @code{<derivation>} objects or |
3445 | derivation paths), and return when the worker is done building them. | |
3446 | Return @code{#t} on success. | |
874e6874 LC |
3447 | @end deffn |
3448 | ||
b860f382 LC |
3449 | Note that the @code{(guix monads)} module provides a monad as well as |
3450 | monadic versions of the above procedures, with the goal of making it | |
3451 | more convenient to work with code that accesses the store (@pxref{The | |
3452 | Store Monad}). | |
3453 | ||
e531ac2a LC |
3454 | @c FIXME |
3455 | @i{This section is currently incomplete.} | |
568717fd LC |
3456 | |
3457 | @node Derivations | |
3458 | @section Derivations | |
3459 | ||
874e6874 LC |
3460 | @cindex derivations |
3461 | Low-level build actions and the environment in which they are performed | |
70458ed5 | 3462 | are represented by @dfn{derivations}. A derivation contains the |
874e6874 LC |
3463 | following pieces of information: |
3464 | ||
3465 | @itemize | |
3466 | @item | |
3467 | The outputs of the derivation---derivations produce at least one file or | |
3468 | directory in the store, but may produce more. | |
3469 | ||
3470 | @item | |
3471 | The inputs of the derivations, which may be other derivations or plain | |
3472 | files in the store (patches, build scripts, etc.) | |
3473 | ||
3474 | @item | |
3475 | The system type targeted by the derivation---e.g., @code{x86_64-linux}. | |
3476 | ||
3477 | @item | |
3478 | The file name of a build script in the store, along with the arguments | |
3479 | to be passed. | |
3480 | ||
3481 | @item | |
3482 | A list of environment variables to be defined. | |
3483 | ||
3484 | @end itemize | |
3485 | ||
3486 | @cindex derivation path | |
3487 | Derivations allow clients of the daemon to communicate build actions to | |
3488 | the store. They exist in two forms: as an in-memory representation, | |
3489 | both on the client- and daemon-side, and as files in the store whose | |
3490 | name end in @code{.drv}---these files are referred to as @dfn{derivation | |
3491 | paths}. Derivations paths can be passed to the @code{build-derivations} | |
3492 | procedure to perform the build actions they prescribe (@pxref{The | |
3493 | Store}). | |
3494 | ||
3495 | The @code{(guix derivations)} module provides a representation of | |
3496 | derivations as Scheme objects, along with procedures to create and | |
3497 | otherwise manipulate derivations. The lowest-level primitive to create | |
3498 | a derivation is the @code{derivation} procedure: | |
3499 | ||
1909431c LC |
3500 | @deffn {Scheme Procedure} derivation @var{store} @var{name} @var{builder} @ |
3501 | @var{args} [#:outputs '("out")] [#:hash #f] [#:hash-algo #f] @ | |
2096ef47 | 3502 | [#:recursive? #f] [#:inputs '()] [#:env-vars '()] @ |
1909431c | 3503 | [#:system (%current-system)] [#:references-graphs #f] @ |
35b5ca78 LC |
3504 | [#:allowed-references #f] [#:disallowed-references #f] @ |
3505 | [#:leaked-env-vars #f] [#:local-build? #f] @ | |
4a6aeb67 | 3506 | [#:substitutable? #t] |
59688fc4 LC |
3507 | Build a derivation with the given arguments, and return the resulting |
3508 | @code{<derivation>} object. | |
874e6874 | 3509 | |
2096ef47 | 3510 | When @var{hash} and @var{hash-algo} are given, a |
874e6874 | 3511 | @dfn{fixed-output derivation} is created---i.e., one whose result is |
36bbbbd1 LC |
3512 | known in advance, such as a file download. If, in addition, |
3513 | @var{recursive?} is true, then that fixed output may be an executable | |
3514 | file or a directory and @var{hash} must be the hash of an archive | |
3515 | containing this output. | |
5b0c9d16 | 3516 | |
858e9282 | 3517 | When @var{references-graphs} is true, it must be a list of file |
5b0c9d16 LC |
3518 | name/store path pairs. In that case, the reference graph of each store |
3519 | path is exported in the build environment in the corresponding file, in | |
3520 | a simple text format. | |
1909431c | 3521 | |
b53be755 | 3522 | When @var{allowed-references} is true, it must be a list of store items |
35b5ca78 LC |
3523 | or outputs that the derivation's output may refer to. Likewise, |
3524 | @var{disallowed-references}, if true, must be a list of things the | |
3525 | outputs may @emph{not} refer to. | |
b53be755 | 3526 | |
c0468155 LC |
3527 | When @var{leaked-env-vars} is true, it must be a list of strings |
3528 | denoting environment variables that are allowed to ``leak'' from the | |
3529 | daemon's environment to the build environment. This is only applicable | |
3530 | to fixed-output derivations---i.e., when @var{hash} is true. The main | |
3531 | use is to allow variables such as @code{http_proxy} to be passed to | |
3532 | derivations that download files. | |
3533 | ||
1909431c LC |
3534 | When @var{local-build?} is true, declare that the derivation is not a |
3535 | good candidate for offloading and should rather be built locally | |
3536 | (@pxref{Daemon Offload Setup}). This is the case for small derivations | |
3537 | where the costs of data transfers would outweigh the benefits. | |
4a6aeb67 LC |
3538 | |
3539 | When @var{substitutable?} is false, declare that substitutes of the | |
3540 | derivation's output should not be used (@pxref{Substitutes}). This is | |
3541 | useful, for instance, when building packages that capture details of the | |
3542 | host CPU instruction set. | |
874e6874 LC |
3543 | @end deffn |
3544 | ||
3545 | @noindent | |
3546 | Here's an example with a shell script as its builder, assuming | |
3547 | @var{store} is an open connection to the daemon, and @var{bash} points | |
3548 | to a Bash executable in the store: | |
3549 | ||
3550 | @lisp | |
3551 | (use-modules (guix utils) | |
3552 | (guix store) | |
3553 | (guix derivations)) | |
3554 | ||
59688fc4 LC |
3555 | (let ((builder ; add the Bash script to the store |
3556 | (add-text-to-store store "my-builder.sh" | |
3557 | "echo hello world > $out\n" '()))) | |
3558 | (derivation store "foo" | |
3559 | bash `("-e" ,builder) | |
21b679f6 | 3560 | #:inputs `((,bash) (,builder)) |
59688fc4 | 3561 | #:env-vars '(("HOME" . "/homeless")))) |
834129e0 | 3562 | @result{} #<derivation /gnu/store/@dots{}-foo.drv => /gnu/store/@dots{}-foo> |
874e6874 LC |
3563 | @end lisp |
3564 | ||
21b679f6 LC |
3565 | As can be guessed, this primitive is cumbersome to use directly. A |
3566 | better approach is to write build scripts in Scheme, of course! The | |
3567 | best course of action for that is to write the build code as a | |
3568 | ``G-expression'', and to pass it to @code{gexp->derivation}. For more | |
6621cdb6 | 3569 | information, @pxref{G-Expressions}. |
21b679f6 | 3570 | |
f2fadbc1 AE |
3571 | Once upon a time, @code{gexp->derivation} did not exist and constructing |
3572 | derivations with build code written in Scheme was achieved with | |
3573 | @code{build-expression->derivation}, documented below. This procedure | |
3574 | is now deprecated in favor of the much nicer @code{gexp->derivation}. | |
3575 | ||
3576 | @deffn {Scheme Procedure} build-expression->derivation @var{store} @ | |
3577 | @var{name} @var{exp} @ | |
3578 | [#:system (%current-system)] [#:inputs '()] @ | |
3579 | [#:outputs '("out")] [#:hash #f] [#:hash-algo #f] @ | |
3580 | [#:recursive? #f] [#:env-vars '()] [#:modules '()] @ | |
3581 | [#:references-graphs #f] [#:allowed-references #f] @ | |
35b5ca78 | 3582 | [#:disallowed-references #f] @ |
f2fadbc1 AE |
3583 | [#:local-build? #f] [#:substitutable? #t] [#:guile-for-build #f] |
3584 | Return a derivation that executes Scheme expression @var{exp} as a | |
3585 | builder for derivation @var{name}. @var{inputs} must be a list of | |
3586 | @code{(name drv-path sub-drv)} tuples; when @var{sub-drv} is omitted, | |
3587 | @code{"out"} is assumed. @var{modules} is a list of names of Guile | |
3588 | modules from the current search path to be copied in the store, | |
3589 | compiled, and made available in the load path during the execution of | |
3590 | @var{exp}---e.g., @code{((guix build utils) (guix build | |
3591 | gnu-build-system))}. | |
3592 | ||
3593 | @var{exp} is evaluated in an environment where @code{%outputs} is bound | |
3594 | to a list of output/path pairs, and where @code{%build-inputs} is bound | |
3595 | to a list of string/output-path pairs made from @var{inputs}. | |
3596 | Optionally, @var{env-vars} is a list of string pairs specifying the name | |
3597 | and value of environment variables visible to the builder. The builder | |
3598 | terminates by passing the result of @var{exp} to @code{exit}; thus, when | |
3599 | @var{exp} returns @code{#f}, the build is considered to have failed. | |
3600 | ||
3601 | @var{exp} is built using @var{guile-for-build} (a derivation). When | |
3602 | @var{guile-for-build} is omitted or is @code{#f}, the value of the | |
3603 | @code{%guile-for-build} fluid is used instead. | |
3604 | ||
3605 | See the @code{derivation} procedure for the meaning of | |
35b5ca78 LC |
3606 | @var{references-graphs}, @var{allowed-references}, |
3607 | @var{disallowed-references}, @var{local-build?}, and | |
3608 | @var{substitutable?}. | |
f2fadbc1 AE |
3609 | @end deffn |
3610 | ||
3611 | @noindent | |
3612 | Here's an example of a single-output derivation that creates a directory | |
3613 | containing one file: | |
3614 | ||
3615 | @lisp | |
3616 | (let ((builder '(let ((out (assoc-ref %outputs "out"))) | |
3617 | (mkdir out) ; create /gnu/store/@dots{}-goo | |
3618 | (call-with-output-file (string-append out "/test") | |
3619 | (lambda (p) | |
3620 | (display '(hello guix) p)))))) | |
3621 | (build-expression->derivation store "goo" builder)) | |
3622 | ||
3623 | @result{} #<derivation /gnu/store/@dots{}-goo.drv => @dots{}> | |
3624 | @end lisp | |
3625 | ||
568717fd | 3626 | |
b860f382 LC |
3627 | @node The Store Monad |
3628 | @section The Store Monad | |
3629 | ||
3630 | @cindex monad | |
3631 | ||
3632 | The procedures that operate on the store described in the previous | |
3633 | sections all take an open connection to the build daemon as their first | |
3634 | argument. Although the underlying model is functional, they either have | |
3635 | side effects or depend on the current state of the store. | |
3636 | ||
3637 | The former is inconvenient: the connection to the build daemon has to be | |
3638 | carried around in all those functions, making it impossible to compose | |
3639 | functions that do not take that parameter with functions that do. The | |
3640 | latter can be problematic: since store operations have side effects | |
3641 | and/or depend on external state, they have to be properly sequenced. | |
3642 | ||
3643 | @cindex monadic values | |
3644 | @cindex monadic functions | |
3645 | This is where the @code{(guix monads)} module comes in. This module | |
3646 | provides a framework for working with @dfn{monads}, and a particularly | |
3647 | useful monad for our uses, the @dfn{store monad}. Monads are a | |
3648 | construct that allows two things: associating ``context'' with values | |
3649 | (in our case, the context is the store), and building sequences of | |
4827b36d | 3650 | computations (here computations include accesses to the store). Values |
b860f382 LC |
3651 | in a monad---values that carry this additional context---are called |
3652 | @dfn{monadic values}; procedures that return such values are called | |
3653 | @dfn{monadic procedures}. | |
3654 | ||
3655 | Consider this ``normal'' procedure: | |
3656 | ||
3657 | @example | |
45adbd62 LC |
3658 | (define (sh-symlink store) |
3659 | ;; Return a derivation that symlinks the 'bash' executable. | |
3660 | (let* ((drv (package-derivation store bash)) | |
3661 | (out (derivation->output-path drv)) | |
3662 | (sh (string-append out "/bin/bash"))) | |
3663 | (build-expression->derivation store "sh" | |
3664 | `(symlink ,sh %output)))) | |
b860f382 LC |
3665 | @end example |
3666 | ||
c6f30b81 LC |
3667 | Using @code{(guix monads)} and @code{(guix gexp)}, it may be rewritten |
3668 | as a monadic function: | |
b860f382 LC |
3669 | |
3670 | @example | |
45adbd62 | 3671 | (define (sh-symlink) |
b860f382 | 3672 | ;; Same, but return a monadic value. |
c6f30b81 LC |
3673 | (mlet %store-monad ((drv (package->derivation bash))) |
3674 | (gexp->derivation "sh" | |
3675 | #~(symlink (string-append #$drv "/bin/bash") | |
3676 | #$output)))) | |
b860f382 LC |
3677 | @end example |
3678 | ||
4827b36d | 3679 | There are several things to note in the second version: the @code{store} |
c6f30b81 LC |
3680 | parameter is now implicit and is ``threaded'' in the calls to the |
3681 | @code{package->derivation} and @code{gexp->derivation} monadic | |
3682 | procedures, and the monadic value returned by @code{package->derivation} | |
3683 | is @dfn{bound} using @code{mlet} instead of plain @code{let}. | |
3684 | ||
3685 | As it turns out, the call to @code{package->derivation} can even be | |
3686 | omitted since it will take place implicitly, as we will see later | |
3687 | (@pxref{G-Expressions}): | |
3688 | ||
3689 | @example | |
3690 | (define (sh-symlink) | |
3691 | (gexp->derivation "sh" | |
3692 | #~(symlink (string-append #$bash "/bin/bash") | |
3693 | #$output))) | |
3694 | @end example | |
b860f382 | 3695 | |
7ce21611 | 3696 | @c See |
a01ad638 | 3697 | @c <https://syntaxexclamation.wordpress.com/2014/06/26/escaping-continuations/> |
7ce21611 LC |
3698 | @c for the funny quote. |
3699 | Calling the monadic @code{sh-symlink} has no effect. As someone once | |
3700 | said, ``you exit a monad like you exit a building on fire: by running''. | |
3701 | So, to exit the monad and get the desired effect, one must use | |
3702 | @code{run-with-store}: | |
b860f382 LC |
3703 | |
3704 | @example | |
8e9aa37f CAW |
3705 | (run-with-store (open-connection) (sh-symlink)) |
3706 | @result{} /gnu/store/...-sh-symlink | |
b860f382 LC |
3707 | @end example |
3708 | ||
f97c9175 | 3709 | Note that the @code{(guix monad-repl)} module extends the Guile REPL with |
b9b86078 | 3710 | new ``meta-commands'' to make it easier to deal with monadic procedures: |
f97c9175 | 3711 | @code{run-in-store}, and @code{enter-store-monad}. The former is used |
b9b86078 LC |
3712 | to ``run'' a single monadic value through the store: |
3713 | ||
3714 | @example | |
3715 | scheme@@(guile-user)> ,run-in-store (package->derivation hello) | |
3716 | $1 = #<derivation /gnu/store/@dots{}-hello-2.9.drv => @dots{}> | |
3717 | @end example | |
3718 | ||
3719 | The latter enters a recursive REPL, where all the return values are | |
3720 | automatically run through the store: | |
3721 | ||
3722 | @example | |
3723 | scheme@@(guile-user)> ,enter-store-monad | |
3724 | store-monad@@(guile-user) [1]> (package->derivation hello) | |
3725 | $2 = #<derivation /gnu/store/@dots{}-hello-2.9.drv => @dots{}> | |
3726 | store-monad@@(guile-user) [1]> (text-file "foo" "Hello!") | |
3727 | $3 = "/gnu/store/@dots{}-foo" | |
3728 | store-monad@@(guile-user) [1]> ,q | |
3729 | scheme@@(guile-user)> | |
3730 | @end example | |
3731 | ||
3732 | @noindent | |
3733 | Note that non-monadic values cannot be returned in the | |
3734 | @code{store-monad} REPL. | |
3735 | ||
e87f0591 LC |
3736 | The main syntactic forms to deal with monads in general are provided by |
3737 | the @code{(guix monads)} module and are described below. | |
b860f382 LC |
3738 | |
3739 | @deffn {Scheme Syntax} with-monad @var{monad} @var{body} ... | |
3740 | Evaluate any @code{>>=} or @code{return} forms in @var{body} as being | |
3741 | in @var{monad}. | |
3742 | @end deffn | |
3743 | ||
3744 | @deffn {Scheme Syntax} return @var{val} | |
3745 | Return a monadic value that encapsulates @var{val}. | |
3746 | @end deffn | |
3747 | ||
751630c9 | 3748 | @deffn {Scheme Syntax} >>= @var{mval} @var{mproc} ... |
b860f382 | 3749 | @dfn{Bind} monadic value @var{mval}, passing its ``contents'' to monadic |
751630c9 LC |
3750 | procedures @var{mproc}@dots{}@footnote{This operation is commonly |
3751 | referred to as ``bind'', but that name denotes an unrelated procedure in | |
3752 | Guile. Thus we use this somewhat cryptic symbol inherited from the | |
3753 | Haskell language.}. There can be one @var{mproc} or several of them, as | |
3754 | in this example: | |
3755 | ||
3756 | @example | |
3757 | (run-with-state | |
3758 | (with-monad %state-monad | |
3759 | (>>= (return 1) | |
3760 | (lambda (x) (return (+ 1 x))) | |
3761 | (lambda (x) (return (* 2 x))))) | |
3762 | 'some-state) | |
3763 | ||
3764 | @result{} 4 | |
3765 | @result{} some-state | |
3766 | @end example | |
b860f382 LC |
3767 | @end deffn |
3768 | ||
3769 | @deffn {Scheme Syntax} mlet @var{monad} ((@var{var} @var{mval}) ...) @ | |
3770 | @var{body} ... | |
3771 | @deffnx {Scheme Syntax} mlet* @var{monad} ((@var{var} @var{mval}) ...) @ | |
3772 | @var{body} ... | |
3773 | Bind the variables @var{var} to the monadic values @var{mval} in | |
3774 | @var{body}. The form (@var{var} -> @var{val}) binds @var{var} to the | |
3775 | ``normal'' value @var{val}, as per @code{let}. | |
3776 | ||
3777 | @code{mlet*} is to @code{mlet} what @code{let*} is to @code{let} | |
3778 | (@pxref{Local Bindings,,, guile, GNU Guile Reference Manual}). | |
3779 | @end deffn | |
3780 | ||
405a9d4e LC |
3781 | @deffn {Scheme System} mbegin @var{monad} @var{mexp} ... |
3782 | Bind @var{mexp} and the following monadic expressions in sequence, | |
3783 | returning the result of the last expression. | |
3784 | ||
3785 | This is akin to @code{mlet}, except that the return values of the | |
3786 | monadic expressions are ignored. In that sense, it is analogous to | |
3787 | @code{begin}, but applied to monadic expressions. | |
3788 | @end deffn | |
3789 | ||
561fb6c3 LC |
3790 | @cindex state monad |
3791 | The @code{(guix monads)} module provides the @dfn{state monad}, which | |
3792 | allows an additional value---the state---to be @emph{threaded} through | |
3793 | monadic procedure calls. | |
3794 | ||
3795 | @defvr {Scheme Variable} %state-monad | |
3796 | The state monad. Procedures in the state monad can access and change | |
3797 | the state that is threaded. | |
3798 | ||
3799 | Consider the example below. The @code{square} procedure returns a value | |
3800 | in the state monad. It returns the square of its argument, but also | |
3801 | increments the current state value: | |
3802 | ||
3803 | @example | |
3804 | (define (square x) | |
3805 | (mlet %state-monad ((count (current-state))) | |
3806 | (mbegin %state-monad | |
3807 | (set-current-state (+ 1 count)) | |
3808 | (return (* x x))))) | |
3809 | ||
3810 | (run-with-state (sequence %state-monad (map square (iota 3))) 0) | |
3811 | @result{} (0 1 4) | |
3812 | @result{} 3 | |
3813 | @end example | |
3814 | ||
3815 | When ``run'' through @var{%state-monad}, we obtain that additional state | |
3816 | value, which is the number of @code{square} calls. | |
3817 | @end defvr | |
3818 | ||
3819 | @deffn {Monadic Procedure} current-state | |
3820 | Return the current state as a monadic value. | |
3821 | @end deffn | |
3822 | ||
3823 | @deffn {Monadic Procedure} set-current-state @var{value} | |
3824 | Set the current state to @var{value} and return the previous state as a | |
3825 | monadic value. | |
3826 | @end deffn | |
3827 | ||
3828 | @deffn {Monadic Procedure} state-push @var{value} | |
3829 | Push @var{value} to the current state, which is assumed to be a list, | |
3830 | and return the previous state as a monadic value. | |
3831 | @end deffn | |
3832 | ||
3833 | @deffn {Monadic Procedure} state-pop | |
3834 | Pop a value from the current state and return it as a monadic value. | |
3835 | The state is assumed to be a list. | |
3836 | @end deffn | |
3837 | ||
3838 | @deffn {Scheme Procedure} run-with-state @var{mval} [@var{state}] | |
3839 | Run monadic value @var{mval} starting with @var{state} as the initial | |
3840 | state. Return two values: the resulting value, and the resulting state. | |
3841 | @end deffn | |
3842 | ||
e87f0591 LC |
3843 | The main interface to the store monad, provided by the @code{(guix |
3844 | store)} module, is as follows. | |
b860f382 LC |
3845 | |
3846 | @defvr {Scheme Variable} %store-monad | |
561fb6c3 LC |
3847 | The store monad---an alias for @var{%state-monad}. |
3848 | ||
3849 | Values in the store monad encapsulate accesses to the store. When its | |
3850 | effect is needed, a value of the store monad must be ``evaluated'' by | |
3851 | passing it to the @code{run-with-store} procedure (see below.) | |
b860f382 LC |
3852 | @end defvr |
3853 | ||
3854 | @deffn {Scheme Procedure} run-with-store @var{store} @var{mval} [#:guile-for-build] [#:system (%current-system)] | |
3855 | Run @var{mval}, a monadic value in the store monad, in @var{store}, an | |
3856 | open store connection. | |
3857 | @end deffn | |
3858 | ||
ad372953 | 3859 | @deffn {Monadic Procedure} text-file @var{name} @var{text} [@var{references}] |
b860f382 | 3860 | Return as a monadic value the absolute file name in the store of the file |
ad372953 LC |
3861 | containing @var{text}, a string. @var{references} is a list of store items that the |
3862 | resulting text file refers to; it defaults to the empty list. | |
45adbd62 LC |
3863 | @end deffn |
3864 | ||
0a90af15 | 3865 | @deffn {Monadic Procedure} interned-file @var{file} [@var{name}] @ |
1ec32f4a | 3866 | [#:recursive? #t] [#:select? (const #t)] |
0a90af15 LC |
3867 | Return the name of @var{file} once interned in the store. Use |
3868 | @var{name} as its store name, or the basename of @var{file} if | |
3869 | @var{name} is omitted. | |
3870 | ||
3871 | When @var{recursive?} is true, the contents of @var{file} are added | |
3872 | recursively; if @var{file} designates a flat file and @var{recursive?} | |
3873 | is true, its contents are added, and its permission bits are kept. | |
3874 | ||
1ec32f4a LC |
3875 | When @var{recursive?} is true, call @code{(@var{select?} @var{file} |
3876 | @var{stat})} for each directory entry, where @var{file} is the entry's | |
3877 | absolute file name and @var{stat} is the result of @code{lstat}; exclude | |
3878 | entries for which @var{select?} does not return true. | |
3879 | ||
0a90af15 LC |
3880 | The example below adds a file to the store, under two different names: |
3881 | ||
3882 | @example | |
3883 | (run-with-store (open-connection) | |
3884 | (mlet %store-monad ((a (interned-file "README")) | |
3885 | (b (interned-file "README" "LEGU-MIN"))) | |
3886 | (return (list a b)))) | |
3887 | ||
3888 | @result{} ("/gnu/store/rwm@dots{}-README" "/gnu/store/44i@dots{}-LEGU-MIN") | |
3889 | @end example | |
3890 | ||
3891 | @end deffn | |
3892 | ||
e87f0591 LC |
3893 | The @code{(guix packages)} module exports the following package-related |
3894 | monadic procedures: | |
3895 | ||
b860f382 | 3896 | @deffn {Monadic Procedure} package-file @var{package} [@var{file}] @ |
4231f05b | 3897 | [#:system (%current-system)] [#:target #f] @ |
f97c9175 AE |
3898 | [#:output "out"] |
3899 | Return as a monadic | |
b860f382 LC |
3900 | value in the absolute file name of @var{file} within the @var{output} |
3901 | directory of @var{package}. When @var{file} is omitted, return the name | |
4231f05b LC |
3902 | of the @var{output} directory of @var{package}. When @var{target} is |
3903 | true, use it as a cross-compilation target triplet. | |
b860f382 LC |
3904 | @end deffn |
3905 | ||
b860f382 | 3906 | @deffn {Monadic Procedure} package->derivation @var{package} [@var{system}] |
4231f05b LC |
3907 | @deffnx {Monadic Procedure} package->cross-derivation @var{package} @ |
3908 | @var{target} [@var{system}] | |
3909 | Monadic version of @code{package-derivation} and | |
3910 | @code{package-cross-derivation} (@pxref{Defining Packages}). | |
b860f382 LC |
3911 | @end deffn |
3912 | ||
3913 | ||
21b679f6 LC |
3914 | @node G-Expressions |
3915 | @section G-Expressions | |
3916 | ||
3917 | @cindex G-expression | |
3918 | @cindex build code quoting | |
3919 | So we have ``derivations'', which represent a sequence of build actions | |
3920 | to be performed to produce an item in the store (@pxref{Derivations}). | |
f97c9175 | 3921 | These build actions are performed when asking the daemon to actually |
21b679f6 LC |
3922 | build the derivations; they are run by the daemon in a container |
3923 | (@pxref{Invoking guix-daemon}). | |
3924 | ||
3925 | @cindex strata of code | |
f97c9175 | 3926 | It should come as no surprise that we like to write these build actions |
21b679f6 LC |
3927 | in Scheme. When we do that, we end up with two @dfn{strata} of Scheme |
3928 | code@footnote{The term @dfn{stratum} in this context was coined by | |
ef4ab0a4 LC |
3929 | Manuel Serrano et al.@: in the context of their work on Hop. Oleg |
3930 | Kiselyov, who has written insightful | |
3931 | @url{http://okmij.org/ftp/meta-programming/#meta-scheme, essays and code | |
3932 | on this topic}, refers to this kind of code generation as | |
3933 | @dfn{staging}.}: the ``host code''---code that defines packages, talks | |
3934 | to the daemon, etc.---and the ``build code''---code that actually | |
3935 | performs build actions, such as making directories, invoking | |
3936 | @command{make}, etc. | |
21b679f6 LC |
3937 | |
3938 | To describe a derivation and its build actions, one typically needs to | |
3939 | embed build code inside host code. It boils down to manipulating build | |
f97c9175 | 3940 | code as data, and the homoiconicity of Scheme---code has a direct |
21b679f6 | 3941 | representation as data---comes in handy for that. But we need more than |
f97c9175 | 3942 | the normal @code{quasiquote} mechanism in Scheme to construct build |
21b679f6 LC |
3943 | expressions. |
3944 | ||
3945 | The @code{(guix gexp)} module implements @dfn{G-expressions}, a form of | |
3946 | S-expressions adapted to build expressions. G-expressions, or | |
f97c9175 | 3947 | @dfn{gexps}, consist essentially of three syntactic forms: @code{gexp}, |
21b679f6 | 3948 | @code{ungexp}, and @code{ungexp-splicing} (or simply: @code{#~}, |
f97c9175 AE |
3949 | @code{#$}, and @code{#$@@}), which are comparable to |
3950 | @code{quasiquote}, @code{unquote}, and @code{unquote-splicing}, | |
4827b36d | 3951 | respectively (@pxref{Expression Syntax, @code{quasiquote},, guile, |
f97c9175 | 3952 | GNU Guile Reference Manual}). However, there are major differences: |
21b679f6 LC |
3953 | |
3954 | @itemize | |
3955 | @item | |
3956 | Gexps are meant to be written to a file and run or manipulated by other | |
3957 | processes. | |
3958 | ||
3959 | @item | |
b39fc6f7 LC |
3960 | When a high-level object such as a package or derivation is unquoted |
3961 | inside a gexp, the result is as if its output file name had been | |
3962 | introduced. | |
ff40e9b7 | 3963 | |
21b679f6 LC |
3964 | @item |
3965 | Gexps carry information about the packages or derivations they refer to, | |
3966 | and these dependencies are automatically added as inputs to the build | |
3967 | processes that use them. | |
3968 | @end itemize | |
3969 | ||
c2b84676 | 3970 | @cindex lowering, of high-level objects in gexps |
343eacbe LC |
3971 | This mechanism is not limited to package and derivation |
3972 | objects: @dfn{compilers} able to ``lower'' other high-level objects to | |
c2b84676 LC |
3973 | derivations or files in the store can be defined, |
3974 | such that these objects can also be inserted | |
f97c9175 | 3975 | into gexps. For example, a useful type of high-level objects that can be |
343eacbe | 3976 | inserted in a gexp is ``file-like objects'', which make it easy to |
f97c9175 | 3977 | add files to the store and to refer to them in |
558e8b11 LC |
3978 | derivations and such (see @code{local-file} and @code{plain-file} |
3979 | below.) | |
b39fc6f7 | 3980 | |
21b679f6 LC |
3981 | To illustrate the idea, here is an example of a gexp: |
3982 | ||
3983 | @example | |
3984 | (define build-exp | |
3985 | #~(begin | |
3986 | (mkdir #$output) | |
3987 | (chdir #$output) | |
aff8ce7c | 3988 | (symlink (string-append #$coreutils "/bin/ls") |
21b679f6 LC |
3989 | "list-files"))) |
3990 | @end example | |
3991 | ||
3992 | This gexp can be passed to @code{gexp->derivation}; we obtain a | |
3993 | derivation that builds a directory containing exactly one symlink to | |
3994 | @file{/gnu/store/@dots{}-coreutils-8.22/bin/ls}: | |
3995 | ||
3996 | @example | |
3997 | (gexp->derivation "the-thing" build-exp) | |
3998 | @end example | |
3999 | ||
e20fd1bf | 4000 | As one would expect, the @code{"/gnu/store/@dots{}-coreutils-8.22"} string is |
21b679f6 LC |
4001 | substituted to the reference to the @var{coreutils} package in the |
4002 | actual build code, and @var{coreutils} is automatically made an input to | |
4003 | the derivation. Likewise, @code{#$output} (equivalent to @code{(ungexp | |
f97c9175 AE |
4004 | output)}) is replaced by a string containing the directory name of the |
4005 | output of the derivation. | |
667b2508 LC |
4006 | |
4007 | @cindex cross compilation | |
4008 | In a cross-compilation context, it is useful to distinguish between | |
4009 | references to the @emph{native} build of a package---that can run on the | |
4010 | host---versus references to cross builds of a package. To that end, the | |
4011 | @code{#+} plays the same role as @code{#$}, but is a reference to a | |
4012 | native package build: | |
4013 | ||
4014 | @example | |
4015 | (gexp->derivation "vi" | |
4016 | #~(begin | |
4017 | (mkdir #$output) | |
4018 | (system* (string-append #+coreutils "/bin/ln") | |
4019 | "-s" | |
4020 | (string-append #$emacs "/bin/emacs") | |
4021 | (string-append #$output "/bin/vi"))) | |
4a3b6aa5 | 4022 | #:target "mips64el-linux-gnu") |
667b2508 LC |
4023 | @end example |
4024 | ||
4025 | @noindent | |
4026 | In the example above, the native build of @var{coreutils} is used, so | |
4027 | that @command{ln} can actually run on the host; but then the | |
4028 | cross-compiled build of @var{emacs} is referenced. | |
4029 | ||
0bb9929e LC |
4030 | @cindex imported modules, for gexps |
4031 | @findex with-imported-modules | |
4032 | Another gexp feature is @dfn{imported modules}: sometimes you want to be | |
4033 | able to use certain Guile modules from the ``host environment'' in the | |
4034 | gexp, so those modules should be imported in the ``build environment''. | |
4035 | The @code{with-imported-modules} form allows you to express that: | |
4036 | ||
4037 | @example | |
4038 | (let ((build (with-imported-modules '((guix build utils)) | |
4039 | #~(begin | |
4040 | (use-modules (guix build utils)) | |
4041 | (mkdir-p (string-append #$output "/bin")))))) | |
4042 | (gexp->derivation "empty-dir" | |
4043 | #~(begin | |
4044 | #$build | |
4045 | (display "success!\n") | |
4046 | #t))) | |
4047 | @end example | |
4048 | ||
4049 | @noindent | |
4050 | In this example, the @code{(guix build utils)} module is automatically | |
4051 | pulled into the isolated build environment of our gexp, such that | |
4052 | @code{(use-modules (guix build utils))} works as expected. | |
4053 | ||
7ca87354 LC |
4054 | @cindex module closure |
4055 | @findex source-module-closure | |
4056 | Usually you want the @emph{closure} of the module to be imported---i.e., | |
4057 | the module itself and all the modules it depends on---rather than just | |
4058 | the module; failing to do that, attempts to use the module will fail | |
4059 | because of missing dependent modules. The @code{source-module-closure} | |
4060 | procedure computes the closure of a module by looking at its source file | |
4061 | headers, which comes in handy in this case: | |
4062 | ||
4063 | @example | |
4064 | (use-modules (guix modules)) ;for 'source-module-closure' | |
4065 | ||
4066 | (with-imported-modules (source-module-closure | |
4067 | '((guix build utils) | |
4068 | (gnu build vm))) | |
4069 | (gexp->derivation "something-with-vms" | |
4070 | #~(begin | |
4071 | (use-modules (guix build utils) | |
4072 | (gnu build vm)) | |
4073 | @dots{}))) | |
4074 | @end example | |
4075 | ||
667b2508 | 4076 | The syntactic form to construct gexps is summarized below. |
21b679f6 LC |
4077 | |
4078 | @deffn {Scheme Syntax} #~@var{exp} | |
4079 | @deffnx {Scheme Syntax} (gexp @var{exp}) | |
4080 | Return a G-expression containing @var{exp}. @var{exp} may contain one | |
4081 | or more of the following forms: | |
4082 | ||
4083 | @table @code | |
4084 | @item #$@var{obj} | |
4085 | @itemx (ungexp @var{obj}) | |
b39fc6f7 LC |
4086 | Introduce a reference to @var{obj}. @var{obj} may have one of the |
4087 | supported types, for example a package or a | |
21b679f6 LC |
4088 | derivation, in which case the @code{ungexp} form is replaced by its |
4089 | output file name---e.g., @code{"/gnu/store/@dots{}-coreutils-8.22}. | |
4090 | ||
b39fc6f7 LC |
4091 | If @var{obj} is a list, it is traversed and references to supported |
4092 | objects are substituted similarly. | |
21b679f6 LC |
4093 | |
4094 | If @var{obj} is another gexp, its contents are inserted and its | |
4095 | dependencies are added to those of the containing gexp. | |
4096 | ||
4097 | If @var{obj} is another kind of object, it is inserted as is. | |
4098 | ||
b39fc6f7 LC |
4099 | @item #$@var{obj}:@var{output} |
4100 | @itemx (ungexp @var{obj} @var{output}) | |
21b679f6 | 4101 | This is like the form above, but referring explicitly to the |
b39fc6f7 LC |
4102 | @var{output} of @var{obj}---this is useful when @var{obj} produces |
4103 | multiple outputs (@pxref{Packages with Multiple Outputs}). | |
21b679f6 | 4104 | |
667b2508 LC |
4105 | @item #+@var{obj} |
4106 | @itemx #+@var{obj}:output | |
4107 | @itemx (ungexp-native @var{obj}) | |
4108 | @itemx (ungexp-native @var{obj} @var{output}) | |
4109 | Same as @code{ungexp}, but produces a reference to the @emph{native} | |
4110 | build of @var{obj} when used in a cross compilation context. | |
4111 | ||
21b679f6 LC |
4112 | @item #$output[:@var{output}] |
4113 | @itemx (ungexp output [@var{output}]) | |
4114 | Insert a reference to derivation output @var{output}, or to the main | |
4115 | output when @var{output} is omitted. | |
4116 | ||
4117 | This only makes sense for gexps passed to @code{gexp->derivation}. | |
4118 | ||
4119 | @item #$@@@var{lst} | |
4120 | @itemx (ungexp-splicing @var{lst}) | |
4121 | Like the above, but splices the contents of @var{lst} inside the | |
4122 | containing list. | |
4123 | ||
667b2508 LC |
4124 | @item #+@@@var{lst} |
4125 | @itemx (ungexp-native-splicing @var{lst}) | |
4126 | Like the above, but refers to native builds of the objects listed in | |
4127 | @var{lst}. | |
4128 | ||
21b679f6 LC |
4129 | @end table |
4130 | ||
4131 | G-expressions created by @code{gexp} or @code{#~} are run-time objects | |
4132 | of the @code{gexp?} type (see below.) | |
4133 | @end deffn | |
4134 | ||
0bb9929e LC |
4135 | @deffn {Scheme Syntax} with-imported-modules @var{modules} @var{body}@dots{} |
4136 | Mark the gexps defined in @var{body}@dots{} as requiring @var{modules} | |
4137 | in their execution environment. @var{modules} must be a list of Guile | |
4138 | module names, such as @code{'((guix build utils) (guix build gremlin))}. | |
4139 | ||
4140 | This form has @emph{lexical} scope: it has an effect on the gexps | |
4141 | directly defined in @var{body}@dots{}, but not on those defined, say, in | |
4142 | procedures called from @var{body}@dots{}. | |
4143 | @end deffn | |
4144 | ||
21b679f6 LC |
4145 | @deffn {Scheme Procedure} gexp? @var{obj} |
4146 | Return @code{#t} if @var{obj} is a G-expression. | |
4147 | @end deffn | |
4148 | ||
4149 | G-expressions are meant to be written to disk, either as code building | |
4150 | some derivation, or as plain files in the store. The monadic procedures | |
4151 | below allow you to do that (@pxref{The Store Monad}, for more | |
4152 | information about monads.) | |
4153 | ||
4154 | @deffn {Monadic Procedure} gexp->derivation @var{name} @var{exp} @ | |
ce45eb4c | 4155 | [#:system (%current-system)] [#:target #f] [#:graft? #t] @ |
21b679f6 LC |
4156 | [#:hash #f] [#:hash-algo #f] @ |
4157 | [#:recursive? #f] [#:env-vars '()] [#:modules '()] @ | |
4684f301 | 4158 | [#:module-path @var{%load-path}] @ |
c8351d9a | 4159 | [#:references-graphs #f] [#:allowed-references #f] @ |
3f4ecf32 | 4160 | [#:disallowed-references #f] @ |
c0468155 | 4161 | [#:leaked-env-vars #f] @ |
0309e1b0 | 4162 | [#:script-name (string-append @var{name} "-builder")] @ |
4a6aeb67 | 4163 | [#:local-build? #f] [#:substitutable? #t] [#:guile-for-build #f] |
21b679f6 | 4164 | Return a derivation @var{name} that runs @var{exp} (a gexp) with |
0309e1b0 LC |
4165 | @var{guile-for-build} (a derivation) on @var{system}; @var{exp} is |
4166 | stored in a file called @var{script-name}. When @var{target} is true, | |
4167 | it is used as the cross-compilation target triplet for packages referred | |
4168 | to by @var{exp}. | |
21b679f6 | 4169 | |
0bb9929e LC |
4170 | @var{modules} is deprecated in favor of @code{with-imported-modules}. |
4171 | Its meaning is to | |
4172 | make @var{modules} available in the evaluation context of @var{exp}; | |
ce45eb4c LC |
4173 | @var{modules} is a list of names of Guile modules searched in |
4174 | @var{module-path} to be copied in the store, compiled, and made available in | |
21b679f6 LC |
4175 | the load path during the execution of @var{exp}---e.g., @code{((guix |
4176 | build utils) (guix build gnu-build-system))}. | |
4177 | ||
ce45eb4c LC |
4178 | @var{graft?} determines whether packages referred to by @var{exp} should be grafted when |
4179 | applicable. | |
4180 | ||
b53833b2 LC |
4181 | When @var{references-graphs} is true, it must be a list of tuples of one of the |
4182 | following forms: | |
4183 | ||
4184 | @example | |
4185 | (@var{file-name} @var{package}) | |
4186 | (@var{file-name} @var{package} @var{output}) | |
4187 | (@var{file-name} @var{derivation}) | |
4188 | (@var{file-name} @var{derivation} @var{output}) | |
4189 | (@var{file-name} @var{store-item}) | |
4190 | @end example | |
4191 | ||
4192 | The right-hand-side of each element of @var{references-graphs} is automatically made | |
4193 | an input of the build process of @var{exp}. In the build environment, each | |
4194 | @var{file-name} contains the reference graph of the corresponding item, in a simple | |
4195 | text format. | |
4196 | ||
c8351d9a LC |
4197 | @var{allowed-references} must be either @code{#f} or a list of output names and packages. |
4198 | In the latter case, the list denotes store items that the result is allowed to | |
4199 | refer to. Any reference to another store item will lead to a build error. | |
3f4ecf32 LC |
4200 | Similarly for @var{disallowed-references}, which can list items that must not be |
4201 | referenced by the outputs. | |
c8351d9a | 4202 | |
e20fd1bf | 4203 | The other arguments are as for @code{derivation} (@pxref{Derivations}). |
21b679f6 LC |
4204 | @end deffn |
4205 | ||
343eacbe | 4206 | @cindex file-like objects |
e1c153e0 LC |
4207 | The @code{local-file}, @code{plain-file}, @code{computed-file}, |
4208 | @code{program-file}, and @code{scheme-file} procedures below return | |
4209 | @dfn{file-like objects}. That is, when unquoted in a G-expression, | |
4210 | these objects lead to a file in the store. Consider this G-expression: | |
343eacbe LC |
4211 | |
4212 | @example | |
a9e5e92f | 4213 | #~(system* #$(file-append glibc "/sbin/nscd") "-f" |
343eacbe LC |
4214 | #$(local-file "/tmp/my-nscd.conf")) |
4215 | @end example | |
4216 | ||
4217 | The effect here is to ``intern'' @file{/tmp/my-nscd.conf} by copying it | |
4218 | to the store. Once expanded, for instance @i{via} | |
4219 | @code{gexp->derivation}, the G-expression refers to that copy under | |
4220 | @file{/gnu/store}; thus, modifying or removing the file in @file{/tmp} | |
4221 | does not have any effect on what the G-expression does. | |
4222 | @code{plain-file} can be used similarly; it differs in that the file | |
4223 | content is directly passed as a string. | |
4224 | ||
d9ae938f | 4225 | @deffn {Scheme Procedure} local-file @var{file} [@var{name}] @ |
0687fc9c | 4226 | [#:recursive? #f] [#:select? (const #t)] |
d9ae938f | 4227 | Return an object representing local file @var{file} to add to the store; this |
9d3994f7 LC |
4228 | object can be used in a gexp. If @var{file} is a relative file name, it is looked |
4229 | up relative to the source file where this form appears. @var{file} will be added to | |
4230 | the store under @var{name}--by default the base name of @var{file}. | |
d9ae938f LC |
4231 | |
4232 | When @var{recursive?} is true, the contents of @var{file} are added recursively; if @var{file} | |
4233 | designates a flat file and @var{recursive?} is true, its contents are added, and its | |
4234 | permission bits are kept. | |
4235 | ||
0687fc9c LC |
4236 | When @var{recursive?} is true, call @code{(@var{select?} @var{file} |
4237 | @var{stat})} for each directory entry, where @var{file} is the entry's | |
4238 | absolute file name and @var{stat} is the result of @code{lstat}; exclude | |
4239 | entries for which @var{select?} does not return true. | |
4240 | ||
d9ae938f LC |
4241 | This is the declarative counterpart of the @code{interned-file} monadic |
4242 | procedure (@pxref{The Store Monad, @code{interned-file}}). | |
4243 | @end deffn | |
4244 | ||
558e8b11 LC |
4245 | @deffn {Scheme Procedure} plain-file @var{name} @var{content} |
4246 | Return an object representing a text file called @var{name} with the given | |
4247 | @var{content} (a string) to be added to the store. | |
4248 | ||
4249 | This is the declarative counterpart of @code{text-file}. | |
4250 | @end deffn | |
4251 | ||
91937029 | 4252 | @deffn {Scheme Procedure} computed-file @var{name} @var{gexp} @ |
a769bffb | 4253 | [#:options '(#:local-build? #t)] |
91937029 | 4254 | Return an object representing the store item @var{name}, a file or |
a769bffb | 4255 | directory computed by @var{gexp}. @var{options} |
91937029 LC |
4256 | is a list of additional arguments to pass to @code{gexp->derivation}. |
4257 | ||
4258 | This is the declarative counterpart of @code{gexp->derivation}. | |
4259 | @end deffn | |
4260 | ||
21b679f6 LC |
4261 | @deffn {Monadic Procedure} gexp->script @var{name} @var{exp} |
4262 | Return an executable script @var{name} that runs @var{exp} using | |
9c14a487 | 4263 | @var{guile}, with @var{exp}'s imported modules in its search path. |
21b679f6 LC |
4264 | |
4265 | The example below builds a script that simply invokes the @command{ls} | |
4266 | command: | |
4267 | ||
4268 | @example | |
4269 | (use-modules (guix gexp) (gnu packages base)) | |
4270 | ||
4271 | (gexp->script "list-files" | |
a9e5e92f | 4272 | #~(execl #$(file-append coreutils "/bin/ls") |
21b679f6 LC |
4273 | "ls")) |
4274 | @end example | |
4275 | ||
4276 | When ``running'' it through the store (@pxref{The Store Monad, | |
e20fd1bf | 4277 | @code{run-with-store}}), we obtain a derivation that produces an |
21b679f6 LC |
4278 | executable file @file{/gnu/store/@dots{}-list-files} along these lines: |
4279 | ||
4280 | @example | |
4281 | #!/gnu/store/@dots{}-guile-2.0.11/bin/guile -ds | |
4282 | !# | |
a9e5e92f | 4283 | (execl "/gnu/store/@dots{}-coreutils-8.22"/bin/ls" "ls") |
21b679f6 LC |
4284 | @end example |
4285 | @end deffn | |
4286 | ||
15a01c72 | 4287 | @deffn {Scheme Procedure} program-file @var{name} @var{exp} @ |
9c14a487 | 4288 | [#:guile #f] |
15a01c72 LC |
4289 | Return an object representing the executable store item @var{name} that |
4290 | runs @var{gexp}. @var{guile} is the Guile package used to execute that | |
9c14a487 | 4291 | script. |
15a01c72 LC |
4292 | |
4293 | This is the declarative counterpart of @code{gexp->script}. | |
4294 | @end deffn | |
4295 | ||
2b418579 LC |
4296 | @deffn {Monadic Procedure} gexp->file @var{name} @var{exp} @ |
4297 | [#:set-load-path? #t] | |
21b679f6 | 4298 | Return a derivation that builds a file @var{name} containing @var{exp}. |
2b418579 LC |
4299 | When @var{set-load-path?} is true, emit code in the resulting file to |
4300 | set @code{%load-path} and @code{%load-compiled-path} to honor | |
4301 | @var{exp}'s imported modules. | |
21b679f6 LC |
4302 | |
4303 | The resulting file holds references to all the dependencies of @var{exp} | |
4304 | or a subset thereof. | |
4305 | @end deffn | |
1ed19464 | 4306 | |
e1c153e0 LC |
4307 | @deffn {Scheme Procedure} scheme-file @var{name} @var{exp} |
4308 | Return an object representing the Scheme file @var{name} that contains | |
4309 | @var{exp}. | |
4310 | ||
4311 | This is the declarative counterpart of @code{gexp->file}. | |
4312 | @end deffn | |
4313 | ||
1ed19464 LC |
4314 | @deffn {Monadic Procedure} text-file* @var{name} @var{text} @dots{} |
4315 | Return as a monadic value a derivation that builds a text file | |
4316 | containing all of @var{text}. @var{text} may list, in addition to | |
d9ae938f LC |
4317 | strings, objects of any type that can be used in a gexp: packages, |
4318 | derivations, local file objects, etc. The resulting store file holds | |
4319 | references to all these. | |
1ed19464 LC |
4320 | |
4321 | This variant should be preferred over @code{text-file} anytime the file | |
4322 | to create will reference items from the store. This is typically the | |
4323 | case when building a configuration file that embeds store file names, | |
4324 | like this: | |
4325 | ||
4326 | @example | |
4327 | (define (profile.sh) | |
4328 | ;; Return the name of a shell script in the store that | |
4329 | ;; initializes the 'PATH' environment variable. | |
4330 | (text-file* "profile.sh" | |
4331 | "export PATH=" coreutils "/bin:" | |
4332 | grep "/bin:" sed "/bin\n")) | |
4333 | @end example | |
4334 | ||
4335 | In this example, the resulting @file{/gnu/store/@dots{}-profile.sh} file | |
b7899749 | 4336 | will reference @var{coreutils}, @var{grep}, and @var{sed}, thereby |
1ed19464 LC |
4337 | preventing them from being garbage-collected during its lifetime. |
4338 | @end deffn | |
21b679f6 | 4339 | |
b751cde3 LC |
4340 | @deffn {Scheme Procedure} mixed-text-file @var{name} @var{text} @dots{} |
4341 | Return an object representing store file @var{name} containing | |
4342 | @var{text}. @var{text} is a sequence of strings and file-like objects, | |
4343 | as in: | |
4344 | ||
4345 | @example | |
4346 | (mixed-text-file "profile" | |
4347 | "export PATH=" coreutils "/bin:" grep "/bin") | |
4348 | @end example | |
4349 | ||
4350 | This is the declarative counterpart of @code{text-file*}. | |
4351 | @end deffn | |
4352 | ||
a9e5e92f LC |
4353 | @deffn {Scheme Procedure} file-append @var{obj} @var{suffix} @dots{} |
4354 | Return a file-like object that expands to the concatenation of @var{obj} | |
4355 | and @var{suffix}, where @var{obj} is a lowerable object and each | |
4356 | @var{suffix} is a string. | |
4357 | ||
4358 | As an example, consider this gexp: | |
4359 | ||
4360 | @example | |
4361 | (gexp->script "run-uname" | |
4362 | #~(system* #$(file-append coreutils | |
4363 | "/bin/uname"))) | |
4364 | @end example | |
4365 | ||
4366 | The same effect could be achieved with: | |
4367 | ||
4368 | @example | |
4369 | (gexp->script "run-uname" | |
4370 | #~(system* (string-append #$coreutils | |
4371 | "/bin/uname"))) | |
4372 | @end example | |
4373 | ||
4374 | There is one difference though: in the @code{file-append} case, the | |
4375 | resulting script contains the absolute file name as a string, whereas in | |
4376 | the second case, the resulting script contains a @code{(string-append | |
4377 | @dots{})} expression to construct the file name @emph{at run time}. | |
4378 | @end deffn | |
4379 | ||
4380 | ||
21b679f6 LC |
4381 | Of course, in addition to gexps embedded in ``host'' code, there are |
4382 | also modules containing build tools. To make it clear that they are | |
4383 | meant to be used in the build stratum, these modules are kept in the | |
4384 | @code{(guix build @dots{})} name space. | |
4385 | ||
c2b84676 LC |
4386 | @cindex lowering, of high-level objects in gexps |
4387 | Internally, high-level objects are @dfn{lowered}, using their compiler, | |
4388 | to either derivations or store items. For instance, lowering a package | |
4389 | yields a derivation, and lowering a @code{plain-file} yields a store | |
4390 | item. This is achieved using the @code{lower-object} monadic procedure. | |
4391 | ||
4392 | @deffn {Monadic Procedure} lower-object @var{obj} [@var{system}] @ | |
4393 | [#:target #f] | |
4394 | Return as a value in @var{%store-monad} the derivation or store item | |
4395 | corresponding to @var{obj} for @var{system}, cross-compiling for | |
4396 | @var{target} if @var{target} is true. @var{obj} must be an object that | |
4397 | has an associated gexp compiler, such as a @code{<package>}. | |
4398 | @end deffn | |
4399 | ||
21b679f6 | 4400 | |
568717fd LC |
4401 | @c ********************************************************************* |
4402 | @node Utilities | |
4403 | @chapter Utilities | |
4404 | ||
6f773606 LC |
4405 | This section describes Guix command-line utilities. Some of them are |
4406 | primarily targeted at developers and users who write new package | |
4407 | definitions, while others are more generally useful. They complement | |
4408 | the Scheme programming interface of Guix in a convenient way. | |
210cc920 | 4409 | |
568717fd | 4410 | @menu |
37166310 | 4411 | * Invoking guix build:: Building packages from the command line. |
39bee8a2 | 4412 | * Invoking guix edit:: Editing package definitions. |
210cc920 | 4413 | * Invoking guix download:: Downloading a file and printing its hash. |
37166310 | 4414 | * Invoking guix hash:: Computing the cryptographic hash of a file. |
2f7d2d91 | 4415 | * Invoking guix import:: Importing package definitions. |
37166310 | 4416 | * Invoking guix refresh:: Updating package definitions. |
b4f5e0e8 | 4417 | * Invoking guix lint:: Finding errors in package definitions. |
fcc58db6 | 4418 | * Invoking guix size:: Profiling disk usage. |
88856916 | 4419 | * Invoking guix graph:: Visualizing the graph of packages. |
372c4bbc | 4420 | * Invoking guix environment:: Setting up development environments. |
aff8ce7c | 4421 | * Invoking guix publish:: Sharing substitutes. |
d23c20f1 | 4422 | * Invoking guix challenge:: Challenging substitute servers. |
32efa254 | 4423 | * Invoking guix container:: Process isolation. |
568717fd LC |
4424 | @end menu |
4425 | ||
e49951eb MW |
4426 | @node Invoking guix build |
4427 | @section Invoking @command{guix build} | |
568717fd | 4428 | |
e32171ee JD |
4429 | @cindex package building |
4430 | @cindex @command{guix build} | |
e49951eb | 4431 | The @command{guix build} command builds packages or derivations and |
6798a8e4 LC |
4432 | their dependencies, and prints the resulting store paths. Note that it |
4433 | does not modify the user's profile---this is the job of the | |
e49951eb | 4434 | @command{guix package} command (@pxref{Invoking guix package}). Thus, |
6798a8e4 LC |
4435 | it is mainly useful for distribution developers. |
4436 | ||
4437 | The general syntax is: | |
c78bd12b LC |
4438 | |
4439 | @example | |
e49951eb | 4440 | guix build @var{options} @var{package-or-derivation}@dots{} |
c78bd12b LC |
4441 | @end example |
4442 | ||
f97c9175 | 4443 | As an example, the following command builds the latest versions of Emacs |
ccd7158d LC |
4444 | and of Guile, displays their build logs, and finally displays the |
4445 | resulting directories: | |
4446 | ||
4447 | @example | |
4448 | guix build emacs guile | |
4449 | @end example | |
4450 | ||
4451 | Similarly, the following command builds all the available packages: | |
4452 | ||
4453 | @example | |
5284339d | 4454 | guix build --quiet --keep-going \ |
ccd7158d LC |
4455 | `guix package -A | cut -f1,2 --output-delimiter=@@` |
4456 | @end example | |
4457 | ||
c78bd12b | 4458 | @var{package-or-derivation} may be either the name of a package found in |
5401dd75 LC |
4459 | the software distribution such as @code{coreutils} or |
4460 | @code{coreutils-8.20}, or a derivation such as | |
834129e0 | 4461 | @file{/gnu/store/@dots{}-coreutils-8.19.drv}. In the former case, a |
e7f34eb0 LC |
4462 | package with the corresponding name (and optionally version) is searched |
4463 | for among the GNU distribution modules (@pxref{Package Modules}). | |
4464 | ||
4465 | Alternatively, the @code{--expression} option may be used to specify a | |
4466 | Scheme expression that evaluates to a package; this is useful when | |
b7899749 | 4467 | disambiguating among several same-named packages or package variants is |
e7f34eb0 | 4468 | needed. |
c78bd12b | 4469 | |
ccd7158d LC |
4470 | There may be zero or more @var{options}. The available options are |
4471 | described in the subsections below. | |
4472 | ||
4473 | @menu | |
4474 | * Common Build Options:: Build options for most commands. | |
88ad6ded | 4475 | * Package Transformation Options:: Creating variants of packages. |
ccd7158d LC |
4476 | * Additional Build Options:: Options specific to 'guix build'. |
4477 | @end menu | |
4478 | ||
4479 | @node Common Build Options | |
4480 | @subsection Common Build Options | |
4481 | ||
4482 | A number of options that control the build process are common to | |
4483 | @command{guix build} and other commands that can spawn builds, such as | |
4484 | @command{guix package} or @command{guix archive}. These are the | |
4485 | following: | |
4486 | ||
4487 | @table @code | |
4488 | ||
4489 | @item --load-path=@var{directory} | |
4490 | @itemx -L @var{directory} | |
4491 | Add @var{directory} to the front of the package module search path | |
4492 | (@pxref{Package Modules}). | |
4493 | ||
4494 | This allows users to define their own packages and make them visible to | |
4495 | the command-line tools. | |
4496 | ||
4497 | @item --keep-failed | |
4498 | @itemx -K | |
b7899749 | 4499 | Keep the build tree of failed builds. Thus, if a build fails, its build |
ccd7158d LC |
4500 | tree is kept under @file{/tmp}, in a directory whose name is shown at |
4501 | the end of the build log. This is useful when debugging build issues. | |
4502 | ||
4503 | @item --keep-going | |
4504 | @itemx -k | |
4505 | Keep going when some of the derivations fail to build; return only once | |
4506 | all the builds have either completed or failed. | |
4507 | ||
4508 | The default behavior is to stop as soon as one of the specified | |
4509 | derivations has failed. | |
4510 | ||
4511 | @item --dry-run | |
4512 | @itemx -n | |
4513 | Do not build the derivations. | |
4514 | ||
4515 | @item --fallback | |
4516 | When substituting a pre-built binary fails, fall back to building | |
4517 | packages locally. | |
4518 | ||
4519 | @item --substitute-urls=@var{urls} | |
4520 | @anchor{client-substitute-urls} | |
4521 | Consider @var{urls} the whitespace-separated list of substitute source | |
4522 | URLs, overriding the default list of URLs of @command{guix-daemon} | |
4523 | (@pxref{daemon-substitute-urls,, @command{guix-daemon} URLs}). | |
4524 | ||
4525 | This means that substitutes may be downloaded from @var{urls}, provided | |
4526 | they are signed by a key authorized by the system administrator | |
4527 | (@pxref{Substitutes}). | |
4528 | ||
71e2065a LC |
4529 | When @var{urls} is the empty string, substitutes are effectively |
4530 | disabled. | |
4531 | ||
ccd7158d LC |
4532 | @item --no-substitutes |
4533 | Do not use substitutes for build products. That is, always build things | |
4534 | locally instead of allowing downloads of pre-built binaries | |
4535 | (@pxref{Substitutes}). | |
4536 | ||
7573d30f LC |
4537 | @item --no-grafts |
4538 | Do not ``graft'' packages. In practice, this means that package updates | |
4539 | available as grafts are not applied. @xref{Security Updates}, for more | |
4540 | information on grafts. | |
4541 | ||
ccd7158d LC |
4542 | @item --rounds=@var{n} |
4543 | Build each derivation @var{n} times in a row, and raise an error if | |
4544 | consecutive build results are not bit-for-bit identical. | |
4545 | ||
4546 | This is a useful way to detect non-deterministic builds processes. | |
4547 | Non-deterministic build processes are a problem because they make it | |
4548 | practically impossible for users to @emph{verify} whether third-party | |
4549 | binaries are genuine. @xref{Invoking guix challenge}, for more. | |
4550 | ||
4551 | Note that, currently, the differing build results are not kept around, | |
4552 | so you will have to manually investigate in case of an error---e.g., by | |
e66d1f59 ML |
4553 | stashing one of the build results with @code{guix archive --export} |
4554 | (@pxref{Invoking guix archive}), then rebuilding, and finally comparing | |
4555 | the two results. | |
ccd7158d LC |
4556 | |
4557 | @item --no-build-hook | |
f97c9175 | 4558 | Do not attempt to offload builds @i{via} the ``build hook'' of the daemon |
ccd7158d LC |
4559 | (@pxref{Daemon Offload Setup}). That is, always build things locally |
4560 | instead of offloading builds to remote machines. | |
4561 | ||
4562 | @item --max-silent-time=@var{seconds} | |
4563 | When the build or substitution process remains silent for more than | |
4564 | @var{seconds}, terminate it and report a build failure. | |
4565 | ||
4566 | @item --timeout=@var{seconds} | |
4567 | Likewise, when the build or substitution process lasts for more than | |
4568 | @var{seconds}, terminate it and report a build failure. | |
4569 | ||
4570 | By default there is no timeout. This behavior can be restored with | |
4571 | @code{--timeout=0}. | |
4572 | ||
4573 | @item --verbosity=@var{level} | |
4574 | Use the given verbosity level. @var{level} must be an integer between 0 | |
4575 | and 5; higher means more verbose output. Setting a level of 4 or more | |
4576 | may be helpful when debugging setup issues with the build daemon. | |
4577 | ||
4578 | @item --cores=@var{n} | |
4579 | @itemx -c @var{n} | |
4580 | Allow the use of up to @var{n} CPU cores for the build. The special | |
4581 | value @code{0} means to use as many CPU cores as available. | |
4582 | ||
4583 | @item --max-jobs=@var{n} | |
4584 | @itemx -M @var{n} | |
4585 | Allow at most @var{n} build jobs in parallel. @xref{Invoking | |
4586 | guix-daemon, @code{--max-jobs}}, for details about this option and the | |
4587 | equivalent @command{guix-daemon} option. | |
4588 | ||
4589 | @end table | |
4590 | ||
4591 | Behind the scenes, @command{guix build} is essentially an interface to | |
4592 | the @code{package-derivation} procedure of the @code{(guix packages)} | |
4593 | module, and to the @code{build-derivations} procedure of the @code{(guix | |
4594 | derivations)} module. | |
4595 | ||
4596 | In addition to options explicitly passed on the command line, | |
4597 | @command{guix build} and other @command{guix} commands that support | |
4598 | building honor the @code{GUIX_BUILD_OPTIONS} environment variable. | |
4599 | ||
4600 | @defvr {Environment Variable} GUIX_BUILD_OPTIONS | |
4601 | Users can define this variable to a list of command line options that | |
4602 | will automatically be used by @command{guix build} and other | |
4603 | @command{guix} commands that can perform builds, as in the example | |
4604 | below: | |
4605 | ||
4606 | @example | |
4607 | $ export GUIX_BUILD_OPTIONS="--no-substitutes -c 2 -L /foo/bar" | |
4608 | @end example | |
4609 | ||
4610 | These options are parsed independently, and the result is appended to | |
4611 | the parsed command-line options. | |
4612 | @end defvr | |
4613 | ||
88ad6ded LC |
4614 | |
4615 | @node Package Transformation Options | |
4616 | @subsection Package Transformation Options | |
4617 | ||
4618 | @cindex package variants | |
4619 | Another set of command-line options supported by @command{guix build} | |
b8638f03 | 4620 | and also @command{guix package} are @dfn{package transformation |
f97c9175 | 4621 | options}. These are options that make it possible to define @dfn{package |
b8638f03 LC |
4622 | variants}---for instance, packages built from different source code. |
4623 | This is a convenient way to create customized packages on the fly | |
4624 | without having to type in the definitions of package variants | |
4625 | (@pxref{Defining Packages}). | |
88ad6ded LC |
4626 | |
4627 | @table @code | |
4628 | ||
4629 | @item --with-source=@var{source} | |
4630 | Use @var{source} as the source of the corresponding package. | |
4631 | @var{source} must be a file name or a URL, as for @command{guix | |
4632 | download} (@pxref{Invoking guix download}). | |
4633 | ||
f97c9175 AE |
4634 | The ``corresponding package'' is taken to be the one specified on the |
4635 | command line the name of which matches the base of @var{source}---e.g., | |
4636 | if @var{source} is @code{/src/guile-2.0.10.tar.gz}, the corresponding | |
88ad6ded | 4637 | package is @code{guile}. Likewise, the version string is inferred from |
f97c9175 | 4638 | @var{source}; in the previous example, it is @code{2.0.10}. |
88ad6ded LC |
4639 | |
4640 | This option allows users to try out versions of packages other than the | |
4641 | one provided by the distribution. The example below downloads | |
4642 | @file{ed-1.7.tar.gz} from a GNU mirror and uses that as the source for | |
4643 | the @code{ed} package: | |
4644 | ||
4645 | @example | |
4646 | guix build ed --with-source=mirror://gnu/ed/ed-1.7.tar.gz | |
4647 | @end example | |
4648 | ||
4649 | As a developer, @code{--with-source} makes it easy to test release | |
4650 | candidates: | |
4651 | ||
4652 | @example | |
4653 | guix build guile --with-source=../guile-2.0.9.219-e1bb7.tar.xz | |
4654 | @end example | |
4655 | ||
4656 | @dots{} or to build from a checkout in a pristine environment: | |
4657 | ||
4658 | @example | |
4659 | $ git clone git://git.sv.gnu.org/guix.git | |
4660 | $ guix build guix --with-source=./guix | |
4661 | @end example | |
4662 | ||
47c0f92c LC |
4663 | @item --with-input=@var{package}=@var{replacement} |
4664 | Replace dependency on @var{package} by a dependency on | |
4665 | @var{replacement}. @var{package} must be a package name, and | |
4666 | @var{replacement} must be a package specification such as @code{guile} | |
4667 | or @code{guile@@1.8}. | |
4668 | ||
f97c9175 | 4669 | For instance, the following command builds Guix, but replaces its |
47c0f92c LC |
4670 | dependency on the current stable version of Guile with a dependency on |
4671 | the development version of Guile, @code{guile-next}: | |
4672 | ||
4673 | @example | |
4674 | guix build --with-input=guile=guile-next guix | |
4675 | @end example | |
4676 | ||
4677 | This is a recursive, deep replacement. So in this example, both | |
4678 | @code{guix} and its dependency @code{guile-json} (which also depends on | |
4679 | @code{guile}) get rebuilt against @code{guile-next}. | |
4680 | ||
2a75b0b6 LC |
4681 | This is implemented using the @code{package-input-rewriting} Scheme |
4682 | procedure (@pxref{Defining Packages, @code{package-input-rewriting}}). | |
645b9df8 LC |
4683 | |
4684 | @item --with-graft=@var{package}=@var{replacement} | |
4685 | This is similar to @code{--with-input} but with an important difference: | |
4686 | instead of rebuilding all the dependency chain, @var{replacement} is | |
4687 | built and then @dfn{grafted} onto the binaries that were initially | |
4688 | referring to @var{package}. @xref{Security Updates}, for more | |
4689 | information on grafts. | |
4690 | ||
4691 | For example, the command below grafts version 3.5.4 of GnuTLS onto Wget | |
4692 | and all its dependencies, replacing references to the version of GnuTLS | |
4693 | they currently refer to: | |
4694 | ||
4695 | @example | |
4696 | guix build --with-graft=gnutls=gnutls@@3.5.4 wget | |
4697 | @end example | |
4698 | ||
4699 | This has the advantage of being much faster than rebuilding everything. | |
4700 | But there is a caveat: it works if and only if @var{package} and | |
4701 | @var{replacement} are strictly compatible---for example, if they provide | |
4702 | a library, the application binary interface (ABI) of those libraries | |
4703 | must be compatible. If @var{replacement} is somehow incompatible with | |
4704 | @var{package}, then the resulting package may be unusable. Use with | |
4705 | care! | |
4706 | ||
88ad6ded LC |
4707 | @end table |
4708 | ||
ccd7158d LC |
4709 | @node Additional Build Options |
4710 | @subsection Additional Build Options | |
4711 | ||
4712 | The command-line options presented below are specific to @command{guix | |
4713 | build}. | |
c78bd12b LC |
4714 | |
4715 | @table @code | |
4716 | ||
5284339d LC |
4717 | @item --quiet |
4718 | @itemx -q | |
4719 | Build quietly, without displaying the build log. Upon completion, the | |
4720 | build log is kept in @file{/var} (or similar) and can always be | |
4721 | retrieved using the @option{--log-file} option. | |
4722 | ||
34a1783f DT |
4723 | @item --file=@var{file} |
4724 | @itemx -f @var{file} | |
4725 | ||
4726 | Build the package or derivation that the code within @var{file} | |
4727 | evaluates to. | |
4728 | ||
4729 | As an example, @var{file} might contain a package definition like this | |
4730 | (@pxref{Defining Packages}): | |
4731 | ||
4732 | @example | |
4733 | @verbatiminclude package-hello.scm | |
4734 | @end example | |
4735 | ||
c78bd12b LC |
4736 | @item --expression=@var{expr} |
4737 | @itemx -e @var{expr} | |
ac5de156 | 4738 | Build the package or derivation @var{expr} evaluates to. |
c78bd12b | 4739 | |
5401dd75 | 4740 | For example, @var{expr} may be @code{(@@ (gnu packages guile) |
c78bd12b LC |
4741 | guile-1.8)}, which unambiguously designates this specific variant of |
4742 | version 1.8 of Guile. | |
4743 | ||
f97c9175 | 4744 | Alternatively, @var{expr} may be a G-expression, in which case it is used |
56b82106 LC |
4745 | as a build program passed to @code{gexp->derivation} |
4746 | (@pxref{G-Expressions}). | |
4747 | ||
4748 | Lastly, @var{expr} may refer to a zero-argument monadic procedure | |
ac5de156 LC |
4749 | (@pxref{The Store Monad}). The procedure must return a derivation as a |
4750 | monadic value, which is then passed through @code{run-with-store}. | |
4751 | ||
c78bd12b LC |
4752 | @item --source |
4753 | @itemx -S | |
f97c9175 | 4754 | Build the source derivations of the packages, rather than the packages |
c78bd12b LC |
4755 | themselves. |
4756 | ||
e49951eb | 4757 | For instance, @code{guix build -S gcc} returns something like |
f97c9175 AE |
4758 | @file{/gnu/store/@dots{}-gcc-4.7.2.tar.bz2}, which is the GCC |
4759 | source tarball. | |
c78bd12b | 4760 | |
f9cc8971 | 4761 | The returned source tarball is the result of applying any patches and |
f97c9175 | 4762 | code snippets specified in the package @code{origin} (@pxref{Defining |
f9cc8971 LC |
4763 | Packages}). |
4764 | ||
2cdfe13d EB |
4765 | @item --sources |
4766 | Fetch and return the source of @var{package-or-derivation} and all their | |
4767 | dependencies, recursively. This is a handy way to obtain a local copy | |
4768 | of all the source code needed to build @var{packages}, allowing you to | |
4769 | eventually build them even without network access. It is an extension | |
4770 | of the @code{--source} option and can accept one of the following | |
4771 | optional argument values: | |
4772 | ||
4773 | @table @code | |
4774 | @item package | |
4775 | This value causes the @code{--sources} option to behave in the same way | |
4776 | as the @code{--source} option. | |
4777 | ||
4778 | @item all | |
f97c9175 AE |
4779 | Build the source derivations of all packages, including any source that |
4780 | might be listed as @code{inputs}. This is the default value. | |
2cdfe13d EB |
4781 | |
4782 | @example | |
4783 | $ guix build --sources tzdata | |
4784 | The following derivations will be built: | |
4785 | /gnu/store/@dots{}-tzdata2015b.tar.gz.drv | |
4786 | /gnu/store/@dots{}-tzcode2015b.tar.gz.drv | |
4787 | @end example | |
4788 | ||
4789 | @item transitive | |
f97c9175 AE |
4790 | Build the source derivations of all packages, as well of all transitive |
4791 | inputs to the packages. This can be used e.g. to | |
2cdfe13d EB |
4792 | prefetch package source for later offline building. |
4793 | ||
4794 | @example | |
4795 | $ guix build --sources=transitive tzdata | |
4796 | The following derivations will be built: | |
4797 | /gnu/store/@dots{}-tzcode2015b.tar.gz.drv | |
4798 | /gnu/store/@dots{}-findutils-4.4.2.tar.xz.drv | |
4799 | /gnu/store/@dots{}-grep-2.21.tar.xz.drv | |
4800 | /gnu/store/@dots{}-coreutils-8.23.tar.xz.drv | |
4801 | /gnu/store/@dots{}-make-4.1.tar.xz.drv | |
4802 | /gnu/store/@dots{}-bash-4.3.tar.xz.drv | |
4803 | @dots{} | |
4804 | @end example | |
4805 | ||
4806 | @end table | |
4807 | ||
c78bd12b LC |
4808 | @item --system=@var{system} |
4809 | @itemx -s @var{system} | |
4810 | Attempt to build for @var{system}---e.g., @code{i686-linux}---instead of | |
f97c9175 | 4811 | the system type of the build host. |
c78bd12b LC |
4812 | |
4813 | An example use of this is on Linux-based systems, which can emulate | |
4814 | different personalities. For instance, passing | |
4815 | @code{--system=i686-linux} on an @code{x86_64-linux} system allows users | |
4816 | to build packages in a complete 32-bit environment. | |
4817 | ||
e55ec43d LC |
4818 | @item --target=@var{triplet} |
4819 | @cindex cross-compilation | |
4820 | Cross-build for @var{triplet}, which must be a valid GNU triplet, such | |
4821 | as @code{"mips64el-linux-gnu"} (@pxref{Configuration Names, GNU | |
4822 | configuration triplets,, configure, GNU Configure and Build System}). | |
4823 | ||
a8d65643 LC |
4824 | @anchor{build-check} |
4825 | @item --check | |
4826 | @cindex determinism, checking | |
4827 | @cindex reproducibility, checking | |
4828 | Rebuild @var{package-or-derivation}, which are already available in the | |
4829 | store, and raise an error if the build results are not bit-for-bit | |
4830 | identical. | |
4831 | ||
f97c9175 AE |
4832 | This mechanism allows you to check whether previously installed |
4833 | substitutes are genuine (@pxref{Substitutes}), or whether the build result | |
4834 | of a package is deterministic. @xref{Invoking guix challenge}, for more | |
a8d65643 LC |
4835 | background information and tools. |
4836 | ||
7f3b2510 ED |
4837 | When used in conjunction with @option{--keep-failed}, the differing |
4838 | output is kept in the store, under @file{/gnu/store/@dots{}-check}. | |
4839 | This makes it easy to look for differences between the two results. | |
4840 | ||
c78bd12b LC |
4841 | @item --derivations |
4842 | @itemx -d | |
4843 | Return the derivation paths, not the output paths, of the given | |
4844 | packages. | |
4845 | ||
70ee5642 LC |
4846 | @item --root=@var{file} |
4847 | @itemx -r @var{file} | |
4848 | Make @var{file} a symlink to the result, and register it as a garbage | |
4849 | collector root. | |
4850 | ||
4851 | @item --log-file | |
3f208ad7 | 4852 | Return the build log file names or URLs for the given |
f97c9175 | 4853 | @var{package-or-derivation}, or raise an error if build logs are |
70ee5642 LC |
4854 | missing. |
4855 | ||
4856 | This works regardless of how packages or derivations are specified. For | |
4857 | instance, the following invocations are equivalent: | |
4858 | ||
4859 | @example | |
4860 | guix build --log-file `guix build -d guile` | |
4861 | guix build --log-file `guix build guile` | |
4862 | guix build --log-file guile | |
4863 | guix build --log-file -e '(@@ (gnu packages guile) guile-2.0)' | |
4864 | @end example | |
4865 | ||
3f208ad7 LC |
4866 | If a log is unavailable locally, and unless @code{--no-substitutes} is |
4867 | passed, the command looks for a corresponding log on one of the | |
4868 | substitute servers (as specified with @code{--substitute-urls}.) | |
70ee5642 | 4869 | |
f97c9175 AE |
4870 | So for instance, imagine you want to see the build log of GDB on MIPS, |
4871 | but you are actually on an @code{x86_64} machine: | |
3f208ad7 LC |
4872 | |
4873 | @example | |
a01ad638 | 4874 | $ guix build --log-file gdb -s mips64el-linux |
df061d07 | 4875 | https://hydra.gnu.org/log/@dots{}-gdb-7.10 |
3f208ad7 LC |
4876 | @end example |
4877 | ||
4878 | You can freely access a huge library of build logs! | |
70ee5642 LC |
4879 | @end table |
4880 | ||
16eb115e | 4881 | |
39bee8a2 LC |
4882 | @node Invoking guix edit |
4883 | @section Invoking @command{guix edit} | |
4884 | ||
e32171ee | 4885 | @cindex @command{guix edit} |
39bee8a2 LC |
4886 | @cindex package definition, editing |
4887 | So many packages, so many source files! The @command{guix edit} command | |
424a323e GC |
4888 | facilitates the life of users and packagers by pointing their editor at |
4889 | the source file containing the definition of the specified packages. | |
4890 | For instance: | |
39bee8a2 LC |
4891 | |
4892 | @example | |
7b9a66e5 | 4893 | guix edit gcc@@4.9 vim |
39bee8a2 LC |
4894 | @end example |
4895 | ||
4896 | @noindent | |
6237b9fa | 4897 | launches the program specified in the @code{VISUAL} or in the |
424a323e | 4898 | @code{EDITOR} environment variable to view the recipe of GCC@tie{}4.9.3 |
6237b9fa | 4899 | and that of Vim. |
39bee8a2 | 4900 | |
424a323e GC |
4901 | If you are using a Guix Git checkout (@pxref{Building from Git}), or |
4902 | have created your own packages on @code{GUIX_PACKAGE_PATH} | |
4903 | (@pxref{Defining Packages}), you will be able to edit the package | |
4904 | recipes. Otherwise, you will be able to examine the read-only recipes | |
4905 | for packages currently in the store. | |
4906 | ||
f97c9175 | 4907 | If you are using Emacs, note that the Emacs user interface provides the |
7c1b1ae2 | 4908 | @kbd{M-x guix-edit} command and a similar functionality in the ``package |
f97c9175 | 4909 | info'' and ``package list'' buffers created by the @kbd{M-x |
7c1b1ae2 | 4910 | guix-search-by-name} and similar commands (@pxref{Emacs Commands}). |
39bee8a2 LC |
4911 | |
4912 | ||
210cc920 LC |
4913 | @node Invoking guix download |
4914 | @section Invoking @command{guix download} | |
4915 | ||
e32171ee JD |
4916 | @cindex @command{guix download} |
4917 | @cindex downloading package sources | |
210cc920 | 4918 | When writing a package definition, developers typically need to download |
f97c9175 | 4919 | a source tarball, compute its SHA256 hash, and write that |
210cc920 LC |
4920 | hash in the package definition (@pxref{Defining Packages}). The |
4921 | @command{guix download} tool helps with this task: it downloads a file | |
4922 | from the given URI, adds it to the store, and prints both its file name | |
4923 | in the store and its SHA256 hash. | |
4924 | ||
4925 | The fact that the downloaded file is added to the store saves bandwidth: | |
4926 | when the developer eventually tries to build the newly defined package | |
4927 | with @command{guix build}, the source tarball will not have to be | |
4928 | downloaded again because it is already in the store. It is also a | |
4929 | convenient way to temporarily stash files, which may be deleted | |
4930 | eventually (@pxref{Invoking guix gc}). | |
4931 | ||
4932 | The @command{guix download} command supports the same URIs as used in | |
4933 | package definitions. In particular, it supports @code{mirror://} URIs. | |
4934 | @code{https} URIs (HTTP over TLS) are supported @emph{provided} the | |
4935 | Guile bindings for GnuTLS are available in the user's environment; when | |
537c8bb3 LC |
4936 | they are not available, an error is raised. @xref{Guile Preparations, |
4937 | how to install the GnuTLS bindings for Guile,, gnutls-guile, | |
4938 | GnuTLS-Guile}, for more information. | |
210cc920 | 4939 | |
bc3c41ce LC |
4940 | @command{guix download} verifies HTTPS server certificates by loading |
4941 | the certificates of X.509 authorities from the directory pointed to by | |
4942 | the @code{SSL_CERT_DIR} environment variable (@pxref{X.509 | |
64b8695c | 4943 | Certificates}), unless @option{--no-check-certificate} is used. |
bc3c41ce | 4944 | |
64b8695c | 4945 | The following options are available: |
210cc920 LC |
4946 | |
4947 | @table @code | |
4948 | @item --format=@var{fmt} | |
4949 | @itemx -f @var{fmt} | |
4950 | Write the hash in the format specified by @var{fmt}. For more | |
081145cf | 4951 | information on the valid values for @var{fmt}, @pxref{Invoking guix hash}. |
64b8695c LC |
4952 | |
4953 | @item --no-check-certificate | |
4954 | Do not validate the X.509 certificates of HTTPS servers. | |
4955 | ||
4956 | When using this option, you have @emph{absolutely no guarantee} that you | |
4957 | are communicating with the authentic server responsible for the given | |
4958 | URL, which makes you vulnerable to ``man-in-the-middle'' attacks. | |
4959 | ||
1bcc87bb LC |
4960 | @item --output=@var{file} |
4961 | @itemx -o @var{file} | |
4962 | Save the downloaded file to @var{file} instead of adding it to the | |
4963 | store. | |
210cc920 LC |
4964 | @end table |
4965 | ||
6c365eca NK |
4966 | @node Invoking guix hash |
4967 | @section Invoking @command{guix hash} | |
4968 | ||
e32171ee | 4969 | @cindex @command{guix hash} |
210cc920 | 4970 | The @command{guix hash} command computes the SHA256 hash of a file. |
6c365eca NK |
4971 | It is primarily a convenience tool for anyone contributing to the |
4972 | distribution: it computes the cryptographic hash of a file, which can be | |
4973 | used in the definition of a package (@pxref{Defining Packages}). | |
4974 | ||
4975 | The general syntax is: | |
4976 | ||
4977 | @example | |
4978 | guix hash @var{option} @var{file} | |
4979 | @end example | |
4980 | ||
343dc117 LC |
4981 | When @var{file} is @code{-} (a hyphen), @command{guix hash} computes the |
4982 | hash of data read from standard input. @command{guix hash} has the | |
4983 | following options: | |
6c365eca NK |
4984 | |
4985 | @table @code | |
4986 | ||
4987 | @item --format=@var{fmt} | |
4988 | @itemx -f @var{fmt} | |
210cc920 | 4989 | Write the hash in the format specified by @var{fmt}. |
6c365eca NK |
4990 | |
4991 | Supported formats: @code{nix-base32}, @code{base32}, @code{base16} | |
4992 | (@code{hex} and @code{hexadecimal} can be used as well). | |
4993 | ||
4994 | If the @option{--format} option is not specified, @command{guix hash} | |
4995 | will output the hash in @code{nix-base32}. This representation is used | |
4996 | in the definitions of packages. | |
4997 | ||
3140f2df LC |
4998 | @item --recursive |
4999 | @itemx -r | |
5000 | Compute the hash on @var{file} recursively. | |
5001 | ||
5002 | In this case, the hash is computed on an archive containing @var{file}, | |
f97c9175 AE |
5003 | including its children if it is a directory. Some of the metadata of |
5004 | @var{file} is part of the archive; for instance, when @var{file} is a | |
3140f2df | 5005 | regular file, the hash is different depending on whether @var{file} is |
f97c9175 | 5006 | executable or not. Metadata such as time stamps has no impact on the |
3140f2df LC |
5007 | hash (@pxref{Invoking guix archive}). |
5008 | @c FIXME: Replace xref above with xref to an ``Archive'' section when | |
5009 | @c it exists. | |
5010 | ||
392a4e12 JN |
5011 | @item --exclude-vcs |
5012 | @itemx -x | |
5013 | When combined with @option{--recursive}, exclude version control system | |
5014 | directories (@file{.bzr}, @file{.git}, @file{.hg}, etc.) | |
5015 | ||
db97a03a LC |
5016 | @vindex git-fetch |
5017 | As an example, here is how you would compute the hash of a Git checkout, | |
5018 | which is useful when using the @code{git-fetch} method (@pxref{origin | |
5019 | Reference}): | |
5020 | ||
5021 | @example | |
5022 | $ git clone http://example.org/foo.git | |
5023 | $ cd foo | |
392a4e12 | 5024 | $ guix hash -rx . |
db97a03a | 5025 | @end example |
6c365eca NK |
5026 | @end table |
5027 | ||
2f7d2d91 LC |
5028 | @node Invoking guix import |
5029 | @section Invoking @command{guix import} | |
5030 | ||
5031 | @cindex importing packages | |
5032 | @cindex package import | |
5033 | @cindex package conversion | |
e32171ee | 5034 | @cindex Invoking @command{guix import} |
f97c9175 AE |
5035 | The @command{guix import} command is useful for people who would like to |
5036 | add a package to the distribution with as little work as | |
5037 | possible---a legitimate demand. The command knows of a few | |
5038 | repositories from which it can ``import'' package metadata. The result | |
2f7d2d91 LC |
5039 | is a package definition, or a template thereof, in the format we know |
5040 | (@pxref{Defining Packages}). | |
5041 | ||
5042 | The general syntax is: | |
5043 | ||
5044 | @example | |
5045 | guix import @var{importer} @var{options}@dots{} | |
5046 | @end example | |
5047 | ||
5048 | @var{importer} specifies the source from which to import package | |
f97c9175 | 5049 | metadata, and @var{options} specifies a package identifier and other |
2f7d2d91 LC |
5050 | options specific to @var{importer}. Currently, the available |
5051 | ``importers'' are: | |
5052 | ||
5053 | @table @code | |
5054 | @item gnu | |
f97c9175 | 5055 | Import metadata for the given GNU package. This provides a template |
2f7d2d91 LC |
5056 | for the latest version of that GNU package, including the hash of its |
5057 | source tarball, and its canonical synopsis and description. | |
5058 | ||
f97c9175 | 5059 | Additional information such as the package dependencies and its |
2f7d2d91 LC |
5060 | license needs to be figured out manually. |
5061 | ||
5062 | For example, the following command returns a package definition for | |
5063 | GNU@tie{}Hello: | |
5064 | ||
5065 | @example | |
5066 | guix import gnu hello | |
5067 | @end example | |
5068 | ||
5069 | Specific command-line options are: | |
5070 | ||
5071 | @table @code | |
5072 | @item --key-download=@var{policy} | |
5073 | As for @code{guix refresh}, specify the policy to handle missing OpenPGP | |
f97c9175 | 5074 | keys when verifying the package signature. @xref{Invoking guix |
2f7d2d91 LC |
5075 | refresh, @code{--key-download}}. |
5076 | @end table | |
5077 | ||
5078 | @item pypi | |
5079 | @cindex pypi | |
f97c9175 | 5080 | Import metadata from the @uref{https://pypi.python.org/, Python Package |
2f7d2d91 LC |
5081 | Index}@footnote{This functionality requires Guile-JSON to be installed. |
5082 | @xref{Requirements}.}. Information is taken from the JSON-formatted | |
5083 | description available at @code{pypi.python.org} and usually includes all | |
266785d2 CR |
5084 | the relevant information, including package dependencies. For maximum |
5085 | efficiency, it is recommended to install the @command{unzip} utility, so | |
5086 | that the importer can unzip Python wheels and gather data from them. | |
2f7d2d91 | 5087 | |
f97c9175 | 5088 | The command below imports metadata for the @code{itsdangerous} Python |
2f7d2d91 LC |
5089 | package: |
5090 | ||
5091 | @example | |
5092 | guix import pypi itsdangerous | |
5093 | @end example | |
5094 | ||
3aae8145 DT |
5095 | @item gem |
5096 | @cindex gem | |
f97c9175 | 5097 | Import metadata from @uref{https://rubygems.org/, |
3aae8145 DT |
5098 | RubyGems}@footnote{This functionality requires Guile-JSON to be |
5099 | installed. @xref{Requirements}.}. Information is taken from the | |
5100 | JSON-formatted description available at @code{rubygems.org} and includes | |
5101 | most relevant information, including runtime dependencies. There are | |
f97c9175 | 5102 | some caveats, however. The metadata doesn't distinguish between |
3aae8145 DT |
5103 | synopses and descriptions, so the same string is used for both fields. |
5104 | Additionally, the details of non-Ruby dependencies required to build | |
5105 | native extensions is unavailable and left as an exercise to the | |
5106 | packager. | |
5107 | ||
f97c9175 | 5108 | The command below imports metadata for the @code{rails} Ruby package: |
3aae8145 DT |
5109 | |
5110 | @example | |
5111 | guix import gem rails | |
5112 | @end example | |
5113 | ||
d45dc6da EB |
5114 | @item cpan |
5115 | @cindex CPAN | |
3c192e4e AE |
5116 | Import metadata from @uref{https://www.metacpan.org/, MetaCPAN}@footnote{This |
5117 | functionality requires Guile-JSON to be installed. | |
5118 | @xref{Requirements}.}. | |
f97c9175 | 5119 | Information is taken from the JSON-formatted metadata provided through |
d45dc6da | 5120 | @uref{https://api.metacpan.org/, MetaCPAN's API} and includes most |
66392e47 EB |
5121 | relevant information, such as module dependencies. License information |
5122 | should be checked closely. If Perl is available in the store, then the | |
5123 | @code{corelist} utility will be used to filter core modules out of the | |
5124 | list of dependencies. | |
d45dc6da | 5125 | |
f97c9175 | 5126 | The command command below imports metadata for the @code{Acme::Boolean} |
d45dc6da EB |
5127 | Perl module: |
5128 | ||
5129 | @example | |
5130 | guix import cpan Acme::Boolean | |
5131 | @end example | |
5132 | ||
e1248602 RW |
5133 | @item cran |
5134 | @cindex CRAN | |
d0bd632f | 5135 | @cindex Bioconductor |
f97c9175 | 5136 | Import metadata from @uref{http://cran.r-project.org/, CRAN}, the |
e1248602 RW |
5137 | central repository for the @uref{http://r-project.org, GNU@tie{}R |
5138 | statistical and graphical environment}. | |
5139 | ||
f97c9175 | 5140 | Information is extracted from the @code{DESCRIPTION} file of the package. |
e1248602 | 5141 | |
f97c9175 | 5142 | The command command below imports metadata for the @code{Cairo} |
e1248602 RW |
5143 | R package: |
5144 | ||
5145 | @example | |
5146 | guix import cran Cairo | |
5147 | @end example | |
5148 | ||
f97c9175 | 5149 | When @code{--archive=bioconductor} is added, metadata is imported from |
d0bd632f RW |
5150 | @uref{http://www.bioconductor.org/, Bioconductor}, a repository of R |
5151 | packages for for the analysis and comprehension of high-throughput | |
5152 | genomic data in bioinformatics. | |
5153 | ||
f97c9175 | 5154 | Information is extracted from the @code{DESCRIPTION} file of a package |
d0bd632f RW |
5155 | published on the web interface of the Bioconductor SVN repository. |
5156 | ||
f97c9175 | 5157 | The command below imports metadata for the @code{GenomicRanges} |
d0bd632f RW |
5158 | R package: |
5159 | ||
5160 | @example | |
5161 | guix import cran --archive=bioconductor GenomicRanges | |
5162 | @end example | |
5163 | ||
2f7d2d91 | 5164 | @item nix |
f97c9175 | 5165 | Import metadata from a local copy of the source of the |
2f7d2d91 LC |
5166 | @uref{http://nixos.org/nixpkgs/, Nixpkgs distribution}@footnote{This |
5167 | relies on the @command{nix-instantiate} command of | |
5168 | @uref{http://nixos.org/nix/, Nix}.}. Package definitions in Nixpkgs are | |
5169 | typically written in a mixture of Nix-language and Bash code. This | |
5170 | command only imports the high-level package structure that is written in | |
5171 | the Nix language. It normally includes all the basic fields of a | |
5172 | package definition. | |
5173 | ||
5174 | When importing a GNU package, the synopsis and descriptions are replaced | |
5175 | by their canonical upstream variant. | |
5176 | ||
961d0d2d LC |
5177 | Usually, you will first need to do: |
5178 | ||
5179 | @example | |
5180 | export NIX_REMOTE=daemon | |
5181 | @end example | |
5182 | ||
5183 | @noindent | |
5184 | so that @command{nix-instantiate} does not try to open the Nix database. | |
5185 | ||
2f7d2d91 LC |
5186 | As an example, the command below imports the package definition of |
5187 | LibreOffice (more precisely, it imports the definition of the package | |
5188 | bound to the @code{libreoffice} top-level attribute): | |
5189 | ||
5190 | @example | |
5191 | guix import nix ~/path/to/nixpkgs libreoffice | |
5192 | @end example | |
863af4e1 FB |
5193 | |
5194 | @item hackage | |
5195 | @cindex hackage | |
f97c9175 | 5196 | Import metadata from the Haskell community's central package archive |
863af4e1 FB |
5197 | @uref{https://hackage.haskell.org/, Hackage}. Information is taken from |
5198 | Cabal files and includes all the relevant information, including package | |
5199 | dependencies. | |
5200 | ||
5201 | Specific command-line options are: | |
5202 | ||
5203 | @table @code | |
a4154748 FB |
5204 | @item --stdin |
5205 | @itemx -s | |
f97c9175 | 5206 | Read a Cabal file from standard input. |
863af4e1 FB |
5207 | @item --no-test-dependencies |
5208 | @itemx -t | |
f97c9175 | 5209 | Do not include dependencies required only by the test suites. |
a4154748 FB |
5210 | @item --cabal-environment=@var{alist} |
5211 | @itemx -e @var{alist} | |
5212 | @var{alist} is a Scheme alist defining the environment in which the | |
5213 | Cabal conditionals are evaluated. The accepted keys are: @code{os}, | |
5214 | @code{arch}, @code{impl} and a string representing the name of a flag. | |
5215 | The value associated with a flag has to be either the symbol | |
5216 | @code{true} or @code{false}. The value associated with other keys | |
5217 | has to conform to the Cabal file format definition. The default value | |
5218 | associated with the keys @code{os}, @code{arch} and @code{impl} is | |
f97c9175 | 5219 | @samp{linux}, @samp{x86_64} and @samp{ghc}, respectively. |
863af4e1 FB |
5220 | @end table |
5221 | ||
f97c9175 | 5222 | The command below imports metadata for the latest version of the |
a4154748 FB |
5223 | @code{HTTP} Haskell package without including test dependencies and |
5224 | specifying the value of the flag @samp{network-uri} as @code{false}: | |
863af4e1 FB |
5225 | |
5226 | @example | |
a4154748 | 5227 | guix import hackage -t -e "'((\"network-uri\" . false))" HTTP |
863af4e1 FB |
5228 | @end example |
5229 | ||
5230 | A specific package version may optionally be specified by following the | |
1b846da8 | 5231 | package name by an at-sign and a version number as in the following example: |
863af4e1 FB |
5232 | |
5233 | @example | |
1b846da8 | 5234 | guix import hackage mtl@@2.1.3.1 |
863af4e1 | 5235 | @end example |
7f74a931 FB |
5236 | |
5237 | @item elpa | |
5238 | @cindex elpa | |
f97c9175 | 5239 | Import metadata from an Emacs Lisp Package Archive (ELPA) package |
7f74a931 FB |
5240 | repository (@pxref{Packages,,, emacs, The GNU Emacs Manual}). |
5241 | ||
5242 | Specific command-line options are: | |
5243 | ||
5244 | @table @code | |
5245 | @item --archive=@var{repo} | |
5246 | @itemx -a @var{repo} | |
5247 | @var{repo} identifies the archive repository from which to retrieve the | |
5248 | information. Currently the supported repositories and their identifiers | |
5249 | are: | |
5250 | @itemize - | |
5251 | @item | |
840bd1d3 | 5252 | @uref{http://elpa.gnu.org/packages, GNU}, selected by the @code{gnu} |
7f74a931 FB |
5253 | identifier. This is the default. |
5254 | ||
624144e0 LC |
5255 | Packages from @code{elpa.gnu.org} are signed with one of the keys |
5256 | contained in the GnuPG keyring at | |
5257 | @file{share/emacs/25.1/etc/package-keyring.gpg} (or similar) in the | |
5258 | @code{emacs} package (@pxref{Package Installation, ELPA package | |
5259 | signatures,, emacs, The GNU Emacs Manual}). | |
5260 | ||
7f74a931 | 5261 | @item |
840bd1d3 | 5262 | @uref{http://stable.melpa.org/packages, MELPA-Stable}, selected by the |
7f74a931 FB |
5263 | @code{melpa-stable} identifier. |
5264 | ||
5265 | @item | |
840bd1d3 | 5266 | @uref{http://melpa.org/packages, MELPA}, selected by the @code{melpa} |
7f74a931 FB |
5267 | identifier. |
5268 | @end itemize | |
5269 | @end table | |
3e0c0365 DC |
5270 | |
5271 | @item crate | |
5272 | @cindex crate | |
5273 | Import metadata from the crates.io Rust package repository | |
5274 | @uref{https://crates.io, crates.io}. | |
2f7d2d91 LC |
5275 | @end table |
5276 | ||
5277 | The structure of the @command{guix import} code is modular. It would be | |
5278 | useful to have more importers for other package formats, and your help | |
5279 | is welcome here (@pxref{Contributing}). | |
5280 | ||
37166310 LC |
5281 | @node Invoking guix refresh |
5282 | @section Invoking @command{guix refresh} | |
5283 | ||
e32171ee | 5284 | @cindex @command {guix refresh} |
37166310 LC |
5285 | The primary audience of the @command{guix refresh} command is developers |
5286 | of the GNU software distribution. By default, it reports any packages | |
5287 | provided by the distribution that are outdated compared to the latest | |
5288 | upstream version, like this: | |
5289 | ||
5290 | @example | |
5291 | $ guix refresh | |
5292 | gnu/packages/gettext.scm:29:13: gettext would be upgraded from 0.18.1.1 to 0.18.2.1 | |
5293 | gnu/packages/glib.scm:77:12: glib would be upgraded from 2.34.3 to 2.37.0 | |
5294 | @end example | |
5295 | ||
e9c72306 LC |
5296 | Alternately, one can specify packages to consider, in which case a |
5297 | warning is emitted for packages that lack an updater: | |
5298 | ||
5299 | @example | |
5300 | $ guix refresh coreutils guile guile-ssh | |
5301 | gnu/packages/ssh.scm:205:2: warning: no updater for guile-ssh | |
5302 | gnu/packages/guile.scm:136:12: guile would be upgraded from 2.0.12 to 2.0.13 | |
5303 | @end example | |
5304 | ||
5305 | @command{guix refresh} browses the upstream repository of each package and determines | |
5306 | the highest version number of the releases therein. The command | |
bcb571cb | 5307 | knows how to update specific types of packages: GNU packages, ELPA |
e9c72306 | 5308 | packages, etc.---see the documentation for @option{--type} below. There |
bcb571cb LC |
5309 | are many packages, though, for which it lacks a method to determine |
5310 | whether a new upstream release is available. However, the mechanism is | |
5311 | extensible, so feel free to get in touch with us to add a new method! | |
37166310 LC |
5312 | |
5313 | When passed @code{--update}, it modifies distribution source files to | |
f97c9175 | 5314 | update the version numbers and source tarball hashes of those package |
37166310 LC |
5315 | recipes (@pxref{Defining Packages}). This is achieved by downloading |
5316 | each package's latest source tarball and its associated OpenPGP | |
5317 | signature, authenticating the downloaded tarball against its signature | |
5318 | using @command{gpg}, and finally computing its hash. When the public | |
5319 | key used to sign the tarball is missing from the user's keyring, an | |
5320 | attempt is made to automatically retrieve it from a public key server; | |
f97c9175 | 5321 | when this is successful, the key is added to the user's keyring; otherwise, |
37166310 LC |
5322 | @command{guix refresh} reports an error. |
5323 | ||
5324 | The following options are supported: | |
5325 | ||
5326 | @table @code | |
5327 | ||
2d7fc7da LC |
5328 | @item --expression=@var{expr} |
5329 | @itemx -e @var{expr} | |
5330 | Consider the package @var{expr} evaluates to. | |
5331 | ||
5332 | This is useful to precisely refer to a package, as in this example: | |
5333 | ||
5334 | @example | |
5335 | guix refresh -l -e '(@@@@ (gnu packages commencement) glibc-final)' | |
5336 | @end example | |
5337 | ||
5338 | This command lists the dependents of the ``final'' libc (essentially all | |
5339 | the packages.) | |
5340 | ||
37166310 LC |
5341 | @item --update |
5342 | @itemx -u | |
38e16b49 LC |
5343 | Update distribution source files (package recipes) in place. This is |
5344 | usually run from a checkout of the Guix source tree (@pxref{Running | |
5345 | Guix Before It Is Installed}): | |
5346 | ||
5347 | @example | |
e9c72306 | 5348 | $ ./pre-inst-env guix refresh -s non-core -u |
38e16b49 LC |
5349 | @end example |
5350 | ||
081145cf | 5351 | @xref{Defining Packages}, for more information on package definitions. |
37166310 LC |
5352 | |
5353 | @item --select=[@var{subset}] | |
5354 | @itemx -s @var{subset} | |
5355 | Select all the packages in @var{subset}, one of @code{core} or | |
5356 | @code{non-core}. | |
5357 | ||
5358 | The @code{core} subset refers to all the packages at the core of the | |
5359 | distribution---i.e., packages that are used to build ``everything | |
5360 | else''. This includes GCC, libc, Binutils, Bash, etc. Usually, | |
5361 | changing one of these packages in the distribution entails a rebuild of | |
5362 | all the others. Thus, such updates are an inconvenience to users in | |
5363 | terms of build time or bandwidth used to achieve the upgrade. | |
5364 | ||
5365 | The @code{non-core} subset refers to the remaining packages. It is | |
5366 | typically useful in cases where an update of the core packages would be | |
5367 | inconvenient. | |
5368 | ||
bcb571cb LC |
5369 | @item --type=@var{updater} |
5370 | @itemx -t @var{updater} | |
7191adc5 AK |
5371 | Select only packages handled by @var{updater} (may be a comma-separated |
5372 | list of updaters). Currently, @var{updater} may be one of: | |
bcb571cb LC |
5373 | |
5374 | @table @code | |
5375 | @item gnu | |
5376 | the updater for GNU packages; | |
e80c0f85 LC |
5377 | @item gnome |
5378 | the updater for GNOME packages; | |
9c97afe8 DC |
5379 | @item kde |
5380 | the updater for KDE packages; | |
62061d6b AW |
5381 | @item xorg |
5382 | the updater for X.org packages; | |
2fd370e8 LC |
5383 | @item kernel.org |
5384 | the updater for packages hosted on kernel.org; | |
bcb571cb | 5385 | @item elpa |
d882c235 LC |
5386 | the updater for @uref{http://elpa.gnu.org/, ELPA} packages; |
5387 | @item cran | |
b9d044ef | 5388 | the updater for @uref{http://cran.r-project.org/, CRAN} packages; |
d0bd632f RW |
5389 | @item bioconductor |
5390 | the updater for @uref{http://www.bioconductor.org/, Bioconductor} R packages; | |
bab020d7 | 5391 | @item pypi |
b9d044ef | 5392 | the updater for @uref{https://pypi.python.org, PyPI} packages. |
fbc5b815 BW |
5393 | @item gem |
5394 | the updater for @uref{https://rubygems.org, RubyGems} packages. | |
917a2a58 BW |
5395 | @item github |
5396 | the updater for @uref{https://github.com, GitHub} packages. | |
42efe27a EB |
5397 | @item hackage |
5398 | the updater for @uref{https://hackage.haskell.org, Hackage} packages. | |
8ac52987 DC |
5399 | @item crate |
5400 | the updater for @uref{https://crates.io, Crates} packages. | |
bcb571cb LC |
5401 | @end table |
5402 | ||
f97c9175 AE |
5403 | For instance, the following command only checks for updates of Emacs |
5404 | packages hosted at @code{elpa.gnu.org} and for updates of CRAN packages: | |
bcb571cb LC |
5405 | |
5406 | @example | |
7191adc5 | 5407 | $ guix refresh --type=elpa,cran |
d882c235 | 5408 | gnu/packages/statistics.scm:819:13: r-testthat would be upgraded from 0.10.0 to 0.11.0 |
bcb571cb LC |
5409 | gnu/packages/emacs.scm:856:13: emacs-auctex would be upgraded from 11.88.6 to 11.88.9 |
5410 | @end example | |
5411 | ||
37166310 LC |
5412 | @end table |
5413 | ||
5414 | In addition, @command{guix refresh} can be passed one or more package | |
5415 | names, as in this example: | |
5416 | ||
5417 | @example | |
e9c72306 | 5418 | $ ./pre-inst-env guix refresh -u emacs idutils gcc@@4.8 |
37166310 LC |
5419 | @end example |
5420 | ||
5421 | @noindent | |
5422 | The command above specifically updates the @code{emacs} and | |
5423 | @code{idutils} packages. The @code{--select} option would have no | |
5424 | effect in this case. | |
5425 | ||
7d193ec3 EB |
5426 | When considering whether to upgrade a package, it is sometimes |
5427 | convenient to know which packages would be affected by the upgrade and | |
5428 | should be checked for compatibility. For this the following option may | |
5429 | be used when passing @command{guix refresh} one or more package names: | |
5430 | ||
5431 | @table @code | |
5432 | ||
6ffa706b AK |
5433 | @item --list-updaters |
5434 | @itemx -L | |
5435 | List available updaters and exit (see @option{--type} above.) | |
5436 | ||
3676f892 LC |
5437 | For each updater, display the fraction of packages it covers; at the |
5438 | end, display the fraction of packages covered by all these updaters. | |
5439 | ||
7d193ec3 EB |
5440 | @item --list-dependent |
5441 | @itemx -l | |
5442 | List top-level dependent packages that would need to be rebuilt as a | |
5443 | result of upgrading one or more packages. | |
5444 | ||
5445 | @end table | |
5446 | ||
5447 | Be aware that the @code{--list-dependent} option only | |
5448 | @emph{approximates} the rebuilds that would be required as a result of | |
5449 | an upgrade. More rebuilds might be required under some circumstances. | |
5450 | ||
5451 | @example | |
7779ab61 LC |
5452 | $ guix refresh --list-dependent flex |
5453 | Building the following 120 packages would ensure 213 dependent packages are rebuilt: | |
5454 | hop-2.4.0 geiser-0.4 notmuch-0.18 mu-0.9.9.5 cflow-1.4 idutils-4.6 @dots{} | |
7d193ec3 EB |
5455 | @end example |
5456 | ||
5457 | The command above lists a set of packages that could be built to check | |
5458 | for compatibility with an upgraded @code{flex} package. | |
5459 | ||
f9230085 LC |
5460 | The following options can be used to customize GnuPG operation: |
5461 | ||
5462 | @table @code | |
5463 | ||
f9230085 LC |
5464 | @item --gpg=@var{command} |
5465 | Use @var{command} as the GnuPG 2.x command. @var{command} is searched | |
5466 | for in @code{$PATH}. | |
5467 | ||
2bc53ba9 LC |
5468 | @item --key-download=@var{policy} |
5469 | Handle missing OpenPGP keys according to @var{policy}, which may be one | |
5470 | of: | |
5471 | ||
5472 | @table @code | |
5473 | @item always | |
5474 | Always download missing OpenPGP keys from the key server, and add them | |
5475 | to the user's GnuPG keyring. | |
5476 | ||
5477 | @item never | |
5478 | Never try to download missing OpenPGP keys. Instead just bail out. | |
5479 | ||
5480 | @item interactive | |
5481 | When a package signed with an unknown OpenPGP key is encountered, ask | |
5482 | the user whether to download it or not. This is the default behavior. | |
5483 | @end table | |
5484 | ||
5485 | @item --key-server=@var{host} | |
5486 | Use @var{host} as the OpenPGP key server when importing a public key. | |
5487 | ||
f9230085 LC |
5488 | @end table |
5489 | ||
917a2a58 BW |
5490 | The @code{github} updater uses the |
5491 | @uref{https://developer.github.com/v3/, GitHub API} to query for new | |
5492 | releases. When used repeatedly e.g. when refreshing all packages, | |
5493 | GitHub will eventually refuse to answer any further API requests. By | |
5494 | default 60 API requests per hour are allowed, and a full refresh on all | |
5495 | GitHub packages in Guix requires more than this. Authentication with | |
5496 | GitHub through the use of an API token alleviates these limits. To use | |
5497 | an API token, set the environment variable @code{GUIX_GITHUB_TOKEN} to a | |
5498 | token procured from @uref{https://github.com/settings/tokens} or | |
5499 | otherwise. | |
5500 | ||
5501 | ||
b4f5e0e8 CR |
5502 | @node Invoking guix lint |
5503 | @section Invoking @command{guix lint} | |
e32171ee JD |
5504 | |
5505 | @cindex @command{guix lint} | |
5506 | @cindex package, checking for errors | |
f97c9175 AE |
5507 | The @command{guix lint} command is meant to help package developers avoid |
5508 | common errors and use a consistent style. It runs a number of checks on | |
5509 | a given set of packages in order to find common mistakes in their | |
873c4085 LC |
5510 | definitions. Available @dfn{checkers} include (see |
5511 | @code{--list-checkers} for a complete list): | |
5512 | ||
5513 | @table @code | |
5514 | @item synopsis | |
5515 | @itemx description | |
5516 | Validate certain typographical and stylistic rules about package | |
5517 | descriptions and synopses. | |
5518 | ||
5519 | @item inputs-should-be-native | |
5520 | Identify inputs that should most likely be native inputs. | |
5521 | ||
5522 | @item source | |
5523 | @itemx home-page | |
fac46e3f | 5524 | @itemx mirror-url |
50f5c46d | 5525 | @itemx source-file-name |
873c4085 | 5526 | Probe @code{home-page} and @code{source} URLs and report those that are |
fac46e3f LC |
5527 | invalid. Suggest a @code{mirror://} URL when applicable. Check that |
5528 | the source file name is meaningful, e.g. is not | |
f97c9175 AE |
5529 | just a version number or ``git-checkout'', without a declared |
5530 | @code{file-name} (@pxref{origin Reference}). | |
40a7d4e5 | 5531 | |
5432734b | 5532 | @item cve |
09866b39 LC |
5533 | @cindex security vulnerabilities |
5534 | @cindex CVE, Common Vulnerabilities and Exposures | |
5432734b | 5535 | Report known vulnerabilities found in the Common Vulnerabilities and |
09866b39 | 5536 | Exposures (CVE) databases of the current and past year |
5432734b LC |
5537 | @uref{https://nvd.nist.gov/download.cfm#CVE_FEED, published by the US |
5538 | NIST}. | |
5539 | ||
09866b39 LC |
5540 | To view information about a particular vulnerability, visit pages such as: |
5541 | ||
5542 | @itemize | |
5543 | @item | |
5544 | @indicateurl{https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-YYYY-ABCD} | |
5545 | @item | |
5546 | @indicateurl{https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-YYYY-ABCD} | |
5547 | @end itemize | |
5548 | ||
5549 | @noindent | |
5550 | where @code{CVE-YYYY-ABCD} is the CVE identifier---e.g., | |
5551 | @code{CVE-2015-7554}. | |
5552 | ||
99effc8f LC |
5553 | Package developers can specify in package recipes the |
5554 | @uref{https://nvd.nist.gov/cpe.cfm,Common Platform Enumeration (CPE)} | |
5555 | name and version of the package when they differ from the name that Guix | |
5556 | uses, as in this example: | |
5557 | ||
5558 | @example | |
5559 | (package | |
5560 | (name "grub") | |
5561 | ;; @dots{} | |
5562 | ;; CPE calls this package "grub2". | |
5563 | (properties '((cpe-name . "grub2")))) | |
5564 | @end example | |
5565 | ||
40a7d4e5 LC |
5566 | @item formatting |
5567 | Warn about obvious source code formatting issues: trailing white space, | |
5568 | use of tabulations, etc. | |
873c4085 | 5569 | @end table |
b4f5e0e8 CR |
5570 | |
5571 | The general syntax is: | |
5572 | ||
5573 | @example | |
5574 | guix lint @var{options} @var{package}@dots{} | |
5575 | @end example | |
5576 | ||
5577 | If no package is given on the command line, then all packages are checked. | |
5578 | The @var{options} may be zero or more of the following: | |
5579 | ||
5580 | @table @code | |
f97c9175 AE |
5581 | @item --list-checkers |
5582 | @itemx -l | |
5583 | List and describe all the available checkers that will be run on packages | |
5584 | and exit. | |
b4f5e0e8 | 5585 | |
dd7c013d CR |
5586 | @item --checkers |
5587 | @itemx -c | |
5588 | Only enable the checkers specified in a comma-separated list using the | |
5589 | names returned by @code{--list-checkers}. | |
5590 | ||
b4f5e0e8 | 5591 | @end table |
37166310 | 5592 | |
fcc58db6 LC |
5593 | @node Invoking guix size |
5594 | @section Invoking @command{guix size} | |
5595 | ||
e32171ee JD |
5596 | @cindex size |
5597 | @cindex package size | |
5598 | @cindex closure | |
5599 | @cindex @command{guix size} | |
fcc58db6 LC |
5600 | The @command{guix size} command helps package developers profile the |
5601 | disk usage of packages. It is easy to overlook the impact of an | |
5602 | additional dependency added to a package, or the impact of using a | |
5603 | single output for a package that could easily be split (@pxref{Packages | |
f97c9175 | 5604 | with Multiple Outputs}). Such are the typical issues that |
fcc58db6 LC |
5605 | @command{guix size} can highlight. |
5606 | ||
5607 | The command can be passed a package specification such as @code{gcc-4.8} | |
5608 | or @code{guile:debug}, or a file name in the store. Consider this | |
5609 | example: | |
5610 | ||
5611 | @example | |
5612 | $ guix size coreutils | |
5613 | store item total self | |
5614 | /gnu/store/@dots{}-coreutils-8.23 70.0 13.9 19.8% | |
5615 | /gnu/store/@dots{}-gmp-6.0.0a 55.3 2.5 3.6% | |
5616 | /gnu/store/@dots{}-acl-2.2.52 53.7 0.5 0.7% | |
5617 | /gnu/store/@dots{}-attr-2.4.46 53.2 0.3 0.5% | |
5618 | /gnu/store/@dots{}-gcc-4.8.4-lib 52.9 15.7 22.4% | |
5619 | /gnu/store/@dots{}-glibc-2.21 37.2 37.2 53.1% | |
5620 | @end example | |
5621 | ||
5622 | @cindex closure | |
5623 | The store items listed here constitute the @dfn{transitive closure} of | |
5624 | Coreutils---i.e., Coreutils and all its dependencies, recursively---as | |
5625 | would be returned by: | |
5626 | ||
5627 | @example | |
5628 | $ guix gc -R /gnu/store/@dots{}-coreutils-8.23 | |
5629 | @end example | |
5630 | ||
f97c9175 | 5631 | Here the output shows three columns next to store items. The first column, |
fcc58db6 LC |
5632 | labeled ``total'', shows the size in mebibytes (MiB) of the closure of |
5633 | the store item---that is, its own size plus the size of all its | |
5634 | dependencies. The next column, labeled ``self'', shows the size of the | |
f97c9175 AE |
5635 | item itself. The last column shows the ratio of the size of the item |
5636 | itself to the space occupied by all the items listed here. | |
fcc58db6 LC |
5637 | |
5638 | In this example, we see that the closure of Coreutils weighs in at | |
5639 | 70@tie{}MiB, half of which is taken by libc. (That libc represents a | |
5640 | large fraction of the closure is not a problem @i{per se} because it is | |
5641 | always available on the system anyway.) | |
5642 | ||
5643 | When the package passed to @command{guix size} is available in the | |
5644 | store, @command{guix size} queries the daemon to determine its | |
5645 | dependencies, and measures its size in the store, similar to @command{du | |
5646 | -ms --apparent-size} (@pxref{du invocation,,, coreutils, GNU | |
5647 | Coreutils}). | |
5648 | ||
5649 | When the given package is @emph{not} in the store, @command{guix size} | |
f97c9175 AE |
5650 | reports information based on the available substitutes |
5651 | (@pxref{Substitutes}). This makes it possible it to profile disk usage of | |
5652 | store items that are not even on disk, only available remotely. | |
fcc58db6 | 5653 | |
db761534 LC |
5654 | You can also specify several package names: |
5655 | ||
5656 | @example | |
5657 | $ guix size coreutils grep sed bash | |
5658 | store item total self | |
5659 | /gnu/store/@dots{}-coreutils-8.24 77.8 13.8 13.4% | |
5660 | /gnu/store/@dots{}-grep-2.22 73.1 0.8 0.8% | |
5661 | /gnu/store/@dots{}-bash-4.3.42 72.3 4.7 4.6% | |
5662 | /gnu/store/@dots{}-readline-6.3 67.6 1.2 1.2% | |
5663 | @dots{} | |
5664 | total: 102.3 MiB | |
5665 | @end example | |
5666 | ||
5667 | @noindent | |
5668 | In this example we see that the combination of the four packages takes | |
5669 | 102.3@tie{}MiB in total, which is much less than the sum of each closure | |
5670 | since they have a lot of dependencies in common. | |
5671 | ||
a8f996c6 | 5672 | The available options are: |
fcc58db6 LC |
5673 | |
5674 | @table @option | |
5675 | ||
d490d06e LC |
5676 | @item --substitute-urls=@var{urls} |
5677 | Use substitute information from @var{urls}. | |
5678 | @xref{client-substitute-urls, the same option for @code{guix build}}. | |
5679 | ||
a8f996c6 | 5680 | @item --map-file=@var{file} |
f97c9175 | 5681 | Write a graphical map of disk usage in PNG format to @var{file}. |
a8f996c6 LC |
5682 | |
5683 | For the example above, the map looks like this: | |
5684 | ||
5685 | @image{images/coreutils-size-map,5in,, map of Coreutils disk usage | |
5686 | produced by @command{guix size}} | |
5687 | ||
5688 | This option requires that | |
5689 | @uref{http://wingolog.org/software/guile-charting/, Guile-Charting} be | |
5690 | installed and visible in Guile's module search path. When that is not | |
5691 | the case, @command{guix size} fails as it tries to load it. | |
5692 | ||
fcc58db6 LC |
5693 | @item --system=@var{system} |
5694 | @itemx -s @var{system} | |
5695 | Consider packages for @var{system}---e.g., @code{x86_64-linux}. | |
5696 | ||
5697 | @end table | |
5698 | ||
88856916 LC |
5699 | @node Invoking guix graph |
5700 | @section Invoking @command{guix graph} | |
5701 | ||
5702 | @cindex DAG | |
e32171ee JD |
5703 | @cindex @command{guix graph} |
5704 | @cindex package dependencies | |
88856916 LC |
5705 | Packages and their dependencies form a @dfn{graph}, specifically a |
5706 | directed acyclic graph (DAG). It can quickly become difficult to have a | |
f97c9175 AE |
5707 | mental model of the package DAG, so the @command{guix graph} command |
5708 | provides a visual representation of the DAG. @command{guix graph} | |
5709 | emits a DAG representation in the input format of | |
88856916 | 5710 | @uref{http://www.graphviz.org/, Graphviz}, so its output can be passed |
f97c9175 | 5711 | directly to the @command{dot} command of Graphviz. The general |
88856916 LC |
5712 | syntax is: |
5713 | ||
5714 | @example | |
5715 | guix graph @var{options} @var{package}@dots{} | |
5716 | @end example | |
5717 | ||
5718 | For example, the following command generates a PDF file representing the | |
5719 | package DAG for the GNU@tie{}Core Utilities, showing its build-time | |
5720 | dependencies: | |
5721 | ||
5722 | @example | |
5723 | guix graph coreutils | dot -Tpdf > dag.pdf | |
5724 | @end example | |
5725 | ||
5726 | The output looks like this: | |
5727 | ||
5728 | @image{images/coreutils-graph,2in,,Dependency graph of the GNU Coreutils} | |
5729 | ||
5730 | Nice little graph, no? | |
5731 | ||
f97c9175 | 5732 | But there is more than one graph! The one above is concise: it is the |
88856916 | 5733 | graph of package objects, omitting implicit inputs such as GCC, libc, |
f97c9175 AE |
5734 | grep, etc. It is often useful to have such a concise graph, but |
5735 | sometimes one may want to see more details. @command{guix graph} supports | |
5736 | several types of graphs, allowing you to choose the level of detail: | |
88856916 LC |
5737 | |
5738 | @table @code | |
5739 | @item package | |
f97c9175 | 5740 | This is the default type used in the example above. It shows the DAG of |
88856916 LC |
5741 | package objects, excluding implicit dependencies. It is concise, but |
5742 | filters out many details. | |
5743 | ||
5744 | @item bag-emerged | |
5745 | This is the package DAG, @emph{including} implicit inputs. | |
5746 | ||
5747 | For instance, the following command: | |
5748 | ||
5749 | @example | |
5750 | guix graph --type=bag-emerged coreutils | dot -Tpdf > dag.pdf | |
5751 | @end example | |
5752 | ||
5753 | ... yields this bigger graph: | |
5754 | ||
5755 | @image{images/coreutils-bag-graph,,5in,Detailed dependency graph of the GNU Coreutils} | |
5756 | ||
5757 | At the bottom of the graph, we see all the implicit inputs of | |
5758 | @var{gnu-build-system} (@pxref{Build Systems, @code{gnu-build-system}}). | |
5759 | ||
f97c9175 | 5760 | Now, note that the dependencies of these implicit inputs---that is, the |
88856916 LC |
5761 | @dfn{bootstrap dependencies} (@pxref{Bootstrapping})---are not shown |
5762 | here, for conciseness. | |
5763 | ||
5764 | @item bag | |
5765 | Similar to @code{bag-emerged}, but this time including all the bootstrap | |
5766 | dependencies. | |
5767 | ||
38b92daa LC |
5768 | @item bag-with-origins |
5769 | Similar to @code{bag}, but also showing origins and their dependencies. | |
5770 | ||
88856916 LC |
5771 | @item derivations |
5772 | This is the most detailed representation: It shows the DAG of | |
5773 | derivations (@pxref{Derivations}) and plain store items. Compared to | |
5774 | the above representation, many additional nodes are visible, including | |
f97c9175 | 5775 | build scripts, patches, Guile modules, etc. |
88856916 | 5776 | |
a773c314 LC |
5777 | For this type of graph, it is also possible to pass a @file{.drv} file |
5778 | name instead of a package name, as in: | |
5779 | ||
5780 | @example | |
5781 | guix graph -t derivation `guix system build -d my-config.scm` | |
5782 | @end example | |
88856916 LC |
5783 | @end table |
5784 | ||
f97c9175 | 5785 | All the types above correspond to @emph{build-time dependencies}. The |
88856916 LC |
5786 | following graph type represents the @emph{run-time dependencies}: |
5787 | ||
5788 | @table @code | |
5789 | @item references | |
5790 | This is the graph of @dfn{references} of a package output, as returned | |
5791 | by @command{guix gc --references} (@pxref{Invoking guix gc}). | |
5792 | ||
5793 | If the given package output is not available in the store, @command{guix | |
5794 | graph} attempts to obtain dependency information from substitutes. | |
a773c314 LC |
5795 | |
5796 | Here you can also pass a store file name instead of a package name. For | |
5797 | example, the command below produces the reference graph of your profile | |
5798 | (which can be big!): | |
5799 | ||
5800 | @example | |
5801 | guix graph -t references `readlink -f ~/.guix-profile` | |
5802 | @end example | |
7f8fec0f LC |
5803 | |
5804 | @item referrers | |
5805 | This is the graph of the @dfn{referrers} of a store item, as returned by | |
5806 | @command{guix gc --referrers} (@pxref{Invoking guix gc}). | |
5807 | ||
5808 | This relies exclusively on local information from your store. For | |
5809 | instance, let us suppose that the current Inkscape is available in 10 | |
5810 | profiles on your machine; @command{guix graph -t referrers inkscape} | |
5811 | will show a graph rooted at Inkscape and with those 10 profiles linked | |
5812 | to it. | |
5813 | ||
5814 | It can help determine what is preventing a store item from being garbage | |
5815 | collected. | |
5816 | ||
88856916 LC |
5817 | @end table |
5818 | ||
5819 | The available options are the following: | |
5820 | ||
5821 | @table @option | |
5822 | @item --type=@var{type} | |
5823 | @itemx -t @var{type} | |
5824 | Produce a graph output of @var{type}, where @var{type} must be one of | |
5825 | the values listed above. | |
5826 | ||
5827 | @item --list-types | |
5828 | List the supported graph types. | |
4c8f997a | 5829 | |
642339dc RW |
5830 | @item --backend=@var{backend} |
5831 | @itemx -b @var{backend} | |
5832 | Produce a graph using the selected @var{backend}. | |
5833 | ||
5834 | @item --list-backends | |
5835 | List the supported graph backends. | |
5836 | ||
4c8f997a LC |
5837 | @item --expression=@var{expr} |
5838 | @itemx -e @var{expr} | |
5839 | Consider the package @var{expr} evaluates to. | |
5840 | ||
5841 | This is useful to precisely refer to a package, as in this example: | |
5842 | ||
5843 | @example | |
5844 | guix graph -e '(@@@@ (gnu packages commencement) gnu-make-final)' | |
5845 | @end example | |
88856916 LC |
5846 | @end table |
5847 | ||
5848 | ||
372c4bbc DT |
5849 | @node Invoking guix environment |
5850 | @section Invoking @command{guix environment} | |
5851 | ||
f5fd4fd2 | 5852 | @cindex reproducible build environments |
fe36d84e | 5853 | @cindex development environments |
e32171ee JD |
5854 | @cindex @command{guix environment} |
5855 | @cindex environment, package build environment | |
372c4bbc DT |
5856 | The purpose of @command{guix environment} is to assist hackers in |
5857 | creating reproducible development environments without polluting their | |
5858 | package profile. The @command{guix environment} tool takes one or more | |
f97c9175 | 5859 | packages, builds all of their inputs, and creates a shell |
372c4bbc DT |
5860 | environment to use them. |
5861 | ||
5862 | The general syntax is: | |
5863 | ||
5864 | @example | |
5865 | guix environment @var{options} @var{package}@dots{} | |
5866 | @end example | |
5867 | ||
fe36d84e LC |
5868 | The following example spawns a new shell set up for the development of |
5869 | GNU@tie{}Guile: | |
372c4bbc DT |
5870 | |
5871 | @example | |
5872 | guix environment guile | |
5873 | @end example | |
5874 | ||
f97c9175 AE |
5875 | If the needed dependencies are not built yet, @command{guix environment} |
5876 | automatically builds them. The environment of the new shell is an augmented | |
372c4bbc DT |
5877 | version of the environment that @command{guix environment} was run in. |
5878 | It contains the necessary search paths for building the given package | |
5879 | added to the existing environment variables. To create a ``pure'' | |
f97c9175 | 5880 | environment, in which the original environment variables have been unset, |
50500f7c LC |
5881 | use the @code{--pure} option@footnote{Users sometimes wrongfully augment |
5882 | environment variables such as @code{PATH} in their @file{~/.bashrc} | |
5883 | file. As a consequence, when @code{guix environment} launches it, Bash | |
5884 | may read @file{~/.bashrc}, thereby introducing ``impurities'' in these | |
5885 | environment variables. It is an error to define such environment | |
5886 | variables in @file{.bashrc}; instead, they should be defined in | |
5887 | @file{.bash_profile}, which is sourced only by log-in shells. | |
5888 | @xref{Bash Startup Files,,, bash, The GNU Bash Reference Manual}, for | |
5889 | details on Bash start-up files.}. | |
372c4bbc | 5890 | |
28de8d25 LC |
5891 | @vindex GUIX_ENVIRONMENT |
5892 | @command{guix environment} defines the @code{GUIX_ENVIRONMENT} | |
20185522 LC |
5893 | variable in the shell it spawns; its value is the file name of the |
5894 | profile of this environment. This allows users to, say, define a | |
28de8d25 LC |
5895 | specific prompt for development environments in their @file{.bashrc} |
5896 | (@pxref{Bash Startup Files,,, bash, The GNU Bash Reference Manual}): | |
5897 | ||
5898 | @example | |
5899 | if [ -n "$GUIX_ENVIRONMENT" ] | |
5900 | then | |
5901 | export PS1="\u@@\h \w [dev]\$ " | |
5902 | fi | |
5903 | @end example | |
5904 | ||
20185522 LC |
5905 | @noindent |
5906 | ... or to browse the profile: | |
5907 | ||
5908 | @example | |
5909 | $ ls "$GUIX_ENVIRONMENT/bin" | |
5910 | @end example | |
5911 | ||
372c4bbc DT |
5912 | Additionally, more than one package may be specified, in which case the |
5913 | union of the inputs for the given packages are used. For example, the | |
5914 | command below spawns a shell where all of the dependencies of both Guile | |
5915 | and Emacs are available: | |
5916 | ||
5917 | @example | |
5918 | guix environment guile emacs | |
5919 | @end example | |
5920 | ||
1de2fe95 DT |
5921 | Sometimes an interactive shell session is not desired. An arbitrary |
5922 | command may be invoked by placing the @code{--} token to separate the | |
5923 | command from the rest of the arguments: | |
372c4bbc DT |
5924 | |
5925 | @example | |
1de2fe95 | 5926 | guix environment guile -- make -j4 |
372c4bbc DT |
5927 | @end example |
5928 | ||
fe36d84e LC |
5929 | In other situations, it is more convenient to specify the list of |
5930 | packages needed in the environment. For example, the following command | |
5931 | runs @command{python} from an environment containing Python@tie{}2.7 and | |
5932 | NumPy: | |
5933 | ||
5934 | @example | |
1de2fe95 | 5935 | guix environment --ad-hoc python2-numpy python-2.7 -- python |
fe36d84e LC |
5936 | @end example |
5937 | ||
cc90fbbf DT |
5938 | Furthermore, one might want the dependencies of a package and also some |
5939 | additional packages that are not build-time or runtime dependencies, but | |
5940 | are useful when developing nonetheless. Because of this, the | |
5941 | @code{--ad-hoc} flag is positional. Packages appearing before | |
5942 | @code{--ad-hoc} are interpreted as packages whose dependencies will be | |
5943 | added to the environment. Packages appearing after are interpreted as | |
5944 | packages that will be added to the environment directly. For example, | |
5945 | the following command creates a Guix development environment that | |
5946 | additionally includes Git and strace: | |
5947 | ||
5948 | @example | |
5949 | guix environment guix --ad-hoc git strace | |
5950 | @end example | |
5951 | ||
f535dcbe DT |
5952 | Sometimes it is desirable to isolate the environment as much as |
5953 | possible, for maximal purity and reproducibility. In particular, when | |
5954 | using Guix on a host distro that is not GuixSD, it is desirable to | |
5955 | prevent access to @file{/usr/bin} and other system-wide resources from | |
5956 | the development environment. For example, the following command spawns | |
5957 | a Guile REPL in a ``container'' where only the store and the current | |
5958 | working directory are mounted: | |
5959 | ||
5960 | @example | |
5961 | guix environment --ad-hoc --container guile -- guile | |
5962 | @end example | |
5963 | ||
0f252e26 | 5964 | @quotation Note |
cfd35b4e | 5965 | The @code{--container} option requires Linux-libre 3.19 or newer. |
0f252e26 DT |
5966 | @end quotation |
5967 | ||
fe36d84e | 5968 | The available options are summarized below. |
372c4bbc DT |
5969 | |
5970 | @table @code | |
5971 | @item --expression=@var{expr} | |
5972 | @itemx -e @var{expr} | |
c9c282ce DT |
5973 | Create an environment for the package or list of packages that |
5974 | @var{expr} evaluates to. | |
372c4bbc | 5975 | |
fe36d84e LC |
5976 | For example, running: |
5977 | ||
5978 | @example | |
5979 | guix environment -e '(@@ (gnu packages maths) petsc-openmpi)' | |
5980 | @end example | |
5981 | ||
5982 | starts a shell with the environment for this specific variant of the | |
5983 | PETSc package. | |
5984 | ||
c9c282ce DT |
5985 | Running: |
5986 | ||
5987 | @example | |
5c2b2f00 | 5988 | guix environment --ad-hoc -e '(@@ (gnu) %base-packages)' |
c9c282ce DT |
5989 | @end example |
5990 | ||
5991 | starts a shell with all the GuixSD base packages available. | |
5992 | ||
779aa003 DT |
5993 | The above commands only the use default output of the given packages. |
5994 | To select other outputs, two element tuples can be specified: | |
5995 | ||
5996 | @example | |
5997 | guix environment --ad-hoc -e '(list (@ (gnu packages bash) bash) "include")' | |
5998 | @end example | |
5999 | ||
372c4bbc DT |
6000 | @item --load=@var{file} |
6001 | @itemx -l @var{file} | |
c9c282ce DT |
6002 | Create an environment for the package or list of packages that the code |
6003 | within @var{file} evaluates to. | |
372c4bbc | 6004 | |
fe36d84e LC |
6005 | As an example, @var{file} might contain a definition like this |
6006 | (@pxref{Defining Packages}): | |
6007 | ||
6008 | @example | |
6009 | @verbatiminclude environment-gdb.scm | |
6010 | @end example | |
6011 | ||
a54bd6d7 DT |
6012 | @item --ad-hoc |
6013 | Include all specified packages in the resulting environment, as if an | |
6014 | @i{ad hoc} package were defined with them as inputs. This option is | |
6015 | useful for quickly creating an environment without having to write a | |
6016 | package expression to contain the desired inputs. | |
6017 | ||
6018 | For instance, the command: | |
6019 | ||
6020 | @example | |
1de2fe95 | 6021 | guix environment --ad-hoc guile guile-sdl -- guile |
a54bd6d7 DT |
6022 | @end example |
6023 | ||
6024 | runs @command{guile} in an environment where Guile and Guile-SDL are | |
6025 | available. | |
6026 | ||
417c39f1 | 6027 | Note that this example implicitly asks for the default output of |
f97c9175 | 6028 | @code{guile} and @code{guile-sdl}, but it is possible to ask for a |
417c39f1 LC |
6029 | specific output---e.g., @code{glib:bin} asks for the @code{bin} output |
6030 | of @code{glib} (@pxref{Packages with Multiple Outputs}). | |
6031 | ||
cc90fbbf DT |
6032 | This option may be composed with the default behavior of @command{guix |
6033 | environment}. Packages appearing before @code{--ad-hoc} are interpreted | |
6034 | as packages whose dependencies will be added to the environment, the | |
6035 | default behavior. Packages appearing after are interpreted as packages | |
6036 | that will be added to the environment directly. | |
6037 | ||
372c4bbc DT |
6038 | @item --pure |
6039 | Unset existing environment variables when building the new environment. | |
6040 | This has the effect of creating an environment in which search paths | |
6041 | only contain package inputs. | |
6042 | ||
6043 | @item --search-paths | |
6044 | Display the environment variable definitions that make up the | |
6045 | environment. | |
ce367ef3 LC |
6046 | |
6047 | @item --system=@var{system} | |
6048 | @itemx -s @var{system} | |
6049 | Attempt to build for @var{system}---e.g., @code{i686-linux}. | |
f535dcbe DT |
6050 | |
6051 | @item --container | |
6052 | @itemx -C | |
6053 | @cindex container | |
6054 | Run @var{command} within an isolated container. The current working | |
a01ad638 DT |
6055 | directory outside the container is mapped inside the container. |
6056 | Additionally, a dummy home directory is created that matches the current | |
6057 | user's home directory, and @file{/etc/passwd} is configured accordingly. | |
6058 | The spawned process runs as the current user outside the container, but | |
6059 | has root privileges in the context of the container. | |
f535dcbe DT |
6060 | |
6061 | @item --network | |
6062 | @itemx -N | |
6063 | For containers, share the network namespace with the host system. | |
6064 | Containers created without this flag only have access to the loopback | |
6065 | device. | |
6066 | ||
6067 | @item --expose=@var{source}[=@var{target}] | |
6068 | For containers, expose the file system @var{source} from the host system | |
6069 | as the read-only file system @var{target} within the container. If | |
6070 | @var{target} is not specified, @var{source} is used as the target mount | |
6071 | point in the container. | |
6072 | ||
6073 | The example below spawns a Guile REPL in a container in which the user's | |
6074 | home directory is accessible read-only via the @file{/exchange} | |
6075 | directory: | |
6076 | ||
6077 | @example | |
6078 | guix environment --container --expose=$HOME=/exchange guile -- guile | |
6079 | @end example | |
6080 | ||
5c2b2f00 | 6081 | @item --share=@var{source}[=@var{target}] |
f535dcbe DT |
6082 | For containers, share the file system @var{source} from the host system |
6083 | as the writable file system @var{target} within the container. If | |
6084 | @var{target} is not specified, @var{source} is used as the target mount | |
6085 | point in the container. | |
6086 | ||
6087 | The example below spawns a Guile REPL in a container in which the user's | |
6088 | home directory is accessible for both reading and writing via the | |
6089 | @file{/exchange} directory: | |
6090 | ||
6091 | @example | |
6092 | guix environment --container --share=$HOME=/exchange guile -- guile | |
6093 | @end example | |
372c4bbc DT |
6094 | @end table |
6095 | ||
6096 | It also supports all of the common build options that @command{guix | |
ccd7158d | 6097 | build} supports (@pxref{Common Build Options}). |
372c4bbc | 6098 | |
aff8ce7c DT |
6099 | @node Invoking guix publish |
6100 | @section Invoking @command{guix publish} | |
6101 | ||
e32171ee | 6102 | @cindex @command{guix publish} |
aff8ce7c | 6103 | The purpose of @command{guix publish} is to enable users to easily share |
f97c9175 | 6104 | their store with others, who can then use it as a substitute server |
8ce229fc LC |
6105 | (@pxref{Substitutes}). |
6106 | ||
6107 | When @command{guix publish} runs, it spawns an HTTP server which allows | |
6108 | anyone with network access to obtain substitutes from it. This means | |
6109 | that any machine running Guix can also act as if it were a build farm, | |
6110 | since the HTTP interface is compatible with Hydra, the software behind | |
6111 | the @code{hydra.gnu.org} build farm. | |
aff8ce7c DT |
6112 | |
6113 | For security, each substitute is signed, allowing recipients to check | |
6114 | their authenticity and integrity (@pxref{Substitutes}). Because | |
f97c9175 | 6115 | @command{guix publish} uses the signing key of the system, which is only |
5463fe51 LC |
6116 | readable by the system administrator, it must be started as root; the |
6117 | @code{--user} option makes it drop root privileges early on. | |
aff8ce7c | 6118 | |
b18812b6 LC |
6119 | The signing key pair must be generated before @command{guix publish} is |
6120 | launched, using @command{guix archive --generate-key} (@pxref{Invoking | |
6121 | guix archive}). | |
6122 | ||
aff8ce7c DT |
6123 | The general syntax is: |
6124 | ||
6125 | @example | |
6126 | guix publish @var{options}@dots{} | |
6127 | @end example | |
6128 | ||
6129 | Running @command{guix publish} without any additional arguments will | |
6130 | spawn an HTTP server on port 8080: | |
6131 | ||
6132 | @example | |
6133 | guix publish | |
6134 | @end example | |
6135 | ||
6136 | Once a publishing server has been authorized (@pxref{Invoking guix | |
6137 | archive}), the daemon may download substitutes from it: | |
6138 | ||
6139 | @example | |
6140 | guix-daemon --substitute-urls=http://example.org:8080 | |
6141 | @end example | |
6142 | ||
ff6638d1 LC |
6143 | As a bonus, @command{guix publish} also serves as a content-addressed |
6144 | mirror for source files referenced in @code{origin} records | |
6145 | (@pxref{origin Reference}). For instance, assuming @command{guix | |
6146 | publish} is running on @code{example.org}, the following URL returns the | |
6147 | raw @file{hello-2.10.tar.gz} file with the given SHA256 hash | |
6148 | (represented in @code{nix-base32} format, @pxref{Invoking guix hash}): | |
6149 | ||
6150 | @example | |
6151 | http://example.org/file/hello-2.10.tar.gz/sha256/0ssi1@dots{}ndq1i | |
6152 | @end example | |
6153 | ||
6154 | Obviously, these URLs only work for files that are in the store; in | |
6155 | other cases, they return 404 (``Not Found''). | |
6156 | ||
aff8ce7c DT |
6157 | The following options are available: |
6158 | ||
6159 | @table @code | |
6160 | @item --port=@var{port} | |
6161 | @itemx -p @var{port} | |
6162 | Listen for HTTP requests on @var{port}. | |
6163 | ||
9e2292ef LC |
6164 | @item --listen=@var{host} |
6165 | Listen on the network interface for @var{host}. The default is to | |
6166 | accept connections from any interface. | |
6167 | ||
5463fe51 LC |
6168 | @item --user=@var{user} |
6169 | @itemx -u @var{user} | |
6170 | Change privileges to @var{user} as soon as possible---i.e., once the | |
6171 | server socket is open and the signing key has been read. | |
6172 | ||
4a1fc562 LC |
6173 | @item --compression[=@var{level}] |
6174 | @itemx -C [@var{level}] | |
6175 | Compress data using the given @var{level}. When @var{level} is zero, | |
6176 | disable compression. The range 1 to 9 corresponds to different gzip | |
6177 | compression levels: 1 is the fastest, and 9 is the best (CPU-intensive). | |
6178 | The default is 3. | |
6179 | ||
4591c02e | 6180 | Compression occurs on the fly and the compressed streams are not |
4a1fc562 LC |
6181 | cached. Thus, to reduce load on the machine that runs @command{guix |
6182 | publish}, it may be a good idea to choose a low compression level, or to | |
6183 | run @command{guix publish} behind a caching proxy. | |
6184 | ||
e4c7a5f7 LC |
6185 | @item --ttl=@var{ttl} |
6186 | Produce @code{Cache-Control} HTTP headers that advertise a time-to-live | |
6187 | (TTL) of @var{ttl}. @var{ttl} must denote a duration: @code{5d} means 5 | |
6188 | days, @code{1m} means 1 month, and so on. | |
6189 | ||
6190 | This allows the user's Guix to keep substitute information in cache for | |
6191 | @var{ttl}. However, note that @code{guix publish} does not itself | |
6192 | guarantee that the store items it provides will indeed remain available | |
6193 | for as long as @var{ttl}. | |
6194 | ||
aff8ce7c DT |
6195 | @item --repl[=@var{port}] |
6196 | @itemx -r [@var{port}] | |
6197 | Spawn a Guile REPL server (@pxref{REPL Servers,,, guile, GNU Guile | |
8ce229fc LC |
6198 | Reference Manual}) on @var{port} (37146 by default). This is used |
6199 | primarily for debugging a running @command{guix publish} server. | |
aff8ce7c DT |
6200 | @end table |
6201 | ||
1c52181f LC |
6202 | Enabling @command{guix publish} on a GuixSD system is a one-liner: just |
6203 | add a call to @code{guix-publish-service} in the @code{services} field | |
6204 | of the @code{operating-system} declaration (@pxref{guix-publish-service, | |
6205 | @code{guix-publish-service}}). | |
6206 | ||
332d7903 HG |
6207 | If you are instead running Guix on a ``foreign distro'', follow these |
6208 | instructions:” | |
6209 | ||
6210 | @itemize | |
6211 | @item | |
6212 | If your host distro uses the systemd init system: | |
6213 | ||
6214 | @example | |
6215 | # ln -s ~root/.guix-profile/lib/systemd/system/guix-publish.service \ | |
6216 | /etc/systemd/system/ | |
6217 | # systemctl start guix-publish && systemctl enable guix-publish | |
6218 | @end example | |
6219 | ||
6220 | @item | |
6221 | If your host distro uses the Upstart init system: | |
6222 | ||
6223 | @example | |
6224 | # ln -s ~root/.guix-profile/lib/upstart/system/guix-publish.conf /etc/init/ | |
6225 | # start guix-publish | |
6226 | @end example | |
6227 | ||
6228 | @item | |
6229 | Otherwise, proceed similarly with your distro's init system. | |
6230 | @end itemize | |
d23c20f1 LC |
6231 | |
6232 | @node Invoking guix challenge | |
6233 | @section Invoking @command{guix challenge} | |
6234 | ||
6235 | @cindex reproducible builds | |
6236 | @cindex verifiable builds | |
e32171ee JD |
6237 | @cindex @command{guix challenge} |
6238 | @cindex challenge | |
d23c20f1 | 6239 | Do the binaries provided by this server really correspond to the source |
f97c9175 | 6240 | code it claims to build? Is a package build process deterministic? |
d23c20f1 LC |
6241 | These are the questions the @command{guix challenge} command attempts to |
6242 | answer. | |
6243 | ||
6244 | The former is obviously an important question: Before using a substitute | |
f97c9175 | 6245 | server (@pxref{Substitutes}), one had better @emph{verify} that it |
d23c20f1 LC |
6246 | provides the right binaries, and thus @emph{challenge} it. The latter |
6247 | is what enables the former: If package builds are deterministic, then | |
6248 | independent builds of the package should yield the exact same result, | |
6249 | bit for bit; if a server provides a binary different from the one | |
6250 | obtained locally, it may be either corrupt or malicious. | |
6251 | ||
6252 | We know that the hash that shows up in @file{/gnu/store} file names is | |
6253 | the hash of all the inputs of the process that built the file or | |
6254 | directory---compilers, libraries, build scripts, | |
6255 | etc. (@pxref{Introduction}). Assuming deterministic build processes, | |
6256 | one store file name should map to exactly one build output. | |
6257 | @command{guix challenge} checks whether there is, indeed, a single | |
6258 | mapping by comparing the build outputs of several independent builds of | |
6259 | any given store item. | |
6260 | ||
f97c9175 | 6261 | The command output looks like this: |
d23c20f1 LC |
6262 | |
6263 | @smallexample | |
ddbc7f7d LC |
6264 | $ guix challenge --substitute-urls="https://hydra.gnu.org https://guix.example.org" |
6265 | updating list of substitutes from 'https://hydra.gnu.org'... 100.0% | |
6266 | updating list of substitutes from 'https://guix.example.org'... 100.0% | |
d23c20f1 LC |
6267 | /gnu/store/@dots{}-openssl-1.0.2d contents differ: |
6268 | local hash: 0725l22r5jnzazaacncwsvp9kgf42266ayyp814v7djxs7nk963q | |
ddbc7f7d LC |
6269 | https://hydra.gnu.org/nar/@dots{}-openssl-1.0.2d: 0725l22r5jnzazaacncwsvp9kgf42266ayyp814v7djxs7nk963q |
6270 | https://guix.example.org/nar/@dots{}-openssl-1.0.2d: 1zy4fmaaqcnjrzzajkdn3f5gmjk754b43qkq47llbyak9z0qjyim | |
d23c20f1 LC |
6271 | /gnu/store/@dots{}-git-2.5.0 contents differ: |
6272 | local hash: 00p3bmryhjxrhpn2gxs2fy0a15lnip05l97205pgbk5ra395hyha | |
ddbc7f7d LC |
6273 | https://hydra.gnu.org/nar/@dots{}-git-2.5.0: 069nb85bv4d4a6slrwjdy8v1cn4cwspm3kdbmyb81d6zckj3nq9f |
6274 | https://guix.example.org/nar/@dots{}-git-2.5.0: 0mdqa9w1p6cmli6976v4wi0sw9r4p5prkj7lzfd1877wk11c9c73 | |
d23c20f1 LC |
6275 | /gnu/store/@dots{}-pius-2.1.1 contents differ: |
6276 | local hash: 0k4v3m9z1zp8xzzizb7d8kjj72f9172xv078sq4wl73vnq9ig3ax | |
ddbc7f7d LC |
6277 | https://hydra.gnu.org/nar/@dots{}-pius-2.1.1: 0k4v3m9z1zp8xzzizb7d8kjj72f9172xv078sq4wl73vnq9ig3ax |
6278 | https://guix.example.org/nar/@dots{}-pius-2.1.1: 1cy25x1a4fzq5rk0pmvc8xhwyffnqz95h2bpvqsz2mpvlbccy0gs | |
d23c20f1 LC |
6279 | @end smallexample |
6280 | ||
6281 | @noindent | |
6282 | In this example, @command{guix challenge} first scans the store to | |
6283 | determine the set of locally-built derivations---as opposed to store | |
6284 | items that were downloaded from a substitute server---and then queries | |
6285 | all the substitute servers. It then reports those store items for which | |
6286 | the servers obtained a result different from the local build. | |
6287 | ||
6288 | @cindex non-determinism, in package builds | |
6289 | As an example, @code{guix.example.org} always gets a different answer. | |
6290 | Conversely, @code{hydra.gnu.org} agrees with local builds, except in the | |
6291 | case of Git. This might indicate that the build process of Git is | |
6292 | non-deterministic, meaning that its output varies as a function of | |
6293 | various things that Guix does not fully control, in spite of building | |
6294 | packages in isolated environments (@pxref{Features}). Most common | |
6295 | sources of non-determinism include the addition of timestamps in build | |
6296 | results, the inclusion of random numbers, and directory listings sorted | |
a70a5004 | 6297 | by inode number. See @uref{https://reproducible-builds.org/docs/}, for |
d23c20f1 LC |
6298 | more information. |
6299 | ||
f97c9175 | 6300 | To find out what is wrong with this Git binary, we can do something along |
d23c20f1 LC |
6301 | these lines (@pxref{Invoking guix archive}): |
6302 | ||
6303 | @example | |
ddbc7f7d | 6304 | $ wget -q -O - https://hydra.gnu.org/nar/@dots{}-git-2.5.0 \ |
d23c20f1 | 6305 | | guix archive -x /tmp/git |
043f4698 | 6306 | $ diff -ur --no-dereference /gnu/store/@dots{}-git.2.5.0 /tmp/git |
d23c20f1 LC |
6307 | @end example |
6308 | ||
6309 | This command shows the difference between the files resulting from the | |
6310 | local build, and the files resulting from the build on | |
6311 | @code{hydra.gnu.org} (@pxref{Overview, Comparing and Merging Files,, | |
6312 | diffutils, Comparing and Merging Files}). The @command{diff} command | |
6313 | works great for text files. When binary files differ, a better option | |
ddbc7f7d | 6314 | is @uref{https://diffoscope.org/, Diffoscope}, a tool that helps |
d23c20f1 LC |
6315 | visualize differences for all kinds of files. |
6316 | ||
f97c9175 | 6317 | Once you have done that work, you can tell whether the differences are due |
d23c20f1 LC |
6318 | to a non-deterministic build process or to a malicious server. We try |
6319 | hard to remove sources of non-determinism in packages to make it easier | |
f97c9175 AE |
6320 | to verify substitutes, but of course, this is a process that |
6321 | involves not just Guix, but a large part of the free software community. | |
d23c20f1 LC |
6322 | In the meantime, @command{guix challenge} is one tool to help address |
6323 | the problem. | |
6324 | ||
6325 | If you are writing packages for Guix, you are encouraged to check | |
6326 | whether @code{hydra.gnu.org} and other substitute servers obtain the | |
6327 | same build result as you did with: | |
6328 | ||
6329 | @example | |
6330 | $ guix challenge @var{package} | |
6331 | @end example | |
6332 | ||
6333 | @noindent | |
f97c9175 | 6334 | where @var{package} is a package specification such as |
7cffaeb6 | 6335 | @code{guile@@2.0} or @code{glibc:debug}. |
d23c20f1 LC |
6336 | |
6337 | The general syntax is: | |
6338 | ||
6339 | @example | |
6340 | guix challenge @var{options} [@var{packages}@dots{}] | |
6341 | @end example | |
6342 | ||
7cffaeb6 LC |
6343 | When a difference is found between the hash of a locally-built item and |
6344 | that of a server-provided substitute, or among substitutes provided by | |
6345 | different servers, the command displays it as in the example above and | |
a17417a8 LC |
6346 | its exit code is 2 (other non-zero exit codes denote other kinds of |
6347 | errors.) | |
7cffaeb6 | 6348 | |
d23c20f1 LC |
6349 | The one option that matters is: |
6350 | ||
6351 | @table @code | |
6352 | ||
6353 | @item --substitute-urls=@var{urls} | |
6354 | Consider @var{urls} the whitespace-separated list of substitute source | |
6355 | URLs to compare to. | |
6356 | ||
6357 | @end table | |
6358 | ||
6359 | ||
32efa254 DT |
6360 | @node Invoking guix container |
6361 | @section Invoking @command{guix container} | |
6362 | @cindex container | |
e32171ee | 6363 | @cindex @command{guix container} |
32efa254 DT |
6364 | @quotation Note |
6365 | As of version @value{VERSION}, this tool is experimental. The interface | |
6366 | is subject to radical change in the future. | |
6367 | @end quotation | |
6368 | ||
6369 | The purpose of @command{guix container} is to manipulate processes | |
6370 | running within an isolated environment, commonly known as a | |
46c36586 | 6371 | ``container'', typically created by the @command{guix environment} |
32efa254 DT |
6372 | (@pxref{Invoking guix environment}) and @command{guix system container} |
6373 | (@pxref{Invoking guix system}) commands. | |
6374 | ||
6375 | The general syntax is: | |
6376 | ||
6377 | @example | |
6378 | guix container @var{action} @var{options}@dots{} | |
6379 | @end example | |
6380 | ||
6381 | @var{action} specifies the operation to perform with a container, and | |
6382 | @var{options} specifies the context-specific arguments for the action. | |
6383 | ||
6384 | The following actions are available: | |
6385 | ||
6386 | @table @code | |
6387 | @item exec | |
6388 | Execute a command within the context of a running container. | |
6389 | ||
6390 | The syntax is: | |
6391 | ||
6392 | @example | |
6393 | guix container exec @var{pid} @var{program} @var{arguments}@dots{} | |
6394 | @end example | |
6395 | ||
6396 | @var{pid} specifies the process ID of the running container. | |
f97c9175 AE |
6397 | @var{program} specifies an executable file name within the root file |
6398 | system of the container. @var{arguments} are the additional options that | |
6399 | will be passed to @var{program}. | |
32efa254 DT |
6400 | |
6401 | The following command launches an interactive login shell inside a | |
6402 | GuixSD container, started by @command{guix system container}, and whose | |
6403 | process ID is 9001: | |
6404 | ||
6405 | @example | |
6406 | guix container exec 9001 /run/current-system/profile/bin/bash --login | |
6407 | @end example | |
6408 | ||
6409 | Note that the @var{pid} cannot be the parent process of a container. It | |
f97c9175 | 6410 | must be PID 1 of the container or one of its child processes. |
32efa254 DT |
6411 | |
6412 | @end table | |
6413 | ||
a1ba8475 LC |
6414 | @c ********************************************************************* |
6415 | @node GNU Distribution | |
6416 | @chapter GNU Distribution | |
6417 | ||
3ca2731c | 6418 | @cindex Guix System Distribution |
4705641f | 6419 | @cindex GuixSD |
3ca2731c LC |
6420 | Guix comes with a distribution of the GNU system consisting entirely of |
6421 | free software@footnote{The term ``free'' here refers to the | |
a1ba8475 | 6422 | @url{http://www.gnu.org/philosophy/free-sw.html,freedom provided to |
3ca2731c | 6423 | users of that software}.}. The |
35ed9306 LC |
6424 | distribution can be installed on its own (@pxref{System Installation}), |
6425 | but it is also possible to install Guix as a package manager on top of | |
6426 | an installed GNU/Linux system (@pxref{Installation}). To distinguish | |
3ca2731c | 6427 | between the two, we refer to the standalone distribution as the Guix |
4705641f | 6428 | System Distribution, or GuixSD. |
35ed9306 LC |
6429 | |
6430 | The distribution provides core GNU packages such as GNU libc, GCC, and | |
6431 | Binutils, as well as many GNU and non-GNU applications. The complete | |
6432 | list of available packages can be browsed | |
093ae1be | 6433 | @url{http://www.gnu.org/software/guix/packages,on-line} or by |
d03bb653 | 6434 | running @command{guix package} (@pxref{Invoking guix package}): |
a1ba8475 LC |
6435 | |
6436 | @example | |
e49951eb | 6437 | guix package --list-available |
a1ba8475 LC |
6438 | @end example |
6439 | ||
f97c9175 | 6440 | Our goal is to provide a practical 100% free software distribution of |
401c53c4 LC |
6441 | Linux-based and other variants of GNU, with a focus on the promotion and |
6442 | tight integration of GNU components, and an emphasis on programs and | |
6443 | tools that help users exert that freedom. | |
6444 | ||
3ca2731c | 6445 | Packages are currently available on the following platforms: |
c320011d LC |
6446 | |
6447 | @table @code | |
6448 | ||
6449 | @item x86_64-linux | |
6450 | Intel/AMD @code{x86_64} architecture, Linux-Libre kernel; | |
6451 | ||
6452 | @item i686-linux | |
6453 | Intel 32-bit architecture (IA32), Linux-Libre kernel; | |
6454 | ||
aa1e1947 | 6455 | @item armhf-linux |
aa725117 | 6456 | ARMv7-A architecture with hard float, Thumb-2 and NEON, |
f97c9175 AE |
6457 | using the EABI hard-float application binary interface (ABI), |
6458 | and Linux-Libre kernel. | |
aa1e1947 | 6459 | |
c320011d LC |
6460 | @item mips64el-linux |
6461 | little-endian 64-bit MIPS processors, specifically the Loongson series, | |
f97c9175 | 6462 | n32 ABI, and Linux-Libre kernel. |
c320011d LC |
6463 | |
6464 | @end table | |
6465 | ||
4705641f | 6466 | GuixSD itself is currently only available on @code{i686} and @code{x86_64}. |
3ca2731c | 6467 | |
c320011d LC |
6468 | @noindent |
6469 | For information on porting to other architectures or kernels, | |
f97c9175 | 6470 | @pxref{Porting}. |
c320011d | 6471 | |
401c53c4 | 6472 | @menu |
5af6de3e | 6473 | * System Installation:: Installing the whole operating system. |
35ed9306 | 6474 | * System Configuration:: Configuring the operating system. |
91ef73d4 | 6475 | * Installing Debugging Files:: Feeding the debugger. |
05962f29 | 6476 | * Security Updates:: Deploying security fixes quickly. |
401c53c4 | 6477 | * Package Modules:: Packages from the programmer's viewpoint. |
da7cabd4 | 6478 | * Packaging Guidelines:: Growing the distribution. |
401c53c4 | 6479 | * Bootstrapping:: GNU/Linux built from scratch. |
8b315a6d | 6480 | * Porting:: Targeting another platform or kernel. |
401c53c4 LC |
6481 | @end menu |
6482 | ||
6483 | Building this distribution is a cooperative effort, and you are invited | |
081145cf | 6484 | to join! @xref{Contributing}, for information about how you can help. |
401c53c4 | 6485 | |
5af6de3e LC |
6486 | @node System Installation |
6487 | @section System Installation | |
6488 | ||
e32171ee | 6489 | @cindex installing GuixSD |
3ca2731c | 6490 | @cindex Guix System Distribution |
c8b54374 | 6491 | This section explains how to install the Guix System Distribution (GuixSD) |
3ca2731c | 6492 | on a machine. The Guix package manager can |
35ed9306 LC |
6493 | also be installed on top of a running GNU/Linux system, |
6494 | @pxref{Installation}. | |
5af6de3e LC |
6495 | |
6496 | @ifinfo | |
9c18cf9b | 6497 | @quotation Note |
5af6de3e LC |
6498 | @c This paragraph is for people reading this from tty2 of the |
6499 | @c installation image. | |
1068f26b | 6500 | You are reading this documentation with an Info reader. For details on |
5af6de3e | 6501 | how to use it, hit the @key{RET} key (``return'' or ``enter'') on the |
de341e7c LC |
6502 | link that follows: @pxref{Top, Info reader,, info-stnd, Stand-alone GNU |
6503 | Info}. Hit @kbd{l} afterwards to come back here. | |
9c18cf9b LC |
6504 | |
6505 | Alternately, run @command{info info} in another tty to keep the manual | |
6506 | available. | |
6507 | @end quotation | |
5af6de3e LC |
6508 | @end ifinfo |
6509 | ||
dedb8d5e | 6510 | @menu |
e3009f60 LC |
6511 | * Limitations:: What you can expect. |
6512 | * Hardware Considerations:: Supported hardware. | |
6513 | * USB Stick Installation:: Preparing the installation medium. | |
6514 | * Preparing for Installation:: Networking, partitioning, etc. | |
6515 | * Proceeding with the Installation:: The real thing. | |
c8b54374 | 6516 | * Installing GuixSD in a VM:: GuixSD playground. |
e3009f60 | 6517 | * Building the Installation Image:: How this comes to be. |
dedb8d5e LC |
6518 | @end menu |
6519 | ||
6520 | @node Limitations | |
8aaaae38 LC |
6521 | @subsection Limitations |
6522 | ||
4705641f | 6523 | As of version @value{VERSION}, the Guix System Distribution (GuixSD) is |
3ca2731c | 6524 | not production-ready. It may contain bugs and lack important |
8aaaae38 LC |
6525 | features. Thus, if you are looking for a stable production system that |
6526 | respects your freedom as a computer user, a good solution at this point | |
6527 | is to consider @url{http://www.gnu.org/distros/free-distros.html, one of | |
f97c9175 | 6528 | the more established GNU/Linux distributions}. We hope you can soon switch |
4705641f | 6529 | to the GuixSD without fear, of course. In the meantime, you can |
8aaaae38 LC |
6530 | also keep using your distribution and try out the package manager on top |
6531 | of it (@pxref{Installation}). | |
6532 | ||
6533 | Before you proceed with the installation, be aware of the following | |
6534 | noteworthy limitations applicable to version @value{VERSION}: | |
6535 | ||
6536 | @itemize | |
6537 | @item | |
6538 | The installation process does not include a graphical user interface and | |
6539 | requires familiarity with GNU/Linux (see the following subsections to | |
6540 | get a feel of what that means.) | |
6541 | ||
8aaaae38 | 6542 | @item |
dbcb0ab1 | 6543 | Support for the Logical Volume Manager (LVM) is missing. |
8aaaae38 LC |
6544 | |
6545 | @item | |
6546 | Few system services are currently supported out-of-the-box | |
6547 | (@pxref{Services}). | |
6548 | ||
6549 | @item | |
29e53b95 | 6550 | More than 4,000 packages are available, but you may |
8aaaae38 | 6551 | occasionally find that a useful package is missing. |
5fe01c2d LC |
6552 | |
6553 | @item | |
6554 | GNOME, Xfce, and Enlightenment are available (@pxref{Desktop Services}), | |
6555 | as well as a number of X11 window managers. However, some graphical | |
6556 | applications may be missing, as well as KDE. | |
8aaaae38 LC |
6557 | @end itemize |
6558 | ||
f97c9175 AE |
6559 | You have been warned! But more than a disclaimer, this is an invitation |
6560 | to report issues (and success stories!), and to join us in improving it. | |
8aaaae38 | 6561 | @xref{Contributing}, for more info. |
5af6de3e | 6562 | |
e3009f60 LC |
6563 | |
6564 | @node Hardware Considerations | |
6565 | @subsection Hardware Considerations | |
6566 | ||
6567 | @cindex hardware support on GuixSD | |
6568 | GNU@tie{}GuixSD focuses on respecting the user's computing freedom. It | |
6569 | builds around the kernel Linux-libre, which means that only hardware for | |
e0b3f97e | 6570 | which free software drivers and firmware exist is supported. Nowadays, |
e3009f60 LC |
6571 | a wide range of off-the-shelf hardware is supported on |
6572 | GNU/Linux-libre---from keyboards to graphics cards to scanners and | |
6573 | Ethernet controllers. Unfortunately, there are still areas where | |
6574 | hardware vendors deny users control over their own computing, and such | |
6575 | hardware is not supported on GuixSD. | |
6576 | ||
6577 | @cindex WiFi, hardware support | |
e0b3f97e | 6578 | One of the main areas where free drivers or firmware are lacking is WiFi |
e3009f60 LC |
6579 | devices. WiFi devices known to work include those using Atheros chips |
6580 | (AR9271 and AR7010), which corresponds to the @code{ath9k} Linux-libre | |
52db41af EB |
6581 | driver, and those using Broadcom/AirForce chips (BCM43xx with |
6582 | Wireless-Core Revision 5), which corresponds to the @code{b43-open} | |
6583 | Linux-libre driver. Free firmware exists for both and is available | |
e3009f60 LC |
6584 | out-of-the-box on GuixSD, as part of @var{%base-firmware} |
6585 | (@pxref{operating-system Reference, @code{firmware}}). | |
6586 | ||
6587 | @cindex RYF, Respects Your Freedom | |
6588 | The @uref{https://www.fsf.org/, Free Software Foundation} runs | |
e0b3f97e | 6589 | @uref{https://www.fsf.org/ryf, @dfn{Respects Your Freedom}} (RYF), a |
e3009f60 LC |
6590 | certification program for hardware products that respect your freedom |
6591 | and your privacy and ensure that you have control over your device. We | |
e0b3f97e | 6592 | encourage you to check the list of RYF-certified devices. |
e3009f60 LC |
6593 | |
6594 | Another useful resource is the @uref{https://www.h-node.org/, H-Node} | |
6595 | web site. It contains a catalog of hardware devices with information | |
6596 | about their support in GNU/Linux. | |
6597 | ||
6598 | ||
dedb8d5e | 6599 | @node USB Stick Installation |
5af6de3e LC |
6600 | @subsection USB Stick Installation |
6601 | ||
6602 | An installation image for USB sticks can be downloaded from | |
4705641f | 6603 | @indicateurl{ftp://alpha.gnu.org/gnu/guix/guixsd-usb-install-@value{VERSION}.@var{system}.xz}, |
5af6de3e LC |
6604 | where @var{system} is one of: |
6605 | ||
6606 | @table @code | |
6607 | @item x86_64-linux | |
6608 | for a GNU/Linux system on Intel/AMD-compatible 64-bit CPUs; | |
6609 | ||
6610 | @item i686-linux | |
6611 | for a 32-bit GNU/Linux system on Intel-compatible CPUs. | |
6612 | @end table | |
6613 | ||
debc6360 LC |
6614 | @c start duplication of authentication part from ``Binary Installation'' |
6615 | Make sure to download the associated @file{.sig} file and to verify the | |
6616 | authenticity of the image against it, along these lines: | |
6617 | ||
6618 | @example | |
6619 | $ wget ftp://alpha.gnu.org/gnu/guix/guixsd-usb-install-@value{VERSION}.@var{system}.xz.sig | |
6620 | $ gpg --verify guixsd-usb-install-@value{VERSION}.@var{system}.xz.sig | |
6621 | @end example | |
6622 | ||
6623 | If that command fails because you do not have the required public key, | |
6624 | then run this command to import it: | |
6625 | ||
6626 | @example | |
6627 | $ gpg --keyserver pgp.mit.edu --recv-keys @value{OPENPGP-SIGNING-KEY-ID} | |
6628 | @end example | |
6629 | ||
6630 | @noindent | |
6631 | and rerun the @code{gpg --verify} command. | |
6632 | @c end duplication | |
6633 | ||
5af6de3e LC |
6634 | This image contains a single partition with the tools necessary for an |
6635 | installation. It is meant to be copied @emph{as is} to a large-enough | |
6636 | USB stick. | |
6637 | ||
6638 | To copy the image to a USB stick, follow these steps: | |
6639 | ||
6640 | @enumerate | |
6641 | @item | |
6642 | Decompress the image using the @command{xz} command: | |
6643 | ||
6644 | @example | |
4705641f | 6645 | xz -d guixsd-usb-install-@value{VERSION}.@var{system}.xz |
5af6de3e LC |
6646 | @end example |
6647 | ||
6648 | @item | |
f97c9175 AE |
6649 | Insert a USB stick of 1@tie{}GiB or more into your machine, and determine |
6650 | its device name. Assuming that the USB stick is known as @file{/dev/sdX}, | |
5af6de3e LC |
6651 | copy the image with: |
6652 | ||
6653 | @example | |
4705641f | 6654 | dd if=guixsd-usb-install-@value{VERSION}.x86_64 of=/dev/sdX |
5af6de3e LC |
6655 | @end example |
6656 | ||
6657 | Access to @file{/dev/sdX} usually requires root privileges. | |
6658 | @end enumerate | |
6659 | ||
6660 | Once this is done, you should be able to reboot the system and boot from | |
6661 | the USB stick. The latter usually requires you to get in the BIOS' boot | |
6662 | menu, where you can choose to boot from the USB stick. | |
6663 | ||
c8b54374 VL |
6664 | @xref{Installing GuixSD in a VM}, if, instead, you would like to install |
6665 | GuixSD in a virtual machine (VM). | |
6666 | ||
dedb8d5e | 6667 | @node Preparing for Installation |
5af6de3e LC |
6668 | @subsection Preparing for Installation |
6669 | ||
6670 | Once you have successfully booted the image on the USB stick, you should | |
6671 | end up with a root prompt. Several console TTYs are configured and can | |
6672 | be used to run commands as root. TTY2 shows this documentation, | |
de341e7c LC |
6673 | browsable using the Info reader commands (@pxref{Top,,, info-stnd, |
6674 | Stand-alone GNU Info}). The installation system runs the GPM mouse | |
6675 | daemon, which allows you to select text with the left mouse button and | |
6676 | to paste it with the middle button. | |
5af6de3e | 6677 | |
ff925d37 LC |
6678 | @quotation Note |
6679 | Installation requires access to the Internet so that any missing | |
6680 | dependencies of your system configuration can be downloaded. See the | |
6681 | ``Networking'' section below. | |
6682 | @end quotation | |
6683 | ||
0e69cf67 LC |
6684 | The installation system includes many common tools needed for this task. |
6685 | But it is also a full-blown GuixSD system, which means that you can | |
6686 | install additional packages, should you need it, using @command{guix | |
6687 | package} (@pxref{Invoking guix package}). | |
6688 | ||
dedb8d5e | 6689 | @subsubsection Keyboard Layout |
5af6de3e | 6690 | |
dedb8d5e LC |
6691 | @cindex keyboard layout |
6692 | The installation image uses the US qwerty keyboard layout. If you want | |
6693 | to change it, you can use the @command{loadkeys} command. For example, | |
6694 | the following command selects the Dvorak keyboard layout: | |
5af6de3e | 6695 | |
dedb8d5e LC |
6696 | @example |
6697 | loadkeys dvorak | |
6698 | @end example | |
6699 | ||
6700 | See the files under @file{/run/current-system/profile/share/keymaps} for | |
6701 | a list of available keyboard layouts. Run @command{man loadkeys} for | |
6702 | more information. | |
6703 | ||
6704 | @subsubsection Networking | |
6705 | ||
6706 | Run the following command see what your network interfaces are called: | |
235cba85 LC |
6707 | |
6708 | @example | |
dedb8d5e | 6709 | ifconfig -a |
235cba85 LC |
6710 | @end example |
6711 | ||
1713c37f LC |
6712 | @noindent |
6713 | @dots{} or, using the GNU/Linux-specific @command{ip} command: | |
6714 | ||
6715 | @example | |
6716 | ip a | |
6717 | @end example | |
6718 | ||
95c559c1 | 6719 | @c http://cgit.freedesktop.org/systemd/systemd/tree/src/udev/udev-builtin-net_id.c#n20 |
dedb8d5e LC |
6720 | Wired interfaces have a name starting with @samp{e}; for example, the |
6721 | interface corresponding to the first on-board Ethernet controller is | |
6722 | called @samp{eno1}. Wireless interfaces have a name starting with | |
6723 | @samp{w}, like @samp{w1p2s0}. | |
6724 | ||
6725 | @table @asis | |
6726 | @item Wired connection | |
6727 | To configure a wired network run the following command, substituting | |
6728 | @var{interface} with the name of the wired interface you want to use. | |
6729 | ||
6730 | @example | |
6731 | ifconfig @var{interface} up | |
6732 | @end example | |
6733 | ||
6734 | @item Wireless connection | |
e32171ee JD |
6735 | @cindex wireless |
6736 | @cindex WiFi | |
dedb8d5e LC |
6737 | To configure wireless networking, you can create a configuration file |
6738 | for the @command{wpa_supplicant} configuration tool (its location is not | |
6739 | important) using one of the available text editors such as | |
6740 | @command{zile}: | |
6741 | ||
6742 | @example | |
6743 | zile wpa_supplicant.conf | |
6744 | @end example | |
6745 | ||
6746 | As an example, the following stanza can go to this file and will work | |
6747 | for many wireless networks, provided you give the actual SSID and | |
6748 | passphrase for the network you are connecting to: | |
6749 | ||
6750 | @example | |
6751 | network=@{ | |
ae768308 | 6752 | ssid="@var{my-ssid}" |
dedb8d5e LC |
6753 | key_mgmt=WPA-PSK |
6754 | psk="the network's secret passphrase" | |
6755 | @} | |
6756 | @end example | |
6757 | ||
6758 | Start the wireless service and run it in the background with the | |
6759 | following command (substitute @var{interface} with the name of the | |
6760 | network interface you want to use): | |
6761 | ||
6762 | @example | |
6763 | wpa_supplicant -c wpa_supplicant.conf -i @var{interface} -B | |
6764 | @end example | |
6765 | ||
641d0518 | 6766 | Run @command{man wpa_supplicant} for more information. |
dedb8d5e LC |
6767 | @end table |
6768 | ||
e32171ee | 6769 | @cindex DHCP |
dedb8d5e LC |
6770 | At this point, you need to acquire an IP address. On a network where IP |
6771 | addresses are automatically assigned @i{via} DHCP, you can run: | |
6772 | ||
6773 | @example | |
15650ac2 | 6774 | dhclient -v @var{interface} |
dedb8d5e | 6775 | @end example |
5af6de3e | 6776 | |
dedb8d5e LC |
6777 | Try to ping a server to see if networking is up and running: |
6778 | ||
6779 | @example | |
6780 | ping -c 3 gnu.org | |
6781 | @end example | |
5af6de3e LC |
6782 | |
6783 | Setting up network access is almost always a requirement because the | |
6784 | image does not contain all the software and tools that may be needed. | |
6785 | ||
dedb8d5e LC |
6786 | @subsubsection Disk Partitioning |
6787 | ||
6788 | Unless this has already been done, the next step is to partition, and | |
6789 | then format the target partition(s). | |
6790 | ||
6791 | The installation image includes several partitioning tools, including | |
6792 | Parted (@pxref{Overview,,, parted, GNU Parted User Manual}), | |
6793 | @command{fdisk}, and @command{cfdisk}. Run it and set up your disk with | |
6794 | the partition layout you want: | |
6795 | ||
6796 | @example | |
6797 | cfdisk | |
6798 | @end example | |
6799 | ||
6800 | Once you are done partitioning the target hard disk drive, you have to | |
6801 | create a file system on the relevant partition(s)@footnote{Currently | |
6802 | GuixSD pretty much assumes an ext4 file system. In particular, code | |
6803 | that reads partition UUIDs and labels only works with ext4. This will | |
6804 | be fixed in the future.}. | |
5af6de3e | 6805 | |
7ab44369 LC |
6806 | Preferably, assign partitions a label so that you can easily and |
6807 | reliably refer to them in @code{file-system} declarations (@pxref{File | |
6808 | Systems}). This is typically done using the @code{-L} option of | |
dedb8d5e LC |
6809 | @command{mkfs.ext4} and related commands. So, assuming the target root |
6810 | partition lives at @file{/dev/sda1}, a file system with the label | |
6811 | @code{my-root} can be created with: | |
7ab44369 | 6812 | |
dedb8d5e LC |
6813 | @example |
6814 | mkfs.ext4 -L my-root /dev/sda1 | |
6815 | @end example | |
dd816355 | 6816 | |
13fb1bd9 LC |
6817 | @cindex encrypted disk |
6818 | If you are instead planning to encrypt the root partition, you can use | |
6819 | the Cryptsetup/LUKS utilities to do that (see @inlinefmtifelse{html, | |
6820 | @uref{https://linux.die.net/man/8/cryptsetup, @code{man cryptsetup}}, | |
6821 | @code{man cryptsetup}} for more information.) Assuming you want to | |
6822 | store the root partition on @file{/dev/sda1}, the command sequence would | |
6823 | be along these lines: | |
6d6e6281 | 6824 | |
13fb1bd9 LC |
6825 | @example |
6826 | cryptsetup luksFormat /dev/sda1 | |
6827 | cryptsetup open --type luks /dev/sda1 my-partition | |
6828 | mkfs.ext4 -L my-root /dev/mapper/my-partition | |
6829 | @end example | |
5af6de3e | 6830 | |
dedb8d5e | 6831 | Once that is done, mount the target root partition under @file{/mnt} |
13fb1bd9 LC |
6832 | with a command like (again, assuming @code{my-root} is the label of the |
6833 | root partition): | |
83a17b62 | 6834 | |
dedb8d5e | 6835 | @example |
13fb1bd9 | 6836 | mount LABEL=my-root /mnt |
dedb8d5e | 6837 | @end example |
83a17b62 | 6838 | |
31b6cdf8 LC |
6839 | Finally, if you plan to use one or more swap partitions (@pxref{Memory |
6840 | Concepts, swap space,, libc, The GNU C Library Reference Manual}), make | |
6841 | sure to initialize them with @command{mkswap}. Assuming you have one | |
6842 | swap partition on @file{/dev/sda2}, you would run: | |
6843 | ||
6844 | @example | |
6845 | mkswap /dev/sda2 | |
6846 | @end example | |
6847 | ||
dedb8d5e LC |
6848 | @node Proceeding with the Installation |
6849 | @subsection Proceeding with the Installation | |
83a17b62 | 6850 | |
dedb8d5e LC |
6851 | With the target partitions ready and the target root mounted on |
6852 | @file{/mnt}, we're ready to go. First, run: | |
5af6de3e | 6853 | |
dedb8d5e LC |
6854 | @example |
6855 | herd start cow-store /mnt | |
6856 | @end example | |
5af6de3e | 6857 | |
b397c0d5 LC |
6858 | This makes @file{/gnu/store} copy-on-write, such that packages added to it |
6859 | during the installation phase are written to the target disk on @file{/mnt} | |
6860 | rather than kept in memory. This is necessary because the first phase of | |
6861 | the @command{guix system init} command (see below) entails downloads or | |
6862 | builds to @file{/gnu/store} which, initially, is an in-memory file system. | |
5af6de3e | 6863 | |
dedb8d5e | 6864 | Next, you have to edit a file and |
5af6de3e | 6865 | provide the declaration of the operating system to be installed. To |
a8cb87ab LC |
6866 | that end, the installation system comes with three text editors: GNU nano |
6867 | (@pxref{Top,,, nano, GNU nano Manual}), GNU Zile (an Emacs clone), and | |
6868 | nvi (a clone of the original BSD @command{vi} editor). | |
efa77c6c LC |
6869 | We strongly recommend storing that file on the target root file system, say, |
6870 | as @file{/mnt/etc/config.scm}. Failing to do that, you will have lost your | |
6871 | configuration file once you have rebooted into the newly-installed system. | |
5af6de3e | 6872 | |
dedb8d5e LC |
6873 | @xref{Using the Configuration System}, for an overview of the |
6874 | configuration file. The example configurations discussed in that | |
6875 | section are available under @file{/etc/configuration} in the | |
6876 | installation image. Thus, to get started with a system configuration | |
6877 | providing a graphical display server (a ``desktop'' system), you can run | |
6878 | something along these lines: | |
6879 | ||
6880 | @example | |
6881 | # mkdir /mnt/etc | |
6882 | # cp /etc/configuration/desktop.scm /mnt/etc/config.scm | |
6883 | # zile /mnt/etc/config.scm | |
6884 | @end example | |
6885 | ||
6886 | You should pay attention to what your configuration file contains, and | |
6887 | in particular: | |
6888 | ||
6889 | @itemize | |
6890 | @item | |
6891 | Make sure the @code{grub-configuration} form refers to the device you | |
6892 | want to install GRUB on. | |
6893 | ||
6894 | @item | |
6895 | Be sure that your partition labels match the value of their respective | |
6896 | @code{device} fields in your @code{file-system} configuration, assuming | |
6897 | your @code{file-system} configuration sets the value of @code{title} to | |
6898 | @code{'label}. | |
13fb1bd9 LC |
6899 | |
6900 | @item | |
6901 | If there are encrypted or RAID partitions, make sure to add a | |
6902 | @code{mapped-devices} field to describe them (@pxref{Mapped Devices}). | |
dedb8d5e | 6903 | @end itemize |
5af6de3e | 6904 | |
dd51caac LC |
6905 | Once you are done preparing the configuration file, the new system must |
6906 | be initialized (remember that the target root file system is mounted | |
6907 | under @file{/mnt}): | |
5af6de3e LC |
6908 | |
6909 | @example | |
6910 | guix system init /mnt/etc/config.scm /mnt | |
6911 | @end example | |
6912 | ||
6913 | @noindent | |
dedb8d5e | 6914 | This copies all the necessary files and installs GRUB on |
5af6de3e | 6915 | @file{/dev/sdX}, unless you pass the @option{--no-grub} option. For |
6621cdb6 | 6916 | more information, @pxref{Invoking guix system}. This command may trigger |
5af6de3e LC |
6917 | downloads or builds of missing packages, which can take some time. |
6918 | ||
1bd4e6db LC |
6919 | Once that command has completed---and hopefully succeeded!---you can run |
6920 | @command{reboot} and boot into the new system. The @code{root} password | |
6921 | in the new system is initially empty; other users' passwords need to be | |
6922 | initialized by running the @command{passwd} command as @code{root}, | |
6923 | unless your configuration specifies otherwise | |
6924 | (@pxref{user-account-password, user account passwords}). | |
6925 | ||
6926 | Join us on @code{#guix} on the Freenode IRC network or on | |
5af6de3e LC |
6927 | @file{guix-devel@@gnu.org} to share your experience---good or not so |
6928 | good. | |
6929 | ||
c8b54374 VL |
6930 | @node Installing GuixSD in a VM |
6931 | @subsection Installing GuixSD in a Virtual Machine | |
6932 | ||
6933 | @cindex virtual machine, GuixSD installation | |
6934 | If you'd like to install GuixSD in a virtual machine (VM) rather than on | |
6935 | your beloved machine, this section is for you. | |
6936 | ||
6937 | To boot a @uref{http://qemu.org/,QEMU} VM for installing GuixSD in a | |
6938 | disk image, follow these steps: | |
6939 | ||
6940 | @enumerate | |
6941 | @item | |
6942 | First, retrieve the GuixSD installation image as described previously | |
6943 | (@pxref{USB Stick Installation}). | |
6944 | ||
6945 | @item | |
6946 | Create a disk image that will hold the installed system. To make a | |
6947 | qcow2-formatted disk image, use the @command{qemu-img} command: | |
6948 | ||
6949 | @example | |
6950 | qemu-img create -f qcow2 guixsd.img 5G | |
6951 | @end example | |
6952 | ||
6953 | This will create a 5GB file. | |
6954 | ||
6955 | @item | |
6956 | Boot the USB installation image in an VM: | |
6957 | ||
6958 | @example | |
6959 | qemu-system-x86_64 -m 1024 -smp 1 \ | |
6960 | -net default -net nic,model=virtio -boot menu=on \ | |
6961 | -drive file=guixsd.img \ | |
6962 | -drive file=guixsd-usb-install-@value{VERSION}.@var{system} | |
6963 | @end example | |
6964 | ||
6965 | In the VM console, quickly press the @kbd{F12} key to enter the boot | |
6966 | menu. Then press the @kbd{2} key and the @kbd{RET} key to validate your | |
6967 | selection. | |
6968 | ||
6969 | @item | |
6970 | You're now root in the VM, proceed with the installation process. | |
6971 | @xref{Preparing for Installation}, and follow the instructions. | |
6972 | @end enumerate | |
6973 | ||
6974 | Once installation is complete, you can boot the system that's on your | |
6975 | @file{guixsd.img} image. @xref{Running GuixSD in a VM}, for how to do | |
6976 | that. | |
6977 | ||
dedb8d5e | 6978 | @node Building the Installation Image |
5af6de3e LC |
6979 | @subsection Building the Installation Image |
6980 | ||
e32171ee | 6981 | @cindex installation image |
5af6de3e LC |
6982 | The installation image described above was built using the @command{guix |
6983 | system} command, specifically: | |
6984 | ||
622b2304 | 6985 | @c FIXME: 1G is too much; see <http://bugs.gnu.org/23077>. |
5af6de3e | 6986 | @example |
622b2304 | 6987 | guix system disk-image --image-size=1G gnu/system/install.scm |
5af6de3e LC |
6988 | @end example |
6989 | ||
6e6a0401 AE |
6990 | Have a look at @file{gnu/system/install.scm} in the source tree, |
6991 | and see also @ref{Invoking guix system} for more information | |
5af6de3e LC |
6992 | about the installation image. |
6993 | ||
cf4a9129 LC |
6994 | @node System Configuration |
6995 | @section System Configuration | |
b208a005 | 6996 | |
cf4a9129 | 6997 | @cindex system configuration |
3ca2731c | 6998 | The Guix System Distribution supports a consistent whole-system configuration |
cf4a9129 LC |
6999 | mechanism. By that we mean that all aspects of the global system |
7000 | configuration---such as the available system services, timezone and | |
7001 | locale settings, user accounts---are declared in a single place. Such | |
7002 | a @dfn{system configuration} can be @dfn{instantiated}---i.e., effected. | |
91ef73d4 | 7003 | |
cf4a9129 LC |
7004 | One of the advantages of putting all the system configuration under the |
7005 | control of Guix is that it supports transactional system upgrades, and | |
1068f26b | 7006 | makes it possible to roll back to a previous system instantiation, |
cf4a9129 | 7007 | should something go wrong with the new one (@pxref{Features}). Another |
1068f26b | 7008 | advantage is that it makes it easy to replicate the exact same configuration |
cf4a9129 LC |
7009 | across different machines, or at different points in time, without |
7010 | having to resort to additional administration tools layered on top of | |
1068f26b | 7011 | the own tools of the system. |
cf4a9129 | 7012 | @c Yes, we're talking of Puppet, Chef, & co. here. ↑ |
91ef73d4 | 7013 | |
cf4a9129 LC |
7014 | This section describes this mechanism. First we focus on the system |
7015 | administrator's viewpoint---explaining how the system is configured and | |
7016 | instantiated. Then we show how this mechanism can be extended, for | |
7017 | instance to support new system services. | |
91ef73d4 | 7018 | |
cf4a9129 LC |
7019 | @menu |
7020 | * Using the Configuration System:: Customizing your GNU system. | |
7313a52e | 7021 | * operating-system Reference:: Detail of operating-system declarations. |
cf4a9129 | 7022 | * File Systems:: Configuring file system mounts. |
510f9d86 | 7023 | * Mapped Devices:: Block device extra processing. |
cf4a9129 | 7024 | * User Accounts:: Specifying user accounts. |
598e19dc | 7025 | * Locales:: Language and cultural convention settings. |
cf4a9129 | 7026 | * Services:: Specifying system services. |
0ae8c15a | 7027 | * Setuid Programs:: Programs running with root privileges. |
efb5e833 | 7028 | * X.509 Certificates:: Authenticating HTTPS servers. |
996ed739 | 7029 | * Name Service Switch:: Configuring libc's name service switch. |
fd1b1fa2 | 7030 | * Initial RAM Disk:: Linux-Libre bootstrapping. |
88faf933 | 7031 | * GRUB Configuration:: Configuring the boot loader. |
cf4a9129 | 7032 | * Invoking guix system:: Instantiating a system configuration. |
97d76250 | 7033 | * Running GuixSD in a VM:: How to run GuixSD in a virtual machine. |
cf4a9129 LC |
7034 | * Defining Services:: Adding new service definitions. |
7035 | @end menu | |
91ef73d4 | 7036 | |
cf4a9129 LC |
7037 | @node Using the Configuration System |
7038 | @subsection Using the Configuration System | |
64d76fa6 | 7039 | |
cf4a9129 LC |
7040 | The operating system is configured by providing an |
7041 | @code{operating-system} declaration in a file that can then be passed to | |
7042 | the @command{guix system} command (@pxref{Invoking guix system}). A | |
7043 | simple setup, with the default system services, the default Linux-Libre | |
7044 | kernel, initial RAM disk, and boot loader looks like this: | |
91ef73d4 | 7045 | |
cf4a9129 LC |
7046 | @findex operating-system |
7047 | @lisp | |
dd51caac | 7048 | @include os-config-bare-bones.texi |
cf4a9129 | 7049 | @end lisp |
401c53c4 | 7050 | |
cf4a9129 LC |
7051 | This example should be self-describing. Some of the fields defined |
7052 | above, such as @code{host-name} and @code{bootloader}, are mandatory. | |
7053 | Others, such as @code{packages} and @code{services}, can be omitted, in | |
7054 | which case they get a default value. | |
e7f34eb0 | 7055 | |
5d94ac51 LC |
7056 | Below we discuss the effect of some of the most important fields |
7057 | (@pxref{operating-system Reference}, for details about all the available | |
7058 | fields), and how to @dfn{instantiate} the operating system using | |
7059 | @command{guix system}. | |
7060 | ||
7061 | @unnumberedsubsubsec Globally-Visible Packages | |
7062 | ||
cf4a9129 | 7063 | @vindex %base-packages |
5d94ac51 LC |
7064 | The @code{packages} field lists packages that will be globally visible |
7065 | on the system, for all user accounts---i.e., in every user's @code{PATH} | |
7066 | environment variable---in addition to the per-user profiles | |
7067 | (@pxref{Invoking guix package}). The @var{%base-packages} variable | |
7068 | provides all the tools one would expect for basic user and administrator | |
7069 | tasks---including the GNU Core Utilities, the GNU Networking Utilities, | |
7070 | the GNU Zile lightweight text editor, @command{find}, @command{grep}, | |
7071 | etc. The example above adds tcpdump to those, taken from the @code{(gnu | |
7072 | packages admin)} module (@pxref{Package Modules}). | |
e7f34eb0 | 7073 | |
f6c9fb1b LC |
7074 | @findex specification->package |
7075 | Referring to packages by variable name, like @var{tcpdump} above, has | |
7076 | the advantage of being unambiguous; it also allows typos and such to be | |
7077 | diagnosed right away as ``unbound variables''. The downside is that one | |
7078 | needs to know which module defines which package, and to augment the | |
7079 | @code{use-package-modules} line accordingly. To avoid that, one can use | |
7080 | the @code{specification->package} procedure of the @code{(gnu packages)} | |
7081 | module, which returns the best package for a given name or name and | |
7082 | version: | |
7083 | ||
7084 | @lisp | |
7085 | (use-modules (gnu packages)) | |
7086 | ||
7087 | (operating-system | |
7088 | ;; ... | |
7089 | (packages (append (map specification->package | |
d5e59248 | 7090 | '("tcpdump" "htop" "gnupg@@2.0")) |
f6c9fb1b LC |
7091 | %base-packages))) |
7092 | @end lisp | |
7093 | ||
5d94ac51 LC |
7094 | @unnumberedsubsubsec System Services |
7095 | ||
e32171ee | 7096 | @cindex services |
cf4a9129 LC |
7097 | @vindex %base-services |
7098 | The @code{services} field lists @dfn{system services} to be made | |
7099 | available when the system starts (@pxref{Services}). | |
7100 | The @code{operating-system} declaration above specifies that, in | |
7101 | addition to the basic services, we want the @command{lshd} secure shell | |
cd6f6c22 LC |
7102 | daemon listening on port 2222 (@pxref{Networking Services, |
7103 | @code{lsh-service}}). Under the hood, | |
cf4a9129 LC |
7104 | @code{lsh-service} arranges so that @code{lshd} is started with the |
7105 | right command-line options, possibly with supporting configuration files | |
cd6f6c22 LC |
7106 | generated as needed (@pxref{Defining Services}). |
7107 | ||
7108 | @cindex customization, of services | |
7109 | @findex modify-services | |
7110 | Occasionally, instead of using the base services as is, you will want to | |
4d343a14 CM |
7111 | customize them. To do this, use @code{modify-services} (@pxref{Service |
7112 | Reference, @code{modify-services}}) to modify the list. | |
7113 | ||
7114 | For example, suppose you want to modify @code{guix-daemon} and Mingetty | |
7115 | (the console log-in) in the @var{%base-services} list (@pxref{Base | |
7116 | Services, @code{%base-services}}). To do that, you can write the | |
7117 | following in your operating system declaration: | |
cd6f6c22 LC |
7118 | |
7119 | @lisp | |
4d343a14 CM |
7120 | (define %my-services |
7121 | ;; My very own list of services. | |
7122 | (modify-services %base-services | |
7123 | (guix-service-type config => | |
7124 | (guix-configuration | |
7125 | (inherit config) | |
7126 | (use-substitutes? #f) | |
7127 | (extra-options '("--gc-keep-derivations")))) | |
7128 | (mingetty-service-type config => | |
7129 | (mingetty-configuration | |
317d3b47 | 7130 | (inherit config))))) |
4d343a14 CM |
7131 | |
7132 | (operating-system | |
7133 | ;; @dots{} | |
7134 | (services %my-services)) | |
cd6f6c22 LC |
7135 | @end lisp |
7136 | ||
4d343a14 CM |
7137 | This changes the configuration---i.e., the service parameters---of the |
7138 | @code{guix-service-type} instance, and that of all the | |
7139 | @code{mingetty-service-type} instances in the @var{%base-services} list. | |
7140 | Observe how this is accomplished: first, we arrange for the original | |
7141 | configuration to be bound to the identifier @code{config} in the | |
7142 | @var{body}, and then we write the @var{body} so that it evaluates to the | |
7143 | desired configuration. In particular, notice how we use @code{inherit} | |
7144 | to create a new configuration which has the same values as the old | |
7145 | configuration, but with a few modifications. | |
a1ba8475 | 7146 | |
13fb1bd9 LC |
7147 | @cindex encrypted disk |
7148 | The configuration for a typical ``desktop'' usage, with an encrypted | |
7149 | root partition, the X11 display | |
d038b674 LC |
7150 | server, GNOME and Xfce (users can choose which of these desktop |
7151 | environments to use at the log-in screen by pressing @kbd{F1}), network | |
7152 | management, power management, and more, would look like this: | |
dd51caac LC |
7153 | |
7154 | @lisp | |
7155 | @include os-config-desktop.texi | |
7156 | @end lisp | |
7157 | ||
d038b674 LC |
7158 | A graphical environment with a choice of lightweight window managers |
7159 | instead of full-blown desktop environments would look like this: | |
7160 | ||
7161 | @lisp | |
7162 | @include os-config-lightweight-desktop.texi | |
7163 | @end lisp | |
7164 | ||
dd51caac | 7165 | @xref{Desktop Services}, for the exact list of services provided by |
efb5e833 LC |
7166 | @var{%desktop-services}. @xref{X.509 Certificates}, for background |
7167 | information about the @code{nss-certs} package that is used here. | |
dd51caac | 7168 | |
5d94ac51 LC |
7169 | Again, @var{%desktop-services} is just a list of service objects. If |
7170 | you want to remove services from there, you can do so using the | |
7171 | procedures for list filtering (@pxref{SRFI-1 Filtering and | |
7172 | Partitioning,,, guile, GNU Guile Reference Manual}). For instance, the | |
7173 | following expression returns a list that contains all the services in | |
7174 | @var{%desktop-services} minus the Avahi service: | |
7175 | ||
7176 | @example | |
7177 | (remove (lambda (service) | |
7178 | (eq? (service-kind service) avahi-service-type)) | |
7179 | %desktop-services) | |
7180 | @end example | |
7181 | ||
7182 | @unnumberedsubsubsec Instantiating the System | |
7183 | ||
7184 | Assuming the @code{operating-system} declaration | |
7185 | is stored in the @file{my-system-config.scm} | |
cf4a9129 LC |
7186 | file, the @command{guix system reconfigure my-system-config.scm} command |
7187 | instantiates that configuration, and makes it the default GRUB boot | |
65797bff LC |
7188 | entry (@pxref{Invoking guix system}). |
7189 | ||
1068f26b | 7190 | The normal way to change the system configuration is by updating this |
65797bff | 7191 | file and re-running @command{guix system reconfigure}. One should never |
8b499030 | 7192 | have to touch files in @file{/etc} or to run commands that modify the |
65797bff LC |
7193 | system state such as @command{useradd} or @command{grub-install}. In |
7194 | fact, you must avoid that since that would not only void your warranty | |
7195 | but also prevent you from rolling back to previous versions of your | |
7196 | system, should you ever need to. | |
7197 | ||
7198 | @cindex roll-back, of the operating system | |
7199 | Speaking of roll-back, each time you run @command{guix system | |
7200 | reconfigure}, a new @dfn{generation} of the system is created---without | |
7201 | modifying or deleting previous generations. Old system generations get | |
7202 | an entry in the GRUB boot menu, allowing you to boot them in case | |
7203 | something went wrong with the latest generation. Reassuring, no? The | |
7204 | @command{guix system list-generations} command lists the system | |
067a2e2d CM |
7205 | generations available on disk. It is also possible to roll back the |
7206 | system via the commands @command{guix system roll-back} and | |
7207 | @command{guix system switch-generation}. | |
7208 | ||
7209 | Although the command @command{guix system reconfigure} will not modify | |
7210 | previous generations, must take care when the current generation is not | |
7211 | the latest (e.g., after invoking @command{guix system roll-back}), since | |
7212 | the operation might overwrite a later generation (@pxref{Invoking guix | |
7213 | system}). | |
b81e1947 | 7214 | |
5d94ac51 LC |
7215 | @unnumberedsubsubsec The Programming Interface |
7216 | ||
cf4a9129 LC |
7217 | At the Scheme level, the bulk of an @code{operating-system} declaration |
7218 | is instantiated with the following monadic procedure (@pxref{The Store | |
7219 | Monad}): | |
b81e1947 | 7220 | |
cf4a9129 LC |
7221 | @deffn {Monadic Procedure} operating-system-derivation os |
7222 | Return a derivation that builds @var{os}, an @code{operating-system} | |
7223 | object (@pxref{Derivations}). | |
b81e1947 | 7224 | |
cf4a9129 LC |
7225 | The output of the derivation is a single directory that refers to all |
7226 | the packages, configuration files, and other supporting files needed to | |
7227 | instantiate @var{os}. | |
7228 | @end deffn | |
b81e1947 | 7229 | |
5d94ac51 LC |
7230 | This procedure is provided by the @code{(gnu system)} module. Along |
7231 | with @code{(gnu services)} (@pxref{Services}), this module contains the | |
7232 | guts of GuixSD. Make sure to visit it! | |
7233 | ||
7234 | ||
7313a52e LC |
7235 | @node operating-system Reference |
7236 | @subsection @code{operating-system} Reference | |
7237 | ||
7238 | This section summarizes all the options available in | |
7239 | @code{operating-system} declarations (@pxref{Using the Configuration | |
7240 | System}). | |
7241 | ||
7242 | @deftp {Data Type} operating-system | |
7243 | This is the data type representing an operating system configuration. | |
7244 | By that, we mean all the global system configuration, not per-user | |
7245 | configuration (@pxref{Using the Configuration System}). | |
7246 | ||
7247 | @table @asis | |
7248 | @item @code{kernel} (default: @var{linux-libre}) | |
fbb25e56 | 7249 | The package object of the operating system kernel to use@footnote{Currently |
7313a52e LC |
7250 | only the Linux-libre kernel is supported. In the future, it will be |
7251 | possible to use the GNU@tie{}Hurd.}. | |
7252 | ||
ee2a6304 LC |
7253 | @item @code{kernel-arguments} (default: @code{'()}) |
7254 | List of strings or gexps representing additional arguments to pass on | |
1068f26b | 7255 | the command-line of the kernel---e.g., @code{("console=ttyS0")}. |
ee2a6304 | 7256 | |
7313a52e | 7257 | @item @code{bootloader} |
88faf933 | 7258 | The system bootloader configuration object. @xref{GRUB Configuration}. |
7313a52e LC |
7259 | |
7260 | @item @code{initrd} (default: @code{base-initrd}) | |
e32171ee JD |
7261 | @cindex initrd |
7262 | @cindex initial RAM disk | |
7313a52e LC |
7263 | A two-argument monadic procedure that returns an initial RAM disk for |
7264 | the Linux kernel. @xref{Initial RAM Disk}. | |
7265 | ||
f34c56be LC |
7266 | @item @code{firmware} (default: @var{%base-firmware}) |
7267 | @cindex firmware | |
7268 | List of firmware packages loadable by the operating system kernel. | |
7269 | ||
52db41af EB |
7270 | The default includes firmware needed for Atheros- and Broadcom-based |
7271 | WiFi devices (Linux-libre modules @code{ath9k} and @code{b43-open}, | |
7272 | respectively). @xref{Hardware Considerations}, for more info on | |
7273 | supported hardware. | |
f34c56be | 7274 | |
7313a52e LC |
7275 | @item @code{host-name} |
7276 | The host name. | |
7277 | ||
7278 | @item @code{hosts-file} | |
7279 | @cindex hosts file | |
24e02c28 | 7280 | A file-like object (@pxref{G-Expressions, file-like objects}) for use as |
7313a52e | 7281 | @file{/etc/hosts} (@pxref{Host Names,,, libc, The GNU C Library |
24e02c28 | 7282 | Reference Manual}). The default is a file with entries for |
7313a52e LC |
7283 | @code{localhost} and @var{host-name}. |
7284 | ||
7285 | @item @code{mapped-devices} (default: @code{'()}) | |
7286 | A list of mapped devices. @xref{Mapped Devices}. | |
7287 | ||
7288 | @item @code{file-systems} | |
7289 | A list of file systems. @xref{File Systems}. | |
7290 | ||
7291 | @item @code{swap-devices} (default: @code{'()}) | |
7292 | @cindex swap devices | |
7293 | A list of strings identifying devices to be used for ``swap space'' | |
7294 | (@pxref{Memory Concepts,,, libc, The GNU C Library Reference Manual}). | |
7295 | For example, @code{'("/dev/sda3")}. | |
7296 | ||
bf87f38a | 7297 | @item @code{users} (default: @code{%base-user-accounts}) |
7313a52e LC |
7298 | @itemx @code{groups} (default: @var{%base-groups}) |
7299 | List of user accounts and groups. @xref{User Accounts}. | |
7300 | ||
7301 | @item @code{skeletons} (default: @code{(default-skeletons)}) | |
e9dffec1 LC |
7302 | A list target file name/file-like object tuples (@pxref{G-Expressions, |
7303 | file-like objects}). These are the skeleton files that will be added to | |
7304 | the home directory of newly-created user accounts. | |
7313a52e LC |
7305 | |
7306 | For instance, a valid value may look like this: | |
7307 | ||
7308 | @example | |
e9dffec1 LC |
7309 | `((".bashrc" ,(plain-file "bashrc" "echo Hello\n")) |
7310 | (".guile" ,(plain-file "guile" | |
7311 | "(use-modules (ice-9 readline)) | |
7312 | (activate-readline)"))) | |
7313a52e LC |
7313 | @end example |
7314 | ||
7315 | @item @code{issue} (default: @var{%default-issue}) | |
7316 | A string denoting the contents of the @file{/etc/issue} file, which is | |
1068f26b | 7317 | displayed when users log in on a text console. |
7313a52e LC |
7318 | |
7319 | @item @code{packages} (default: @var{%base-packages}) | |
7320 | The set of packages installed in the global profile, which is accessible | |
7321 | at @file{/run/current-system/profile}. | |
7322 | ||
1068f26b | 7323 | The default set includes core utilities and it is good practice to |
7313a52e LC |
7324 | install non-core utilities in user profiles (@pxref{Invoking guix |
7325 | package}). | |
7326 | ||
7327 | @item @code{timezone} | |
7328 | A timezone identifying string---e.g., @code{"Europe/Paris"}. | |
7329 | ||
17c20385 LC |
7330 | You can run the @command{tzselect} command to find out which timezone |
7331 | string corresponds to your region. Choosing an invalid timezone name | |
7332 | causes @command{guix system} to fail. | |
7333 | ||
598e19dc LC |
7334 | @item @code{locale} (default: @code{"en_US.utf8"}) |
7335 | The name of the default locale (@pxref{Locale Names,,, libc, The GNU C | |
7336 | Library Reference Manual}). @xref{Locales}, for more information. | |
7337 | ||
7338 | @item @code{locale-definitions} (default: @var{%default-locale-definitions}) | |
7339 | The list of locale definitions to be compiled and that may be used at | |
7340 | run time. @xref{Locales}. | |
7313a52e | 7341 | |
34760ae7 LC |
7342 | @item @code{locale-libcs} (default: @code{(list @var{glibc})}) |
7343 | The list of GNU@tie{}libc packages whose locale data and tools are used | |
7344 | to build the locale definitions. @xref{Locales}, for compatibility | |
7345 | considerations that justify this option. | |
7346 | ||
996ed739 | 7347 | @item @code{name-service-switch} (default: @var{%default-nss}) |
1068f26b | 7348 | Configuration of the libc name service switch (NSS)---a |
996ed739 LC |
7349 | @code{<name-service-switch>} object. @xref{Name Service Switch}, for |
7350 | details. | |
7351 | ||
7313a52e | 7352 | @item @code{services} (default: @var{%base-services}) |
28d939af | 7353 | A list of service objects denoting system services. @xref{Services}. |
7313a52e LC |
7354 | |
7355 | @item @code{pam-services} (default: @code{(base-pam-services)}) | |
7356 | @cindex PAM | |
7357 | @cindex pluggable authentication modules | |
7358 | Linux @dfn{pluggable authentication module} (PAM) services. | |
7359 | @c FIXME: Add xref to PAM services section. | |
7360 | ||
7361 | @item @code{setuid-programs} (default: @var{%setuid-programs}) | |
7362 | List of string-valued G-expressions denoting setuid programs. | |
7363 | @xref{Setuid Programs}. | |
7364 | ||
f5a9ffa0 AK |
7365 | @item @code{sudoers-file} (default: @var{%sudoers-specification}) |
7366 | @cindex sudoers file | |
84765839 LC |
7367 | The contents of the @file{/etc/sudoers} file as a file-like object |
7368 | (@pxref{G-Expressions, @code{local-file} and @code{plain-file}}). | |
7313a52e LC |
7369 | |
7370 | This file specifies which users can use the @command{sudo} command, what | |
7371 | they are allowed to do, and what privileges they may gain. The default | |
7372 | is that only @code{root} and members of the @code{wheel} group may use | |
7373 | @code{sudo}. | |
7374 | ||
7375 | @end table | |
7376 | @end deftp | |
7377 | ||
cf4a9129 LC |
7378 | @node File Systems |
7379 | @subsection File Systems | |
b81e1947 | 7380 | |
cf4a9129 | 7381 | The list of file systems to be mounted is specified in the |
1068f26b | 7382 | @code{file-systems} field of the operating system declaration |
cf4a9129 LC |
7383 | (@pxref{Using the Configuration System}). Each file system is declared |
7384 | using the @code{file-system} form, like this: | |
b81e1947 LC |
7385 | |
7386 | @example | |
cf4a9129 LC |
7387 | (file-system |
7388 | (mount-point "/home") | |
7389 | (device "/dev/sda3") | |
7390 | (type "ext4")) | |
b81e1947 LC |
7391 | @end example |
7392 | ||
cf4a9129 LC |
7393 | As usual, some of the fields are mandatory---those shown in the example |
7394 | above---while others can be omitted. These are described below. | |
b81e1947 | 7395 | |
cf4a9129 LC |
7396 | @deftp {Data Type} file-system |
7397 | Objects of this type represent file systems to be mounted. They | |
7398 | contain the following members: | |
5ff3c4b8 | 7399 | |
cf4a9129 LC |
7400 | @table @asis |
7401 | @item @code{type} | |
7402 | This is a string specifying the type of the file system---e.g., | |
7403 | @code{"ext4"}. | |
5ff3c4b8 | 7404 | |
cf4a9129 LC |
7405 | @item @code{mount-point} |
7406 | This designates the place where the file system is to be mounted. | |
b81e1947 | 7407 | |
cf4a9129 LC |
7408 | @item @code{device} |
7409 | This names the ``source'' of the file system. By default it is the name | |
7410 | of a node under @file{/dev}, but its meaning depends on the @code{title} | |
7411 | field described below. | |
401c53c4 | 7412 | |
cf4a9129 LC |
7413 | @item @code{title} (default: @code{'device}) |
7414 | This is a symbol that specifies how the @code{device} field is to be | |
7415 | interpreted. | |
401c53c4 | 7416 | |
cf4a9129 LC |
7417 | When it is the symbol @code{device}, then the @code{device} field is |
7418 | interpreted as a file name; when it is @code{label}, then @code{device} | |
7419 | is interpreted as a partition label name; when it is @code{uuid}, | |
7420 | @code{device} is interpreted as a partition unique identifier (UUID). | |
da7cabd4 | 7421 | |
661a1d79 | 7422 | UUIDs may be converted from their string representation (as shown by the |
0767f6a6 LC |
7423 | @command{tune2fs -l} command) using the @code{uuid} form@footnote{The |
7424 | @code{uuid} form expects 16-byte UUIDs as defined in | |
7425 | @uref{https://tools.ietf.org/html/rfc4122, RFC@tie{}4122}. This is the | |
7426 | form of UUID used by the ext2 family of file systems and others, but it | |
7427 | is different from ``UUIDs'' found in FAT file systems, for instance.}, | |
7428 | like this: | |
661a1d79 LC |
7429 | |
7430 | @example | |
7431 | (file-system | |
7432 | (mount-point "/home") | |
7433 | (type "ext4") | |
7434 | (title 'uuid) | |
7435 | (device (uuid "4dab5feb-d176-45de-b287-9b0a6e4c01cb"))) | |
7436 | @end example | |
7437 | ||
cf4a9129 | 7438 | The @code{label} and @code{uuid} options offer a way to refer to disk |
661a1d79 LC |
7439 | partitions without having to hard-code their actual device |
7440 | name@footnote{Note that, while it is tempting to use | |
7441 | @file{/dev/disk/by-uuid} and similar device names to achieve the same | |
7442 | result, this is not recommended: These special device nodes are created | |
7443 | by the udev daemon and may be unavailable at the time the device is | |
7444 | mounted.}. | |
da7cabd4 | 7445 | |
1068f26b | 7446 | However, when the source of a file system is a mapped device (@pxref{Mapped |
5f86a66e LC |
7447 | Devices}), its @code{device} field @emph{must} refer to the mapped |
7448 | device name---e.g., @file{/dev/mapper/root-partition}---and consequently | |
7449 | @code{title} must be set to @code{'device}. This is required so that | |
7450 | the system knows that mounting the file system depends on having the | |
7451 | corresponding device mapping established. | |
7452 | ||
cf4a9129 LC |
7453 | @item @code{flags} (default: @code{'()}) |
7454 | This is a list of symbols denoting mount flags. Recognized flags | |
2c071ce9 LC |
7455 | include @code{read-only}, @code{bind-mount}, @code{no-dev} (disallow |
7456 | access to special files), @code{no-suid} (ignore setuid and setgid | |
7457 | bits), and @code{no-exec} (disallow program execution.) | |
da7cabd4 | 7458 | |
cf4a9129 LC |
7459 | @item @code{options} (default: @code{#f}) |
7460 | This is either @code{#f}, or a string denoting mount options. | |
da7cabd4 | 7461 | |
be21979d LC |
7462 | @item @code{mount?} (default: @code{#t}) |
7463 | This value indicates whether to automatically mount the file system when | |
7464 | the system is brought up. When set to @code{#f}, the file system gets | |
7465 | an entry in @file{/etc/fstab} (read by the @command{mount} command) but | |
7466 | is not automatically mounted. | |
7467 | ||
cf4a9129 LC |
7468 | @item @code{needed-for-boot?} (default: @code{#f}) |
7469 | This Boolean value indicates whether the file system is needed when | |
7470 | booting. If that is true, then the file system is mounted when the | |
7471 | initial RAM disk (initrd) is loaded. This is always the case, for | |
7472 | instance, for the root file system. | |
da7cabd4 | 7473 | |
cf4a9129 LC |
7474 | @item @code{check?} (default: @code{#t}) |
7475 | This Boolean indicates whether the file system needs to be checked for | |
7476 | errors before being mounted. | |
f9cc8971 | 7477 | |
4e469051 LC |
7478 | @item @code{create-mount-point?} (default: @code{#f}) |
7479 | When true, the mount point is created if it does not exist yet. | |
7480 | ||
e51710d1 | 7481 | @item @code{dependencies} (default: @code{'()}) |
13fb1bd9 LC |
7482 | This is a list of @code{<file-system>} or @code{<mapped-device>} objects |
7483 | representing file systems that must be mounted or mapped devices that | |
7484 | must be opened before (and unmounted or closed after) this one. | |
e51710d1 LC |
7485 | |
7486 | As an example, consider a hierarchy of mounts: @file{/sys/fs/cgroup} is | |
7487 | a dependency of @file{/sys/fs/cgroup/cpu} and | |
7488 | @file{/sys/fs/cgroup/memory}. | |
7489 | ||
13fb1bd9 LC |
7490 | Another example is a file system that depends on a mapped device, for |
7491 | example for an encrypted partition (@pxref{Mapped Devices}). | |
cf4a9129 LC |
7492 | @end table |
7493 | @end deftp | |
da7cabd4 | 7494 | |
a69576ea LC |
7495 | The @code{(gnu system file-systems)} exports the following useful |
7496 | variables. | |
7497 | ||
7498 | @defvr {Scheme Variable} %base-file-systems | |
7499 | These are essential file systems that are required on normal systems, | |
cc0e575a | 7500 | such as @var{%pseudo-terminal-file-system} and @var{%immutable-store} (see |
3392ce5d LC |
7501 | below.) Operating system declarations should always contain at least |
7502 | these. | |
a69576ea LC |
7503 | @end defvr |
7504 | ||
7f239fd3 LC |
7505 | @defvr {Scheme Variable} %pseudo-terminal-file-system |
7506 | This is the file system to be mounted as @file{/dev/pts}. It supports | |
7507 | @dfn{pseudo-terminals} created @i{via} @code{openpty} and similar | |
7508 | functions (@pxref{Pseudo-Terminals,,, libc, The GNU C Library Reference | |
7509 | Manual}). Pseudo-terminals are used by terminal emulators such as | |
7510 | @command{xterm}. | |
7511 | @end defvr | |
7512 | ||
db17ae5c LC |
7513 | @defvr {Scheme Variable} %shared-memory-file-system |
7514 | This file system is mounted as @file{/dev/shm} and is used to support | |
7515 | memory sharing across processes (@pxref{Memory-mapped I/O, | |
7516 | @code{shm_open},, libc, The GNU C Library Reference Manual}). | |
7517 | @end defvr | |
7518 | ||
3392ce5d LC |
7519 | @defvr {Scheme Variable} %immutable-store |
7520 | This file system performs a read-only ``bind mount'' of | |
7521 | @file{/gnu/store}, making it read-only for all the users including | |
7522 | @code{root}. This prevents against accidental modification by software | |
7523 | running as @code{root} or by system administrators. | |
7524 | ||
7525 | The daemon itself is still able to write to the store: it remounts it | |
7526 | read-write in its own ``name space.'' | |
7527 | @end defvr | |
7528 | ||
a69576ea LC |
7529 | @defvr {Scheme Variable} %binary-format-file-system |
7530 | The @code{binfmt_misc} file system, which allows handling of arbitrary | |
7531 | executable file types to be delegated to user space. This requires the | |
7532 | @code{binfmt.ko} kernel module to be loaded. | |
7533 | @end defvr | |
7534 | ||
7535 | @defvr {Scheme Variable} %fuse-control-file-system | |
7536 | The @code{fusectl} file system, which allows unprivileged users to mount | |
7537 | and unmount user-space FUSE file systems. This requires the | |
7538 | @code{fuse.ko} kernel module to be loaded. | |
7539 | @end defvr | |
7540 | ||
510f9d86 LC |
7541 | @node Mapped Devices |
7542 | @subsection Mapped Devices | |
7543 | ||
7544 | @cindex device mapping | |
7545 | @cindex mapped devices | |
7546 | The Linux kernel has a notion of @dfn{device mapping}: a block device, | |
7547 | such as a hard disk partition, can be @dfn{mapped} into another device, | |
97c8aef1 | 7548 | usually in @code{/dev/mapper/}, |
510f9d86 LC |
7549 | with additional processing over the data that flows through |
7550 | it@footnote{Note that the GNU@tie{}Hurd makes no difference between the | |
7551 | concept of a ``mapped device'' and that of a file system: both boil down | |
7552 | to @emph{translating} input/output operations made on a file to | |
7553 | operations on its backing store. Thus, the Hurd implements mapped | |
7554 | devices, like file systems, using the generic @dfn{translator} mechanism | |
7555 | (@pxref{Translators,,, hurd, The GNU Hurd Reference Manual}).}. A | |
7556 | typical example is encryption device mapping: all writes to the mapped | |
7557 | device are encrypted, and all reads are deciphered, transparently. | |
97c8aef1 AE |
7558 | Guix extends this notion by considering any device or set of devices that |
7559 | are @dfn{transformed} in some way to create a new device; for instance, | |
7560 | RAID devices are obtained by @dfn{assembling} several other devices, such | |
7561 | as hard disks or partitions, into a new one that behaves as one partition. | |
7562 | Other examples, not yet implemented, are LVM logical volumes. | |
510f9d86 | 7563 | |
97c8aef1 AE |
7564 | Mapped devices are declared using the @code{mapped-device} form, |
7565 | defined as follows; for examples, see below. | |
510f9d86 LC |
7566 | |
7567 | @deftp {Data Type} mapped-device | |
7568 | Objects of this type represent device mappings that will be made when | |
7569 | the system boots up. | |
7570 | ||
9cb426b8 LC |
7571 | @table @code |
7572 | @item source | |
97c8aef1 AE |
7573 | This is either a string specifying the name of the block device to be mapped, |
7574 | such as @code{"/dev/sda3"}, or a list of such strings when several devices | |
7575 | need to be assembled for creating a new one. | |
510f9d86 | 7576 | |
9cb426b8 | 7577 | @item target |
97c8aef1 AE |
7578 | This string specifies the name of the resulting mapped device. For |
7579 | kernel mappers such as encrypted devices of type @code{luks-device-mapping}, | |
7580 | specifying @code{"my-partition"} leads to the creation of | |
510f9d86 | 7581 | the @code{"/dev/mapper/my-partition"} device. |
97c8aef1 AE |
7582 | For RAID devices of type @code{raid-device-mapping}, the full device name |
7583 | such as @code{"/dev/md0"} needs to be given. | |
510f9d86 | 7584 | |
9cb426b8 | 7585 | @item type |
510f9d86 LC |
7586 | This must be a @code{mapped-device-kind} object, which specifies how |
7587 | @var{source} is mapped to @var{target}. | |
7588 | @end table | |
7589 | @end deftp | |
7590 | ||
7591 | @defvr {Scheme Variable} luks-device-mapping | |
7592 | This defines LUKS block device encryption using the @command{cryptsetup} | |
1068f26b | 7593 | command from the package with the same name. It relies on the |
510f9d86 LC |
7594 | @code{dm-crypt} Linux kernel module. |
7595 | @end defvr | |
7596 | ||
97c8aef1 AE |
7597 | @defvr {Scheme Variable} raid-device-mapping |
7598 | This defines a RAID device, which is assembled using the @code{mdadm} | |
7599 | command from the package with the same name. It requires a Linux kernel | |
7600 | module for the appropriate RAID level to be loaded, such as @code{raid456} | |
7601 | for RAID-4, RAID-5 or RAID-6, or @code{raid10} for RAID-10. | |
7602 | @end defvr | |
7603 | ||
7604 | @cindex disk encryption | |
7605 | @cindex LUKS | |
7606 | The following example specifies a mapping from @file{/dev/sda3} to | |
7607 | @file{/dev/mapper/home} using LUKS---the | |
7608 | @url{http://code.google.com/p/cryptsetup,Linux Unified Key Setup}, a | |
7609 | standard mechanism for disk encryption. | |
7610 | The @file{/dev/mapper/home} | |
7611 | device can then be used as the @code{device} of a @code{file-system} | |
7612 | declaration (@pxref{File Systems}). | |
7613 | ||
7614 | @example | |
7615 | (mapped-device | |
7616 | (source "/dev/sda3") | |
7617 | (target "home") | |
7618 | (type luks-device-mapping)) | |
7619 | @end example | |
7620 | ||
7621 | Alternatively, to become independent of device numbering, one may obtain | |
7622 | the LUKS UUID (@dfn{unique identifier}) of the source device by a | |
7623 | command like: | |
7624 | ||
7625 | @example | |
7626 | cryptsetup luksUUID /dev/sda3 | |
7627 | @end example | |
7628 | ||
7629 | and use it as follows: | |
7630 | ||
7631 | @example | |
7632 | (mapped-device | |
7633 | (source (uuid "cb67fc72-0d54-4c88-9d4b-b225f30b0f44")) | |
7634 | (target "home") | |
7635 | (type luks-device-mapping)) | |
7636 | @end example | |
7637 | ||
7638 | A RAID device formed of the partitions @file{/dev/sda1} and @file{/dev/sdb1} | |
7639 | may be declared as follows: | |
7640 | ||
7641 | @example | |
7642 | (mapped-device | |
7643 | (source (list "/dev/sda1" "/dev/sdb1")) | |
7644 | (target "/dev/md0") | |
7645 | (type raid-device-mapping)) | |
7646 | @end example | |
7647 | ||
7648 | The @file{/dev/md0} device can then be used as the @code{device} of a | |
7649 | @code{file-system} declaration (@pxref{File Systems}). | |
7650 | Note that the RAID level need not be given; it is chosen during the | |
7651 | initial creation and formatting of the RAID device and is determined | |
7652 | automatically later. | |
7653 | ||
7654 | ||
cf4a9129 LC |
7655 | @node User Accounts |
7656 | @subsection User Accounts | |
ee85f3db | 7657 | |
e32171ee JD |
7658 | @cindex users |
7659 | @cindex accounts | |
7660 | @cindex user accounts | |
9bea87a5 LC |
7661 | User accounts and groups are entirely managed through the |
7662 | @code{operating-system} declaration. They are specified with the | |
7663 | @code{user-account} and @code{user-group} forms: | |
ee85f3db | 7664 | |
cf4a9129 LC |
7665 | @example |
7666 | (user-account | |
7667 | (name "alice") | |
7668 | (group "users") | |
24e752c0 LC |
7669 | (supplementary-groups '("wheel" ;allow use of sudo, etc. |
7670 | "audio" ;sound card | |
7671 | "video" ;video devices such as webcams | |
7672 | "cdrom")) ;the good ol' CD-ROM | |
cf4a9129 LC |
7673 | (comment "Bob's sister") |
7674 | (home-directory "/home/alice")) | |
7675 | @end example | |
25083588 | 7676 | |
9bea87a5 LC |
7677 | When booting or upon completion of @command{guix system reconfigure}, |
7678 | the system ensures that only the user accounts and groups specified in | |
7679 | the @code{operating-system} declaration exist, and with the specified | |
7680 | properties. Thus, account or group creations or modifications made by | |
7681 | directly invoking commands such as @command{useradd} are lost upon | |
7682 | reconfiguration or reboot. This ensures that the system remains exactly | |
7683 | as declared. | |
7684 | ||
cf4a9129 LC |
7685 | @deftp {Data Type} user-account |
7686 | Objects of this type represent user accounts. The following members may | |
7687 | be specified: | |
ee85f3db | 7688 | |
cf4a9129 LC |
7689 | @table @asis |
7690 | @item @code{name} | |
7691 | The name of the user account. | |
ee85f3db | 7692 | |
cf4a9129 | 7693 | @item @code{group} |
e32171ee | 7694 | @cindex groups |
cf4a9129 LC |
7695 | This is the name (a string) or identifier (a number) of the user group |
7696 | this account belongs to. | |
ee85f3db | 7697 | |
cf4a9129 LC |
7698 | @item @code{supplementary-groups} (default: @code{'()}) |
7699 | Optionally, this can be defined as a list of group names that this | |
7700 | account belongs to. | |
ee85f3db | 7701 | |
cf4a9129 LC |
7702 | @item @code{uid} (default: @code{#f}) |
7703 | This is the user ID for this account (a number), or @code{#f}. In the | |
7704 | latter case, a number is automatically chosen by the system when the | |
7705 | account is created. | |
ee85f3db | 7706 | |
cf4a9129 | 7707 | @item @code{comment} (default: @code{""}) |
1068f26b | 7708 | A comment about the account, such as the account owner's full name. |
c8c871d1 | 7709 | |
cf4a9129 LC |
7710 | @item @code{home-directory} |
7711 | This is the name of the home directory for the account. | |
ee85f3db | 7712 | |
eb56ee02 LC |
7713 | @item @code{create-home-directory?} (default: @code{#t}) |
7714 | Indicates whether the home directory of this account should be created | |
7715 | if it does not exist yet. | |
7716 | ||
cf4a9129 LC |
7717 | @item @code{shell} (default: Bash) |
7718 | This is a G-expression denoting the file name of a program to be used as | |
7719 | the shell (@pxref{G-Expressions}). | |
ee85f3db | 7720 | |
cf4a9129 LC |
7721 | @item @code{system?} (default: @code{#f}) |
7722 | This Boolean value indicates whether the account is a ``system'' | |
7723 | account. System accounts are sometimes treated specially; for instance, | |
7724 | graphical login managers do not list them. | |
ee85f3db | 7725 | |
1bd4e6db | 7726 | @anchor{user-account-password} |
cf4a9129 | 7727 | @item @code{password} (default: @code{#f}) |
eb59595c LC |
7728 | You would normally leave this field to @code{#f}, initialize user |
7729 | passwords as @code{root} with the @command{passwd} command, and then let | |
9bea87a5 LC |
7730 | users change it with @command{passwd}. Passwords set with |
7731 | @command{passwd} are of course preserved across reboot and | |
7732 | reconfiguration. | |
eb59595c LC |
7733 | |
7734 | If you @emph{do} want to have a preset password for an account, then | |
7735 | this field must contain the encrypted password, as a string. | |
5d1f1177 LC |
7736 | @xref{crypt,,, libc, The GNU C Library Reference Manual}, for more information |
7737 | on password encryption, and @ref{Encryption,,, guile, GNU Guile Reference | |
eb59595c | 7738 | Manual}, for information on Guile's @code{crypt} procedure. |
c8c871d1 | 7739 | |
cf4a9129 LC |
7740 | @end table |
7741 | @end deftp | |
ee85f3db | 7742 | |
e32171ee | 7743 | @cindex groups |
cf4a9129 | 7744 | User group declarations are even simpler: |
ee85f3db | 7745 | |
cf4a9129 LC |
7746 | @example |
7747 | (user-group (name "students")) | |
7748 | @end example | |
ee85f3db | 7749 | |
cf4a9129 LC |
7750 | @deftp {Data Type} user-group |
7751 | This type is for, well, user groups. There are just a few fields: | |
af8a56b8 | 7752 | |
cf4a9129 LC |
7753 | @table @asis |
7754 | @item @code{name} | |
1068f26b | 7755 | The name of the group. |
ee85f3db | 7756 | |
cf4a9129 LC |
7757 | @item @code{id} (default: @code{#f}) |
7758 | The group identifier (a number). If @code{#f}, a new number is | |
7759 | automatically allocated when the group is created. | |
ee85f3db | 7760 | |
c8fa3426 LC |
7761 | @item @code{system?} (default: @code{#f}) |
7762 | This Boolean value indicates whether the group is a ``system'' group. | |
7763 | System groups have low numerical IDs. | |
7764 | ||
cf4a9129 LC |
7765 | @item @code{password} (default: @code{#f}) |
7766 | What, user groups can have a password? Well, apparently yes. Unless | |
1068f26b | 7767 | @code{#f}, this field specifies the password of the group. |
ee85f3db | 7768 | |
cf4a9129 LC |
7769 | @end table |
7770 | @end deftp | |
401c53c4 | 7771 | |
cf4a9129 LC |
7772 | For convenience, a variable lists all the basic user groups one may |
7773 | expect: | |
401c53c4 | 7774 | |
cf4a9129 LC |
7775 | @defvr {Scheme Variable} %base-groups |
7776 | This is the list of basic user groups that users and/or packages expect | |
7777 | to be present on the system. This includes groups such as ``root'', | |
7778 | ``wheel'', and ``users'', as well as groups used to control access to | |
7779 | specific devices such as ``audio'', ``disk'', and ``cdrom''. | |
7780 | @end defvr | |
401c53c4 | 7781 | |
bf87f38a LC |
7782 | @defvr {Scheme Variable} %base-user-accounts |
7783 | This is the list of basic system accounts that programs may expect to | |
7784 | find on a GNU/Linux system, such as the ``nobody'' account. | |
7785 | ||
7786 | Note that the ``root'' account is not included here. It is a | |
7787 | special-case and is automatically added whether or not it is specified. | |
7788 | @end defvr | |
7789 | ||
598e19dc LC |
7790 | @node Locales |
7791 | @subsection Locales | |
7792 | ||
7793 | @cindex locale | |
7794 | A @dfn{locale} defines cultural conventions for a particular language | |
7795 | and region of the world (@pxref{Locales,,, libc, The GNU C Library | |
7796 | Reference Manual}). Each locale has a name that typically has the form | |
b2636518 | 7797 | @code{@var{language}_@var{territory}.@var{codeset}}---e.g., |
598e19dc LC |
7798 | @code{fr_LU.utf8} designates the locale for the French language, with |
7799 | cultural conventions from Luxembourg, and using the UTF-8 encoding. | |
7800 | ||
7801 | @cindex locale definition | |
7802 | Usually, you will want to specify the default locale for the machine | |
7803 | using the @code{locale} field of the @code{operating-system} declaration | |
7804 | (@pxref{operating-system Reference, @code{locale}}). | |
7805 | ||
f5582b2c LC |
7806 | The selected locale is automatically added to the @dfn{locale |
7807 | definitions} known to the system if needed, with its codeset inferred | |
7808 | from its name---e.g., @code{bo_CN.utf8} will be assumed to use the | |
7809 | @code{UTF-8} codeset. Additional locale definitions can be specified in | |
7810 | the @code{locale-definitions} slot of @code{operating-system}---this is | |
7811 | useful, for instance, if the codeset could not be inferred from the | |
7812 | locale name. The default set of locale definitions includes some widely | |
7813 | used locales, but not all the available locales, in order to save space. | |
7814 | ||
7815 | For instance, to add the North Frisian locale for Germany, the value of | |
7816 | that field may be: | |
598e19dc LC |
7817 | |
7818 | @example | |
7819 | (cons (locale-definition | |
7820 | (name "fy_DE.utf8") (source "fy_DE")) | |
7821 | %default-locale-definitions) | |
7822 | @end example | |
7823 | ||
7824 | Likewise, to save space, one might want @code{locale-definitions} to | |
7825 | list only the locales that are actually used, as in: | |
7826 | ||
7827 | @example | |
7828 | (list (locale-definition | |
7829 | (name "ja_JP.eucjp") (source "ja_JP") | |
7830 | (charset "EUC-JP"))) | |
7831 | @end example | |
7832 | ||
5c3c1427 LC |
7833 | @vindex LOCPATH |
7834 | The compiled locale definitions are available at | |
46bd6edd LC |
7835 | @file{/run/current-system/locale/X.Y}, where @code{X.Y} is the libc |
7836 | version, which is the default location where the GNU@tie{}libc provided | |
7837 | by Guix looks for locale data. This can be overridden using the | |
7838 | @code{LOCPATH} environment variable (@pxref{locales-and-locpath, | |
5c3c1427 LC |
7839 | @code{LOCPATH} and locale packages}). |
7840 | ||
598e19dc LC |
7841 | The @code{locale-definition} form is provided by the @code{(gnu system |
7842 | locale)} module. Details are given below. | |
7843 | ||
7844 | @deftp {Data Type} locale-definition | |
7845 | This is the data type of a locale definition. | |
7846 | ||
7847 | @table @asis | |
7848 | ||
7849 | @item @code{name} | |
7850 | The name of the locale. @xref{Locale Names,,, libc, The GNU C Library | |
7851 | Reference Manual}, for more information on locale names. | |
7852 | ||
7853 | @item @code{source} | |
7854 | The name of the source for that locale. This is typically the | |
7855 | @code{@var{language}_@var{territory}} part of the locale name. | |
7856 | ||
7857 | @item @code{charset} (default: @code{"UTF-8"}) | |
7858 | The ``character set'' or ``code set'' for that locale, | |
7859 | @uref{http://www.iana.org/assignments/character-sets, as defined by | |
7860 | IANA}. | |
7861 | ||
7862 | @end table | |
7863 | @end deftp | |
7864 | ||
7865 | @defvr {Scheme Variable} %default-locale-definitions | |
1068f26b | 7866 | A list of commonly used UTF-8 locales, used as the default |
b2636518 | 7867 | value of the @code{locale-definitions} field of @code{operating-system} |
598e19dc | 7868 | declarations. |
b2636518 LC |
7869 | |
7870 | @cindex locale name | |
7871 | @cindex normalized codeset in locale names | |
7872 | These locale definitions use the @dfn{normalized codeset} for the part | |
7873 | that follows the dot in the name (@pxref{Using gettextized software, | |
7874 | normalized codeset,, libc, The GNU C Library Reference Manual}). So for | |
7875 | instance it has @code{uk_UA.utf8} but @emph{not}, say, | |
7876 | @code{uk_UA.UTF-8}. | |
598e19dc | 7877 | @end defvr |
401c53c4 | 7878 | |
34760ae7 LC |
7879 | @subsubsection Locale Data Compatibility Considerations |
7880 | ||
7881 | @cindex incompatibility, of locale data | |
7882 | @code{operating-system} declarations provide a @code{locale-libcs} field | |
7883 | to specify the GNU@tie{}libc packages that are used to compile locale | |
7884 | declarations (@pxref{operating-system Reference}). ``Why would I | |
7885 | care?'', you may ask. Well, it turns out that the binary format of | |
7886 | locale data is occasionally incompatible from one libc version to | |
7887 | another. | |
7888 | ||
7889 | @c See <https://sourceware.org/ml/libc-alpha/2015-09/msg00575.html> | |
7890 | @c and <https://lists.gnu.org/archive/html/guix-devel/2015-08/msg00737.html>. | |
7891 | For instance, a program linked against libc version 2.21 is unable to | |
7892 | read locale data produced with libc 2.22; worse, that program | |
7893 | @emph{aborts} instead of simply ignoring the incompatible locale | |
7894 | data@footnote{Versions 2.23 and later of GNU@tie{}libc will simply skip | |
7895 | the incompatible locale data, which is already an improvement.}. | |
7896 | Similarly, a program linked against libc 2.22 can read most, but not | |
201fff9e | 7897 | all, of the locale data from libc 2.21 (specifically, @code{LC_COLLATE} |
34760ae7 LC |
7898 | data is incompatible); thus calls to @code{setlocale} may fail, but |
7899 | programs will not abort. | |
7900 | ||
7901 | The ``problem'' in GuixSD is that users have a lot of freedom: They can | |
7902 | choose whether and when to upgrade software in their profiles, and might | |
7903 | be using a libc version different from the one the system administrator | |
7904 | used to build the system-wide locale data. | |
7905 | ||
7906 | Fortunately, unprivileged users can also install their own locale data | |
7907 | and define @var{GUIX_LOCPATH} accordingly (@pxref{locales-and-locpath, | |
7908 | @code{GUIX_LOCPATH} and locale packages}). | |
7909 | ||
7910 | Still, it is best if the system-wide locale data at | |
7911 | @file{/run/current-system/locale} is built for all the libc versions | |
7912 | actually in use on the system, so that all the programs can access | |
7913 | it---this is especially crucial on a multi-user system. To do that, the | |
7914 | administrator can specify several libc packages in the | |
7915 | @code{locale-libcs} field of @code{operating-system}: | |
7916 | ||
7917 | @example | |
7918 | (use-package-modules base) | |
7919 | ||
7920 | (operating-system | |
7921 | ;; @dots{} | |
7922 | (locale-libcs (list glibc-2.21 (canonical-package glibc)))) | |
7923 | @end example | |
7924 | ||
7925 | This example would lead to a system containing locale definitions for | |
7926 | both libc 2.21 and the current version of libc in | |
7927 | @file{/run/current-system/locale}. | |
7928 | ||
7929 | ||
cf4a9129 LC |
7930 | @node Services |
7931 | @subsection Services | |
401c53c4 | 7932 | |
cf4a9129 LC |
7933 | @cindex system services |
7934 | An important part of preparing an @code{operating-system} declaration is | |
7935 | listing @dfn{system services} and their configuration (@pxref{Using the | |
7936 | Configuration System}). System services are typically daemons launched | |
7937 | when the system boots, or other actions needed at that time---e.g., | |
d8b94dbd LC |
7938 | configuring network access. |
7939 | ||
e8b652d4 LC |
7940 | GuixSD has a broad definition of ``service'' (@pxref{Service |
7941 | Composition}), but many services are managed by the GNU@tie{}Shepherd | |
7942 | (@pxref{Shepherd Services}). On a running system, the @command{herd} | |
7943 | command allows you to list the available services, show their status, | |
7944 | start and stop them, or do other specific operations (@pxref{Jump | |
7945 | Start,,, shepherd, The GNU Shepherd Manual}). For example: | |
d8b94dbd LC |
7946 | |
7947 | @example | |
dd17bc38 | 7948 | # herd status |
d8b94dbd LC |
7949 | @end example |
7950 | ||
7951 | The above command, run as @code{root}, lists the currently defined | |
dd17bc38 | 7952 | services. The @command{herd doc} command shows a synopsis of the given |
d8b94dbd LC |
7953 | service: |
7954 | ||
7955 | @example | |
dd17bc38 | 7956 | # herd doc nscd |
d8b94dbd LC |
7957 | Run libc's name service cache daemon (nscd). |
7958 | @end example | |
7959 | ||
7960 | The @command{start}, @command{stop}, and @command{restart} sub-commands | |
7961 | have the effect you would expect. For instance, the commands below stop | |
7962 | the nscd service and restart the Xorg display server: | |
7963 | ||
7964 | @example | |
dd17bc38 | 7965 | # herd stop nscd |
d8b94dbd | 7966 | Service nscd has been stopped. |
dd17bc38 | 7967 | # herd restart xorg-server |
d8b94dbd LC |
7968 | Service xorg-server has been stopped. |
7969 | Service xorg-server has been started. | |
7970 | @end example | |
401c53c4 | 7971 | |
cf4a9129 | 7972 | The following sections document the available services, starting with |
d8b94dbd LC |
7973 | the core services, that may be used in an @code{operating-system} |
7974 | declaration. | |
401c53c4 | 7975 | |
cf4a9129 LC |
7976 | @menu |
7977 | * Base Services:: Essential system services. | |
c311089b | 7978 | * Scheduled Job Execution:: The mcron service. |
92c03a87 | 7979 | * Log Rotation:: The rottlog service. |
cf4a9129 LC |
7980 | * Networking Services:: Network setup, SSH daemon, etc. |
7981 | * X Window:: Graphical display. | |
f2ec23d1 | 7982 | * Printing Services:: Local and remote printer support. |
fe1a39d3 | 7983 | * Desktop Services:: D-Bus and desktop services. |
105369a4 | 7984 | * Database Services:: SQL databases. |
d8c18af8 | 7985 | * Mail Services:: IMAP, POP3, SMTP, and all that. |
859e367d | 7986 | * Kerberos Services:: Kerberos services. |
58724c48 | 7987 | * Web Services:: Web servers. |
eb419bc9 | 7988 | * Network File System:: NFS related services. |
a7cf4eb6 | 7989 | * Continuous Integration:: The Cuirass service. |
dbc6d370 | 7990 | * Miscellaneous Services:: Other services. |
cf4a9129 | 7991 | @end menu |
401c53c4 | 7992 | |
cf4a9129 LC |
7993 | @node Base Services |
7994 | @subsubsection Base Services | |
a1ba8475 | 7995 | |
cf4a9129 LC |
7996 | The @code{(gnu services base)} module provides definitions for the basic |
7997 | services that one expects from the system. The services exported by | |
7998 | this module are listed below. | |
401c53c4 | 7999 | |
cf4a9129 | 8000 | @defvr {Scheme Variable} %base-services |
31771497 LC |
8001 | This variable contains a list of basic services (@pxref{Service Types |
8002 | and Services}, for more information on service objects) one would | |
cf4a9129 | 8003 | expect from the system: a login service (mingetty) on each tty, syslogd, |
1068f26b | 8004 | the libc name service cache daemon (nscd), the udev device manager, and |
cf4a9129 | 8005 | more. |
401c53c4 | 8006 | |
cf4a9129 LC |
8007 | This is the default value of the @code{services} field of |
8008 | @code{operating-system} declarations. Usually, when customizing a | |
8009 | system, you will want to append services to @var{%base-services}, like | |
8010 | this: | |
401c53c4 | 8011 | |
cf4a9129 | 8012 | @example |
fa1e31b8 | 8013 | (cons* (avahi-service) (lsh-service) %base-services) |
cf4a9129 LC |
8014 | @end example |
8015 | @end defvr | |
401c53c4 | 8016 | |
be1c2c54 | 8017 | @deffn {Scheme Procedure} host-name-service @var{name} |
cf4a9129 LC |
8018 | Return a service that sets the host name to @var{name}. |
8019 | @end deffn | |
401c53c4 | 8020 | |
317d3b47 DC |
8021 | @deffn {Scheme Procedure} login-service @var{config} |
8022 | Return a service to run login according to @var{config}, a | |
8023 | @code{<login-configuration>} object, which specifies the message of the day, | |
8024 | among other things. | |
8025 | @end deffn | |
8026 | ||
8027 | @deftp {Data Type} login-configuration | |
8028 | This is the data type representing the configuration of login. | |
8029 | ||
8030 | @table @asis | |
8031 | ||
8032 | @item @code{motd} | |
e32171ee | 8033 | @cindex message of the day |
317d3b47 DC |
8034 | A file-like object containing the ``message of the day''. |
8035 | ||
8036 | @item @code{allow-empty-passwords?} (default: @code{#t}) | |
8037 | Allow empty passwords by default so that first-time users can log in when | |
8038 | the 'root' account has just been created. | |
8039 | ||
8040 | @end table | |
8041 | @end deftp | |
8042 | ||
66e4f01c LC |
8043 | @deffn {Scheme Procedure} mingetty-service @var{config} |
8044 | Return a service to run mingetty according to @var{config}, a | |
8045 | @code{<mingetty-configuration>} object, which specifies the tty to run, among | |
8046 | other things. | |
cf4a9129 | 8047 | @end deffn |
401c53c4 | 8048 | |
66e4f01c LC |
8049 | @deftp {Data Type} mingetty-configuration |
8050 | This is the data type representing the configuration of Mingetty, which | |
8051 | implements console log-in. | |
8052 | ||
8053 | @table @asis | |
8054 | ||
8055 | @item @code{tty} | |
8056 | The name of the console this Mingetty runs on---e.g., @code{"tty1"}. | |
8057 | ||
66e4f01c LC |
8058 | @item @code{auto-login} (default: @code{#f}) |
8059 | When true, this field must be a string denoting the user name under | |
f9b9a033 | 8060 | which the system automatically logs in. When it is @code{#f}, a |
66e4f01c LC |
8061 | user name and password must be entered to log in. |
8062 | ||
8063 | @item @code{login-program} (default: @code{#f}) | |
8064 | This must be either @code{#f}, in which case the default log-in program | |
8065 | is used (@command{login} from the Shadow tool suite), or a gexp denoting | |
8066 | the name of the log-in program. | |
8067 | ||
8068 | @item @code{login-pause?} (default: @code{#f}) | |
8069 | When set to @code{#t} in conjunction with @var{auto-login}, the user | |
8070 | will have to press a key before the log-in shell is launched. | |
8071 | ||
8072 | @item @code{mingetty} (default: @var{mingetty}) | |
8073 | The Mingetty package to use. | |
8074 | ||
8075 | @end table | |
8076 | @end deftp | |
8077 | ||
46ec2707 DC |
8078 | @deffn {Scheme Procedure} kmscon-service-type @var{config} |
8079 | Return a service to run @uref{https://www.freedesktop.org/wiki/Software/kmscon,kmscon} | |
8080 | according to @var{config}, a @code{<kmscon-configuration>} object, which | |
8081 | specifies the tty to run, among other things. | |
8082 | @end deffn | |
8083 | ||
8084 | @deftp {Data Type} kmscon-configuration | |
8085 | This is the data type representing the configuration of Kmscon, which | |
8086 | implements console log-in. | |
8087 | ||
8088 | @table @asis | |
8089 | ||
8090 | @item @code{virtual-terminal} | |
8091 | The name of the console this Kmscon runs on---e.g., @code{"tty1"}. | |
8092 | ||
8093 | @item @code{login-program} (default: @code{#~(string-append #$shadow "/bin/login")}) | |
8094 | A gexp denoting the name of the log-in program. The default log-in program is | |
8095 | @command{login} from the Shadow tool suite. | |
8096 | ||
8097 | @item @code{login-arguments} (default: @code{'("-p")}) | |
8098 | A list of arguments to pass to @command{login}. | |
8099 | ||
8100 | @item @code{hardware-acceleration?} (default: #f) | |
8101 | Whether to use hardware acceleration. | |
8102 | ||
8103 | @item @code{kmscon} (default: @var{kmscon}) | |
8104 | The Kmscon package to use. | |
8105 | ||
8106 | @end table | |
8107 | @end deftp | |
8108 | ||
6454b333 LC |
8109 | @cindex name service cache daemon |
8110 | @cindex nscd | |
be1c2c54 | 8111 | @deffn {Scheme Procedure} nscd-service [@var{config}] [#:glibc glibc] @ |
4aee6e60 | 8112 | [#:name-services '()] |
1068f26b | 8113 | Return a service that runs the libc name service cache daemon (nscd) with the |
b893f1ae LC |
8114 | given @var{config}---an @code{<nscd-configuration>} object. @xref{Name |
8115 | Service Switch}, for an example. | |
cf4a9129 | 8116 | @end deffn |
401c53c4 | 8117 | |
6454b333 LC |
8118 | @defvr {Scheme Variable} %nscd-default-configuration |
8119 | This is the default @code{<nscd-configuration>} value (see below) used | |
1068f26b | 8120 | by @code{nscd-service}. It uses the caches defined by |
6454b333 LC |
8121 | @var{%nscd-default-caches}; see below. |
8122 | @end defvr | |
8123 | ||
8124 | @deftp {Data Type} nscd-configuration | |
1068f26b | 8125 | This is the data type representing the name service cache daemon (nscd) |
6454b333 LC |
8126 | configuration. |
8127 | ||
8128 | @table @asis | |
8129 | ||
b893f1ae LC |
8130 | @item @code{name-services} (default: @code{'()}) |
8131 | List of packages denoting @dfn{name services} that must be visible to | |
8132 | the nscd---e.g., @code{(list @var{nss-mdns})}. | |
8133 | ||
8134 | @item @code{glibc} (default: @var{glibc}) | |
8135 | Package object denoting the GNU C Library providing the @command{nscd} | |
8136 | command. | |
8137 | ||
6454b333 | 8138 | @item @code{log-file} (default: @code{"/var/log/nscd.log"}) |
1068f26b | 8139 | Name of the nscd log file. This is where debugging output goes when |
6454b333 LC |
8140 | @code{debug-level} is strictly positive. |
8141 | ||
8142 | @item @code{debug-level} (default: @code{0}) | |
1068f26b | 8143 | Integer denoting the debugging levels. Higher numbers mean that more |
6454b333 LC |
8144 | debugging output is logged. |
8145 | ||
8146 | @item @code{caches} (default: @var{%nscd-default-caches}) | |
8147 | List of @code{<nscd-cache>} objects denoting things to be cached; see | |
8148 | below. | |
8149 | ||
8150 | @end table | |
8151 | @end deftp | |
8152 | ||
8153 | @deftp {Data Type} nscd-cache | |
8154 | Data type representing a cache database of nscd and its parameters. | |
8155 | ||
8156 | @table @asis | |
8157 | ||
8158 | @item @code{database} | |
8159 | This is a symbol representing the name of the database to be cached. | |
8160 | Valid values are @code{passwd}, @code{group}, @code{hosts}, and | |
8161 | @code{services}, which designate the corresponding NSS database | |
8162 | (@pxref{NSS Basics,,, libc, The GNU C Library Reference Manual}). | |
8163 | ||
8164 | @item @code{positive-time-to-live} | |
8165 | @itemx @code{negative-time-to-live} (default: @code{20}) | |
8166 | A number representing the number of seconds during which a positive or | |
8167 | negative lookup result remains in cache. | |
8168 | ||
8169 | @item @code{check-files?} (default: @code{#t}) | |
8170 | Whether to check for updates of the files corresponding to | |
8171 | @var{database}. | |
8172 | ||
8173 | For instance, when @var{database} is @code{hosts}, setting this flag | |
8174 | instructs nscd to check for updates in @file{/etc/hosts} and to take | |
8175 | them into account. | |
8176 | ||
8177 | @item @code{persistent?} (default: @code{#t}) | |
8178 | Whether the cache should be stored persistently on disk. | |
8179 | ||
8180 | @item @code{shared?} (default: @code{#t}) | |
8181 | Whether the cache should be shared among users. | |
8182 | ||
8183 | @item @code{max-database-size} (default: 32@tie{}MiB) | |
8184 | Maximum size in bytes of the database cache. | |
8185 | ||
8186 | @c XXX: 'suggested-size' and 'auto-propagate?' seem to be expert | |
8187 | @c settings, so leave them out. | |
8188 | ||
8189 | @end table | |
8190 | @end deftp | |
8191 | ||
8192 | @defvr {Scheme Variable} %nscd-default-caches | |
8193 | List of @code{<nscd-cache>} objects used by default by | |
1068f26b | 8194 | @code{nscd-configuration} (see above). |
6454b333 LC |
8195 | |
8196 | It enables persistent and aggressive caching of service and host name | |
8197 | lookups. The latter provides better host name lookup performance, | |
8198 | resilience in the face of unreliable name servers, and also better | |
8199 | privacy---often the result of host name lookups is in local cache, so | |
8200 | external name servers do not even need to be queried. | |
8201 | @end defvr | |
8202 | ||
ec2e2f6c | 8203 | @anchor{syslog-configuration-type} |
e32171ee JD |
8204 | @cindex syslog |
8205 | @cindex logging | |
ec2e2f6c DC |
8206 | @deftp {Data Type} syslog-configuration |
8207 | This data type represents the configuration of the syslog daemon. | |
6454b333 | 8208 | |
ec2e2f6c DC |
8209 | @table @asis |
8210 | @item @code{syslogd} (default: @code{#~(string-append #$inetutils "/libexec/syslogd")}) | |
8211 | The syslog daemon to use. | |
8212 | ||
8213 | @item @code{config-file} (default: @code{%default-syslog.conf}) | |
8214 | The syslog configuration file to use. | |
8215 | ||
8216 | @end table | |
8217 | @end deftp | |
8218 | ||
8219 | @anchor{syslog-service} | |
e32171ee | 8220 | @cindex syslog |
ec2e2f6c DC |
8221 | @deffn {Scheme Procedure} syslog-service @var{config} |
8222 | Return a service that runs a syslog daemon according to @var{config}. | |
44abcb28 LC |
8223 | |
8224 | @xref{syslogd invocation,,, inetutils, GNU Inetutils}, for more | |
8225 | information on the configuration file syntax. | |
cf4a9129 | 8226 | @end deffn |
401c53c4 | 8227 | |
0adfe95a LC |
8228 | @anchor{guix-configuration-type} |
8229 | @deftp {Data Type} guix-configuration | |
8230 | This data type represents the configuration of the Guix build daemon. | |
8231 | @xref{Invoking guix-daemon}, for more information. | |
8232 | ||
8233 | @table @asis | |
8234 | @item @code{guix} (default: @var{guix}) | |
8235 | The Guix package to use. | |
401c53c4 | 8236 | |
0adfe95a LC |
8237 | @item @code{build-group} (default: @code{"guixbuild"}) |
8238 | Name of the group for build user accounts. | |
401c53c4 | 8239 | |
0adfe95a LC |
8240 | @item @code{build-accounts} (default: @code{10}) |
8241 | Number of build user accounts to create. | |
401c53c4 | 8242 | |
0adfe95a | 8243 | @item @code{authorize-key?} (default: @code{#t}) |
e32171ee | 8244 | @cindex substitutes, authorization thereof |
5b58c28b LC |
8245 | Whether to authorize the substitute keys listed in |
8246 | @code{authorized-keys}---by default that of @code{hydra.gnu.org} | |
0adfe95a LC |
8247 | (@pxref{Substitutes}). |
8248 | ||
5b58c28b LC |
8249 | @vindex %default-authorized-guix-keys |
8250 | @item @code{authorized-keys} (default: @var{%default-authorized-guix-keys}) | |
8251 | The list of authorized key files for archive imports, as a list of | |
8252 | string-valued gexps (@pxref{Invoking guix archive}). By default, it | |
8253 | contains that of @code{hydra.gnu.org} (@pxref{Substitutes}). | |
8254 | ||
0adfe95a LC |
8255 | @item @code{use-substitutes?} (default: @code{#t}) |
8256 | Whether to use substitutes. | |
8257 | ||
b0b9f6e0 LC |
8258 | @item @code{substitute-urls} (default: @var{%default-substitute-urls}) |
8259 | The list of URLs where to look for substitutes by default. | |
8260 | ||
0adfe95a LC |
8261 | @item @code{extra-options} (default: @code{'()}) |
8262 | List of extra command-line options for @command{guix-daemon}. | |
8263 | ||
8264 | @item @code{lsof} (default: @var{lsof}) | |
8265 | @itemx @code{lsh} (default: @var{lsh}) | |
8266 | The lsof and lsh packages to use. | |
8267 | ||
8268 | @end table | |
8269 | @end deftp | |
8270 | ||
8271 | @deffn {Scheme Procedure} guix-service @var{config} | |
8272 | Return a service that runs the Guix build daemon according to | |
8273 | @var{config}. | |
cf4a9129 | 8274 | @end deffn |
a1ba8475 | 8275 | |
be1c2c54 | 8276 | @deffn {Scheme Procedure} udev-service [#:udev udev] |
cf4a9129 LC |
8277 | Run @var{udev}, which populates the @file{/dev} directory dynamically. |
8278 | @end deffn | |
401c53c4 | 8279 | |
a535e122 LF |
8280 | @deffn {Scheme Procedure} urandom-seed-service @var{#f} |
8281 | Save some entropy in @var{%random-seed-file} to seed @file{/dev/urandom} | |
8282 | when rebooting. | |
8283 | @end deffn | |
8284 | ||
8285 | @defvr {Scheme Variable} %random-seed-file | |
8286 | This is the name of the file where some random bytes are saved by | |
8287 | @var{urandom-seed-service} to seed @file{/dev/urandom} when rebooting. | |
8288 | It defaults to @file{/var/lib/random-seed}. | |
8289 | @end defvr | |
8290 | ||
e32171ee JD |
8291 | @cindex keymap |
8292 | @cindex keyboard | |
b3d05f48 | 8293 | @deffn {Scheme Procedure} console-keymap-service @var{files} ... |
dedb8d5e | 8294 | @cindex keyboard layout |
b3d05f48 AK |
8295 | Return a service to load console keymaps from @var{files} using |
8296 | @command{loadkeys} command. Most likely, you want to load some default | |
8297 | keymap, which can be done like this: | |
8298 | ||
8299 | @example | |
8300 | (console-keymap-service "dvorak") | |
8301 | @end example | |
8302 | ||
8303 | Or, for example, for a Swedish keyboard, you may need to combine | |
8304 | the following keymaps: | |
8305 | @example | |
8306 | (console-keymap-service "se-lat6" "se-fi-lat6") | |
8307 | @end example | |
8308 | ||
8309 | Also you can specify a full file name (or file names) of your keymap(s). | |
8310 | See @code{man loadkeys} for details. | |
8311 | ||
5eca9459 AK |
8312 | @end deffn |
8313 | ||
e32171ee JD |
8314 | @cindex mouse |
8315 | @cindex gpm | |
1aaf116d | 8316 | @deffn {Scheme Procedure} gpm-service [#:gpm @var{gpm}] @ |
8664cc88 LC |
8317 | [#:options] |
8318 | Run @var{gpm}, the general-purpose mouse daemon, with the given | |
8319 | command-line @var{options}. GPM allows users to use the mouse in the console, | |
8320 | notably to select, copy, and paste text. The default value of @var{options} | |
8321 | uses the @code{ps2} protocol, which works for both USB and PS/2 mice. | |
8322 | ||
8323 | This service is not part of @var{%base-services}. | |
8324 | @end deffn | |
8325 | ||
1c52181f LC |
8326 | @anchor{guix-publish-service} |
8327 | @deffn {Scheme Procedure} guix-publish-service [#:guix @var{guix}] @ | |
8328 | [#:port 80] [#:host "localhost"] | |
8329 | Return a service that runs @command{guix publish} listening on @var{host} | |
8330 | and @var{port} (@pxref{Invoking guix publish}). | |
8331 | ||
8332 | This assumes that @file{/etc/guix} already contains a signing key pair as | |
8333 | created by @command{guix archive --generate-key} (@pxref{Invoking guix | |
8334 | archive}). If that is not the case, the service will fail to start. | |
8335 | @end deffn | |
8336 | ||
b58cbf9a DC |
8337 | @anchor{rngd-service} |
8338 | @deffn {Scheme Procedure} rngd-service [#:rng-tools @var{rng-tools}] @ | |
8339 | [#:device "/dev/hwrng"] | |
8340 | Return a service that runs the @command{rngd} program from @var{rng-tools} | |
8341 | to add @var{device} to the kernel's entropy pool. The service will fail if | |
8342 | @var{device} does not exist. | |
8343 | @end deffn | |
a69576ea | 8344 | |
909147e4 RW |
8345 | @anchor{pam-limits-service} |
8346 | @cindex session limits | |
8347 | @cindex ulimit | |
8348 | @cindex priority | |
8349 | @deffn {Scheme Procedure} pam-limits-service [#:limits @var{limits}] | |
8350 | ||
8351 | Return a service that installs a configuration file for the | |
8352 | @uref{http://linux-pam.org/Linux-PAM-html/sag-pam_limits.html, | |
8353 | @code{pam_limits} module}. The procedure optionally takes a list of | |
8354 | @code{pam-limits-entry} values, which can be used to specify | |
8355 | @code{ulimit} limits and nice priority limits to user sessions. | |
8356 | ||
8357 | The following limits definition sets two hard and soft limits for all | |
8358 | login sessions of users in the @code{realtime} group: | |
8359 | ||
8360 | @example | |
8361 | (pam-limits-service | |
8362 | (list | |
8363 | (pam-limits-entry "@@realtime" 'both 'rtprio 99) | |
8364 | (pam-limits-entry "@@realtime" 'both 'memlock 'unlimited))) | |
8365 | @end example | |
8366 | ||
8367 | The first entry increases the maximum realtime priority for | |
8368 | non-privileged processes; the second entry lifts any restriction of the | |
8369 | maximum address space that can be locked in memory. These settings are | |
8370 | commonly used for real-time audio systems. | |
8371 | @end deffn | |
8372 | ||
c311089b LC |
8373 | @node Scheduled Job Execution |
8374 | @subsubsection Scheduled Job Execution | |
8375 | ||
8376 | @cindex cron | |
e32171ee | 8377 | @cindex mcron |
c311089b LC |
8378 | @cindex scheduling jobs |
8379 | The @code{(gnu services mcron)} module provides an interface to | |
8380 | GNU@tie{}mcron, a daemon to run jobs at scheduled times (@pxref{Top,,, | |
8381 | mcron, GNU@tie{}mcron}). GNU@tie{}mcron is similar to the traditional | |
8382 | Unix @command{cron} daemon; the main difference is that it is | |
8383 | implemented in Guile Scheme, which provides a lot of flexibility when | |
8384 | specifying the scheduling of jobs and their actions. | |
8385 | ||
8ac6282c | 8386 | The example below defines an operating system that runs the |
c311089b | 8387 | @command{updatedb} (@pxref{Invoking updatedb,,, find, Finding Files}) |
8ac6282c LC |
8388 | and the @command{guix gc} commands (@pxref{Invoking guix gc}) daily, as |
8389 | well as the @command{mkid} command on behalf of an unprivileged user | |
8390 | (@pxref{mkid invocation,,, idutils, ID Database Utilities}). It uses | |
8391 | gexps to introduce job definitions that are passed to mcron | |
8392 | (@pxref{G-Expressions}). | |
c311089b LC |
8393 | |
8394 | @lisp | |
8395 | (use-modules (guix) (gnu) (gnu services mcron)) | |
8ac6282c | 8396 | (use-package-modules base idutils) |
c311089b LC |
8397 | |
8398 | (define updatedb-job | |
8ac6282c LC |
8399 | ;; Run 'updatedb' at 3AM every day. Here we write the |
8400 | ;; job's action as a Scheme procedure. | |
c311089b | 8401 | #~(job '(next-hour '(3)) |
8ac6282c LC |
8402 | (lambda () |
8403 | (execl (string-append #$findutils "/bin/updatedb") | |
8404 | "updatedb" | |
8405 | "--prunepaths=/tmp /var/tmp /gnu/store")))) | |
c311089b LC |
8406 | |
8407 | (define garbage-collector-job | |
8408 | ;; Collect garbage 5 minutes after midnight every day. | |
8ac6282c | 8409 | ;; The job's action is a shell command. |
c311089b LC |
8410 | #~(job "5 0 * * *" ;Vixie cron syntax |
8411 | "guix gc -F 1G")) | |
8412 | ||
80d944b7 | 8413 | (define idutils-job |
8ac6282c LC |
8414 | ;; Update the index database as user "charlie" at 12:15PM |
8415 | ;; and 19:15PM. This runs from the user's home directory. | |
8416 | #~(job '(next-minute-from (next-hour '(12 19)) '(15)) | |
8417 | (string-append #$idutils "/bin/mkid src") | |
8418 | #:user "charlie")) | |
8419 | ||
c311089b LC |
8420 | (operating-system |
8421 | ;; @dots{} | |
8422 | (services (cons (mcron-service (list garbage-collector-job | |
8ac6282c LC |
8423 | updatedb-job |
8424 | idutils-job)) | |
c311089b LC |
8425 | %base-services))) |
8426 | @end lisp | |
8427 | ||
8428 | @xref{Guile Syntax, mcron job specifications,, mcron, GNU@tie{}mcron}, | |
8429 | for more information on mcron job specifications. Below is the | |
8430 | reference of the mcron service. | |
8431 | ||
8432 | @deffn {Scheme Procedure} mcron-service @var{jobs} [#:mcron @var{mcron2}] | |
8433 | Return an mcron service running @var{mcron} that schedules @var{jobs}, a | |
8434 | list of gexps denoting mcron job specifications. | |
8435 | ||
8436 | This is a shorthand for: | |
8437 | @example | |
80d944b7 LC |
8438 | (service mcron-service-type |
8439 | (mcron-configuration (mcron mcron) (jobs jobs))) | |
c311089b LC |
8440 | @end example |
8441 | @end deffn | |
8442 | ||
8443 | @defvr {Scheme Variable} mcron-service-type | |
8444 | This is the type of the @code{mcron} service, whose value is an | |
8445 | @code{mcron-configuration} object. | |
8446 | ||
8447 | This service type can be the target of a service extension that provides | |
8448 | it additional job specifications (@pxref{Service Composition}). In | |
80d944b7 | 8449 | other words, it is possible to define services that provide additional |
c311089b LC |
8450 | mcron jobs to run. |
8451 | @end defvr | |
8452 | ||
8453 | @deftp {Data Type} mcron-configuration | |
8454 | Data type representing the configuration of mcron. | |
8455 | ||
8456 | @table @asis | |
8457 | @item @code{mcron} (default: @var{mcron2}) | |
8458 | The mcron package to use. | |
8459 | ||
8460 | @item @code{jobs} | |
8461 | This is a list of gexps (@pxref{G-Expressions}), where each gexp | |
8462 | corresponds to an mcron job specification (@pxref{Syntax, mcron job | |
8463 | specifications,, mcron, GNU@tie{}mcron}). | |
8464 | @end table | |
8465 | @end deftp | |
8466 | ||
8467 | ||
92c03a87 JN |
8468 | @node Log Rotation |
8469 | @subsubsection Log Rotation | |
8470 | ||
8471 | @cindex rottlog | |
8472 | @cindex log rotation | |
e32171ee | 8473 | @cindex logging |
92c03a87 JN |
8474 | Log files such as those found in @file{/var/log} tend to grow endlessly, |
8475 | so it's a good idea to @dfn{rotate} them once in a while---i.e., archive | |
8476 | their contents in separate files, possibly compressed. The @code{(gnu | |
8477 | services admin)} module provides an interface to GNU@tie{}Rot[t]log, a | |
8478 | log rotation tool (@pxref{Top,,, rottlog, GNU Rot[t]log Manual}). | |
8479 | ||
8480 | The example below defines an operating system that provides log rotation | |
8481 | with the default settings. | |
8482 | ||
8483 | @lisp | |
8484 | (use-modules (guix) (gnu)) | |
8485 | (use-service-modules admin mcron) | |
8486 | (use-package-modules base idutils) | |
8487 | ||
8488 | (operating-system | |
8489 | ;; @dots{} | |
8490 | (services (cons* (mcron-service) | |
8491 | (service rottlog-service-type (rottlog-configuration)) | |
8492 | %base-services))) | |
8493 | @end lisp | |
8494 | ||
8495 | @defvr {Scheme Variable} rottlog-service-type | |
8496 | This is the type of the Rottlog service, whose value is a | |
8497 | @code{rottlog-configuration} object. | |
8498 | ||
8499 | This service type can define mcron jobs (@pxref{Scheduled Job | |
8500 | Execution}) to run the rottlog service. | |
8501 | @end defvr | |
8502 | ||
8503 | @deftp {Data Type} rottlog-configuration | |
8504 | Data type representing the configuration of rottlog. | |
8505 | ||
8506 | @table @asis | |
8507 | @item @code{rottlog} (default: @code{rottlog}) | |
8508 | The Rottlog package to use. | |
8509 | ||
8510 | @item @code{rc-file} (default: @code{(file-append rottlog "/etc/rc")}) | |
8511 | The Rottlog configuration file to use (@pxref{Mandatory RC Variables,,, | |
8512 | rottlog, GNU Rot[t]log Manual}). | |
8513 | ||
8514 | @item @code{periodic-rotations} (default: @code{`(("weekly" %default-rotatations))}) | |
8515 | A list of Rottlog period-name/period-config tuples. | |
8516 | ||
8517 | For example, taking an example from the Rottlog manual (@pxref{Period | |
8518 | Related File Examples,,, rottlog, GNU Rot[t]log Manual}), a valid tuple | |
8519 | might be: | |
8520 | ||
8521 | @example | |
8522 | ("daily" ,(plain-file "daily" | |
8523 | "\ | |
8524 | /var/log/apache/* @{ | |
8525 | storedir apache-archives | |
8526 | rotate 6 | |
8527 | notifempty | |
8528 | nocompress | |
8529 | @}")) | |
8530 | @end example | |
8531 | ||
8532 | @item @code{jobs} | |
8533 | This is a list of gexps where each gexp corresponds to an mcron job | |
8534 | specification (@pxref{Scheduled Job Execution}). | |
8535 | @end table | |
8536 | @end deftp | |
8537 | ||
8538 | @defvr {Scheme Variable} %default-rotations | |
8539 | Specifies weekly rotation of @var{%rotated-files} and | |
8540 | @code{"/var/log/shepherd.log"}. | |
8541 | @end defvr | |
8542 | ||
8543 | @defvr {Scheme Variable} %rotated-files | |
8544 | The list of syslog-controlled files to be rotated. By default it is: | |
8545 | @code{'("/var/log/messages" "/var/log/secure")}. | |
8546 | @end defvr | |
8547 | ||
cf4a9129 LC |
8548 | @node Networking Services |
8549 | @subsubsection Networking Services | |
401c53c4 | 8550 | |
fa1e31b8 | 8551 | The @code{(gnu services networking)} module provides services to configure |
cf4a9129 | 8552 | the network interface. |
a1ba8475 | 8553 | |
a023cca8 | 8554 | @cindex DHCP, networking service |
be1c2c54 | 8555 | @deffn {Scheme Procedure} dhcp-client-service [#:dhcp @var{isc-dhcp}] |
a023cca8 LC |
8556 | Return a service that runs @var{dhcp}, a Dynamic Host Configuration |
8557 | Protocol (DHCP) client, on all the non-loopback network interfaces. | |
8558 | @end deffn | |
8559 | ||
be1c2c54 | 8560 | @deffn {Scheme Procedure} static-networking-service @var{interface} @var{ip} @ |
1f9803c2 | 8561 | [#:netmask #f] [#:gateway #f] [#:name-servers @code{'()}] |
cf4a9129 | 8562 | Return a service that starts @var{interface} with address @var{ip}. If |
1f9803c2 LC |
8563 | @var{netmask} is true, use it as the network mask. If @var{gateway} is true, |
8564 | it must be a string specifying the default network gateway. | |
cf4a9129 | 8565 | @end deffn |
8b315a6d | 8566 | |
b7d0c494 | 8567 | @cindex wicd |
e32171ee JD |
8568 | @cindex wireless |
8569 | @cindex WiFi | |
87f40011 | 8570 | @cindex network management |
be1c2c54 | 8571 | @deffn {Scheme Procedure} wicd-service [#:wicd @var{wicd}] |
87f40011 LC |
8572 | Return a service that runs @url{https://launchpad.net/wicd,Wicd}, a network |
8573 | management daemon that aims to simplify wired and wireless networking. | |
8574 | ||
8575 | This service adds the @var{wicd} package to the global profile, providing | |
8576 | several commands to interact with the daemon and configure networking: | |
8577 | @command{wicd-client}, a graphical user interface, and the @command{wicd-cli} | |
8578 | and @command{wicd-curses} user interfaces. | |
b7d0c494 MW |
8579 | @end deffn |
8580 | ||
c0a9589d SB |
8581 | @cindex NetworkManager |
8582 | @deffn {Scheme Procedure} network-manager-service @ | |
8583 | [#:network-manager @var{network-manager}] | |
8584 | Return a service that runs NetworkManager, a network connection manager | |
1068f26b | 8585 | attempting to keep network connectivity active when available. |
c0a9589d SB |
8586 | @end deffn |
8587 | ||
76192896 EF |
8588 | @cindex Connman |
8589 | @deffn {Scheme Procedure} connman-service @ | |
8590 | [#:connman @var{connman}] | |
8591 | Return a service that runs @url{https://01.org/connman,Connman}, a network | |
8592 | connection manager. | |
8593 | ||
8594 | This service adds the @var{connman} package to the global profile, providing | |
8595 | several the @command{connmanctl} command to interact with the daemon and | |
8596 | configure networking." | |
8597 | @end deffn | |
8598 | ||
2cccbc2a | 8599 | @cindex WPA Supplicant |
cbf1024e LC |
8600 | @defvr {Scheme Variable} wpa-supplicant-service-type |
8601 | This is the service type to run @url{https://w1.fi/wpa_supplicant/,WPA | |
2cccbc2a | 8602 | supplicant}, an authentication daemon required to authenticate against |
cbf1024e | 8603 | encrypted WiFi or ethernet networks. It is configured to listen for |
2cccbc2a | 8604 | requests on D-Bus. |
cbf1024e LC |
8605 | |
8606 | The value of this service is the @code{wpa-supplicant} package to use. | |
8607 | Thus, it can be instantiated like this: | |
8608 | ||
8609 | @lisp | |
8610 | (use-modules (gnu services networking) | |
8611 | (gnu packages admin)) | |
8612 | ||
9747d189 | 8613 | (service wpa-supplicant-service-type wpa-supplicant) |
cbf1024e LC |
8614 | @end lisp |
8615 | @end defvr | |
2cccbc2a | 8616 | |
e32171ee JD |
8617 | @cindex NTP |
8618 | @cindex real time clock | |
be1c2c54 | 8619 | @deffn {Scheme Procedure} ntp-service [#:ntp @var{ntp}] @ |
dc0322b5 LC |
8620 | [#:servers @var{%ntp-servers}] @ |
8621 | [#:allow-large-adjustment? #f] | |
63854bcb LC |
8622 | Return a service that runs the daemon from @var{ntp}, the |
8623 | @uref{http://www.ntp.org, Network Time Protocol package}. The daemon will | |
8624 | keep the system clock synchronized with that of @var{servers}. | |
dc0322b5 LC |
8625 | @var{allow-large-adjustment?} determines whether @command{ntpd} is allowed to |
8626 | make an initial adjustment of more than 1,000 seconds. | |
63854bcb LC |
8627 | @end deffn |
8628 | ||
8629 | @defvr {Scheme Variable} %ntp-servers | |
8630 | List of host names used as the default NTP servers. | |
8631 | @end defvr | |
8632 | ||
e32171ee | 8633 | @cindex Tor |
375c6108 LC |
8634 | @deffn {Scheme Procedure} tor-service [@var{config-file}] [#:tor @var{tor}] |
8635 | Return a service to run the @uref{https://torproject.org, Tor} anonymous | |
8636 | networking daemon. | |
8b315a6d | 8637 | |
375c6108 | 8638 | The daemon runs as the @code{tor} unprivileged user. It is passed |
6331bde7 LC |
8639 | @var{config-file}, a file-like object, with an additional @code{User tor} line |
8640 | and lines for hidden services added via @code{tor-hidden-service}. Run | |
8641 | @command{man tor} for information about the configuration file. | |
8642 | @end deffn | |
8643 | ||
24a8ef3b | 8644 | @cindex hidden service |
6331bde7 LC |
8645 | @deffn {Scheme Procedure} tor-hidden-service @var{name} @var{mapping} |
8646 | Define a new Tor @dfn{hidden service} called @var{name} and implementing | |
8647 | @var{mapping}. @var{mapping} is a list of port/host tuples, such as: | |
8648 | ||
8649 | @example | |
24a8ef3b LC |
8650 | '((22 "127.0.0.1:22") |
8651 | (80 "127.0.0.1:8080")) | |
6331bde7 LC |
8652 | @end example |
8653 | ||
8654 | In this example, port 22 of the hidden service is mapped to local port 22, and | |
8655 | port 80 is mapped to local port 8080. | |
8656 | ||
6629099a LC |
8657 | This creates a @file{/var/lib/tor/hidden-services/@var{name}} directory, where |
8658 | the @file{hostname} file contains the @code{.onion} host name for the hidden | |
6331bde7 LC |
8659 | service. |
8660 | ||
8661 | See @uref{https://www.torproject.org/docs/tor-hidden-service.html.en, the Tor | |
8662 | project's documentation} for more information. | |
cf4a9129 | 8663 | @end deffn |
8b315a6d | 8664 | |
be1c2c54 | 8665 | @deffn {Scheme Procedure} bitlbee-service [#:bitlbee bitlbee] @ |
4627a464 LC |
8666 | [#:interface "127.0.0.1"] [#:port 6667] @ |
8667 | [#:extra-settings ""] | |
8668 | Return a service that runs @url{http://bitlbee.org,BitlBee}, a daemon that | |
8669 | acts as a gateway between IRC and chat networks. | |
8670 | ||
8671 | The daemon will listen to the interface corresponding to the IP address | |
8672 | specified in @var{interface}, on @var{port}. @code{127.0.0.1} means that only | |
8673 | local clients can connect, whereas @code{0.0.0.0} means that connections can | |
8674 | come from any networking interface. | |
8675 | ||
8676 | In addition, @var{extra-settings} specifies a string to append to the | |
8677 | configuration file. | |
8678 | @end deffn | |
8679 | ||
71b0601a | 8680 | Furthermore, @code{(gnu services ssh)} provides the following services. |
e32171ee JD |
8681 | @cindex SSH |
8682 | @cindex SSH server | |
8b315a6d | 8683 | |
be1c2c54 | 8684 | @deffn {Scheme Procedure} lsh-service [#:host-key "/etc/lsh/host-key"] @ |
5833bf33 | 8685 | [#:daemonic? #t] [#:interfaces '()] [#:port-number 22] @ |
cf4a9129 LC |
8686 | [#:allow-empty-passwords? #f] [#:root-login? #f] @ |
8687 | [#:syslog-output? #t] [#:x11-forwarding? #t] @ | |
8688 | [#:tcp/ip-forwarding? #t] [#:password-authentication? #t] @ | |
21cc905a | 8689 | [#:public-key-authentication? #t] [#:initialize? #t] |
cf4a9129 LC |
8690 | Run the @command{lshd} program from @var{lsh} to listen on port @var{port-number}. |
8691 | @var{host-key} must designate a file containing the host key, and readable | |
8692 | only by root. | |
72e25e35 | 8693 | |
5833bf33 DP |
8694 | When @var{daemonic?} is true, @command{lshd} will detach from the |
8695 | controlling terminal and log its output to syslogd, unless one sets | |
8696 | @var{syslog-output?} to false. Obviously, it also makes lsh-service | |
8697 | depend on existence of syslogd service. When @var{pid-file?} is true, | |
8698 | @command{lshd} writes its PID to the file called @var{pid-file}. | |
8699 | ||
cf4a9129 LC |
8700 | When @var{initialize?} is true, automatically create the seed and host key |
8701 | upon service activation if they do not exist yet. This may take long and | |
8702 | require interaction. | |
8b315a6d | 8703 | |
20dd519c LC |
8704 | When @var{initialize?} is false, it is up to the user to initialize the |
8705 | randomness generator (@pxref{lsh-make-seed,,, lsh, LSH Manual}), and to create | |
8706 | a key pair with the private key stored in file @var{host-key} (@pxref{lshd | |
8707 | basics,,, lsh, LSH Manual}). | |
8708 | ||
cf4a9129 LC |
8709 | When @var{interfaces} is empty, lshd listens for connections on all the |
8710 | network interfaces; otherwise, @var{interfaces} must be a list of host names | |
8711 | or addresses. | |
9bf3c1a7 | 8712 | |
20dd519c LC |
8713 | @var{allow-empty-passwords?} specifies whether to accept log-ins with empty |
8714 | passwords, and @var{root-login?} specifies whether to accept log-ins as | |
cf4a9129 | 8715 | root. |
4af2447e | 8716 | |
cf4a9129 LC |
8717 | The other options should be self-descriptive. |
8718 | @end deffn | |
4af2447e | 8719 | |
e32171ee JD |
8720 | @cindex SSH |
8721 | @cindex SSH server | |
d8f31281 LC |
8722 | @deffn {Scheme Variable} openssh-service-type |
8723 | This is the type for the @uref{http://www.openssh.org, OpenSSH} secure | |
8724 | shell daemon, @command{sshd}. Its value must be an | |
8725 | @code{openssh-configuration} record as in this example: | |
8726 | ||
8727 | @example | |
8728 | (service openssh-service-type | |
8729 | (openssh-configuration | |
8730 | (x11-forwarding? #t) | |
8731 | (permit-root-login 'without-password))) | |
8732 | @end example | |
8733 | ||
8734 | See below for details about @code{openssh-configuration}. | |
86d8f6d3 JL |
8735 | @end deffn |
8736 | ||
d8f31281 LC |
8737 | @deftp {Data Type} openssh-configuration |
8738 | This is the configuration record for OpenSSH's @command{sshd}. | |
8739 | ||
8740 | @table @asis | |
8741 | @item @code{pid-file} (default: @code{"/var/run/sshd.pid"}) | |
8742 | Name of the file where @command{sshd} writes its PID. | |
8743 | ||
8744 | @item @code{port-number} (default: @code{22}) | |
8745 | TCP port on which @command{sshd} listens for incoming connections. | |
8746 | ||
8747 | @item @code{permit-root-login} (default: @code{#f}) | |
8748 | This field determines whether and when to allow logins as root. If | |
8749 | @code{#f}, root logins are disallowed; if @code{#t}, they are allowed. | |
8750 | If it's the symbol @code{'without-password}, then root logins are | |
8751 | permitted but not with password-based authentication. | |
8752 | ||
8753 | @item @code{allow-empty-passwords?} (default: @code{#f}) | |
8754 | When true, users with empty passwords may log in. When false, they may | |
8755 | not. | |
8756 | ||
8757 | @item @code{password-authentication?} (default: @code{#t}) | |
8758 | When true, users may log in with their password. When false, they have | |
8759 | other authentication methods. | |
8760 | ||
8761 | @item @code{public-key-authentication?} (default: @code{#t}) | |
8762 | When true, users may log in using public key authentication. When | |
8763 | false, users have to use other authentication method. | |
8764 | ||
8765 | Authorized public keys are stored in @file{~/.ssh/authorized_keys}. | |
8766 | This is used only by protocol version 2. | |
8767 | ||
8768 | @item @code{rsa-authentication?} (default: @code{#t}) | |
8769 | When true, users may log in using pure RSA authentication. When false, | |
8770 | users have to use other means of authentication. This is used only by | |
8771 | protocol 1. | |
8772 | ||
8773 | @item @code{x11-forwarding?} (default: @code{#f}) | |
8774 | When true, forwarding of X11 graphical client connections is | |
8775 | enabled---in other words, @command{ssh} options @option{-X} and | |
8776 | @option{-Y} will work. | |
8777 | ||
8778 | @item @code{protocol-number} (default: @code{2}) | |
8779 | The SSH protocol number to use. | |
8780 | @end table | |
8781 | @end deftp | |
8782 | ||
71b0601a DC |
8783 | @deffn {Scheme Procedure} dropbear-service [@var{config}] |
8784 | Run the @uref{https://matt.ucc.asn.au/dropbear/dropbear.html,Dropbear SSH | |
8785 | daemon} with the given @var{config}, a @code{<dropbear-configuration>} | |
8786 | object. | |
8787 | ||
8788 | For example, to specify a Dropbear service listening on port 1234, add | |
8789 | this call to the operating system's @code{services} field: | |
8790 | ||
8791 | @example | |
8792 | (dropbear-service (dropbear-configuration | |
8793 | (port-number 1234))) | |
8794 | @end example | |
8795 | @end deffn | |
8796 | ||
8797 | @deftp {Data Type} dropbear-configuration | |
8798 | This data type represents the configuration of a Dropbear SSH daemon. | |
8799 | ||
8800 | @table @asis | |
8801 | @item @code{dropbear} (default: @var{dropbear}) | |
8802 | The Dropbear package to use. | |
8803 | ||
8804 | @item @code{port-number} (default: 22) | |
8805 | The TCP port where the daemon waits for incoming connections. | |
8806 | ||
8807 | @item @code{syslog-output?} (default: @code{#t}) | |
8808 | Whether to enable syslog output. | |
8809 | ||
8810 | @item @code{pid-file} (default: @code{"/var/run/dropbear.pid"}) | |
8811 | File name of the daemon's PID file. | |
8812 | ||
8813 | @item @code{root-login?} (default: @code{#f}) | |
8814 | Whether to allow @code{root} logins. | |
8815 | ||
8816 | @item @code{allow-empty-passwords?} (default: @code{#f}) | |
8817 | Whether to allow empty passwords. | |
8818 | ||
8819 | @item @code{password-authentication?} (default: @code{#t}) | |
8820 | Whether to enable password-based authentication. | |
8821 | @end table | |
8822 | @end deftp | |
8823 | ||
fa0c1d61 LC |
8824 | @defvr {Scheme Variable} %facebook-host-aliases |
8825 | This variable contains a string for use in @file{/etc/hosts} | |
8826 | (@pxref{Host Names,,, libc, The GNU C Library Reference Manual}). Each | |
8827 | line contains a entry that maps a known server name of the Facebook | |
8828 | on-line service---e.g., @code{www.facebook.com}---to the local | |
8829 | host---@code{127.0.0.1} or its IPv6 equivalent, @code{::1}. | |
8830 | ||
8831 | This variable is typically used in the @code{hosts-file} field of an | |
7313a52e LC |
8832 | @code{operating-system} declaration (@pxref{operating-system Reference, |
8833 | @file{/etc/hosts}}): | |
fa0c1d61 LC |
8834 | |
8835 | @example | |
8836 | (use-modules (gnu) (guix)) | |
8837 | ||
8838 | (operating-system | |
8839 | (host-name "mymachine") | |
8840 | ;; ... | |
8841 | (hosts-file | |
8842 | ;; Create a /etc/hosts file with aliases for "localhost" | |
8843 | ;; and "mymachine", as well as for Facebook servers. | |
24e02c28 LC |
8844 | (plain-file "hosts" |
8845 | (string-append (local-host-aliases host-name) | |
8846 | %facebook-host-aliases)))) | |
fa0c1d61 LC |
8847 | @end example |
8848 | ||
8849 | This mechanism can prevent programs running locally, such as Web | |
8850 | browsers, from accessing Facebook. | |
8851 | @end defvr | |
8852 | ||
965a7332 LC |
8853 | The @code{(gnu services avahi)} provides the following definition. |
8854 | ||
be1c2c54 | 8855 | @deffn {Scheme Procedure} avahi-service [#:avahi @var{avahi}] @ |
965a7332 LC |
8856 | [#:host-name #f] [#:publish? #t] [#:ipv4? #t] @ |
8857 | [#:ipv6? #t] [#:wide-area? #f] @ | |
c8695f32 | 8858 | [#:domains-to-browse '()] [#:debug? #f] |
965a7332 LC |
8859 | Return a service that runs @command{avahi-daemon}, a system-wide |
8860 | mDNS/DNS-SD responder that allows for service discovery and | |
cc9c1f39 LC |
8861 | "zero-configuration" host name lookups (see @uref{http://avahi.org/}), and |
8862 | extends the name service cache daemon (nscd) so that it can resolve | |
8863 | @code{.local} host names using | |
1065bed9 LC |
8864 | @uref{http://0pointer.de/lennart/projects/nss-mdns/, nss-mdns}. Additionally, |
8865 | add the @var{avahi} package to the system profile so that commands such as | |
8866 | @command{avahi-browse} are directly usable. | |
965a7332 LC |
8867 | |
8868 | If @var{host-name} is different from @code{#f}, use that as the host name to | |
8869 | publish for this machine; otherwise, use the machine's actual host name. | |
8870 | ||
8871 | When @var{publish?} is true, publishing of host names and services is allowed; | |
8872 | in particular, avahi-daemon will publish the machine's host name and IP | |
8873 | address via mDNS on the local network. | |
8874 | ||
8875 | When @var{wide-area?} is true, DNS-SD over unicast DNS is enabled. | |
8876 | ||
8877 | Boolean values @var{ipv4?} and @var{ipv6?} determine whether to use IPv4/IPv6 | |
8878 | sockets. | |
8879 | @end deffn | |
8880 | ||
8881 | ||
cf4a9129 LC |
8882 | @node X Window |
8883 | @subsubsection X Window | |
68ad877c | 8884 | |
e32171ee JD |
8885 | @cindex X11 |
8886 | @cindex X Window System | |
cf4a9129 LC |
8887 | Support for the X Window graphical display system---specifically |
8888 | Xorg---is provided by the @code{(gnu services xorg)} module. Note that | |
8889 | there is no @code{xorg-service} procedure. Instead, the X server is | |
8890 | started by the @dfn{login manager}, currently SLiM. | |
4af2447e | 8891 | |
935644c0 DC |
8892 | @deftp {Data Type} sddm-configuration |
8893 | This is the data type representing the sddm service configuration. | |
8894 | ||
8895 | @table @asis | |
8896 | @item @code{display-server} (default: "x11") | |
8897 | Select display server to use for the greeter. Valid values are "x11" | |
8898 | or "wayland". | |
8899 | ||
8900 | @item @code{numlock} (default: "on") | |
8901 | Valid values are "on", "off" or "none". | |
8902 | ||
8903 | @item @code{halt-command} (default @code{#~(string-apppend #$shepherd "/sbin/halt")}) | |
8904 | Command to run when halting. | |
8905 | ||
8906 | @item @code{reboot-command} (default @code{#~(string-append #$shepherd "/sbin/reboot")}) | |
8907 | Command to run when rebooting. | |
8908 | ||
8909 | @item @code{theme} (default "maldives") | |
8910 | Theme to use. Default themes provided by SDDM are "elarun" or "maldives". | |
8911 | ||
8912 | @item @code{themes-directory} (default "/run/current-system/profile/share/sddm/themes") | |
8913 | Directory to look for themes. | |
8914 | ||
8915 | @item @code{faces-directory} (default "/run/current-system/profile/share/sddm/faces") | |
8916 | Directory to look for faces. | |
8917 | ||
8918 | @item @code{default-path} (default "/run/current-system/profile/bin") | |
8919 | Default PATH to use. | |
8920 | ||
8921 | @item @code{minimum-uid} (default 1000) | |
8922 | Minimum UID to display in SDDM. | |
8923 | ||
8924 | @item @code{maximum-uid} (default 2000) | |
8925 | Maximum UID to display in SDDM | |
8926 | ||
8927 | @item @code{remember-last-user?} (default #t) | |
8928 | Remember last user. | |
8929 | ||
8930 | @item @code{remember-last-session?} (default #t) | |
8931 | Remember last session. | |
8932 | ||
8933 | @item @code{hide-users} (default "") | |
8934 | Usernames to hide from SDDM greeter. | |
8935 | ||
8936 | @item @code{hide-shells} (default @code{#~(string-append #$shadow "/sbin/nologin")}) | |
8937 | Users with shells listed will be hidden from the SDDM greeter. | |
8938 | ||
8939 | @item @code{session-command} (default @code{#~(string-append #$sddm "/share/sddm/scripts/wayland-session")}) | |
8940 | Script to run before starting a wayland session. | |
8941 | ||
8942 | @item @code{sessions-directory} (default "/run/current-system/profile/share/wayland-sessions") | |
8943 | Directory to look for desktop files starting wayland sessions. | |
8944 | ||
8945 | @item @code{xorg-server-path} (default @code{xorg-start-command}) | |
8946 | Path to xorg-server. | |
8947 | ||
8948 | @item @code{xauth-path} (default @code{#~(string-append #$xauth "/bin/xauth")}) | |
8949 | Path to xauth. | |
8950 | ||
8951 | @item @code{xephyr-path} (default @code{#~(string-append #$xorg-server "/bin/Xephyr")}) | |
8952 | Path to Xephyr. | |
8953 | ||
8954 | @item @code{xdisplay-start} (default @code{#~(string-append #$sddm "/share/sddm/scripts/Xsetup")}) | |
8955 | Script to run after starting xorg-server. | |
8956 | ||
8957 | @item @code{xdisplay-stop} (default @code{#~(string-append #$sddm "/share/sddm/scripts/Xstop")}) | |
8958 | Script to run before stopping xorg-server. | |
8959 | ||
8960 | @item @code{xsession-command} (default: @code{xinitr }) | |
8961 | Script to run before starting a X session. | |
8962 | ||
8963 | @item @code{xsessions-directory} (default: "/run/current-system/profile/share/xsessions") | |
8964 | Directory to look for desktop files starting X sessions. | |
8965 | ||
8966 | @item @code{minimum-vt} (default: 7) | |
8967 | Minimum VT to use. | |
8968 | ||
8969 | @item @code{xserver-arguments} (default "-nolisten tcp") | |
8970 | Arguments to pass to xorg-server. | |
8971 | ||
8972 | @item @code{auto-login-user} (default "") | |
8973 | User to use for auto-login. | |
8974 | ||
8975 | @item @code{auto-login-session} (default "") | |
8976 | Desktop file to use for auto-login. | |
8977 | ||
8978 | @item @code{relogin?} (default #f) | |
8979 | Relogin after logout. | |
8980 | ||
8981 | @end table | |
8982 | @end deftp | |
8983 | ||
e32171ee | 8984 | @cindex login manager |
935644c0 DC |
8985 | @deffn {Scheme Procedure} sddm-service config |
8986 | Return a service that spawns the SDDM graphical login manager for config of | |
8987 | type @code{<sddm-configuration>}. | |
8988 | ||
8989 | @example | |
8990 | (sddm-service (sddm-configuration | |
8991 | (auto-login-user "Alice") | |
8992 | (auto-login-session "xfce.desktop"))) | |
8993 | @end example | |
8994 | @end deffn | |
8995 | ||
be1c2c54 | 8996 | @deffn {Scheme Procedure} slim-service [#:allow-empty-passwords? #f] @ |
0ecc3bf3 LC |
8997 | [#:auto-login? #f] [#:default-user ""] [#:startx] @ |
8998 | [#:theme @var{%default-slim-theme}] @ | |
4bd43bbe | 8999 | [#:theme-name @var{%default-slim-theme-name}] |
cf4a9129 LC |
9000 | Return a service that spawns the SLiM graphical login manager, which in |
9001 | turn starts the X display server with @var{startx}, a command as returned by | |
9002 | @code{xorg-start-command}. | |
4af2447e | 9003 | |
04e4e6ab LC |
9004 | @cindex X session |
9005 | ||
9006 | SLiM automatically looks for session types described by the @file{.desktop} | |
9007 | files in @file{/run/current-system/profile/share/xsessions} and allows users | |
9008 | to choose a session from the log-in screen using @kbd{F1}. Packages such as | |
9009 | @var{xfce}, @var{sawfish}, and @var{ratpoison} provide @file{.desktop} files; | |
9010 | adding them to the system-wide set of packages automatically makes them | |
9011 | available at the log-in screen. | |
9012 | ||
9013 | In addition, @file{~/.xsession} files are honored. When available, | |
9014 | @file{~/.xsession} must be an executable that starts a window manager | |
9015 | and/or other X clients. | |
9016 | ||
cf4a9129 LC |
9017 | When @var{allow-empty-passwords?} is true, allow logins with an empty |
9018 | password. When @var{auto-login?} is true, log in automatically as | |
9019 | @var{default-user}. | |
0ecc3bf3 | 9020 | |
1068f26b | 9021 | If @var{theme} is @code{#f}, use the default log-in theme; otherwise |
0ecc3bf3 LC |
9022 | @var{theme} must be a gexp denoting the name of a directory containing the |
9023 | theme to use. In that case, @var{theme-name} specifies the name of the | |
9024 | theme. | |
cf4a9129 | 9025 | @end deffn |
4af2447e | 9026 | |
0ecc3bf3 LC |
9027 | @defvr {Scheme Variable} %default-theme |
9028 | @defvrx {Scheme Variable} %default-theme-name | |
9029 | The G-Expression denoting the default SLiM theme and its name. | |
9030 | @end defvr | |
9031 | ||
be1c2c54 | 9032 | @deffn {Scheme Procedure} xorg-start-command [#:guile] @ |
d1cdd7ba | 9033 | [#:configuration-file #f] [#:xorg-server @var{xorg-server}] |
f703413e | 9034 | Return a derivation that builds a @var{guile} script to start the X server |
d1cdd7ba LC |
9035 | from @var{xorg-server}. @var{configuration-file} is the server configuration |
9036 | file or a derivation that builds it; when omitted, the result of | |
9037 | @code{xorg-configuration-file} is used. | |
9038 | ||
9039 | Usually the X server is started by a login manager. | |
9040 | @end deffn | |
9041 | ||
be1c2c54 | 9042 | @deffn {Scheme Procedure} xorg-configuration-file @ |
12422c9d | 9043 | [#:drivers '()] [#:resolutions '()] [#:extra-config '()] |
d1cdd7ba LC |
9044 | Return a configuration file for the Xorg server containing search paths for |
9045 | all the common drivers. | |
f703413e LC |
9046 | |
9047 | @var{drivers} must be either the empty list, in which case Xorg chooses a | |
9048 | graphics driver automatically, or a list of driver names that will be tried in | |
d1cdd7ba | 9049 | this order---e.g., @code{(\"modesetting\" \"vesa\")}. |
d2e59637 LC |
9050 | |
9051 | Likewise, when @var{resolutions} is the empty list, Xorg chooses an | |
9052 | appropriate screen resolution; otherwise, it must be a list of | |
9053 | resolutions---e.g., @code{((1024 768) (640 480))}. | |
12422c9d LC |
9054 | |
9055 | Last, @var{extra-config} is a list of strings or objects appended to the | |
9056 | @code{text-file*} argument list. It is used to pass extra text to be added | |
9057 | verbatim to the configuration file. | |
f703413e | 9058 | @end deffn |
4af2447e | 9059 | |
6726282b LC |
9060 | @deffn {Scheme Procedure} screen-locker-service @var{package} [@var{name}] |
9061 | Add @var{package}, a package for a screen-locker or screen-saver whose | |
9062 | command is @var{program}, to the set of setuid programs and add a PAM entry | |
9063 | for it. For example: | |
9064 | ||
9065 | @lisp | |
9066 | (screen-locker-service xlockmore "xlock") | |
9067 | @end lisp | |
9068 | ||
9069 | makes the good ol' XlockMore usable. | |
9070 | @end deffn | |
9071 | ||
9072 | ||
f2ec23d1 AW |
9073 | @node Printing Services |
9074 | @subsubsection Printing Services | |
9075 | ||
9076 | The @code{(gnu services cups)} module provides a Guix service definition | |
9077 | for the CUPS printing service. To add printer support to a GuixSD | |
9078 | system, add a @code{cups-service} to the operating system definition: | |
9079 | ||
9080 | @deffn {Scheme Variable} cups-service-type | |
9081 | The service type for the CUPS print server. Its value should be a valid | |
9082 | CUPS configuration (see below). For example: | |
9083 | @example | |
9084 | (service cups-service-type (cups-configuration)) | |
9085 | @end example | |
9086 | @end deffn | |
9087 | ||
9088 | The CUPS configuration controls the basic things about your CUPS | |
9089 | installation: what interfaces it listens on, what to do if a print job | |
9090 | fails, how much logging to do, and so on. To actually add a printer, | |
9091 | you have to visit the @url{http://localhost:631} URL, or use a tool such | |
9092 | as GNOME's printer configuration services. By default, configuring a | |
9093 | CUPS service will generate a self-signed certificate if needed, for | |
9094 | secure connections to the print server. | |
9095 | ||
9096 | One way you might want to customize CUPS is to enable or disable the web | |
9097 | interface. You can do that directly, like this: | |
9098 | ||
9099 | @example | |
9100 | (service cups-service-type | |
9101 | (cups-configuration | |
9102 | (web-interface? #f))) | |
9103 | @end example | |
9104 | ||
9105 | The available configuration parameters follow. Each parameter | |
9106 | definition is preceded by its type; for example, @samp{string-list foo} | |
9107 | indicates that the @code{foo} parameter should be specified as a list of | |
9108 | strings. There is also a way to specify the configuration as a string, | |
9109 | if you have an old @code{cupsd.conf} file that you want to port over | |
9110 | from some other system; see the end for more details. | |
9111 | ||
9112 | @c The following documentation was initially generated by | |
9113 | @c (generate-documentation) in (gnu services cups). Manually maintained | |
9114 | @c documentation is better, so we shouldn't hesitate to edit below as | |
9115 | @c needed. However if the change you want to make to this documentation | |
9116 | @c can be done in an automated way, it's probably easier to change | |
9117 | @c (generate-documentation) than to make it below and have to deal with | |
9118 | @c the churn as CUPS updates. | |
9119 | ||
9120 | ||
9121 | Available @code{cups-configuration} fields are: | |
9122 | ||
9123 | @deftypevr {@code{cups-configuration} parameter} package cups | |
9124 | The CUPS package. | |
9125 | @end deftypevr | |
9126 | ||
9127 | @deftypevr {@code{cups-configuration} parameter} package-list extensions | |
9128 | Drivers and other extensions to the CUPS package. | |
9129 | @end deftypevr | |
9130 | ||
9131 | @deftypevr {@code{cups-configuration} parameter} files-configuration files-configuration | |
9132 | Configuration of where to write logs, what directories to use for print | |
9133 | spools, and related privileged configuration parameters. | |
9134 | ||
9135 | Available @code{files-configuration} fields are: | |
9136 | ||
9137 | @deftypevr {@code{files-configuration} parameter} log-location access-log | |
9138 | Defines the access log filename. Specifying a blank filename disables | |
9139 | access log generation. The value @code{stderr} causes log entries to be | |
9140 | sent to the standard error file when the scheduler is running in the | |
9141 | foreground, or to the system log daemon when run in the background. The | |
9142 | value @code{syslog} causes log entries to be sent to the system log | |
9143 | daemon. The server name may be included in filenames using the string | |
9144 | @code{%s}, as in @code{/var/log/cups/%s-access_log}. | |
9145 | ||
9146 | Defaults to @samp{"/var/log/cups/access_log"}. | |
9147 | @end deftypevr | |
9148 | ||
9149 | @deftypevr {@code{files-configuration} parameter} file-name cache-dir | |
9150 | Where CUPS should cache data. | |
9151 | ||
9152 | Defaults to @samp{"/var/cache/cups"}. | |
9153 | @end deftypevr | |
9154 | ||
9155 | @deftypevr {@code{files-configuration} parameter} string config-file-perm | |
9156 | Specifies the permissions for all configuration files that the scheduler | |
9157 | writes. | |
9158 | ||
9159 | Note that the permissions for the printers.conf file are currently | |
9160 | masked to only allow access from the scheduler user (typically root). | |
9161 | This is done because printer device URIs sometimes contain sensitive | |
9162 | authentication information that should not be generally known on the | |
9163 | system. There is no way to disable this security feature. | |
9164 | ||
9165 | Defaults to @samp{"0640"}. | |
9166 | @end deftypevr | |
9167 | ||
9168 | @deftypevr {@code{files-configuration} parameter} log-location error-log | |
9169 | Defines the error log filename. Specifying a blank filename disables | |
9170 | access log generation. The value @code{stderr} causes log entries to be | |
9171 | sent to the standard error file when the scheduler is running in the | |
9172 | foreground, or to the system log daemon when run in the background. The | |
9173 | value @code{syslog} causes log entries to be sent to the system log | |
9174 | daemon. The server name may be included in filenames using the string | |
9175 | @code{%s}, as in @code{/var/log/cups/%s-error_log}. | |
9176 | ||
9177 | Defaults to @samp{"/var/log/cups/error_log"}. | |
9178 | @end deftypevr | |
9179 | ||
9180 | @deftypevr {@code{files-configuration} parameter} string fatal-errors | |
9181 | Specifies which errors are fatal, causing the scheduler to exit. The | |
9182 | kind strings are: | |
9183 | ||
9184 | @table @code | |
9185 | @item none | |
9186 | No errors are fatal. | |
9187 | ||
9188 | @item all | |
9189 | All of the errors below are fatal. | |
9190 | ||
9191 | @item browse | |
9192 | Browsing initialization errors are fatal, for example failed connections | |
9193 | to the DNS-SD daemon. | |
9194 | ||
9195 | @item config | |
9196 | Configuration file syntax errors are fatal. | |
9197 | ||
9198 | @item listen | |
9199 | Listen or Port errors are fatal, except for IPv6 failures on the | |
9200 | loopback or @code{any} addresses. | |
9201 | ||
9202 | @item log | |
9203 | Log file creation or write errors are fatal. | |
9204 | ||
9205 | @item permissions | |
9206 | Bad startup file permissions are fatal, for example shared TLS | |
9207 | certificate and key files with world-read permissions. | |
9208 | @end table | |
9209 | ||
9210 | Defaults to @samp{"all -browse"}. | |
9211 | @end deftypevr | |
9212 | ||
9213 | @deftypevr {@code{files-configuration} parameter} boolean file-device? | |
9214 | Specifies whether the file pseudo-device can be used for new printer | |
9215 | queues. The URI @uref{file:///dev/null} is always allowed. | |
9216 | ||
9217 | Defaults to @samp{#f}. | |
9218 | @end deftypevr | |
9219 | ||
9220 | @deftypevr {@code{files-configuration} parameter} string group | |
9221 | Specifies the group name or ID that will be used when executing external | |
9222 | programs. | |
9223 | ||
9224 | Defaults to @samp{"lp"}. | |
9225 | @end deftypevr | |
9226 | ||
9227 | @deftypevr {@code{files-configuration} parameter} string log-file-perm | |
9228 | Specifies the permissions for all log files that the scheduler writes. | |
9229 | ||
9230 | Defaults to @samp{"0644"}. | |
9231 | @end deftypevr | |
9232 | ||
9233 | @deftypevr {@code{files-configuration} parameter} log-location page-log | |
9234 | Defines the page log filename. Specifying a blank filename disables | |
9235 | access log generation. The value @code{stderr} causes log entries to be | |
9236 | sent to the standard error file when the scheduler is running in the | |
9237 | foreground, or to the system log daemon when run in the background. The | |
9238 | value @code{syslog} causes log entries to be sent to the system log | |
9239 | daemon. The server name may be included in filenames using the string | |
9240 | @code{%s}, as in @code{/var/log/cups/%s-page_log}. | |
9241 | ||
9242 | Defaults to @samp{"/var/log/cups/page_log"}. | |
9243 | @end deftypevr | |
9244 | ||
9245 | @deftypevr {@code{files-configuration} parameter} string remote-root | |
9246 | Specifies the username that is associated with unauthenticated accesses | |
9247 | by clients claiming to be the root user. The default is @code{remroot}. | |
9248 | ||
9249 | Defaults to @samp{"remroot"}. | |
9250 | @end deftypevr | |
9251 | ||
9252 | @deftypevr {@code{files-configuration} parameter} file-name request-root | |
9253 | Specifies the directory that contains print jobs and other HTTP request | |
9254 | data. | |
9255 | ||
9256 | Defaults to @samp{"/var/spool/cups"}. | |
9257 | @end deftypevr | |
9258 | ||
9259 | @deftypevr {@code{files-configuration} parameter} sandboxing sandboxing | |
9260 | Specifies the level of security sandboxing that is applied to print | |
9261 | filters, backends, and other child processes of the scheduler; either | |
9262 | @code{relaxed} or @code{strict}. This directive is currently only | |
9263 | used/supported on macOS. | |
9264 | ||
9265 | Defaults to @samp{strict}. | |
9266 | @end deftypevr | |
9267 | ||
9268 | @deftypevr {@code{files-configuration} parameter} file-name server-keychain | |
9269 | Specifies the location of TLS certificates and private keys. CUPS will | |
9270 | look for public and private keys in this directory: a @code{.crt} files | |
9271 | for PEM-encoded certificates and corresponding @code{.key} files for | |
9272 | PEM-encoded private keys. | |
9273 | ||
9274 | Defaults to @samp{"/etc/cups/ssl"}. | |
9275 | @end deftypevr | |
9276 | ||
9277 | @deftypevr {@code{files-configuration} parameter} file-name server-root | |
9278 | Specifies the directory containing the server configuration files. | |
9279 | ||
9280 | Defaults to @samp{"/etc/cups"}. | |
9281 | @end deftypevr | |
9282 | ||
9283 | @deftypevr {@code{files-configuration} parameter} boolean sync-on-close? | |
9284 | Specifies whether the scheduler calls fsync(2) after writing | |
9285 | configuration or state files. | |
9286 | ||
9287 | Defaults to @samp{#f}. | |
9288 | @end deftypevr | |
9289 | ||
9290 | @deftypevr {@code{files-configuration} parameter} space-separated-string-list system-group | |
9291 | Specifies the group(s) to use for @code{@@SYSTEM} group authentication. | |
9292 | @end deftypevr | |
9293 | ||
9294 | @deftypevr {@code{files-configuration} parameter} file-name temp-dir | |
9295 | Specifies the directory where temporary files are stored. | |
9296 | ||
9297 | Defaults to @samp{"/var/spool/cups/tmp"}. | |
9298 | @end deftypevr | |
9299 | ||
9300 | @deftypevr {@code{files-configuration} parameter} string user | |
9301 | Specifies the user name or ID that is used when running external | |
9302 | programs. | |
9303 | ||
9304 | Defaults to @samp{"lp"}. | |
9305 | @end deftypevr | |
9306 | @end deftypevr | |
9307 | ||
9308 | @deftypevr {@code{cups-configuration} parameter} access-log-level access-log-level | |
9309 | Specifies the logging level for the AccessLog file. The @code{config} | |
9310 | level logs when printers and classes are added, deleted, or modified and | |
9311 | when configuration files are accessed or updated. The @code{actions} | |
9312 | level logs when print jobs are submitted, held, released, modified, or | |
9313 | canceled, and any of the conditions for @code{config}. The @code{all} | |
9314 | level logs all requests. | |
9315 | ||
9316 | Defaults to @samp{actions}. | |
9317 | @end deftypevr | |
9318 | ||
9319 | @deftypevr {@code{cups-configuration} parameter} boolean auto-purge-jobs? | |
9320 | Specifies whether to purge job history data automatically when it is no | |
9321 | longer required for quotas. | |
9322 | ||
9323 | Defaults to @samp{#f}. | |
9324 | @end deftypevr | |
9325 | ||
9326 | @deftypevr {@code{cups-configuration} parameter} browse-local-protocols browse-local-protocols | |
9327 | Specifies which protocols to use for local printer sharing. | |
9328 | ||
9329 | Defaults to @samp{dnssd}. | |
9330 | @end deftypevr | |
9331 | ||
9332 | @deftypevr {@code{cups-configuration} parameter} boolean browse-web-if? | |
9333 | Specifies whether the CUPS web interface is advertised. | |
9334 | ||
9335 | Defaults to @samp{#f}. | |
9336 | @end deftypevr | |
9337 | ||
9338 | @deftypevr {@code{cups-configuration} parameter} boolean browsing? | |
9339 | Specifies whether shared printers are advertised. | |
9340 | ||
9341 | Defaults to @samp{#f}. | |
9342 | @end deftypevr | |
9343 | ||
9344 | @deftypevr {@code{cups-configuration} parameter} string classification | |
9345 | Specifies the security classification of the server. Any valid banner | |
9346 | name can be used, including "classified", "confidential", "secret", | |
9347 | "topsecret", and "unclassified", or the banner can be omitted to disable | |
9348 | secure printing functions. | |
9349 | ||
9350 | Defaults to @samp{""}. | |
9351 | @end deftypevr | |
9352 | ||
9353 | @deftypevr {@code{cups-configuration} parameter} boolean classify-override? | |
9354 | Specifies whether users may override the classification (cover page) of | |
9355 | individual print jobs using the @code{job-sheets} option. | |
9356 | ||
9357 | Defaults to @samp{#f}. | |
9358 | @end deftypevr | |
9359 | ||
9360 | @deftypevr {@code{cups-configuration} parameter} default-auth-type default-auth-type | |
9361 | Specifies the default type of authentication to use. | |
9362 | ||
9363 | Defaults to @samp{Basic}. | |
9364 | @end deftypevr | |
9365 | ||
9366 | @deftypevr {@code{cups-configuration} parameter} default-encryption default-encryption | |
9367 | Specifies whether encryption will be used for authenticated requests. | |
9368 | ||
9369 | Defaults to @samp{Required}. | |
9370 | @end deftypevr | |
9371 | ||
9372 | @deftypevr {@code{cups-configuration} parameter} string default-language | |
9373 | Specifies the default language to use for text and web content. | |
9374 | ||
9375 | Defaults to @samp{"en"}. | |
9376 | @end deftypevr | |
9377 | ||
9378 | @deftypevr {@code{cups-configuration} parameter} string default-paper-size | |
9379 | Specifies the default paper size for new print queues. @samp{"Auto"} | |
9380 | uses a locale-specific default, while @samp{"None"} specifies there is | |
9381 | no default paper size. Specific size names are typically | |
9382 | @samp{"Letter"} or @samp{"A4"}. | |
9383 | ||
9384 | Defaults to @samp{"Auto"}. | |
9385 | @end deftypevr | |
9386 | ||
9387 | @deftypevr {@code{cups-configuration} parameter} string default-policy | |
9388 | Specifies the default access policy to use. | |
9389 | ||
9390 | Defaults to @samp{"default"}. | |
9391 | @end deftypevr | |
9392 | ||
9393 | @deftypevr {@code{cups-configuration} parameter} boolean default-shared? | |
9394 | Specifies whether local printers are shared by default. | |
9395 | ||
9396 | Defaults to @samp{#t}. | |
9397 | @end deftypevr | |
9398 | ||
9399 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer dirty-clean-interval | |
9400 | Specifies the delay for updating of configuration and state files, in | |
9401 | seconds. A value of 0 causes the update to happen as soon as possible, | |
9402 | typically within a few milliseconds. | |
9403 | ||
9404 | Defaults to @samp{30}. | |
9405 | @end deftypevr | |
9406 | ||
9407 | @deftypevr {@code{cups-configuration} parameter} error-policy error-policy | |
9408 | Specifies what to do when an error occurs. Possible values are | |
9409 | @code{abort-job}, which will discard the failed print job; | |
9410 | @code{retry-job}, which will retry the job at a later time; | |
9411 | @code{retry-this-job}, which retries the failed job immediately; and | |
9412 | @code{stop-printer}, which stops the printer. | |
9413 | ||
9414 | Defaults to @samp{stop-printer}. | |
9415 | @end deftypevr | |
9416 | ||
9417 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer filter-limit | |
9418 | Specifies the maximum cost of filters that are run concurrently, which | |
9419 | can be used to minimize disk, memory, and CPU resource problems. A | |
9420 | limit of 0 disables filter limiting. An average print to a | |
9421 | non-PostScript printer needs a filter limit of about 200. A PostScript | |
9422 | printer needs about half that (100). Setting the limit below these | |
9423 | thresholds will effectively limit the scheduler to printing a single job | |
9424 | at any time. | |
9425 | ||
9426 | Defaults to @samp{0}. | |
9427 | @end deftypevr | |
9428 | ||
9429 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer filter-nice | |
9430 | Specifies the scheduling priority of filters that are run to print a | |
9431 | job. The nice value ranges from 0, the highest priority, to 19, the | |
9432 | lowest priority. | |
9433 | ||
9434 | Defaults to @samp{0}. | |
9435 | @end deftypevr | |
9436 | ||
9437 | @deftypevr {@code{cups-configuration} parameter} host-name-lookups host-name-lookups | |
9438 | Specifies whether to do reverse lookups on connecting clients. The | |
9439 | @code{double} setting causes @code{cupsd} to verify that the hostname | |
9440 | resolved from the address matches one of the addresses returned for that | |
9441 | hostname. Double lookups also prevent clients with unregistered | |
9442 | addresses from connecting to your server. Only set this option to | |
9443 | @code{#t} or @code{double} if absolutely required. | |
9444 | ||
9445 | Defaults to @samp{#f}. | |
9446 | @end deftypevr | |
9447 | ||
9448 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer job-kill-delay | |
9449 | Specifies the number of seconds to wait before killing the filters and | |
9450 | backend associated with a canceled or held job. | |
9451 | ||
9452 | Defaults to @samp{30}. | |
9453 | @end deftypevr | |
9454 | ||
9455 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer job-retry-interval | |
9456 | Specifies the interval between retries of jobs in seconds. This is | |
9457 | typically used for fax queues but can also be used with normal print | |
9458 | queues whose error policy is @code{retry-job} or | |
9459 | @code{retry-current-job}. | |
9460 | ||
9461 | Defaults to @samp{30}. | |
9462 | @end deftypevr | |
9463 | ||
9464 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer job-retry-limit | |
9465 | Specifies the number of retries that are done for jobs. This is | |
9466 | typically used for fax queues but can also be used with normal print | |
9467 | queues whose error policy is @code{retry-job} or | |
9468 | @code{retry-current-job}. | |
9469 | ||
9470 | Defaults to @samp{5}. | |
9471 | @end deftypevr | |
9472 | ||
9473 | @deftypevr {@code{cups-configuration} parameter} boolean keep-alive? | |
9474 | Specifies whether to support HTTP keep-alive connections. | |
9475 | ||
9476 | Defaults to @samp{#t}. | |
9477 | @end deftypevr | |
9478 | ||
9479 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer keep-alive-timeout | |
9480 | Specifies how long an idle client connection remains open, in seconds. | |
9481 | ||
9482 | Defaults to @samp{30}. | |
9483 | @end deftypevr | |
9484 | ||
9485 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer limit-request-body | |
9486 | Specifies the maximum size of print files, IPP requests, and HTML form | |
9487 | data. A limit of 0 disables the limit check. | |
9488 | ||
9489 | Defaults to @samp{0}. | |
9490 | @end deftypevr | |
9491 | ||
9492 | @deftypevr {@code{cups-configuration} parameter} multiline-string-list listen | |
9493 | Listens on the specified interfaces for connections. Valid values are | |
9494 | of the form @var{address}:@var{port}, where @var{address} is either an | |
9495 | IPv6 address enclosed in brackets, an IPv4 address, or @code{*} to | |
9496 | indicate all addresses. Values can also be file names of local UNIX | |
9497 | domain sockets. The Listen directive is similar to the Port directive | |
9498 | but allows you to restrict access to specific interfaces or networks. | |
9499 | @end deftypevr | |
9500 | ||
9501 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer listen-back-log | |
9502 | Specifies the number of pending connections that will be allowed. This | |
9503 | normally only affects very busy servers that have reached the MaxClients | |
9504 | limit, but can also be triggered by large numbers of simultaneous | |
9505 | connections. When the limit is reached, the operating system will | |
9506 | refuse additional connections until the scheduler can accept the pending | |
9507 | ones. | |
9508 | ||
9509 | Defaults to @samp{128}. | |
9510 | @end deftypevr | |
9511 | ||
9512 | @deftypevr {@code{cups-configuration} parameter} location-access-control-list location-access-controls | |
9513 | Specifies a set of additional access controls. | |
9514 | ||
9515 | Available @code{location-access-controls} fields are: | |
9516 | ||
9517 | @deftypevr {@code{location-access-controls} parameter} file-name path | |
9518 | Specifies the URI path to which the access control applies. | |
9519 | @end deftypevr | |
9520 | ||
9521 | @deftypevr {@code{location-access-controls} parameter} access-control-list access-controls | |
9522 | Access controls for all access to this path, in the same format as the | |
9523 | @code{access-controls} of @code{operation-access-control}. | |
9524 | ||
9525 | Defaults to @samp{()}. | |
9526 | @end deftypevr | |
9527 | ||
9528 | @deftypevr {@code{location-access-controls} parameter} method-access-control-list method-access-controls | |
9529 | Access controls for method-specific access to this path. | |
9530 | ||
9531 | Defaults to @samp{()}. | |
9532 | ||
9533 | Available @code{method-access-controls} fields are: | |
9534 | ||
9535 | @deftypevr {@code{method-access-controls} parameter} boolean reverse? | |
9536 | If @code{#t}, apply access controls to all methods except the listed | |
9537 | methods. Otherwise apply to only the listed methods. | |
9538 | ||
9539 | Defaults to @samp{#f}. | |
9540 | @end deftypevr | |
9541 | ||
9542 | @deftypevr {@code{method-access-controls} parameter} method-list methods | |
9543 | Methods to which this access control applies. | |
9544 | ||
9545 | Defaults to @samp{()}. | |
9546 | @end deftypevr | |
9547 | ||
9548 | @deftypevr {@code{method-access-controls} parameter} access-control-list access-controls | |
9549 | Access control directives, as a list of strings. Each string should be | |
9550 | one directive, such as "Order allow,deny". | |
9551 | ||
9552 | Defaults to @samp{()}. | |
9553 | @end deftypevr | |
9554 | @end deftypevr | |
9555 | @end deftypevr | |
9556 | ||
9557 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer log-debug-history | |
9558 | Specifies the number of debugging messages that are retained for logging | |
9559 | if an error occurs in a print job. Debug messages are logged regardless | |
9560 | of the LogLevel setting. | |
9561 | ||
9562 | Defaults to @samp{100}. | |
9563 | @end deftypevr | |
9564 | ||
9565 | @deftypevr {@code{cups-configuration} parameter} log-level log-level | |
9566 | Specifies the level of logging for the ErrorLog file. The value | |
9567 | @code{none} stops all logging while @code{debug2} logs everything. | |
9568 | ||
9569 | Defaults to @samp{info}. | |
9570 | @end deftypevr | |
9571 | ||
9572 | @deftypevr {@code{cups-configuration} parameter} log-time-format log-time-format | |
9573 | Specifies the format of the date and time in the log files. The value | |
9574 | @code{standard} logs whole seconds while @code{usecs} logs microseconds. | |
9575 | ||
9576 | Defaults to @samp{standard}. | |
9577 | @end deftypevr | |
9578 | ||
9579 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer max-clients | |
9580 | Specifies the maximum number of simultaneous clients that are allowed by | |
9581 | the scheduler. | |
9582 | ||
9583 | Defaults to @samp{100}. | |
9584 | @end deftypevr | |
9585 | ||
9586 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer max-clients-per-host | |
9587 | Specifies the maximum number of simultaneous clients that are allowed | |
9588 | from a single address. | |
9589 | ||
9590 | Defaults to @samp{100}. | |
9591 | @end deftypevr | |
9592 | ||
9593 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer max-copies | |
9594 | Specifies the maximum number of copies that a user can print of each | |
9595 | job. | |
9596 | ||
9597 | Defaults to @samp{9999}. | |
9598 | @end deftypevr | |
9599 | ||
9600 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer max-hold-time | |
9601 | Specifies the maximum time a job may remain in the @code{indefinite} | |
9602 | hold state before it is canceled. A value of 0 disables cancellation of | |
9603 | held jobs. | |
9604 | ||
9605 | Defaults to @samp{0}. | |
9606 | @end deftypevr | |
9607 | ||
9608 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer max-jobs | |
9609 | Specifies the maximum number of simultaneous jobs that are allowed. Set | |
9610 | to 0 to allow an unlimited number of jobs. | |
9611 | ||
9612 | Defaults to @samp{500}. | |
9613 | @end deftypevr | |
9614 | ||
9615 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer max-jobs-per-printer | |
9616 | Specifies the maximum number of simultaneous jobs that are allowed per | |
9617 | printer. A value of 0 allows up to MaxJobs jobs per printer. | |
9618 | ||
9619 | Defaults to @samp{0}. | |
9620 | @end deftypevr | |
9621 | ||
9622 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer max-jobs-per-user | |
9623 | Specifies the maximum number of simultaneous jobs that are allowed per | |
9624 | user. A value of 0 allows up to MaxJobs jobs per user. | |
9625 | ||
9626 | Defaults to @samp{0}. | |
9627 | @end deftypevr | |
9628 | ||
9629 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer max-job-time | |
9630 | Specifies the maximum time a job may take to print before it is | |
9631 | canceled, in seconds. Set to 0 to disable cancellation of "stuck" jobs. | |
9632 | ||
9633 | Defaults to @samp{10800}. | |
9634 | @end deftypevr | |
9635 | ||
9636 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer max-log-size | |
9637 | Specifies the maximum size of the log files before they are rotated, in | |
9638 | bytes. The value 0 disables log rotation. | |
9639 | ||
9640 | Defaults to @samp{1048576}. | |
9641 | @end deftypevr | |
9642 | ||
9643 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer multiple-operation-timeout | |
9644 | Specifies the maximum amount of time to allow between files in a | |
9645 | multiple file print job, in seconds. | |
9646 | ||
9647 | Defaults to @samp{300}. | |
9648 | @end deftypevr | |
9649 | ||
9650 | @deftypevr {@code{cups-configuration} parameter} string page-log-format | |
9651 | Specifies the format of PageLog lines. Sequences beginning with percent | |
9652 | (@samp{%}) characters are replaced with the corresponding information, | |
9653 | while all other characters are copied literally. The following percent | |
9654 | sequences are recognized: | |
9655 | ||
9656 | @table @samp | |
9657 | @item %% | |
9658 | insert a single percent character | |
9659 | ||
9660 | @item %@{name@} | |
9661 | insert the value of the specified IPP attribute | |
9662 | ||
9663 | @item %C | |
9664 | insert the number of copies for the current page | |
9665 | ||
9666 | @item %P | |
9667 | insert the current page number | |
9668 | ||
9669 | @item %T | |
9670 | insert the current date and time in common log format | |
9671 | ||
9672 | @item %j | |
9673 | insert the job ID | |
9674 | ||
9675 | @item %p | |
9676 | insert the printer name | |
9677 | ||
9678 | @item %u | |
9679 | insert the username | |
9680 | @end table | |
9681 | ||
9682 | A value of the empty string disables page logging. The string @code{%p | |
9683 | %u %j %T %P %C %@{job-billing@} %@{job-originating-host-name@} | |
9684 | %@{job-name@} %@{media@} %@{sides@}} creates a page log with the | |
9685 | standard items. | |
9686 | ||
9687 | Defaults to @samp{""}. | |
9688 | @end deftypevr | |
9689 | ||
9690 | @deftypevr {@code{cups-configuration} parameter} environment-variables environment-variables | |
9691 | Passes the specified environment variable(s) to child processes; a list | |
9692 | of strings. | |
9693 | ||
9694 | Defaults to @samp{()}. | |
9695 | @end deftypevr | |
9696 | ||
9697 | @deftypevr {@code{cups-configuration} parameter} policy-configuration-list policies | |
9698 | Specifies named access control policies. | |
9699 | ||
9700 | Available @code{policy-configuration} fields are: | |
9701 | ||
9702 | @deftypevr {@code{policy-configuration} parameter} string name | |
9703 | Name of the policy. | |
9704 | @end deftypevr | |
9705 | ||
9706 | @deftypevr {@code{policy-configuration} parameter} string job-private-access | |
9707 | Specifies an access list for a job's private values. @code{@@ACL} maps | |
9708 | to the printer's requesting-user-name-allowed or | |
9709 | requesting-user-name-denied values. @code{@@OWNER} maps to the job's | |
9710 | owner. @code{@@SYSTEM} maps to the groups listed for the | |
9711 | @code{system-group} field of the @code{files-config} configuration, | |
9712 | which is reified into the @code{cups-files.conf(5)} file. Other | |
9713 | possible elements of the access list include specific user names, and | |
9714 | @code{@@@var{group}} to indicate members of a specific group. The | |
9715 | access list may also be simply @code{all} or @code{default}. | |
9716 | ||
9717 | Defaults to @samp{"@@OWNER @@SYSTEM"}. | |
9718 | @end deftypevr | |
9719 | ||
9720 | @deftypevr {@code{policy-configuration} parameter} string job-private-values | |
9721 | Specifies the list of job values to make private, or @code{all}, | |
9722 | @code{default}, or @code{none}. | |
9723 | ||
9724 | Defaults to @samp{"job-name job-originating-host-name | |
9725 | job-originating-user-name phone"}. | |
9726 | @end deftypevr | |
9727 | ||
9728 | @deftypevr {@code{policy-configuration} parameter} string subscription-private-access | |
9729 | Specifies an access list for a subscription's private values. | |
9730 | @code{@@ACL} maps to the printer's requesting-user-name-allowed or | |
9731 | requesting-user-name-denied values. @code{@@OWNER} maps to the job's | |
9732 | owner. @code{@@SYSTEM} maps to the groups listed for the | |
9733 | @code{system-group} field of the @code{files-config} configuration, | |
9734 | which is reified into the @code{cups-files.conf(5)} file. Other | |
9735 | possible elements of the access list include specific user names, and | |
9736 | @code{@@@var{group}} to indicate members of a specific group. The | |
9737 | access list may also be simply @code{all} or @code{default}. | |
9738 | ||
9739 | Defaults to @samp{"@@OWNER @@SYSTEM"}. | |
9740 | @end deftypevr | |
9741 | ||
9742 | @deftypevr {@code{policy-configuration} parameter} string subscription-private-values | |
9743 | Specifies the list of job values to make private, or @code{all}, | |
9744 | @code{default}, or @code{none}. | |
9745 | ||
9746 | Defaults to @samp{"notify-events notify-pull-method notify-recipient-uri | |
9747 | notify-subscriber-user-name notify-user-data"}. | |
9748 | @end deftypevr | |
9749 | ||
9750 | @deftypevr {@code{policy-configuration} parameter} operation-access-control-list access-controls | |
9751 | Access control by IPP operation. | |
9752 | ||
9753 | Defaults to @samp{()}. | |
9754 | @end deftypevr | |
9755 | @end deftypevr | |
9756 | ||
9757 | @deftypevr {@code{cups-configuration} parameter} boolean-or-non-negative-integer preserve-job-files | |
9758 | Specifies whether job files (documents) are preserved after a job is | |
9759 | printed. If a numeric value is specified, job files are preserved for | |
9760 | the indicated number of seconds after printing. Otherwise a boolean | |
9761 | value applies indefinitely. | |
9762 | ||
9763 | Defaults to @samp{86400}. | |
9764 | @end deftypevr | |
9765 | ||
9766 | @deftypevr {@code{cups-configuration} parameter} boolean-or-non-negative-integer preserve-job-history | |
9767 | Specifies whether the job history is preserved after a job is printed. | |
9768 | If a numeric value is specified, the job history is preserved for the | |
9769 | indicated number of seconds after printing. If @code{#t}, the job | |
9770 | history is preserved until the MaxJobs limit is reached. | |
9771 | ||
9772 | Defaults to @samp{#t}. | |
9773 | @end deftypevr | |
9774 | ||
9775 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer reload-timeout | |
9776 | Specifies the amount of time to wait for job completion before | |
9777 | restarting the scheduler. | |
9778 | ||
9779 | Defaults to @samp{30}. | |
9780 | @end deftypevr | |
9781 | ||
9782 | @deftypevr {@code{cups-configuration} parameter} string rip-cache | |
9783 | Specifies the maximum amount of memory to use when converting documents | |
9784 | into bitmaps for a printer. | |
9785 | ||
9786 | Defaults to @samp{"128m"}. | |
9787 | @end deftypevr | |
9788 | ||
9789 | @deftypevr {@code{cups-configuration} parameter} string server-admin | |
9790 | Specifies the email address of the server administrator. | |
9791 | ||
9792 | Defaults to @samp{"root@@localhost.localdomain"}. | |
9793 | @end deftypevr | |
9794 | ||
9795 | @deftypevr {@code{cups-configuration} parameter} host-name-list-or-* server-alias | |
9796 | The ServerAlias directive is used for HTTP Host header validation when | |
9797 | clients connect to the scheduler from external interfaces. Using the | |
9798 | special name @code{*} can expose your system to known browser-based DNS | |
9799 | rebinding attacks, even when accessing sites through a firewall. If the | |
9800 | auto-discovery of alternate names does not work, we recommend listing | |
9801 | each alternate name with a ServerAlias directive instead of using | |
9802 | @code{*}. | |
9803 | ||
9804 | Defaults to @samp{*}. | |
9805 | @end deftypevr | |
9806 | ||
9807 | @deftypevr {@code{cups-configuration} parameter} string server-name | |
9808 | Specifies the fully-qualified host name of the server. | |
9809 | ||
9810 | Defaults to @samp{"localhost"}. | |
9811 | @end deftypevr | |
9812 | ||
9813 | @deftypevr {@code{cups-configuration} parameter} server-tokens server-tokens | |
9814 | Specifies what information is included in the Server header of HTTP | |
9815 | responses. @code{None} disables the Server header. @code{ProductOnly} | |
9816 | reports @code{CUPS}. @code{Major} reports @code{CUPS 2}. @code{Minor} | |
9817 | reports @code{CUPS 2.0}. @code{Minimal} reports @code{CUPS 2.0.0}. | |
9818 | @code{OS} reports @code{CUPS 2.0.0 (@var{uname})} where @var{uname} is | |
9819 | the output of the @code{uname} command. @code{Full} reports @code{CUPS | |
9820 | 2.0.0 (@var{uname}) IPP/2.0}. | |
9821 | ||
9822 | Defaults to @samp{Minimal}. | |
9823 | @end deftypevr | |
9824 | ||
9825 | @deftypevr {@code{cups-configuration} parameter} string set-env | |
9826 | Set the specified environment variable to be passed to child processes. | |
9827 | ||
9828 | Defaults to @samp{"variable value"}. | |
9829 | @end deftypevr | |
9830 | ||
9831 | @deftypevr {@code{cups-configuration} parameter} multiline-string-list ssl-listen | |
9832 | Listens on the specified interfaces for encrypted connections. Valid | |
9833 | values are of the form @var{address}:@var{port}, where @var{address} is | |
9834 | either an IPv6 address enclosed in brackets, an IPv4 address, or | |
9835 | @code{*} to indicate all addresses. | |
9836 | ||
9837 | Defaults to @samp{()}. | |
9838 | @end deftypevr | |
9839 | ||
9840 | @deftypevr {@code{cups-configuration} parameter} ssl-options ssl-options | |
9841 | Sets encryption options. By default, CUPS only supports encryption | |
9842 | using TLS v1.0 or higher using known secure cipher suites. The | |
9843 | @code{AllowRC4} option enables the 128-bit RC4 cipher suites, which are | |
9844 | required for some older clients that do not implement newer ones. The | |
9845 | @code{AllowSSL3} option enables SSL v3.0, which is required for some | |
9846 | older clients that do not support TLS v1.0. | |
9847 | ||
9848 | Defaults to @samp{()}. | |
9849 | @end deftypevr | |
9850 | ||
9851 | @deftypevr {@code{cups-configuration} parameter} boolean strict-conformance? | |
9852 | Specifies whether the scheduler requires clients to strictly adhere to | |
9853 | the IPP specifications. | |
9854 | ||
9855 | Defaults to @samp{#f}. | |
9856 | @end deftypevr | |
9857 | ||
9858 | @deftypevr {@code{cups-configuration} parameter} non-negative-integer timeout | |
9859 | Specifies the HTTP request timeout, in seconds. | |
9860 | ||
9861 | Defaults to @samp{300}. | |
9862 | ||
9863 | @end deftypevr | |
9864 | ||
9865 | @deftypevr {@code{cups-configuration} parameter} boolean web-interface? | |
9866 | Specifies whether the web interface is enabled. | |
9867 | ||
9868 | Defaults to @samp{#f}. | |
9869 | @end deftypevr | |
9870 | ||
9871 | At this point you're probably thinking ``oh dear, Guix manual, I like | |
9872 | you but you can stop already with the configuration options''. Indeed. | |
9873 | However, one more point: it could be that you have an existing | |
9874 | @code{cupsd.conf} that you want to use. In that case, you can pass an | |
9875 | @code{opaque-cups-configuration} as the configuration of a | |
9876 | @code{cups-service-type}. | |
9877 | ||
9878 | Available @code{opaque-cups-configuration} fields are: | |
9879 | ||
9880 | @deftypevr {@code{opaque-cups-configuration} parameter} package cups | |
9881 | The CUPS package. | |
9882 | @end deftypevr | |
9883 | ||
9884 | @deftypevr {@code{opaque-cups-configuration} parameter} string cupsd.conf | |
9885 | The contents of the @code{cupsd.conf}, as a string. | |
9886 | @end deftypevr | |
9887 | ||
9888 | @deftypevr {@code{opaque-cups-configuration} parameter} string cups-files.conf | |
9889 | The contents of the @code{cups-files.conf} file, as a string. | |
9890 | @end deftypevr | |
9891 | ||
9892 | For example, if your @code{cupsd.conf} and @code{cups-files.conf} are in | |
9893 | strings of the same name, you could instantiate a CUPS service like | |
9894 | this: | |
9895 | ||
9896 | @example | |
9897 | (service cups-service-type | |
9898 | (opaque-cups-configuration | |
9899 | (cupsd.conf cupsd.conf) | |
9900 | (cups-files.conf cups-files.conf))) | |
9901 | @end example | |
9902 | ||
9903 | ||
fe1a39d3 LC |
9904 | @node Desktop Services |
9905 | @subsubsection Desktop Services | |
aa4ed923 | 9906 | |
fe1a39d3 LC |
9907 | The @code{(gnu services desktop)} module provides services that are |
9908 | usually useful in the context of a ``desktop'' setup---that is, on a | |
9909 | machine running a graphical display server, possibly with graphical user | |
7a2413e4 AW |
9910 | interfaces, etc. It also defines services that provide specific desktop |
9911 | environments like GNOME and XFCE. | |
aa4ed923 | 9912 | |
4467be21 LC |
9913 | To simplify things, the module defines a variable containing the set of |
9914 | services that users typically expect on a machine with a graphical | |
9915 | environment and networking: | |
9916 | ||
9917 | @defvr {Scheme Variable} %desktop-services | |
9918 | This is a list of services that builds upon @var{%base-services} and | |
1068f26b | 9919 | adds or adjusts services for a typical ``desktop'' setup. |
4467be21 LC |
9920 | |
9921 | In particular, it adds a graphical login manager (@pxref{X Window, | |
6726282b LC |
9922 | @code{slim-service}}), screen lockers, |
9923 | a network management tool (@pxref{Networking | |
4467be21 | 9924 | Services, @code{wicd-service}}), energy and color management services, |
4650a77e | 9925 | the @code{elogind} login and seat manager, the Polkit privilege service, |
cee32ee4 AW |
9926 | the GeoClue location service, an NTP client (@pxref{Networking |
9927 | Services}), the Avahi daemon, and has the name service switch service | |
9928 | configured to be able to use @code{nss-mdns} (@pxref{Name Service | |
9929 | Switch, mDNS}). | |
4467be21 LC |
9930 | @end defvr |
9931 | ||
9932 | The @var{%desktop-services} variable can be used as the @code{services} | |
9933 | field of an @code{operating-system} declaration (@pxref{operating-system | |
9934 | Reference, @code{services}}). | |
9935 | ||
7a2413e4 AW |
9936 | Additionally, the @code{gnome-desktop-service} and |
9937 | @code{xfce-desktop-service} procedures can add GNOME and/or XFCE to a | |
9938 | system. To ``add GNOME'' means that system-level services like the | |
9939 | backlight adjustment helpers and the power management utilities are | |
9940 | added to the system, extending @code{polkit} and @code{dbus} | |
9941 | appropriately, allowing GNOME to operate with elevated privileges on a | |
9942 | limited number of special-purpose system interfaces. Additionally, | |
9943 | adding a service made by @code{gnome-desktop-service} adds the GNOME | |
9944 | metapackage to the system profile. Likewise, adding the XFCE service | |
9945 | not only adds the @code{xfce} metapackage to the system profile, but it | |
9946 | also gives the Thunar file manager the ability to open a ``root-mode'' | |
9947 | file management window, if the user authenticates using the | |
9948 | administrator's password via the standard polkit graphical interface. | |
9949 | ||
9950 | @deffn {Scheme Procedure} gnome-desktop-service | |
9951 | Return a service that adds the @code{gnome} package to the system | |
9952 | profile, and extends polkit with the actions from | |
9953 | @code{gnome-settings-daemon}. | |
9954 | @end deffn | |
9955 | ||
9956 | @deffn {Scheme Procedure} xfce-desktop-service | |
9957 | Return a service that adds the @code{xfce} package to the system profile, | |
5741e3e5 | 9958 | and extends polkit with the ability for @code{thunar} to manipulate the |
7a2413e4 AW |
9959 | file system as root from within a user session, after the user has |
9960 | authenticated with the administrator's password. | |
9961 | @end deffn | |
9962 | ||
9963 | Because the GNOME and XFCE desktop services pull in so many packages, | |
9964 | the default @code{%desktop-services} variable doesn't include either of | |
9965 | them by default. To add GNOME or XFCE, just @code{cons} them onto | |
9966 | @code{%desktop-services} in the @code{services} field of your | |
9967 | @code{operating-system}: | |
9968 | ||
9969 | @example | |
9970 | (use-modules (gnu)) | |
9971 | (use-service-modules desktop) | |
9972 | (operating-system | |
9973 | ... | |
9974 | ;; cons* adds items to the list given as its last argument. | |
9975 | (services (cons* (gnome-desktop-service) | |
9976 | (xfce-desktop-service) | |
9977 | %desktop-services)) | |
9978 | ...) | |
9979 | @end example | |
9980 | ||
9981 | These desktop environments will then be available as options in the | |
9982 | graphical login window. | |
9983 | ||
9984 | The actual service definitions included in @code{%desktop-services} and | |
9985 | provided by @code{(gnu services dbus)} and @code{(gnu services desktop)} | |
9986 | are described below. | |
4467be21 | 9987 | |
0adfe95a | 9988 | @deffn {Scheme Procedure} dbus-service [#:dbus @var{dbus}] [#:services '()] |
fe1a39d3 LC |
9989 | Return a service that runs the ``system bus'', using @var{dbus}, with |
9990 | support for @var{services}. | |
aa4ed923 | 9991 | |
fe1a39d3 LC |
9992 | @uref{http://dbus.freedesktop.org/, D-Bus} is an inter-process communication |
9993 | facility. Its system bus is used to allow system services to communicate | |
1068f26b | 9994 | and to be notified of system-wide events. |
aa4ed923 | 9995 | |
fe1a39d3 LC |
9996 | @var{services} must be a list of packages that provide an |
9997 | @file{etc/dbus-1/system.d} directory containing additional D-Bus configuration | |
9998 | and policy files. For example, to allow avahi-daemon to use the system bus, | |
9999 | @var{services} must be equal to @code{(list avahi)}. | |
aa4ed923 AK |
10000 | @end deffn |
10001 | ||
0adfe95a | 10002 | @deffn {Scheme Procedure} elogind-service [#:config @var{config}] |
4650a77e AW |
10003 | Return a service that runs the @code{elogind} login and |
10004 | seat management daemon. @uref{https://github.com/andywingo/elogind, | |
10005 | Elogind} exposes a D-Bus interface that can be used to know which users | |
10006 | are logged in, know what kind of sessions they have open, suspend the | |
10007 | system, inhibit system suspend, reboot the system, and other tasks. | |
10008 | ||
10009 | Elogind handles most system-level power events for a computer, for | |
10010 | example suspending the system when a lid is closed, or shutting it down | |
10011 | when the power button is pressed. | |
10012 | ||
10013 | The @var{config} keyword argument specifies the configuration for | |
1068f26b | 10014 | elogind, and should be the result of an @code{(elogind-configuration |
4650a77e AW |
10015 | (@var{parameter} @var{value})...)} invocation. Available parameters and |
10016 | their default values are: | |
10017 | ||
10018 | @table @code | |
10019 | @item kill-user-processes? | |
10020 | @code{#f} | |
10021 | @item kill-only-users | |
10022 | @code{()} | |
10023 | @item kill-exclude-users | |
10024 | @code{("root")} | |
10025 | @item inhibit-delay-max-seconds | |
10026 | @code{5} | |
10027 | @item handle-power-key | |
10028 | @code{poweroff} | |
10029 | @item handle-suspend-key | |
10030 | @code{suspend} | |
10031 | @item handle-hibernate-key | |
10032 | @code{hibernate} | |
10033 | @item handle-lid-switch | |
10034 | @code{suspend} | |
10035 | @item handle-lid-switch-docked | |
10036 | @code{ignore} | |
10037 | @item power-key-ignore-inhibited? | |
10038 | @code{#f} | |
10039 | @item suspend-key-ignore-inhibited? | |
10040 | @code{#f} | |
10041 | @item hibernate-key-ignore-inhibited? | |
10042 | @code{#f} | |
10043 | @item lid-switch-ignore-inhibited? | |
10044 | @code{#t} | |
10045 | @item holdoff-timeout-seconds | |
10046 | @code{30} | |
10047 | @item idle-action | |
10048 | @code{ignore} | |
10049 | @item idle-action-seconds | |
10050 | @code{(* 30 60)} | |
10051 | @item runtime-directory-size-percent | |
10052 | @code{10} | |
10053 | @item runtime-directory-size | |
10054 | @code{#f} | |
10055 | @item remove-ipc? | |
10056 | @code{#t} | |
10057 | @item suspend-state | |
10058 | @code{("mem" "standby" "freeze")} | |
10059 | @item suspend-mode | |
10060 | @code{()} | |
10061 | @item hibernate-state | |
10062 | @code{("disk")} | |
10063 | @item hibernate-mode | |
10064 | @code{("platform" "shutdown")} | |
10065 | @item hybrid-sleep-state | |
10066 | @code{("disk")} | |
10067 | @item hybrid-sleep-mode | |
10068 | @code{("suspend" "platform" "shutdown")} | |
10069 | @end table | |
10070 | @end deffn | |
10071 | ||
be1c2c54 | 10072 | @deffn {Scheme Procedure} polkit-service @ |
4650a77e | 10073 | [#:polkit @var{polkit}] |
222e3319 LC |
10074 | Return a service that runs the |
10075 | @uref{http://www.freedesktop.org/wiki/Software/polkit/, Polkit privilege | |
10076 | management service}, which allows system administrators to grant access to | |
10077 | privileged operations in a structured way. By querying the Polkit service, a | |
10078 | privileged system component can know when it should grant additional | |
10079 | capabilities to ordinary users. For example, an ordinary user can be granted | |
10080 | the capability to suspend the system if the user is logged in locally. | |
4650a77e AW |
10081 | @end deffn |
10082 | ||
be1c2c54 | 10083 | @deffn {Scheme Procedure} upower-service [#:upower @var{upower}] @ |
be234128 AW |
10084 | [#:watts-up-pro? #f] @ |
10085 | [#:poll-batteries? #t] @ | |
10086 | [#:ignore-lid? #f] @ | |
10087 | [#:use-percentage-for-policy? #f] @ | |
10088 | [#:percentage-low 10] @ | |
10089 | [#:percentage-critical 3] @ | |
10090 | [#:percentage-action 2] @ | |
10091 | [#:time-low 1200] @ | |
10092 | [#:time-critical 300] @ | |
10093 | [#:time-action 120] @ | |
10094 | [#:critical-power-action 'hybrid-sleep] | |
10095 | Return a service that runs @uref{http://upower.freedesktop.org/, | |
10096 | @command{upowerd}}, a system-wide monitor for power consumption and battery | |
10097 | levels, with the given configuration settings. It implements the | |
10098 | @code{org.freedesktop.UPower} D-Bus interface, and is notably used by | |
10099 | GNOME. | |
10100 | @end deffn | |
10101 | ||
2b9e0a94 LC |
10102 | @deffn {Scheme Procedure} udisks-service [#:udisks @var{udisks}] |
10103 | Return a service for @uref{http://udisks.freedesktop.org/docs/latest/, | |
10104 | UDisks}, a @dfn{disk management} daemon that provides user interfaces with | |
10105 | notifications and ways to mount/unmount disks. Programs that talk to UDisks | |
10106 | include the @command{udisksctl} command, part of UDisks, and GNOME Disks. | |
10107 | @end deffn | |
10108 | ||
be1c2c54 | 10109 | @deffn {Scheme Procedure} colord-service [#:colord @var{colord}] |
7ce597ff AW |
10110 | Return a service that runs @command{colord}, a system service with a D-Bus |
10111 | interface to manage the color profiles of input and output devices such as | |
10112 | screens and scanners. It is notably used by the GNOME Color Manager graphical | |
10113 | tool. See @uref{http://www.freedesktop.org/software/colord/, the colord web | |
10114 | site} for more information. | |
10115 | @end deffn | |
10116 | ||
cee32ee4 | 10117 | @deffn {Scheme Procedure} geoclue-application name [#:allowed? #t] [#:system? #f] [#:users '()] |
1068f26b | 10118 | Return a configuration allowing an application to access GeoClue |
cee32ee4 AW |
10119 | location data. @var{name} is the Desktop ID of the application, without |
10120 | the @code{.desktop} part. If @var{allowed?} is true, the application | |
10121 | will have access to location information by default. The boolean | |
1068f26b | 10122 | @var{system?} value indicates whether an application is a system component |
cee32ee4 AW |
10123 | or not. Finally @var{users} is a list of UIDs of all users for which |
10124 | this application is allowed location info access. An empty users list | |
10125 | means that all users are allowed. | |
10126 | @end deffn | |
10127 | ||
10128 | @defvr {Scheme Variable} %standard-geoclue-applications | |
10129 | The standard list of well-known GeoClue application configurations, | |
1068f26b AE |
10130 | granting authority to the GNOME date-and-time utility to ask for the |
10131 | current location in order to set the time zone, and allowing the | |
10132 | IceCat and Epiphany web browsers to request location information. | |
10133 | IceCat and Epiphany both query the user before allowing a web page to | |
cee32ee4 AW |
10134 | know the user's location. |
10135 | @end defvr | |
10136 | ||
be1c2c54 | 10137 | @deffn {Scheme Procedure} geoclue-service [#:colord @var{colord}] @ |
cee32ee4 AW |
10138 | [#:whitelist '()] @ |
10139 | [#:wifi-geolocation-url "https://location.services.mozilla.com/v1/geolocate?key=geoclue"] @ | |
10140 | [#:submit-data? #f] | |
10141 | [#:wifi-submission-url "https://location.services.mozilla.com/v1/submit?key=geoclue"] @ | |
10142 | [#:submission-nick "geoclue"] @ | |
10143 | [#:applications %standard-geoclue-applications] | |
10144 | Return a service that runs the GeoClue location service. This service | |
10145 | provides a D-Bus interface to allow applications to request access to a | |
10146 | user's physical location, and optionally to add information to online | |
10147 | location databases. See | |
10148 | @uref{https://wiki.freedesktop.org/www/Software/GeoClue/, the GeoClue | |
10149 | web site} for more information. | |
10150 | @end deffn | |
10151 | ||
922e21f4 SB |
10152 | @deffn {Scheme Procedure} bluetooth-service [#:bluez @var{bluez}] |
10153 | Return a service that runs the @command{bluetoothd} daemon, which manages | |
10154 | all the Bluetooth devices and provides a number of D-Bus interfaces. | |
10155 | ||
10156 | Users need to be in the @code{lp} group to access the D-Bus service. | |
10157 | @end deffn | |
10158 | ||
105369a4 DT |
10159 | @node Database Services |
10160 | @subsubsection Database Services | |
10161 | ||
e32171ee JD |
10162 | @cindex database |
10163 | @cindex SQL | |
6575183b | 10164 | The @code{(gnu services databases)} module provides the following services. |
105369a4 | 10165 | |
be1c2c54 | 10166 | @deffn {Scheme Procedure} postgresql-service [#:postgresql postgresql] @ |
105369a4 DT |
10167 | [#:config-file] [#:data-directory ``/var/lib/postgresql/data''] |
10168 | Return a service that runs @var{postgresql}, the PostgreSQL database | |
10169 | server. | |
10170 | ||
10171 | The PostgreSQL daemon loads its runtime configuration from | |
10172 | @var{config-file} and stores the database cluster in | |
10173 | @var{data-directory}. | |
10174 | @end deffn | |
fe1a39d3 | 10175 | |
6575183b SB |
10176 | @deffn {Scheme Procedure} mysql-service [#:config (mysql-configuration)] |
10177 | Return a service that runs @command{mysqld}, the MySQL or MariaDB | |
10178 | database server. | |
10179 | ||
10180 | The optional @var{config} argument specifies the configuration for | |
c940b8e6 | 10181 | @command{mysqld}, which should be a @code{<mysql-configuration>} object. |
6575183b SB |
10182 | @end deffn |
10183 | ||
10184 | @deftp {Data Type} mysql-configuration | |
10185 | Data type representing the configuration of @var{mysql-service}. | |
10186 | ||
10187 | @table @asis | |
10188 | @item @code{mysql} (default: @var{mariadb}) | |
10189 | Package object of the MySQL database server, can be either @var{mariadb} | |
10190 | or @var{mysql}. | |
10191 | ||
7414de0a | 10192 | For MySQL, a temporary root password will be displayed at activation time. |
6575183b | 10193 | For MariaDB, the root password is empty. |
4b41febf CB |
10194 | |
10195 | @item @code{port} (default: @code{3306}) | |
10196 | TCP port on which the database server listens for incoming connections. | |
6575183b SB |
10197 | @end table |
10198 | @end deftp | |
10199 | ||
d8c18af8 AW |
10200 | @node Mail Services |
10201 | @subsubsection Mail Services | |
10202 | ||
e32171ee JD |
10203 | @cindex mail |
10204 | @cindex email | |
d8c18af8 | 10205 | The @code{(gnu services mail)} module provides Guix service definitions |
f88371e8 SB |
10206 | for email services: IMAP, POP3, and LMTP servers, as well as mail |
10207 | transport agents (MTAs). Lots of acronyms! These services are detailed | |
10208 | in the subsections below. | |
d8c18af8 | 10209 | |
f88371e8 | 10210 | @subsubheading Dovecot Service |
d8c18af8 AW |
10211 | |
10212 | @deffn {Scheme Procedure} dovecot-service [#:config (dovecot-configuration)] | |
10213 | Return a service that runs the Dovecot IMAP/POP3/LMTP mail server. | |
10214 | @end deffn | |
10215 | ||
1068f26b | 10216 | By default, Dovecot does not need much configuration; the default |
d8c18af8 AW |
10217 | configuration object created by @code{(dovecot-configuration)} will |
10218 | suffice if your mail is delivered to @code{~/Maildir}. A self-signed | |
10219 | certificate will be generated for TLS-protected connections, though | |
10220 | Dovecot will also listen on cleartext ports by default. There are a | |
1068f26b | 10221 | number of options, though, which mail administrators might need to change, |
d8c18af8 AW |
10222 | and as is the case with other services, Guix allows the system |
10223 | administrator to specify these parameters via a uniform Scheme interface. | |
10224 | ||
10225 | For example, to specify that mail is located at @code{maildir~/.mail}, | |
10226 | one would instantiate the Dovecot service like this: | |
10227 | ||
10228 | @example | |
10229 | (dovecot-service #:config | |
10230 | (dovecot-configuration | |
10231 | (mail-location "maildir:~/.mail"))) | |
10232 | @end example | |
10233 | ||
10234 | The available configuration parameters follow. Each parameter | |
10235 | definition is preceded by its type; for example, @samp{string-list foo} | |
10236 | indicates that the @code{foo} parameter should be specified as a list of | |
10237 | strings. There is also a way to specify the configuration as a string, | |
10238 | if you have an old @code{dovecot.conf} file that you want to port over | |
10239 | from some other system; see the end for more details. | |
10240 | ||
10241 | @c The following documentation was initially generated by | |
10242 | @c (generate-documentation) in (gnu services mail). Manually maintained | |
10243 | @c documentation is better, so we shouldn't hesitate to edit below as | |
10244 | @c needed. However if the change you want to make to this documentation | |
10245 | @c can be done in an automated way, it's probably easier to change | |
10246 | @c (generate-documentation) than to make it below and have to deal with | |
10247 | @c the churn as dovecot updates. | |
10248 | ||
10249 | Available @code{dovecot-configuration} fields are: | |
10250 | ||
10251 | @deftypevr {@code{dovecot-configuration} parameter} package dovecot | |
10252 | The dovecot package. | |
10253 | @end deftypevr | |
10254 | ||
10255 | @deftypevr {@code{dovecot-configuration} parameter} comma-separated-string-list listen | |
1068f26b AE |
10256 | A list of IPs or hosts where to listen for connections. @samp{*} |
10257 | listens on all IPv4 interfaces, @samp{::} listens on all IPv6 | |
d8c18af8 AW |
10258 | interfaces. If you want to specify non-default ports or anything more |
10259 | complex, customize the address and port fields of the | |
10260 | @samp{inet-listener} of the specific services you are interested in. | |
10261 | @end deftypevr | |
10262 | ||
10263 | @deftypevr {@code{dovecot-configuration} parameter} protocol-configuration-list protocols | |
10264 | List of protocols we want to serve. Available protocols include | |
10265 | @samp{imap}, @samp{pop3}, and @samp{lmtp}. | |
10266 | ||
10267 | Available @code{protocol-configuration} fields are: | |
10268 | ||
10269 | @deftypevr {@code{protocol-configuration} parameter} string name | |
10270 | The name of the protocol. | |
10271 | @end deftypevr | |
10272 | ||
10273 | @deftypevr {@code{protocol-configuration} parameter} string auth-socket-path | |
1068f26b | 10274 | UNIX socket path to the master authentication server to find users. |
d8c18af8 | 10275 | This is used by imap (for shared users) and lda. |
1068f26b | 10276 | It defaults to @samp{"/var/run/dovecot/auth-userdb"}. |
d8c18af8 AW |
10277 | @end deftypevr |
10278 | ||
10279 | @deftypevr {@code{protocol-configuration} parameter} space-separated-string-list mail-plugins | |
10280 | Space separated list of plugins to load. | |
10281 | @end deftypevr | |
10282 | ||
10283 | @deftypevr {@code{protocol-configuration} parameter} non-negative-integer mail-max-userip-connections | |
10284 | Maximum number of IMAP connections allowed for a user from each IP | |
10285 | address. NOTE: The username is compared case-sensitively. | |
10286 | Defaults to @samp{10}. | |
10287 | @end deftypevr | |
10288 | ||
10289 | @end deftypevr | |
10290 | ||
10291 | @deftypevr {@code{dovecot-configuration} parameter} service-configuration-list services | |
10292 | List of services to enable. Available services include @samp{imap}, | |
10293 | @samp{imap-login}, @samp{pop3}, @samp{pop3-login}, @samp{auth}, and | |
10294 | @samp{lmtp}. | |
10295 | ||
10296 | Available @code{service-configuration} fields are: | |
10297 | ||
10298 | @deftypevr {@code{service-configuration} parameter} string kind | |
10299 | The service kind. Valid values include @code{director}, | |
10300 | @code{imap-login}, @code{pop3-login}, @code{lmtp}, @code{imap}, | |
10301 | @code{pop3}, @code{auth}, @code{auth-worker}, @code{dict}, | |
10302 | @code{tcpwrap}, @code{quota-warning}, or anything else. | |
10303 | @end deftypevr | |
10304 | ||
10305 | @deftypevr {@code{service-configuration} parameter} listener-configuration-list listeners | |
1068f26b | 10306 | Listeners for the service. A listener is either a |
d8c18af8 AW |
10307 | @code{unix-listener-configuration}, a @code{fifo-listener-configuration}, or |
10308 | an @code{inet-listener-configuration}. | |
10309 | Defaults to @samp{()}. | |
10310 | ||
10311 | Available @code{unix-listener-configuration} fields are: | |
10312 | ||
10313 | @deftypevr {@code{unix-listener-configuration} parameter} file-name path | |
10314 | The file name on which to listen. | |
10315 | @end deftypevr | |
10316 | ||
10317 | @deftypevr {@code{unix-listener-configuration} parameter} string mode | |
10318 | The access mode for the socket. | |
10319 | Defaults to @samp{"0600"}. | |
10320 | @end deftypevr | |
10321 | ||
10322 | @deftypevr {@code{unix-listener-configuration} parameter} string user | |
f9b9a033 | 10323 | The user to own the socket. |
d8c18af8 AW |
10324 | Defaults to @samp{""}. |
10325 | @end deftypevr | |
10326 | ||
10327 | @deftypevr {@code{unix-listener-configuration} parameter} string group | |
10328 | The group to own the socket. | |
10329 | Defaults to @samp{""}. | |
10330 | @end deftypevr | |
10331 | ||
10332 | ||
10333 | Available @code{fifo-listener-configuration} fields are: | |
10334 | ||
10335 | @deftypevr {@code{fifo-listener-configuration} parameter} file-name path | |
10336 | The file name on which to listen. | |
10337 | @end deftypevr | |
10338 | ||
10339 | @deftypevr {@code{fifo-listener-configuration} parameter} string mode | |
10340 | The access mode for the socket. | |
10341 | Defaults to @samp{"0600"}. | |
10342 | @end deftypevr | |
10343 | ||
10344 | @deftypevr {@code{fifo-listener-configuration} parameter} string user | |
f9b9a033 | 10345 | The user to own the socket. |
d8c18af8 AW |
10346 | Defaults to @samp{""}. |
10347 | @end deftypevr | |
10348 | ||
10349 | @deftypevr {@code{fifo-listener-configuration} parameter} string group | |
10350 | The group to own the socket. | |
10351 | Defaults to @samp{""}. | |
10352 | @end deftypevr | |
10353 | ||
10354 | ||
10355 | Available @code{inet-listener-configuration} fields are: | |
10356 | ||
10357 | @deftypevr {@code{inet-listener-configuration} parameter} string protocol | |
10358 | The protocol to listen for. | |
10359 | @end deftypevr | |
10360 | ||
10361 | @deftypevr {@code{inet-listener-configuration} parameter} string address | |
10362 | The address on which to listen, or empty for all addresses. | |
10363 | Defaults to @samp{""}. | |
10364 | @end deftypevr | |
10365 | ||
10366 | @deftypevr {@code{inet-listener-configuration} parameter} non-negative-integer port | |
10367 | The port on which to listen. | |
10368 | @end deftypevr | |
10369 | ||
10370 | @deftypevr {@code{inet-listener-configuration} parameter} boolean ssl? | |
10371 | Whether to use SSL for this service; @samp{yes}, @samp{no}, or | |
10372 | @samp{required}. | |
10373 | Defaults to @samp{#t}. | |
10374 | @end deftypevr | |
10375 | ||
10376 | @end deftypevr | |
10377 | ||
10378 | @deftypevr {@code{service-configuration} parameter} non-negative-integer service-count | |
10379 | Number of connections to handle before starting a new process. | |
10380 | Typically the only useful values are 0 (unlimited) or 1. 1 is more | |
10381 | secure, but 0 is faster. <doc/wiki/LoginProcess.txt>. | |
10382 | Defaults to @samp{1}. | |
10383 | @end deftypevr | |
10384 | ||
10385 | @deftypevr {@code{service-configuration} parameter} non-negative-integer process-min-avail | |
10386 | Number of processes to always keep waiting for more connections. | |
10387 | Defaults to @samp{0}. | |
10388 | @end deftypevr | |
10389 | ||
10390 | @deftypevr {@code{service-configuration} parameter} non-negative-integer vsz-limit | |
10391 | If you set @samp{service-count 0}, you probably need to grow | |
10392 | this. | |
10393 | Defaults to @samp{256000000}. | |
10394 | @end deftypevr | |
10395 | ||
10396 | @end deftypevr | |
10397 | ||
10398 | @deftypevr {@code{dovecot-configuration} parameter} dict-configuration dict | |
10399 | Dict configuration, as created by the @code{dict-configuration} | |
10400 | constructor. | |
10401 | ||
10402 | Available @code{dict-configuration} fields are: | |
10403 | ||
10404 | @deftypevr {@code{dict-configuration} parameter} free-form-fields entries | |
10405 | A list of key-value pairs that this dict should hold. | |
10406 | Defaults to @samp{()}. | |
10407 | @end deftypevr | |
10408 | ||
10409 | @end deftypevr | |
10410 | ||
10411 | @deftypevr {@code{dovecot-configuration} parameter} passdb-configuration-list passdbs | |
1068f26b | 10412 | A list of passdb configurations, each one created by the |
d8c18af8 AW |
10413 | @code{passdb-configuration} constructor. |
10414 | ||
10415 | Available @code{passdb-configuration} fields are: | |
10416 | ||
10417 | @deftypevr {@code{passdb-configuration} parameter} string driver | |
10418 | The driver that the passdb should use. Valid values include | |
10419 | @samp{pam}, @samp{passwd}, @samp{shadow}, @samp{bsdauth}, and | |
10420 | @samp{static}. | |
10421 | Defaults to @samp{"pam"}. | |
10422 | @end deftypevr | |
10423 | ||
10424 | @deftypevr {@code{passdb-configuration} parameter} free-form-args args | |
10425 | A list of key-value args to the passdb driver. | |
10426 | Defaults to @samp{()}. | |
10427 | @end deftypevr | |
10428 | ||
10429 | @end deftypevr | |
10430 | ||
10431 | @deftypevr {@code{dovecot-configuration} parameter} userdb-configuration-list userdbs | |
10432 | List of userdb configurations, each one created by the | |
10433 | @code{userdb-configuration} constructor. | |
10434 | ||
10435 | Available @code{userdb-configuration} fields are: | |
10436 | ||
10437 | @deftypevr {@code{userdb-configuration} parameter} string driver | |
10438 | The driver that the userdb should use. Valid values include | |
10439 | @samp{passwd} and @samp{static}. | |
10440 | Defaults to @samp{"passwd"}. | |
10441 | @end deftypevr | |
10442 | ||
10443 | @deftypevr {@code{userdb-configuration} parameter} free-form-args args | |
10444 | A list of key-value args to the userdb driver. | |
10445 | Defaults to @samp{()}. | |
10446 | @end deftypevr | |
10447 | ||
10448 | @deftypevr {@code{userdb-configuration} parameter} free-form-args override-fields | |
10449 | Override fields from passwd. | |
10450 | Defaults to @samp{()}. | |
10451 | @end deftypevr | |
10452 | ||
10453 | @end deftypevr | |
10454 | ||
10455 | @deftypevr {@code{dovecot-configuration} parameter} plugin-configuration plugin-configuration | |
10456 | Plug-in configuration, created by the @code{plugin-configuration} | |
10457 | constructor. | |
10458 | @end deftypevr | |
10459 | ||
10460 | @deftypevr {@code{dovecot-configuration} parameter} list-of-namespace-configuration namespaces | |
10461 | List of namespaces. Each item in the list is created by the | |
10462 | @code{namespace-configuration} constructor. | |
10463 | ||
10464 | Available @code{namespace-configuration} fields are: | |
10465 | ||
10466 | @deftypevr {@code{namespace-configuration} parameter} string name | |
10467 | Name for this namespace. | |
10468 | @end deftypevr | |
10469 | ||
10470 | @deftypevr {@code{namespace-configuration} parameter} string type | |
10471 | Namespace type: @samp{private}, @samp{shared} or @samp{public}. | |
10472 | Defaults to @samp{"private"}. | |
10473 | @end deftypevr | |
10474 | ||
10475 | @deftypevr {@code{namespace-configuration} parameter} string separator | |
10476 | Hierarchy separator to use. You should use the same separator for | |
10477 | all namespaces or some clients get confused. @samp{/} is usually a good | |
10478 | one. The default however depends on the underlying mail storage | |
10479 | format. | |
10480 | Defaults to @samp{""}. | |
10481 | @end deftypevr | |
10482 | ||
10483 | @deftypevr {@code{namespace-configuration} parameter} string prefix | |
10484 | Prefix required to access this namespace. This needs to be | |
10485 | different for all namespaces. For example @samp{Public/}. | |
10486 | Defaults to @samp{""}. | |
10487 | @end deftypevr | |
10488 | ||
10489 | @deftypevr {@code{namespace-configuration} parameter} string location | |
1068f26b | 10490 | Physical location of the mailbox. This is in the same format as |
d8c18af8 AW |
10491 | mail_location, which is also the default for it. |
10492 | Defaults to @samp{""}. | |
10493 | @end deftypevr | |
10494 | ||
10495 | @deftypevr {@code{namespace-configuration} parameter} boolean inbox? | |
10496 | There can be only one INBOX, and this setting defines which | |
10497 | namespace has it. | |
10498 | Defaults to @samp{#f}. | |
10499 | @end deftypevr | |
10500 | ||
10501 | @deftypevr {@code{namespace-configuration} parameter} boolean hidden? | |
10502 | If namespace is hidden, it's not advertised to clients via NAMESPACE | |
10503 | extension. You'll most likely also want to set @samp{list? #f}. This is mostly | |
10504 | useful when converting from another server with different namespaces | |
10505 | which you want to deprecate but still keep working. For example you can | |
10506 | create hidden namespaces with prefixes @samp{~/mail/}, @samp{~%u/mail/} | |
10507 | and @samp{mail/}. | |
10508 | Defaults to @samp{#f}. | |
10509 | @end deftypevr | |
10510 | ||
10511 | @deftypevr {@code{namespace-configuration} parameter} boolean list? | |
1068f26b AE |
10512 | Show the mailboxes under this namespace with the LIST command. This |
10513 | makes the namespace visible for clients that do not support the NAMESPACE | |
d8c18af8 AW |
10514 | extension. The special @code{children} value lists child mailboxes, but |
10515 | hides the namespace prefix. | |
10516 | Defaults to @samp{#t}. | |
10517 | @end deftypevr | |
10518 | ||
10519 | @deftypevr {@code{namespace-configuration} parameter} boolean subscriptions? | |
10520 | Namespace handles its own subscriptions. If set to @code{#f}, the | |
10521 | parent namespace handles them. The empty prefix should always have this | |
1068f26b | 10522 | as @code{#t}). |
d8c18af8 AW |
10523 | Defaults to @samp{#t}. |
10524 | @end deftypevr | |
10525 | ||
10526 | @deftypevr {@code{namespace-configuration} parameter} mailbox-configuration-list mailboxes | |
10527 | List of predefined mailboxes in this namespace. | |
10528 | Defaults to @samp{()}. | |
10529 | ||
10530 | Available @code{mailbox-configuration} fields are: | |
10531 | ||
10532 | @deftypevr {@code{mailbox-configuration} parameter} string name | |
10533 | Name for this mailbox. | |
10534 | @end deftypevr | |
10535 | ||
10536 | @deftypevr {@code{mailbox-configuration} parameter} string auto | |
10537 | @samp{create} will automatically create this mailbox. | |
10538 | @samp{subscribe} will both create and subscribe to the mailbox. | |
10539 | Defaults to @samp{"no"}. | |
10540 | @end deftypevr | |
10541 | ||
10542 | @deftypevr {@code{mailbox-configuration} parameter} space-separated-string-list special-use | |
10543 | List of IMAP @code{SPECIAL-USE} attributes as specified by RFC 6154. | |
10544 | Valid values are @code{\All}, @code{\Archive}, @code{\Drafts}, | |
10545 | @code{\Flagged}, @code{\Junk}, @code{\Sent}, and @code{\Trash}. | |
10546 | Defaults to @samp{()}. | |
10547 | @end deftypevr | |
10548 | ||
10549 | @end deftypevr | |
10550 | ||
10551 | @end deftypevr | |
10552 | ||
10553 | @deftypevr {@code{dovecot-configuration} parameter} file-name base-dir | |
10554 | Base directory where to store runtime data. | |
10555 | Defaults to @samp{"/var/run/dovecot/"}. | |
10556 | @end deftypevr | |
10557 | ||
10558 | @deftypevr {@code{dovecot-configuration} parameter} string login-greeting | |
10559 | Greeting message for clients. | |
10560 | Defaults to @samp{"Dovecot ready."}. | |
10561 | @end deftypevr | |
10562 | ||
10563 | @deftypevr {@code{dovecot-configuration} parameter} space-separated-string-list login-trusted-networks | |
10564 | List of trusted network ranges. Connections from these IPs are | |
10565 | allowed to override their IP addresses and ports (for logging and for | |
10566 | authentication checks). @samp{disable-plaintext-auth} is also ignored | |
1068f26b | 10567 | for these networks. Typically you would specify your IMAP proxy servers |
d8c18af8 AW |
10568 | here. |
10569 | Defaults to @samp{()}. | |
10570 | @end deftypevr | |
10571 | ||
10572 | @deftypevr {@code{dovecot-configuration} parameter} space-separated-string-list login-access-sockets | |
10573 | List of login access check sockets (e.g. tcpwrap). | |
10574 | Defaults to @samp{()}. | |
10575 | @end deftypevr | |
10576 | ||
10577 | @deftypevr {@code{dovecot-configuration} parameter} boolean verbose-proctitle? | |
10578 | Show more verbose process titles (in ps). Currently shows user name | |
1068f26b AE |
10579 | and IP address. Useful for seeing who is actually using the IMAP |
10580 | processes (e.g. shared mailboxes or if the same uid is used for multiple | |
d8c18af8 AW |
10581 | accounts). |
10582 | Defaults to @samp{#f}. | |
10583 | @end deftypevr | |
10584 | ||
10585 | @deftypevr {@code{dovecot-configuration} parameter} boolean shutdown-clients? | |
10586 | Should all processes be killed when Dovecot master process shuts down. | |
10587 | Setting this to @code{#f} means that Dovecot can be upgraded without | |
10588 | forcing existing client connections to close (although that could also | |
1068f26b | 10589 | be a problem if the upgrade is e.g. due to a security fix). |
d8c18af8 AW |
10590 | Defaults to @samp{#t}. |
10591 | @end deftypevr | |
10592 | ||
10593 | @deftypevr {@code{dovecot-configuration} parameter} non-negative-integer doveadm-worker-count | |
10594 | If non-zero, run mail commands via this many connections to doveadm | |
10595 | server, instead of running them directly in the same process. | |
10596 | Defaults to @samp{0}. | |
10597 | @end deftypevr | |
10598 | ||
10599 | @deftypevr {@code{dovecot-configuration} parameter} string doveadm-socket-path | |
10600 | UNIX socket or host:port used for connecting to doveadm server. | |
10601 | Defaults to @samp{"doveadm-server"}. | |
10602 | @end deftypevr | |
10603 | ||
10604 | @deftypevr {@code{dovecot-configuration} parameter} space-separated-string-list import-environment | |
10605 | List of environment variables that are preserved on Dovecot startup | |
10606 | and passed down to all of its child processes. You can also give | |
10607 | key=value pairs to always set specific settings. | |
10608 | @end deftypevr | |
10609 | ||
10610 | @deftypevr {@code{dovecot-configuration} parameter} boolean disable-plaintext-auth? | |
10611 | Disable LOGIN command and all other plaintext authentications unless | |
10612 | SSL/TLS is used (LOGINDISABLED capability). Note that if the remote IP | |
10613 | matches the local IP (i.e. you're connecting from the same computer), | |
10614 | the connection is considered secure and plaintext authentication is | |
10615 | allowed. See also ssl=required setting. | |
10616 | Defaults to @samp{#t}. | |
10617 | @end deftypevr | |
10618 | ||
10619 | @deftypevr {@code{dovecot-configuration} parameter} non-negative-integer auth-cache-size | |
10620 | Authentication cache size (e.g. @samp{#e10e6}). 0 means it's disabled. | |
10621 | Note that bsdauth, PAM and vpopmail require @samp{cache-key} to be set | |
10622 | for caching to be used. | |
10623 | Defaults to @samp{0}. | |
10624 | @end deftypevr | |
10625 | ||
10626 | @deftypevr {@code{dovecot-configuration} parameter} string auth-cache-ttl | |
10627 | Time to live for cached data. After TTL expires the cached record | |
10628 | is no longer used, *except* if the main database lookup returns internal | |
10629 | failure. We also try to handle password changes automatically: If | |
10630 | user's previous authentication was successful, but this one wasn't, the | |
10631 | cache isn't used. For now this works only with plaintext | |
10632 | authentication. | |
10633 | Defaults to @samp{"1 hour"}. | |
10634 | @end deftypevr | |
10635 | ||
10636 | @deftypevr {@code{dovecot-configuration} parameter} string auth-cache-negative-ttl | |
10637 | TTL for negative hits (user not found, password mismatch). | |
10638 | 0 disables caching them completely. | |
10639 | Defaults to @samp{"1 hour"}. | |
10640 | @end deftypevr | |
10641 | ||
10642 | @deftypevr {@code{dovecot-configuration} parameter} space-separated-string-list auth-realms | |
10643 | List of realms for SASL authentication mechanisms that need them. | |
10644 | You can leave it empty if you don't want to support multiple realms. | |
10645 | Many clients simply use the first one listed here, so keep the default | |
10646 | realm first. | |
10647 | Defaults to @samp{()}. | |
10648 | @end deftypevr | |
10649 | ||
10650 | @deftypevr {@code{dovecot-configuration} parameter} string auth-default-realm | |
10651 | Default realm/domain to use if none was specified. This is used for | |
10652 | both SASL realms and appending @@domain to username in plaintext | |
10653 | logins. | |
10654 | Defaults to @samp{""}. | |
10655 | @end deftypevr | |
10656 | ||
10657 | @deftypevr {@code{dovecot-configuration} parameter} string auth-username-chars | |
10658 | List of allowed characters in username. If the user-given username | |
10659 | contains a character not listed in here, the login automatically fails. | |
10660 | This is just an extra check to make sure user can't exploit any | |
10661 | potential quote escaping vulnerabilities with SQL/LDAP databases. If | |
10662 | you want to allow all characters, set this value to empty. | |
10663 | Defaults to @samp{"abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@@"}. | |
10664 | @end deftypevr | |
10665 | ||
10666 | @deftypevr {@code{dovecot-configuration} parameter} string auth-username-translation | |
10667 | Username character translations before it's looked up from | |
10668 | databases. The value contains series of from -> to characters. For | |
10669 | example @samp{#@@/@@} means that @samp{#} and @samp{/} characters are | |
10670 | translated to @samp{@@}. | |
10671 | Defaults to @samp{""}. | |
10672 | @end deftypevr | |
10673 | ||
10674 | @deftypevr {@code{dovecot-configuration} parameter} string auth-username-format | |
10675 | Username formatting before it's looked up from databases. You can | |
10676 | use the standard variables here, e.g. %Lu would lowercase the username, | |
10677 | %n would drop away the domain if it was given, or @samp{%n-AT-%d} would | |
10678 | change the @samp{@@} into @samp{-AT-}. This translation is done after | |
10679 | @samp{auth-username-translation} changes. | |
10680 | Defaults to @samp{"%Lu"}. | |
10681 | @end deftypevr | |
10682 | ||
10683 | @deftypevr {@code{dovecot-configuration} parameter} string auth-master-user-separator | |
10684 | If you want to allow master users to log in by specifying the master | |
10685 | username within the normal username string (i.e. not using SASL | |
10686 | mechanism's support for it), you can specify the separator character | |
10687 | here. The format is then <username><separator><master username>. | |
10688 | UW-IMAP uses @samp{*} as the separator, so that could be a good | |
10689 | choice. | |
10690 | Defaults to @samp{""}. | |
10691 | @end deftypevr | |
10692 | ||
10693 | @deftypevr {@code{dovecot-configuration} parameter} string auth-anonymous-username | |
10694 | Username to use for users logging in with ANONYMOUS SASL | |
10695 | mechanism. | |
10696 | Defaults to @samp{"anonymous"}. | |
10697 | @end deftypevr | |
10698 | ||
10699 | @deftypevr {@code{dovecot-configuration} parameter} non-negative-integer auth-worker-max-count | |
10700 | Maximum number of dovecot-auth worker processes. They're used to | |
10701 | execute blocking passdb and userdb queries (e.g. MySQL and PAM). | |
10702 | They're automatically created and destroyed as needed. | |
10703 | Defaults to @samp{30}. | |
10704 | @end deftypevr | |
10705 | ||
10706 | @deftypevr {@code{dovecot-configuration} parameter} string auth-gssapi-hostname | |
10707 | Host name to use in GSSAPI principal names. The default is to use | |
10708 | the name returned by gethostname(). Use @samp{$ALL} (with quotes) to | |
10709 | allow all keytab entries. | |
10710 | Defaults to @samp{""}. | |
10711 | @end deftypevr | |
10712 | ||
10713 | @deftypevr {@code{dovecot-configuration} parameter} string auth-krb5-keytab | |
10714 | Kerberos keytab to use for the GSSAPI mechanism. Will use the | |
8b499030 | 10715 | system default (usually @file{/etc/krb5.keytab}) if not specified. You may |
d8c18af8 AW |
10716 | need to change the auth service to run as root to be able to read this |
10717 | file. | |
10718 | Defaults to @samp{""}. | |
10719 | @end deftypevr | |
10720 | ||
10721 | @deftypevr {@code{dovecot-configuration} parameter} boolean auth-use-winbind? | |
10722 | Do NTLM and GSS-SPNEGO authentication using Samba's winbind daemon | |
10723 | and @samp{ntlm-auth} helper. | |
10724 | <doc/wiki/Authentication/Mechanisms/Winbind.txt>. | |
10725 | Defaults to @samp{#f}. | |
10726 | @end deftypevr | |
10727 | ||
10728 | @deftypevr {@code{dovecot-configuration} parameter} file-name auth-winbind-helper-path | |
10729 | Path for Samba's @samp{ntlm-auth} helper binary. | |
10730 | Defaults to @samp{"/usr/bin/ntlm_auth"}. | |
10731 | @end deftypevr | |
10732 | ||
10733 | @deftypevr {@code{dovecot-configuration} parameter} string auth-failure-delay | |
10734 | Time to delay before replying to failed authentications. | |
10735 | Defaults to @samp{"2 secs"}. | |
10736 | @end deftypevr | |
10737 | ||
10738 | @deftypevr {@code{dovecot-configuration} parameter} boolean auth-ssl-require-client-cert? | |
10739 | Require a valid SSL client certificate or the authentication | |
10740 | fails. | |
10741 | Defaults to @samp{#f}. | |
10742 | @end deftypevr | |
10743 | ||
10744 | @deftypevr {@code{dovecot-configuration} parameter} boolean auth-ssl-username-from-cert? | |
10745 | Take the username from client's SSL certificate, using | |
10746 | @code{X509_NAME_get_text_by_NID()} which returns the subject's DN's | |
10747 | CommonName. | |
10748 | Defaults to @samp{#f}. | |
10749 | @end deftypevr | |
10750 | ||
10751 | @deftypevr {@code{dovecot-configuration} parameter} space-separated-string-list auth-mechanisms | |
10752 | List of wanted authentication mechanisms. Supported mechanisms are: | |
10753 | @samp{plain}, @samp{login}, @samp{digest-md5}, @samp{cram-md5}, | |
10754 | @samp{ntlm}, @samp{rpa}, @samp{apop}, @samp{anonymous}, @samp{gssapi}, | |
10755 | @samp{otp}, @samp{skey}, and @samp{gss-spnego}. NOTE: See also | |
10756 | @samp{disable-plaintext-auth} setting. | |
10757 | @end deftypevr | |
10758 | ||
10759 | @deftypevr {@code{dovecot-configuration} parameter} space-separated-string-list director-servers | |
10760 | List of IPs or hostnames to all director servers, including ourself. | |
10761 | Ports can be specified as ip:port. The default port is the same as what | |
10762 | director service's @samp{inet-listener} is using. | |
10763 | Defaults to @samp{()}. | |
10764 | @end deftypevr | |
10765 | ||
10766 | @deftypevr {@code{dovecot-configuration} parameter} space-separated-string-list director-mail-servers | |
10767 | List of IPs or hostnames to all backend mail servers. Ranges are | |
10768 | allowed too, like 10.0.0.10-10.0.0.30. | |
10769 | Defaults to @samp{()}. | |
10770 | @end deftypevr | |
10771 | ||
10772 | @deftypevr {@code{dovecot-configuration} parameter} string director-user-expire | |
10773 | How long to redirect users to a specific server after it no longer | |
10774 | has any connections. | |
10775 | Defaults to @samp{"15 min"}. | |
10776 | @end deftypevr | |
10777 | ||
10778 | @deftypevr {@code{dovecot-configuration} parameter} non-negative-integer director-doveadm-port | |
10779 | TCP/IP port that accepts doveadm connections (instead of director | |
10780 | connections) If you enable this, you'll also need to add | |
10781 | @samp{inet-listener} for the port. | |
10782 | Defaults to @samp{0}. | |
10783 | @end deftypevr | |
10784 | ||
10785 | @deftypevr {@code{dovecot-configuration} parameter} string director-username-hash | |
10786 | How the username is translated before being hashed. Useful values | |
10787 | include %Ln if user can log in with or without @@domain, %Ld if mailboxes | |
10788 | are shared within domain. | |
10789 | Defaults to @samp{"%Lu"}. | |
10790 | @end deftypevr | |
10791 | ||
10792 | @deftypevr {@code{dovecot-configuration} parameter} string log-path | |
10793 | Log file to use for error messages. @samp{syslog} logs to syslog, | |
10794 | @samp{/dev/stderr} logs to stderr. | |
10795 | Defaults to @samp{"syslog"}. | |
10796 | @end deftypevr | |
10797 | ||
10798 | @deftypevr {@code{dovecot-configuration} parameter} string info-log-path | |
10799 | Log file to use for informational messages. Defaults to | |
10800 | @samp{log-path}. | |
10801 | Defaults to @samp{""}. | |
10802 | @end deftypevr | |
10803 | ||
10804 | @deftypevr {@code{dovecot-configuration} parameter} string debug-log-path | |
10805 | Log file to use for debug messages. Defaults to | |
10806 | @samp{info-log-path}. | |
10807 | Defaults to @samp{""}. | |
10808 | @end deftypevr | |
10809 | ||
10810 | @deftypevr {@code{dovecot-configuration} parameter} string syslog-facility | |
10811 | Syslog facility to use if you're logging to syslog. Usually if you | |
10812 | don't want to use @samp{mail}, you'll use local0..local7. Also other | |
10813 | standard facilities are supported. | |
10814 | Defaults to @samp{"mail"}. | |
10815 | @end deftypevr | |
10816 | ||
10817 | @deftypevr {@code{dovecot-configuration} parameter} boolean auth-verbose? | |
10818 | Log unsuccessful authentication attempts and the reasons why they | |
10819 | failed. | |
10820 | Defaults to @samp{#f}. | |
10821 | @end deftypevr | |
10822 | ||
10823 | @deftypevr {@code{dovecot-configuration} parameter} boolean auth-verbose-passwords? | |
10824 | In case of password mismatches, log the attempted password. Valid | |
10825 | values are no, plain and sha1. sha1 can be useful for detecting brute | |
10826 | force password attempts vs. user simply trying the same password over | |
10827 | and over again. You can also truncate the value to n chars by appending | |
10828 | ":n" (e.g. sha1:6). | |
10829 | Defaults to @samp{#f}. | |
10830 | @end deftypevr | |
10831 | ||
10832 | @deftypevr {@code{dovecot-configuration} parameter} boolean auth-debug? | |
10833 | Even more verbose logging for debugging purposes. Shows for example | |
10834 | SQL queries. | |
10835 | Defaults to @samp{#f}. | |
10836 | @end deftypevr | |
10837 | ||
10838 | @deftypevr {@code{dovecot-configuration} parameter} boolean auth-debug-passwords? | |
10839 | In case of password mismatches, log the passwords and used scheme so | |
10840 | the problem can be debugged. Enabling this also enables | |
10841 | @samp{auth-debug}. | |
10842 | Defaults to @samp{#f}. | |
10843 | @end deftypevr | |
10844 | ||
10845 | @deftypevr {@code{dovecot-configuration} parameter} boolean mail-debug? | |
10846 | Enable mail process debugging. This can help you figure out why | |
10847 | Dovecot isn't finding your mails. | |
10848 | Defaults to @samp{#f}. | |
10849 | @end deftypevr | |
10850 | ||
10851 | @deftypevr {@code{dovecot-configuration} parameter} boolean verbose-ssl? | |
10852 | Show protocol level SSL errors. | |
10853 | Defaults to @samp{#f}. | |
10854 | @end deftypevr | |
10855 | ||
10856 | @deftypevr {@code{dovecot-configuration} parameter} string log-timestamp | |
10857 | Prefix for each line written to log file. % codes are in | |
10858 | strftime(3) format. | |
10859 | Defaults to @samp{"\"%b %d %H:%M:%S \""}. | |
10860 | @end deftypevr | |
10861 | ||
10862 | @deftypevr {@code{dovecot-configuration} parameter} space-separated-string-list login-log-format-elements | |
10863 | List of elements we want to log. The elements which have a | |
10864 | non-empty variable value are joined together to form a comma-separated | |
10865 | string. | |
10866 | @end deftypevr | |
10867 | ||
10868 | @deftypevr {@code{dovecot-configuration} parameter} string login-log-format | |
10869 | Login log format. %s contains @samp{login-log-format-elements} | |
10870 | string, %$ contains the data we want to log. | |
10871 | Defaults to @samp{"%$: %s"}. | |
10872 | @end deftypevr | |
10873 | ||
10874 | @deftypevr {@code{dovecot-configuration} parameter} string mail-log-prefix | |
10875 | Log prefix for mail processes. See doc/wiki/Variables.txt for list | |
10876 | of possible variables you can use. | |
10877 | Defaults to @samp{"\"%s(%u): \""}. | |
10878 | @end deftypevr | |
10879 | ||
10880 | @deftypevr {@code{dovecot-configuration} parameter} string deliver-log-format | |
10881 | Format to use for logging mail deliveries. You can use variables: | |
10882 | @table @code | |
10883 | @item %$ | |
10884 | Delivery status message (e.g. @samp{saved to INBOX}) | |
10885 | @item %m | |
10886 | Message-ID | |
10887 | @item %s | |
10888 | Subject | |
10889 | @item %f | |
10890 | From address | |
10891 | @item %p | |
10892 | Physical size | |
10893 | @item %w | |
10894 | Virtual size. | |
10895 | @end table | |
10896 | Defaults to @samp{"msgid=%m: %$"}. | |
10897 | @end deftypevr | |
10898 | ||
10899 | @deftypevr {@code{dovecot-configuration} parameter} string mail-location | |
10900 | Location for users' mailboxes. The default is empty, which means | |
10901 | that Dovecot tries to find the mailboxes automatically. This won't work | |
10902 | if the user doesn't yet have any mail, so you should explicitly tell | |
10903 | Dovecot the full location. | |
10904 | ||
10905 | If you're using mbox, giving a path to the INBOX | |
10906 | file (e.g. /var/mail/%u) isn't enough. You'll also need to tell Dovecot | |
10907 | where the other mailboxes are kept. This is called the "root mail | |
10908 | directory", and it must be the first path given in the | |
10909 | @samp{mail-location} setting. | |
10910 | ||
10911 | There are a few special variables you can use, eg.: | |
10912 | ||
10913 | @table @samp | |
10914 | @item %u | |
10915 | username | |
10916 | @item %n | |
10917 | user part in user@@domain, same as %u if there's no domain | |
10918 | @item %d | |
10919 | domain part in user@@domain, empty if there's no domain | |
10920 | @item %h | |
10921 | home director | |
10922 | @end table | |
10923 | ||
10924 | See doc/wiki/Variables.txt for full list. Some examples: | |
10925 | @table @samp | |
10926 | @item maildir:~/Maildir | |
10927 | @item mbox:~/mail:INBOX=/var/mail/%u | |
10928 | @item mbox:/var/mail/%d/%1n/%n:INDEX=/var/indexes/%d/%1n/% | |
10929 | @end table | |
10930 | Defaults to @samp{""}. | |
10931 | @end deftypevr | |
10932 | ||
10933 | @deftypevr {@code{dovecot-configuration} parameter} string mail-uid | |
10934 | System user and group used to access mails. If you use multiple, | |
10935 | userdb can override these by returning uid or gid fields. You can use | |
10936 | either numbers or names. <doc/wiki/UserIds.txt>. | |
10937 | Defaults to @samp{""}. | |
10938 | @end deftypevr | |
10939 | ||
10940 | @deftypevr {@code{dovecot-configuration} parameter} string mail-gid | |
10941 | ||
10942 | Defaults to @samp{""}. | |
10943 | @end deftypevr | |
10944 | ||
10945 | @deftypevr {@code{dovecot-configuration} parameter} string mail-privileged-group | |
10946 | Group to enable temporarily for privileged operations. Currently | |
10947 | this is used only with INBOX when either its initial creation or | |
10948 | dotlocking fails. Typically this is set to "mail" to give access to | |
10949 | /var/mail. | |
10950 | Defaults to @samp{""}. | |
10951 | @end deftypevr | |
10952 | ||
10953 | @deftypevr {@code{dovecot-configuration} parameter} string mail-access-groups | |
10954 | Grant access to these supplementary groups for mail processes. | |
10955 | Typically these are used to set up access to shared mailboxes. Note | |
10956 | that it may be dangerous to set these if users can create | |
10957 | symlinks (e.g. if "mail" group is set here, ln -s /var/mail ~/mail/var | |
10958 | could allow a user to delete others' mailboxes, or ln -s | |
10959 | /secret/shared/box ~/mail/mybox would allow reading it). | |
10960 | Defaults to @samp{""}. | |
10961 | @end deftypevr | |
10962 | ||
10963 | @deftypevr {@code{dovecot-configuration} parameter} boolean mail-full-filesystem-access? | |
8f65585b | 10964 | Allow full file system access to clients. There's no access checks |
d8c18af8 AW |
10965 | other than what the operating system does for the active UID/GID. It |
10966 | works with both maildir and mboxes, allowing you to prefix mailboxes | |
10967 | names with e.g. /path/ or ~user/. | |
10968 | Defaults to @samp{#f}. | |
10969 | @end deftypevr | |
10970 | ||
10971 | @deftypevr {@code{dovecot-configuration} parameter} boolean mmap-disable? | |
10972 | Don't use mmap() at all. This is required if you store indexes to | |
8f65585b | 10973 | shared file systems (NFS or clustered file system). |
d8c18af8 AW |
10974 | Defaults to @samp{#f}. |
10975 | @end deftypevr | |
10976 | ||
10977 | @deftypevr {@code{dovecot-configuration} parameter} boolean dotlock-use-excl? | |
10978 | Rely on @samp{O_EXCL} to work when creating dotlock files. NFS | |
10979 | supports @samp{O_EXCL} since version 3, so this should be safe to use | |
10980 | nowadays by default. | |
10981 | Defaults to @samp{#t}. | |
10982 | @end deftypevr | |
10983 | ||
10984 | @deftypevr {@code{dovecot-configuration} parameter} string mail-fsync | |
10985 | When to use fsync() or fdatasync() calls: | |
10986 | @table @code | |
10987 | @item optimized | |
10988 | Whenever necessary to avoid losing important data | |
10989 | @item always | |
10990 | Useful with e.g. NFS when write()s are delayed | |
10991 | @item never | |
10992 | Never use it (best performance, but crashes can lose data). | |
10993 | @end table | |
10994 | Defaults to @samp{"optimized"}. | |
10995 | @end deftypevr | |
10996 | ||
10997 | @deftypevr {@code{dovecot-configuration} parameter} boolean mail-nfs-storage? | |
10998 | Mail storage exists in NFS. Set this to yes to make Dovecot flush | |
10999 | NFS caches whenever needed. If you're using only a single mail server | |
11000 | this isn't needed. | |
11001 | Defaults to @samp{#f}. | |
11002 | @end deftypevr | |
11003 | ||
11004 | @deftypevr {@code{dovecot-configuration} parameter} boolean mail-nfs-index? | |
11005 | Mail index files also exist in NFS. Setting this to yes requires | |
11006 | @samp{mmap-disable? #t} and @samp{fsync-disable? #f}. | |
11007 | Defaults to @samp{#f}. | |
11008 | @end deftypevr | |
11009 | ||
11010 | @deftypevr {@code{dovecot-configuration} parameter} string lock-method | |
11011 | Locking method for index files. Alternatives are fcntl, flock and | |
11012 | dotlock. Dotlocking uses some tricks which may create more disk I/O | |
11013 | than other locking methods. NFS users: flock doesn't work, remember to | |
11014 | change @samp{mmap-disable}. | |
11015 | Defaults to @samp{"fcntl"}. | |
11016 | @end deftypevr | |
11017 | ||
11018 | @deftypevr {@code{dovecot-configuration} parameter} file-name mail-temp-dir | |
11019 | Directory in which LDA/LMTP temporarily stores incoming mails >128 | |
11020 | kB. | |
11021 | Defaults to @samp{"/tmp"}. | |
11022 | @end deftypevr | |
11023 | ||
11024 | @deftypevr {@code{dovecot-configuration} parameter} non-negative-integer first-valid-uid | |
11025 | Valid UID range for users. This is mostly to make sure that users can't | |
11026 | log in as daemons or other system users. Note that denying root logins is | |
11027 | hardcoded to dovecot binary and can't be done even if @samp{first-valid-uid} | |
11028 | is set to 0. | |
11029 | Defaults to @samp{500}. | |
11030 | @end deftypevr | |
11031 | ||
11032 | @deftypevr {@code{dovecot-configuration} parameter} non-negative-integer last-valid-uid | |
11033 | ||
11034 | Defaults to @samp{0}. | |
11035 | @end deftypevr | |
11036 | ||
11037 | @deftypevr {@code{dovecot-configuration} parameter} non-negative-integer first-valid-gid | |
11038 | Valid GID range for users. Users having non-valid GID as primary group ID | |
11039 | aren't allowed to log in. If user belongs to supplementary groups with | |
11040 | non-valid GIDs, those groups are not set. | |
11041 | Defaults to @samp{1}. | |
11042 | @end deftypevr | |
11043 | ||
11044 | @deftypevr {@code{dovecot-configuration} parameter} non-negative-integer last-valid-gid | |
11045 | ||
11046 | Defaults to @samp{0}. | |
11047 | @end deftypevr | |
11048 | ||
11049 | @deftypevr {@code{dovecot-configuration} parameter} non-negative-integer mail-max-keyword-length | |
11050 | Maximum allowed length for mail keyword name. It's only forced when | |
11051 | trying to create new keywords. | |
11052 | Defaults to @samp{50}. | |
11053 | @end deftypevr | |
11054 | ||
11055 | @deftypevr {@code{dovecot-configuration} parameter} colon-separated-file-name-list valid-chroot-dirs | |
11056 | List of directories under which chrooting is allowed for mail | |
11057 | processes (i.e. /var/mail will allow chrooting to /var/mail/foo/bar | |
11058 | too). This setting doesn't affect @samp{login-chroot} | |
11059 | @samp{mail-chroot} or auth chroot settings. If this setting is empty, | |
11060 | "/./" in home dirs are ignored. WARNING: Never add directories here | |
11061 | which local users can modify, that may lead to root exploit. Usually | |
11062 | this should be done only if you don't allow shell access for users. | |
11063 | <doc/wiki/Chrooting.txt>. | |
11064 | Defaults to @samp{()}. | |
11065 | @end deftypevr | |
11066 | ||
11067 | @deftypevr {@code{dovecot-configuration} parameter} string mail-chroot | |
11068 | Default chroot directory for mail processes. This can be overridden | |
11069 | for specific users in user database by giving /./ in user's home | |
11070 | directory (e.g. /home/./user chroots into /home). Note that usually | |
11071 | there is no real need to do chrooting, Dovecot doesn't allow users to | |
11072 | access files outside their mail directory anyway. If your home | |
11073 | directories are prefixed with the chroot directory, append "/." to | |
11074 | @samp{mail-chroot}. <doc/wiki/Chrooting.txt>. | |
11075 | Defaults to @samp{""}. | |
11076 | @end deftypevr | |
11077 | ||
11078 | @deftypevr {@code{dovecot-configuration} parameter} file-name auth-socket-path | |
11079 | UNIX socket path to master authentication server to find users. | |
11080 | This is used by imap (for shared users) and lda. | |
11081 | Defaults to @samp{"/var/run/dovecot/auth-userdb"}. | |
11082 | @end deftypevr | |
11083 | ||
11084 | @deftypevr {@code{dovecot-configuration} parameter} file-name mail-plugin-dir | |
11085 | Directory where to look up mail plugins. | |
11086 | Defaults to @samp{"/usr/lib/dovecot"}. | |
11087 | @end deftypevr | |
11088 | ||
11089 | @deftypevr {@code{dovecot-configuration} parameter} space-separated-string-list mail-plugins | |
11090 | List of plugins to load for all services. Plugins specific to IMAP, | |
11091 | LDA, etc. are added to this list in their own .conf files. | |
11092 | Defaults to @samp{()}. | |
11093 | @end deftypevr | |
11094 | ||
11095 | @deftypevr {@code{dovecot-configuration} parameter} non-negative-integer mail-cache-min-mail-count | |
11096 | The minimum number of mails in a mailbox before updates are done to | |
11097 | cache file. This allows optimizing Dovecot's behavior to do less disk | |
11098 | writes at the cost of more disk reads. | |
11099 | Defaults to @samp{0}. | |
11100 | @end deftypevr | |
11101 | ||
11102 | @deftypevr {@code{dovecot-configuration} parameter} string mailbox-idle-check-interval | |
11103 | When IDLE command is running, mailbox is checked once in a while to | |
11104 | see if there are any new mails or other changes. This setting defines | |
11105 | the minimum time to wait between those checks. Dovecot can also use | |
11106 | dnotify, inotify and kqueue to find out immediately when changes | |
11107 | occur. | |
11108 | Defaults to @samp{"30 secs"}. | |
11109 | @end deftypevr | |
11110 | ||
11111 | @deftypevr {@code{dovecot-configuration} parameter} boolean mail-save-crlf? | |
11112 | Save mails with CR+LF instead of plain LF. This makes sending those | |
11113 | mails take less CPU, especially with sendfile() syscall with Linux and | |
11114 | FreeBSD. But it also creates a bit more disk I/O which may just make it | |
11115 | slower. Also note that if other software reads the mboxes/maildirs, | |
11116 | they may handle the extra CRs wrong and cause problems. | |
11117 | Defaults to @samp{#f}. | |
11118 | @end deftypevr | |
11119 | ||
11120 | @deftypevr {@code{dovecot-configuration} parameter} boolean maildir-stat-dirs? | |
11121 | By default LIST command returns all entries in maildir beginning | |
11122 | with a dot. Enabling this option makes Dovecot return only entries | |
11123 | which are directories. This is done by stat()ing each entry, so it | |
11124 | causes more disk I/O. | |
11125 | (For systems setting struct @samp{dirent->d_type} this check is free | |
11126 | and it's done always regardless of this setting). | |
11127 | Defaults to @samp{#f}. | |
11128 | @end deftypevr | |
11129 | ||
11130 | @deftypevr {@code{dovecot-configuration} parameter} boolean maildir-copy-with-hardlinks? | |
11131 | When copying a message, do it with hard links whenever possible. | |
11132 | This makes the performance much better, and it's unlikely to have any | |
11133 | side effects. | |
11134 | Defaults to @samp{#t}. | |
11135 | @end deftypevr | |
11136 | ||
11137 | @deftypevr {@code{dovecot-configuration} parameter} boolean maildir-very-dirty-syncs? | |
11138 | Assume Dovecot is the only MUA accessing Maildir: Scan cur/ | |
11139 | directory only when its mtime changes unexpectedly or when we can't find | |
11140 | the mail otherwise. | |
11141 | Defaults to @samp{#f}. | |
11142 | @end deftypevr | |
11143 | ||
11144 | @deftypevr {@code{dovecot-configuration} parameter} space-separated-string-list mbox-read-locks | |
11145 | Which locking methods to use for locking mbox. There are four | |
11146 | available: | |
11147 | ||
11148 | @table @code | |
11149 | @item dotlock | |
11150 | Create <mailbox>.lock file. This is the oldest and most NFS-safe | |
11151 | solution. If you want to use /var/mail/ like directory, the users will | |
11152 | need write access to that directory. | |
11153 | @item dotlock-try | |
11154 | Same as dotlock, but if it fails because of permissions or because there | |
11155 | isn't enough disk space, just skip it. | |
11156 | @item fcntl | |
11157 | Use this if possible. Works with NFS too if lockd is used. | |
11158 | @item flock | |
a01ad638 | 11159 | May not exist in all systems. Doesn't work with NFS. |
d8c18af8 AW |
11160 | @item lockf |
11161 | May not exist in all systems. Doesn't work with NFS. | |
11162 | @end table | |
11163 | ||
11164 | You can use multiple locking methods; if you do the order they're declared | |
11165 | in is important to avoid deadlocks if other MTAs/MUAs are using multiple | |
11166 | locking methods as well. Some operating systems don't allow using some of | |
11167 | them simultaneously. | |
11168 | @end deftypevr | |
11169 | ||
11170 | @deftypevr {@code{dovecot-configuration} parameter} space-separated-string-list mbox-write-locks | |
11171 | ||
11172 | @end deftypevr | |
11173 | ||
11174 | @deftypevr {@code{dovecot-configuration} parameter} string mbox-lock-timeout | |
11175 | Maximum time to wait for lock (all of them) before aborting. | |
11176 | Defaults to @samp{"5 mins"}. | |
11177 | @end deftypevr | |
11178 | ||
11179 | @deftypevr {@code{dovecot-configuration} parameter} string mbox-dotlock-change-timeout | |
11180 | If dotlock exists but the mailbox isn't modified in any way, | |
11181 | override the lock file after this much time. | |
11182 | Defaults to @samp{"2 mins"}. | |
11183 | @end deftypevr | |
11184 | ||
11185 | @deftypevr {@code{dovecot-configuration} parameter} boolean mbox-dirty-syncs? | |
11186 | When mbox changes unexpectedly we have to fully read it to find out | |
11187 | what changed. If the mbox is large this can take a long time. Since | |
11188 | the change is usually just a newly appended mail, it'd be faster to | |
11189 | simply read the new mails. If this setting is enabled, Dovecot does | |
11190 | this but still safely fallbacks to re-reading the whole mbox file | |
11191 | whenever something in mbox isn't how it's expected to be. The only real | |
11192 | downside to this setting is that if some other MUA changes message | |
11193 | flags, Dovecot doesn't notice it immediately. Note that a full sync is | |
11194 | done with SELECT, EXAMINE, EXPUNGE and CHECK commands. | |
11195 | Defaults to @samp{#t}. | |
11196 | @end deftypevr | |
11197 | ||
11198 | @deftypevr {@code{dovecot-configuration} parameter} boolean mbox-very-dirty-syncs? | |
11199 | Like @samp{mbox-dirty-syncs}, but don't do full syncs even with SELECT, | |
11200 | EXAMINE, EXPUNGE or CHECK commands. If this is set, | |
11201 | @samp{mbox-dirty-syncs} is ignored. | |
11202 | Defaults to @samp{#f}. | |
11203 | @end deftypevr | |
11204 | ||
11205 | @deftypevr {@code{dovecot-configuration} parameter} boolean mbox-lazy-writes? | |
11206 | Delay writing mbox headers until doing a full write sync (EXPUNGE | |
11207 | and CHECK commands and when closing the mailbox). This is especially | |
11208 | useful for POP3 where clients often delete all mails. The downside is | |
11209 | that our changes aren't immediately visible to other MUAs. | |
11210 | Defaults to @samp{#t}. | |
11211 | @end deftypevr | |
11212 | ||
11213 | @deftypevr {@code{dovecot-configuration} parameter} non-negative-integer mbox-min-index-size | |
11214 | If mbox size is smaller than this (e.g. 100k), don't write index | |
11215 | files. If an index file already exists it's still read, just not | |
11216 | updated. | |
11217 | Defaults to @samp{0}. | |
11218 | @end deftypevr | |
11219 | ||
11220 | @deftypevr {@code{dovecot-configuration} parameter} non-negative-integer mdbox-rotate-size | |
11221 | Maximum dbox file size until it's rotated. | |
11222 | Defaults to @samp{2000000}. | |
11223 | @end deftypevr | |
11224 | ||
11225 | @deftypevr {@code{dovecot-configuration} parameter} string mdbox-rotate-interval | |
11226 | Maximum dbox file age until it's rotated. Typically in days. Day | |
11227 | begins from midnight, so 1d = today, 2d = yesterday, etc. 0 = check | |
11228 | disabled. | |
11229 | Defaults to @samp{"1d"}. | |
11230 | @end deftypevr | |
11231 | ||
11232 | @deftypevr {@code{dovecot-configuration} parameter} boolean mdbox-preallocate-space? | |
11233 | When creating new mdbox files, immediately preallocate their size to | |
11234 | @samp{mdbox-rotate-size}. This setting currently works only in Linux | |
8f65585b | 11235 | with some file systems (ext4, xfs). |
d8c18af8 AW |
11236 | Defaults to @samp{#f}. |
11237 | @end deftypevr | |
11238 | ||
11239 | @deftypevr {@code{dovecot-configuration} parameter} string mail-attachment-dir | |
11240 | sdbox and mdbox support saving mail attachments to external files, | |
11241 | which also allows single instance storage for them. Other backends | |
11242 | don't support this for now. | |
11243 | ||
11244 | WARNING: This feature hasn't been tested much yet. Use at your own risk. | |
11245 | ||
11246 | Directory root where to store mail attachments. Disabled, if empty. | |
11247 | Defaults to @samp{""}. | |
11248 | @end deftypevr | |
11249 | ||
11250 | @deftypevr {@code{dovecot-configuration} parameter} non-negative-integer mail-attachment-min-size | |
11251 | Attachments smaller than this aren't saved externally. It's also | |
11252 | possible to write a plugin to disable saving specific attachments | |
11253 | externally. | |
11254 | Defaults to @samp{128000}. | |
11255 | @end deftypevr | |
11256 | ||
11257 | @deftypevr {@code{dovecot-configuration} parameter} string mail-attachment-fs | |
8f65585b | 11258 | File system backend to use for saving attachments: |
d8c18af8 AW |
11259 | @table @code |
11260 | @item posix | |
11261 | No SiS done by Dovecot (but this might help FS's own deduplication) | |
11262 | @item sis posix | |
11263 | SiS with immediate byte-by-byte comparison during saving | |
11264 | @item sis-queue posix | |
11265 | SiS with delayed comparison and deduplication. | |
11266 | @end table | |
11267 | Defaults to @samp{"sis posix"}. | |
11268 | @end deftypevr | |
11269 | ||
11270 | @deftypevr {@code{dovecot-configuration} parameter} string mail-attachment-hash | |
11271 | Hash format to use in attachment filenames. You can add any text and | |
11272 | variables: @code{%@{md4@}}, @code{%@{md5@}}, @code{%@{sha1@}}, | |
11273 | @code{%@{sha256@}}, @code{%@{sha512@}}, @code{%@{size@}}. Variables can be | |
11274 | truncated, e.g. @code{%@{sha256:80@}} returns only first 80 bits. | |
11275 | Defaults to @samp{"%@{sha1@}"}. | |
11276 | @end deftypevr | |
11277 | ||
11278 | @deftypevr {@code{dovecot-configuration} parameter} non-negative-integer default-process-limit | |
11279 | ||
11280 | Defaults to @samp{100}. | |
11281 | @end deftypevr | |
11282 | ||
11283 | @deftypevr {@code{dovecot-configuration} parameter} non-negative-integer default-client-limit | |
11284 | ||
11285 | Defaults to @samp{1000}. | |
11286 | @end deftypevr | |
11287 | ||
11288 | @deftypevr {@code{dovecot-configuration} parameter} non-negative-integer default-vsz-limit | |
11289 | Default VSZ (virtual memory size) limit for service processes. | |
11290 | This is mainly intended to catch and kill processes that leak memory | |
11291 | before they eat up everything. | |
11292 | Defaults to @samp{256000000}. | |
11293 | @end deftypevr | |
11294 | ||
11295 | @deftypevr {@code{dovecot-configuration} parameter} string default-login-user | |
11296 | Login user is internally used by login processes. This is the most | |
11297 | untrusted user in Dovecot system. It shouldn't have access to anything | |
11298 | at all. | |
11299 | Defaults to @samp{"dovenull"}. | |
11300 | @end deftypevr | |
11301 | ||
11302 | @deftypevr {@code{dovecot-configuration} parameter} string default-internal-user | |
11303 | Internal user is used by unprivileged processes. It should be | |
11304 | separate from login user, so that login processes can't disturb other | |
11305 | processes. | |
11306 | Defaults to @samp{"dovecot"}. | |
11307 | @end deftypevr | |
11308 | ||
11309 | @deftypevr {@code{dovecot-configuration} parameter} string ssl? | |
11310 | SSL/TLS support: yes, no, required. <doc/wiki/SSL.txt>. | |
11311 | Defaults to @samp{"required"}. | |
11312 | @end deftypevr | |
11313 | ||
11314 | @deftypevr {@code{dovecot-configuration} parameter} string ssl-cert | |
11315 | PEM encoded X.509 SSL/TLS certificate (public key). | |
11316 | Defaults to @samp{"</etc/dovecot/default.pem"}. | |
11317 | @end deftypevr | |
11318 | ||
11319 | @deftypevr {@code{dovecot-configuration} parameter} string ssl-key | |
11320 | PEM encoded SSL/TLS private key. The key is opened before | |
11321 | dropping root privileges, so keep the key file unreadable by anyone but | |
11322 | root. | |
11323 | Defaults to @samp{"</etc/dovecot/private/default.pem"}. | |
11324 | @end deftypevr | |
11325 | ||
11326 | @deftypevr {@code{dovecot-configuration} parameter} string ssl-key-password | |
11327 | If key file is password protected, give the password here. | |
11328 | Alternatively give it when starting dovecot with -p parameter. Since | |
11329 | this file is often world-readable, you may want to place this setting | |
11330 | instead to a different. | |
11331 | Defaults to @samp{""}. | |
11332 | @end deftypevr | |
11333 | ||
11334 | @deftypevr {@code{dovecot-configuration} parameter} string ssl-ca | |
11335 | PEM encoded trusted certificate authority. Set this only if you | |
11336 | intend to use @samp{ssl-verify-client-cert? #t}. The file should | |
11337 | contain the CA certificate(s) followed by the matching | |
11338 | CRL(s). (e.g. @samp{ssl-ca </etc/ssl/certs/ca.pem}). | |
11339 | Defaults to @samp{""}. | |
11340 | @end deftypevr | |
11341 | ||
11342 | @deftypevr {@code{dovecot-configuration} parameter} boolean ssl-require-crl? | |
11343 | Require that CRL check succeeds for client certificates. | |
11344 | Defaults to @samp{#t}. | |
11345 | @end deftypevr | |
11346 | ||
11347 | @deftypevr {@code{dovecot-configuration} parameter} boolean ssl-verify-client-cert? | |
11348 | Request client to send a certificate. If you also want to require | |
11349 | it, set @samp{auth-ssl-require-client-cert? #t} in auth section. | |
11350 | Defaults to @samp{#f}. | |
11351 | @end deftypevr | |
11352 | ||
11353 | @deftypevr {@code{dovecot-configuration} parameter} string ssl-cert-username-field | |
11354 | Which field from certificate to use for username. commonName and | |
11355 | x500UniqueIdentifier are the usual choices. You'll also need to set | |
11356 | @samp{auth-ssl-username-from-cert? #t}. | |
11357 | Defaults to @samp{"commonName"}. | |
11358 | @end deftypevr | |
11359 | ||
11360 | @deftypevr {@code{dovecot-configuration} parameter} hours ssl-parameters-regenerate | |
11361 | How often to regenerate the SSL parameters file. Generation is | |
11362 | quite CPU intensive operation. The value is in hours, 0 disables | |
11363 | regeneration entirely. | |
11364 | Defaults to @samp{168}. | |
11365 | @end deftypevr | |
11366 | ||
11367 | @deftypevr {@code{dovecot-configuration} parameter} string ssl-protocols | |
11368 | SSL protocols to use. | |
11369 | Defaults to @samp{"!SSLv2"}. | |
11370 | @end deftypevr | |
11371 | ||
11372 | @deftypevr {@code{dovecot-configuration} parameter} string ssl-cipher-list | |
11373 | SSL ciphers to use. | |
11374 | Defaults to @samp{"ALL:!LOW:!SSLv2:!EXP:!aNULL"}. | |
11375 | @end deftypevr | |
11376 | ||
11377 | @deftypevr {@code{dovecot-configuration} parameter} string ssl-crypto-device | |
11378 | SSL crypto device to use, for valid values run "openssl engine". | |
11379 | Defaults to @samp{""}. | |
11380 | @end deftypevr | |
11381 | ||
11382 | @deftypevr {@code{dovecot-configuration} parameter} string postmaster-address | |
11383 | Address to use when sending rejection mails. | |
66329c23 AW |
11384 | %d expands to recipient domain. |
11385 | Defaults to @samp{"postmaster@@%d"}. | |
d8c18af8 AW |
11386 | @end deftypevr |
11387 | ||
11388 | @deftypevr {@code{dovecot-configuration} parameter} string hostname | |
11389 | Hostname to use in various parts of sent mails (e.g. in Message-Id) | |
11390 | and in LMTP replies. Default is the system's real hostname@@domain. | |
11391 | Defaults to @samp{""}. | |
11392 | @end deftypevr | |
11393 | ||
11394 | @deftypevr {@code{dovecot-configuration} parameter} boolean quota-full-tempfail? | |
11395 | If user is over quota, return with temporary failure instead of | |
11396 | bouncing the mail. | |
11397 | Defaults to @samp{#f}. | |
11398 | @end deftypevr | |
11399 | ||
11400 | @deftypevr {@code{dovecot-configuration} parameter} file-name sendmail-path | |
11401 | Binary to use for sending mails. | |
11402 | Defaults to @samp{"/usr/sbin/sendmail"}. | |
11403 | @end deftypevr | |
11404 | ||
11405 | @deftypevr {@code{dovecot-configuration} parameter} string submission-host | |
11406 | If non-empty, send mails via this SMTP host[:port] instead of | |
11407 | sendmail. | |
11408 | Defaults to @samp{""}. | |
11409 | @end deftypevr | |
11410 | ||
11411 | @deftypevr {@code{dovecot-configuration} parameter} string rejection-subject | |
11412 | Subject: header to use for rejection mails. You can use the same | |
11413 | variables as for @samp{rejection-reason} below. | |
11414 | Defaults to @samp{"Rejected: %s"}. | |
11415 | @end deftypevr | |
11416 | ||
11417 | @deftypevr {@code{dovecot-configuration} parameter} string rejection-reason | |
11418 | Human readable error message for rejection mails. You can use | |
11419 | variables: | |
11420 | ||
11421 | @table @code | |
11422 | @item %n | |
11423 | CRLF | |
11424 | @item %r | |
11425 | reason | |
11426 | @item %s | |
11427 | original subject | |
11428 | @item %t | |
11429 | recipient | |
11430 | @end table | |
11431 | Defaults to @samp{"Your message to <%t> was automatically rejected:%n%r"}. | |
11432 | @end deftypevr | |
11433 | ||
11434 | @deftypevr {@code{dovecot-configuration} parameter} string recipient-delimiter | |
11435 | Delimiter character between local-part and detail in email | |
11436 | address. | |
11437 | Defaults to @samp{"+"}. | |
11438 | @end deftypevr | |
11439 | ||
11440 | @deftypevr {@code{dovecot-configuration} parameter} string lda-original-recipient-header | |
11441 | Header where the original recipient address (SMTP's RCPT TO: | |
11442 | address) is taken from if not available elsewhere. With dovecot-lda -a | |
11443 | parameter overrides this. A commonly used header for this is | |
11444 | X-Original-To. | |
11445 | Defaults to @samp{""}. | |
11446 | @end deftypevr | |
11447 | ||
11448 | @deftypevr {@code{dovecot-configuration} parameter} boolean lda-mailbox-autocreate? | |
11449 | Should saving a mail to a nonexistent mailbox automatically create | |
11450 | it?. | |
11451 | Defaults to @samp{#f}. | |
11452 | @end deftypevr | |
11453 | ||
11454 | @deftypevr {@code{dovecot-configuration} parameter} boolean lda-mailbox-autosubscribe? | |
11455 | Should automatically created mailboxes be also automatically | |
11456 | subscribed?. | |
11457 | Defaults to @samp{#f}. | |
11458 | @end deftypevr | |
11459 | ||
11460 | @deftypevr {@code{dovecot-configuration} parameter} non-negative-integer imap-max-line-length | |
11461 | Maximum IMAP command line length. Some clients generate very long | |
11462 | command lines with huge mailboxes, so you may need to raise this if you | |
11463 | get "Too long argument" or "IMAP command line too large" errors | |
11464 | often. | |
11465 | Defaults to @samp{64000}. | |
11466 | @end deftypevr | |
11467 | ||
11468 | @deftypevr {@code{dovecot-configuration} parameter} string imap-logout-format | |
11469 | IMAP logout format string: | |
11470 | @table @code | |
11471 | @item %i | |
11472 | total number of bytes read from client | |
11473 | @item %o | |
11474 | total number of bytes sent to client. | |
11475 | @end table | |
11476 | Defaults to @samp{"in=%i out=%o"}. | |
11477 | @end deftypevr | |
11478 | ||
11479 | @deftypevr {@code{dovecot-configuration} parameter} string imap-capability | |
11480 | Override the IMAP CAPABILITY response. If the value begins with '+', | |
11481 | add the given capabilities on top of the defaults (e.g. +XFOO XBAR). | |
11482 | Defaults to @samp{""}. | |
11483 | @end deftypevr | |
11484 | ||
11485 | @deftypevr {@code{dovecot-configuration} parameter} string imap-idle-notify-interval | |
11486 | How long to wait between "OK Still here" notifications when client | |
11487 | is IDLEing. | |
11488 | Defaults to @samp{"2 mins"}. | |
11489 | @end deftypevr | |
11490 | ||
11491 | @deftypevr {@code{dovecot-configuration} parameter} string imap-id-send | |
11492 | ID field names and values to send to clients. Using * as the value | |
11493 | makes Dovecot use the default value. The following fields have default | |
11494 | values currently: name, version, os, os-version, support-url, | |
11495 | support-email. | |
11496 | Defaults to @samp{""}. | |
11497 | @end deftypevr | |
11498 | ||
11499 | @deftypevr {@code{dovecot-configuration} parameter} string imap-id-log | |
11500 | ID fields sent by client to log. * means everything. | |
11501 | Defaults to @samp{""}. | |
11502 | @end deftypevr | |
11503 | ||
11504 | @deftypevr {@code{dovecot-configuration} parameter} space-separated-string-list imap-client-workarounds | |
11505 | Workarounds for various client bugs: | |
11506 | ||
11507 | @table @code | |
11508 | @item delay-newmail | |
11509 | Send EXISTS/RECENT new mail notifications only when replying to NOOP and | |
11510 | CHECK commands. Some clients ignore them otherwise, for example OSX | |
11511 | Mail (<v2.1). Outlook Express breaks more badly though, without this it | |
11512 | may show user "Message no longer in server" errors. Note that OE6 | |
11513 | still breaks even with this workaround if synchronization is set to | |
11514 | "Headers Only". | |
11515 | ||
11516 | @item tb-extra-mailbox-sep | |
11517 | Thunderbird gets somehow confused with LAYOUT=fs (mbox and dbox) and | |
11518 | adds extra @samp{/} suffixes to mailbox names. This option causes Dovecot to | |
11519 | ignore the extra @samp{/} instead of treating it as invalid mailbox name. | |
11520 | ||
11521 | @item tb-lsub-flags | |
11522 | Show \Noselect flags for LSUB replies with LAYOUT=fs (e.g. mbox). | |
11523 | This makes Thunderbird realize they aren't selectable and show them | |
11524 | greyed out, instead of only later giving "not selectable" popup error. | |
11525 | @end table | |
11526 | Defaults to @samp{()}. | |
11527 | @end deftypevr | |
11528 | ||
11529 | @deftypevr {@code{dovecot-configuration} parameter} string imap-urlauth-host | |
11530 | Host allowed in URLAUTH URLs sent by client. "*" allows all. | |
11531 | Defaults to @samp{""}. | |
11532 | @end deftypevr | |
11533 | ||
11534 | ||
11535 | Whew! Lots of configuration options. The nice thing about it though is | |
11536 | that GuixSD has a complete interface to Dovecot's configuration | |
11537 | language. This allows not only a nice way to declare configurations, | |
11538 | but also offers reflective capabilities as well: users can write code to | |
11539 | inspect and transform configurations from within Scheme. | |
11540 | ||
11541 | However, it could be that you just want to get a @code{dovecot.conf} up | |
11542 | and running. In that case, you can pass an | |
7414de0a | 11543 | @code{opaque-dovecot-configuration} as the @code{#:config} parameter to |
d8c18af8 AW |
11544 | @code{dovecot-service}. As its name indicates, an opaque configuration |
11545 | does not have easy reflective capabilities. | |
11546 | ||
11547 | Available @code{opaque-dovecot-configuration} fields are: | |
11548 | ||
11549 | @deftypevr {@code{opaque-dovecot-configuration} parameter} package dovecot | |
11550 | The dovecot package. | |
11551 | @end deftypevr | |
11552 | ||
11553 | @deftypevr {@code{opaque-dovecot-configuration} parameter} string string | |
11554 | The contents of the @code{dovecot.conf}, as a string. | |
11555 | @end deftypevr | |
11556 | ||
11557 | For example, if your @code{dovecot.conf} is just the empty string, you | |
11558 | could instantiate a dovecot service like this: | |
11559 | ||
11560 | @example | |
11561 | (dovecot-service #:config | |
11562 | (opaque-dovecot-configuration | |
11563 | (string ""))) | |
11564 | @end example | |
11565 | ||
f88371e8 SB |
11566 | @subsubheading OpenSMTPD Service |
11567 | ||
11568 | @deffn {Scheme Variable} opensmtpd-service-type | |
11569 | This is the type of the @uref{https://www.opensmtpd.org, OpenSMTPD} | |
11570 | service, whose value should be an @code{opensmtpd-configuration} object | |
11571 | as in this example: | |
11572 | ||
11573 | @example | |
11574 | (service opensmtpd-service-type | |
11575 | (opensmtpd-configuration | |
11576 | (config-file (local-file "./my-smtpd.conf")))) | |
11577 | @end example | |
11578 | @end deffn | |
11579 | ||
11580 | @deftp {Data Type} opensmtpd-configuration | |
11581 | Data type regresenting the configuration of opensmtpd. | |
11582 | ||
11583 | @table @asis | |
11584 | @item @code{package} (default: @var{opensmtpd}) | |
11585 | Package object of the OpenSMTPD SMTP server. | |
11586 | ||
11587 | @item @code{config-file} (default: @var{%default-opensmtpd-file}) | |
11588 | File-like object of the OpenSMTPD configuration file to use. By default | |
11589 | it listens on the loopback network interface, and allows for mail from | |
11590 | users and daemons on the local machine, as well as permitting email to | |
11591 | remote servers. Run @command{man smtpd.conf} for more information. | |
11592 | ||
11593 | @end table | |
11594 | @end deftp | |
859e367d JD |
11595 | |
11596 | @node Kerberos Services | |
11597 | @subsubsection Kerberos Services | |
11598 | @cindex Kerberos | |
11599 | ||
df31e36a | 11600 | The @code{(gnu services kerberos)} module provides services relating to |
859e367d JD |
11601 | the authentication protocol @dfn{Kerberos}. |
11602 | ||
8e3f813f JD |
11603 | @subsubheading Krb5 Service |
11604 | ||
11605 | Programs using a Kerberos client library normally | |
11606 | expect a configuration file in @file{/etc/krb5.conf}. | |
11607 | This service generates such a file from a definition provided in the | |
11608 | operating system declaration. | |
11609 | It does not cause any daemon to be started. | |
11610 | ||
11611 | No ``keytab'' files are provided by this service---you must explicitly create them. | |
11612 | This service is known to work with the MIT client library, @code{mit-krb5}. | |
11613 | Other implementations have not been tested. | |
11614 | ||
11615 | @defvr {Scheme Variable} krb5-service-type | |
11616 | A service type for Kerberos 5 clients. | |
11617 | @end defvr | |
11618 | ||
11619 | @noindent | |
11620 | Here is an example of its use: | |
11621 | @lisp | |
11622 | (service krb5-service-type | |
11623 | (krb5-configuration | |
11624 | (default-realm "EXAMPLE.COM") | |
11625 | (allow-weak-crypto? #t) | |
11626 | (realms (list | |
11627 | (krb5-realm | |
11628 | (name "EXAMPLE.COM") | |
11629 | (admin-server "groucho.example.com") | |
11630 | (kdc "karl.example.com")) | |
11631 | (krb5-realm | |
11632 | (name "ARGRX.EDU") | |
11633 | (admin-server "kerb-admin.argrx.edu") | |
11634 | (kdc "keys.argrx.edu")))))) | |
11635 | @end lisp | |
11636 | ||
11637 | @noindent | |
11638 | This example provides a Kerberos@tie{}5 client configuration which: | |
11639 | @itemize | |
11640 | @item Recognizes two realms, @i{viz:} ``EXAMPLE.COM'' and ``ARGRX.EDU'', both | |
11641 | of which have distinct administration servers and key distribution centers; | |
11642 | @item Will default to the realm ``EXAMPLE.COM'' if the realm is not explicitly | |
11643 | specified by clients; | |
11644 | @item Accepts services which only support encryption types known to be weak. | |
11645 | @end itemize | |
11646 | ||
11647 | The @code{krb5-realm} and @code{krb5-configuration} types have many fields. | |
11648 | Only the most commonly used ones are described here. | |
11649 | For a full list, and more detailed explanation of each, see the MIT | |
11650 | @uref{http://web.mit.edu/kerberos/krb5-devel/doc/admin/conf_files/krb5_conf.html,,krb5.conf} | |
11651 | documentation. | |
11652 | ||
11653 | ||
11654 | @deftp {Data Type} krb5-realm | |
11655 | @cindex realm, kerberos | |
11656 | @table @asis | |
11657 | @item @code{name} | |
11658 | This field is a string identifying the name of the realm. | |
11659 | A common convention is to use the fully qualified DNS name of your organization, | |
11660 | converted to upper case. | |
11661 | ||
11662 | @item @code{admin-server} | |
11663 | This field is a string identifying the host where the administration server is | |
11664 | running. | |
11665 | ||
11666 | @item @code{kdc} | |
11667 | This field is a string identifying the key distribution center | |
11668 | for the realm. | |
11669 | @end table | |
11670 | @end deftp | |
11671 | ||
11672 | @deftp {Data Type} krb5-configuration | |
11673 | ||
11674 | @table @asis | |
11675 | @item @code{allow-weak-crypto?} (default: @code{#f}) | |
11676 | If this flag is @code{#t} then services which only offer encryption algorithms | |
11677 | known to be weak will be accepted. | |
11678 | ||
11679 | @item @code{default-realm} (default: @code{#f}) | |
11680 | This field should be a string identifying the default Kerberos | |
11681 | realm for the client. | |
11682 | You should set this field to the name of your Kerberos realm. | |
11683 | If this value is @code{#f} | |
11684 | then a realm must be specified with every Kerberos principal when invoking programs | |
11685 | such as @command{kinit}. | |
11686 | ||
11687 | @item @code{realms} | |
11688 | This should be a non-empty list of @code{krb5-realm} objects, which clients may | |
11689 | access. | |
11690 | Normally, one of them will have a @code{name} field matching the @code{default-realm} | |
11691 | field. | |
11692 | @end table | |
11693 | @end deftp | |
11694 | ||
11695 | ||
859e367d JD |
11696 | @subsubheading PAM krb5 Service |
11697 | @cindex pam-krb5 | |
11698 | ||
df31e36a | 11699 | The @code{pam-krb5} service allows for login authentication and password |
859e367d JD |
11700 | management via Kerberos. |
11701 | You will need this service if you want PAM enabled applications to authenticate | |
11702 | users using Kerberos. | |
11703 | ||
11704 | @defvr {Scheme Variable} pam-krb5-service-type | |
11705 | A service type for the Kerberos 5 PAM module. | |
11706 | @end defvr | |
11707 | ||
11708 | @deftp {Data Type} pam-krb5-configuration | |
11709 | Data type representing the configuration of the Kerberos 5 PAM module | |
11710 | This type has the following parameters: | |
11711 | @table @asis | |
11712 | @item @code{pam-krb5} (default: @code{pam-krb5}) | |
11713 | The pam-krb5 package to use. | |
11714 | ||
11715 | @item @code{minimum-uid} (default: @code{1000}) | |
11716 | The smallest user ID for which Kerberos authentications should be attempted. | |
11717 | Local accounts with lower values will silently fail to authenticate. | |
11718 | @end table | |
11719 | @end deftp | |
11720 | ||
11721 | ||
58724c48 DT |
11722 | @node Web Services |
11723 | @subsubsection Web Services | |
11724 | ||
e32171ee JD |
11725 | @cindex web |
11726 | @cindex www | |
11727 | @cindex HTTP | |
58724c48 DT |
11728 | The @code{(gnu services web)} module provides the following service: |
11729 | ||
be1c2c54 | 11730 | @deffn {Scheme Procedure} nginx-service [#:nginx nginx] @ |
58724c48 DT |
11731 | [#:log-directory ``/var/log/nginx''] @ |
11732 | [#:run-directory ``/var/run/nginx''] @ | |
8c00b838 | 11733 | [#:vhost-list (list (nginx-vhost-configuration))] @ |
58724c48 DT |
11734 | [#:config-file] |
11735 | ||
11736 | Return a service that runs @var{nginx}, the nginx web server. | |
11737 | ||
11738 | The nginx daemon loads its runtime configuration from @var{config-file}. | |
11739 | Log files are written to @var{log-directory} and temporary runtime data | |
11740 | files are written to @var{run-directory}. For proper operation, these | |
11741 | arguments should match what is in @var{config-file} to ensure that the | |
11742 | directories are created when the service is activated. | |
11743 | ||
8c00b838 JL |
11744 | As an alternative to using a @var{config-file}, @var{vhost-list} can be |
11745 | used to specify the list of @dfn{virtual hosts} required on the host. For | |
11746 | this to work, use the default value for @var{config-file}. | |
11747 | ||
58724c48 DT |
11748 | @end deffn |
11749 | ||
8c00b838 JL |
11750 | @deftp {Data Type} nginx-vhost-configuration |
11751 | Data type representing the configuration of an nginx virtual host. | |
11752 | This type has the following parameters: | |
11753 | ||
11754 | @table @asis | |
11755 | @item @code{http-port} (default: @code{80}) | |
11756 | Nginx will listen for HTTP connection on this port. Set it at @code{#f} if | |
11757 | nginx should not listen for HTTP (non secure) connection for this | |
11758 | @dfn{virtual host}. | |
11759 | ||
11760 | @item @code{https-port} (default: @code{443}) | |
11761 | Nginx will listen for HTTPS connection on this port. Set it at @code{#f} if | |
11762 | nginx should not listen for HTTPS (secure) connection for this @dfn{virtual host}. | |
11763 | ||
11764 | Note that nginx can listen for HTTP and HTTPS connections in the same | |
11765 | @dfn{virtual host}. | |
11766 | ||
11767 | @item @code{server-name} (default: @code{(list 'default)}) | |
11768 | A list of server names this vhost represents. @code{'default} represents the | |
11769 | default vhost for connections matching no other vhost. | |
11770 | ||
11771 | @item @code{root} (default: @code{"/srv/http"}) | |
11772 | Root of the website nginx will serve. | |
11773 | ||
11774 | @item @code{index} (default: @code{(list "index.html")}) | |
11775 | Index files to look for when clients ask for a directory. If it cannot be found, | |
11776 | Nginx will send the list of files in the directory. | |
11777 | ||
11778 | @item @code{ssl-certificate} (default: @code{"/etc/nginx/cert.pem"}) | |
11779 | Where to find the certificate for secure connections. Set it to @code{#f} if | |
11780 | you don't have a certificate or you don't want to use HTTPS. | |
11781 | ||
11782 | @item @code{ssl-certificate-key} (default: @code{"/etc/nginx/key.pem"}) | |
11783 | Where to find the private key for secure connections. Set it to @code{#f} if | |
11784 | you don't have a key or you don't want to use HTTPS. | |
11785 | ||
11786 | @item @code{server-tokens?} (default: @code{#f}) | |
11787 | Whether the server should add its configuration to response. | |
11788 | ||
11789 | @end table | |
11790 | @end deftp | |
11791 | ||
eb419bc9 JD |
11792 | @node Network File System |
11793 | @subsubsection Network File System | |
11794 | @cindex NFS | |
fe1a39d3 | 11795 | |
eb419bc9 JD |
11796 | The @code{(gnu services nfs)} module provides the following services, |
11797 | which are most commonly used in relation to mounting or exporting | |
11798 | directory trees as @dfn{network file systems} (NFS). | |
d6a07ee6 JD |
11799 | |
11800 | @subsubheading RPC Bind Service | |
11801 | @cindex rpcbind | |
11802 | ||
eb419bc9 JD |
11803 | The RPC Bind service provides a facility to map program numbers into |
11804 | universal addresses. | |
11805 | Many NFS related services use this facility. Hence it is automatically | |
11806 | started when a dependent service starts. | |
d6a07ee6 JD |
11807 | |
11808 | @defvr {Scheme Variable} rpcbind-service-type | |
11809 | A service type for the RPC portmapper daemon. | |
11810 | @end defvr | |
11811 | ||
11812 | ||
11813 | @deftp {Data Type} rpcbind-configuration | |
11814 | Data type representing the configuration of the RPC Bind Service. | |
11815 | This type has the following parameters: | |
11816 | @table @asis | |
11817 | @item @code{rpcbind} (default: @code{rpcbind}) | |
11818 | The rpcbind package to use. | |
11819 | ||
11820 | @item @code{warm-start?} (default: @code{#t}) | |
11821 | If this parameter is @code{#t}, then the daemon will read a | |
11822 | state file on startup thus reloading state information saved by a previous | |
11823 | instance. | |
11824 | @end table | |
11825 | @end deftp | |
11826 | ||
eb419bc9 JD |
11827 | |
11828 | @subsubheading Pipefs Pseudo File System | |
11829 | @cindex pipefs | |
11830 | @cindex rpc_pipefs | |
11831 | ||
11832 | The pipefs file system is used to transfer NFS related data | |
11833 | between the kernel and user space programs. | |
11834 | ||
11835 | @defvr {Scheme Variable} pipefs-service-type | |
11836 | A service type for the pipefs pseudo file system. | |
11837 | @end defvr | |
11838 | ||
11839 | @deftp {Data Type} pipefs-configuration | |
11840 | Data type representing the configuration of the pipefs pseudo file system service. | |
11841 | This type has the following parameters: | |
11842 | @table @asis | |
11843 | @item @code{mount-point} (default: @code{"/var/lib/nfs/rpc_pipefs"}) | |
11844 | The directory to which the file system is to be attached. | |
11845 | @end table | |
11846 | @end deftp | |
11847 | ||
11848 | ||
11849 | @subsubheading GSS Daemon Service | |
11850 | @cindex GSSD | |
11851 | @cindex GSS | |
11852 | @cindex global security system | |
11853 | ||
11854 | The @dfn{global security system} (GSS) daemon provides strong security for RPC | |
11855 | based protocols. | |
11856 | Before exchanging RPC requests an RPC client must establish a security | |
11857 | context. Typically this is done using the Kerberos command @command{kinit} | |
859e367d | 11858 | or automatically at login time using PAM services (@pxref{Kerberos Services}). |
eb419bc9 JD |
11859 | |
11860 | @defvr {Scheme Variable} gss-service-type | |
11861 | A service type for the Global Security System (GSS) daemon. | |
11862 | @end defvr | |
11863 | ||
11864 | @deftp {Data Type} gss-configuration | |
11865 | Data type representing the configuration of the GSS daemon service. | |
11866 | This type has the following parameters: | |
11867 | @table @asis | |
11868 | @item @code{nfs-utils} (default: @code{nfs-utils}) | |
11869 | The package in which the @command{rpc.gssd} command is to be found. | |
11870 | ||
11871 | @item @code{pipefs-directory} (default: @code{"/var/lib/nfs/rpc_pipefs"}) | |
11872 | The directory where the pipefs file system is mounted. | |
11873 | ||
11874 | @end table | |
11875 | @end deftp | |
11876 | ||
11877 | ||
11878 | @subsubheading IDMAP Daemon Service | |
11879 | @cindex idmapd | |
11880 | @cindex name mapper | |
11881 | ||
11882 | The idmap daemon service provides mapping between user IDs and user names. | |
11883 | Typically it is required in order to access file systems mounted via NFSv4. | |
11884 | ||
11885 | @defvr {Scheme Variable} idmap-service-type | |
11886 | A service type for the Identity Mapper (IDMAP) daemon. | |
11887 | @end defvr | |
11888 | ||
11889 | @deftp {Data Type} idmap-configuration | |
11890 | Data type representing the configuration of the IDMAP daemon service. | |
11891 | This type has the following parameters: | |
11892 | @table @asis | |
11893 | @item @code{nfs-utils} (default: @code{nfs-utils}) | |
11894 | The package in which the @command{rpc.idmapd} command is to be found. | |
11895 | ||
11896 | @item @code{pipefs-directory} (default: @code{"/var/lib/nfs/rpc_pipefs"}) | |
11897 | The directory where the pipefs file system is mounted. | |
11898 | ||
11899 | @item @code{domain} (default: @code{#f}) | |
11900 | The local NFSv4 domain name. | |
11901 | This must be a string or @code{#f}. | |
11902 | If it is @code{#f} then the daemon will use the host's fully qualified domain name. | |
11903 | ||
11904 | @end table | |
11905 | @end deftp | |
11906 | ||
a7cf4eb6 ML |
11907 | @node Continuous Integration |
11908 | @subsubsection Continuous Integration | |
11909 | ||
11910 | @cindex continuous integration | |
11911 | @uref{https://notabug.org/mthl/cuirass, Cuirass} is a continuous | |
11912 | integration tool for Guix. It can be used both for development and for | |
11913 | providing substitutes to others (@pxref{Substitutes}). | |
11914 | ||
11915 | The @code{(gnu services cuirass)} module provides the following service. | |
11916 | ||
11917 | @deffn {Scheme Procedure} cuirass-service @ | |
11918 | [#:config @code{(cuirass-configuration)}] | |
11919 | Return a service that runs @command{cuirass}. | |
11920 | ||
11921 | The @var{#:config} keyword argument specifies the configuration for | |
11922 | @command{cuirass}, which must be a @code{<cuirass-configuration>} | |
11923 | object, by default it doesn't provide any build job. If you want to | |
11924 | provide your own configuration you will most likely use the | |
11925 | @code{cuirass-configuration} special form which returns such objects. | |
11926 | @end deffn | |
11927 | ||
11928 | In order to add build jobs you will have to set the | |
11929 | @code{specifications} field. Here is an example of a cuirass service | |
11930 | defining a build job based on a specification that can be found in | |
11931 | Cuirass source tree. | |
11932 | ||
11933 | @example | |
11934 | (let ((spec `((#:name . "guix") | |
11935 | (#:url . "git://git.savannah.gnu.org/guix.git") | |
11936 | (#:load-path . ".") | |
11937 | ;; Adapt to a valid absolute file name. | |
11938 | (#:file . "/.../cuirass/tests/gnu-system.scm") | |
11939 | (#:proc . hydra-jobs) | |
11940 | (#:arguments (subset . "hello")) | |
11941 | (#:branch . "master")))) | |
11942 | (cuirass-service #:config (cuirass-configuration | |
11943 | (specifications (list spec))))) | |
11944 | @end example | |
11945 | ||
11946 | While information related to build jobs are located directly in the | |
11947 | specifications, global settings for the @command{cuirass} process are | |
11948 | accessible in other @code{cuirass-configuration} fields. | |
11949 | ||
11950 | @deftp {Data Type} cuirass-configuration | |
11951 | Data type representing the configuration of Cuirass. | |
11952 | ||
11953 | @table @asis | |
11954 | @item @code{cache-directory} (default: @code{""}) | |
11955 | Location of the repository cache. | |
11956 | ||
11957 | @item @code{user} (default: @code{"cuirass"}) | |
11958 | Owner of the @code{cuirass} process. | |
11959 | ||
11960 | @item @code{group} (default: @code{"cuirass"}) | |
11961 | Owner's group of the @code{cuirass} process. | |
11962 | ||
11963 | @item @code{interval} (default: @code{60}) | |
11964 | Number of seconds between the poll of the repositories followed by the | |
11965 | Cuirass jobs. | |
11966 | ||
11967 | @item @code{database} (default: @code{"/var/run/cuirass/cuirass.db"}) | |
11968 | Location of sqlite database which contains the build results and previously | |
11969 | added specifications. | |
11970 | ||
11971 | @item @code{specifications} (default: @code{'()}) | |
11972 | A list of specifications, where a specification is an association list | |
11973 | (@pxref{Associations Lists,,, guile, GNU Guile Reference Manual}) whose | |
11974 | keys are keywords (@code{#:keyword-example}) as shown in the example | |
11975 | above. | |
11976 | ||
11977 | @item @code{use-substitutes?} (default: @code{#f}) | |
11978 | This allows using substitutes to avoid building every dependencies of a job | |
11979 | from source. | |
11980 | ||
11981 | @item @code{one-shot?} (default: @code{#f}) | |
11982 | Only evaluate specifications and build derivations once. | |
11983 | @end table | |
11984 | @end deftp | |
eb419bc9 JD |
11985 | |
11986 | @node Miscellaneous Services | |
11987 | @subsubsection Miscellaneous Services | |
11988 | ||
11989 | ||
8ff4dcbe DC |
11990 | @cindex lirc |
11991 | @subsubheading Lirc Service | |
11992 | ||
fe1a39d3 LC |
11993 | The @code{(gnu services lirc)} module provides the following service. |
11994 | ||
be1c2c54 | 11995 | @deffn {Scheme Procedure} lirc-service [#:lirc lirc] @ |
fe1a39d3 LC |
11996 | [#:device #f] [#:driver #f] [#:config-file #f] @ |
11997 | [#:extra-options '()] | |
11998 | Return a service that runs @url{http://www.lirc.org,LIRC}, a daemon that | |
11999 | decodes infrared signals from remote controls. | |
12000 | ||
12001 | Optionally, @var{device}, @var{driver} and @var{config-file} | |
12002 | (configuration file name) may be specified. See @command{lircd} manual | |
12003 | for details. | |
12004 | ||
12005 | Finally, @var{extra-options} is a list of additional command-line options | |
12006 | passed to @command{lircd}. | |
12007 | @end deffn | |
12008 | ||
00f46905 DC |
12009 | @cindex spice |
12010 | @subsubheading Spice Service | |
12011 | ||
12012 | The @code{(gnu services spice)} module provides the following service. | |
12013 | ||
12014 | @deffn {Scheme Procedure} spice-vdagent-service [#:spice-vdagent] | |
12015 | Returns a service that runs @url{http://www.spice-space.org,VDAGENT}, a daemon | |
12016 | that enables sharing the clipboard with a vm and setting the guest display | |
12017 | resolution when the graphical console window resizes. | |
12018 | @end deffn | |
12019 | ||
c3d38b2b | 12020 | @subsubsection Dictionary Services |
e32171ee | 12021 | @cindex dictionary |
c3d38b2b SB |
12022 | The @code{(gnu services dict)} module provides the following service: |
12023 | ||
12024 | @deffn {Scheme Procedure} dicod-service [#:config (dicod-configuration)] | |
12025 | Return a service that runs the @command{dicod} daemon, an implementation | |
12026 | of DICT server (@pxref{Dicod,,, dico, GNU Dico Manual}). | |
12027 | ||
12028 | The optional @var{config} argument specifies the configuration for | |
12029 | @command{dicod}, which should be a @code{<dicod-configuration>} object, by | |
12030 | default it serves the GNU Collaborative International Dictonary of English. | |
12031 | ||
12032 | You can add @command{open localhost} to your @file{~/.dico} file to make | |
12033 | @code{localhost} the default server for @command{dico} client | |
12034 | (@pxref{Initialization File,,, dico, GNU Dico Manual}). | |
12035 | @end deffn | |
12036 | ||
12037 | @deftp {Data Type} dicod-configuration | |
12038 | Data type representing the configuration of dicod. | |
12039 | ||
12040 | @table @asis | |
12041 | @item @code{dico} (default: @var{dico}) | |
12042 | Package object of the GNU Dico dictionary server. | |
12043 | ||
a1b48465 LC |
12044 | @item @code{interfaces} (default: @var{'("localhost")}) |
12045 | This is the list of IP addresses and ports and possibly socket file | |
12046 | names to listen to (@pxref{Server Settings, @code{listen} directive,, | |
12047 | dico, GNU Dico Manual}). | |
12048 | ||
c3d38b2b SB |
12049 | @item @code{databases} (default: @var{(list %dicod-database:gcide)}) |
12050 | List of @code{<dicod-database>} objects denoting dictionaries to be served. | |
12051 | @end table | |
12052 | @end deftp | |
12053 | ||
12054 | @deftp {Data Type} dicod-database | |
12055 | Data type representing a dictionary database. | |
12056 | ||
12057 | @table @asis | |
12058 | @item @code{name} | |
12059 | Name of the database, will be used in DICT commands. | |
12060 | ||
12061 | @item @code{module} | |
12062 | Name of the dicod module used by this database | |
12063 | (@pxref{Modules,,, dico, GNU Dico Manual}). | |
12064 | ||
12065 | @item @code{options} | |
12066 | List of strings or gexps representing the arguments for the module handler | |
12067 | (@pxref{Handlers,,, dico, GNU Dico Manual}). | |
12068 | @end table | |
12069 | @end deftp | |
12070 | ||
12071 | @defvr {Scheme Variable} %dicod-database:gcide | |
12072 | A @code{<dicod-database>} object serving the GNU Collaborative International | |
12073 | Dictonary of English using the @code{gcide} package. | |
12074 | @end defvr | |
fe1a39d3 | 12075 | |
e01e2c6c | 12076 | @subsubsection Version Control |
12077 | ||
12078 | The @code{(gnu services version-control)} module provides the following services: | |
12079 | ||
12080 | @subsubheading Git daemon service | |
12081 | ||
12082 | @deffn {Scheme Procedure} git-daemon-service [#:config (git-daemon-configuration)] | |
12083 | ||
12084 | Return a service that runs @command{git daemon}, a simple TCP server to | |
12085 | expose repositiories over the Git protocol for annoymous access. | |
12086 | ||
12087 | The optional @var{config} argument should be a | |
12088 | @code{<git-daemon-configuration>} object, by default it allows read-only | |
12089 | access to exported@footnote{By creating the magic file | |
12090 | "git-daemon-export-ok" in the repository directory.} repositories under | |
12091 | @file{/srv/git}. | |
12092 | ||
12093 | @end deffn | |
12094 | ||
12095 | @deftp {Data Type} git-daemon-configuration | |
12096 | Data type representing the configuration for @code{git-daemon-service}. | |
12097 | ||
12098 | @table @asis | |
12099 | @item @code{package} (default: @var{git}) | |
12100 | Package object of the Git distributed version control system. | |
12101 | ||
12102 | @item @code{export-all?} (default: @var{#f}) | |
12103 | Whether to allow access for all Git repositories, even if they do not | |
12104 | have the @file{git-daemon-export-ok} file. | |
12105 | ||
12106 | @item @code{base-path} (default: @file{/srv/git}) | |
12107 | Whether to remap all the path requests as relative to the given path. | |
12108 | If you run git daemon with @var{(base-path "/srv/git")} on example.com, | |
12109 | then if you later try to pull @code{git://example.com/hello.git}, git | |
12110 | daemon will interpret the path as @code{/srv/git/hello.git}. | |
12111 | ||
12112 | @item @code{user-path} (default: @var{#f}) | |
12113 | Whether to allow @code{~user} notation to be used in requests. When | |
12114 | specified with empty string, requests to @code{git://host/~alice/foo} is | |
12115 | taken as a request to access @code{foo} repository in the home directory | |
12116 | of user @code{alice}. If @var{(user-path "path")} is specified, the | |
12117 | same request is taken as a request to access @code{path/foo} repository | |
12118 | in the home directory of user @code{alice}. | |
12119 | ||
12120 | @item @code{listen} (default: @var{'()}) | |
12121 | Whether to listen on specific IP addresses or hostnames, defaults to | |
12122 | all. | |
12123 | ||
12124 | @item @code{port} (default: @var{#f}) | |
12125 | Whether to listen on an alternative port, which defaults to 9418. | |
12126 | ||
12127 | @item @code{whitelist} (default: @var{'()}) | |
12128 | If not empty, only allow access to this list of directories. | |
12129 | ||
12130 | @item @code{extra-options} (default: @var{'()}) | |
12131 | Extra options will be passed to @code{git daemon}, please run | |
12132 | @command{man git-daemon} for more information. | |
12133 | ||
12134 | @end table | |
12135 | @end deftp | |
12136 | ||
0ae8c15a LC |
12137 | @node Setuid Programs |
12138 | @subsection Setuid Programs | |
12139 | ||
12140 | @cindex setuid programs | |
12141 | Some programs need to run with ``root'' privileges, even when they are | |
12142 | launched by unprivileged users. A notorious example is the | |
4d40227c LC |
12143 | @command{passwd} program, which users can run to change their |
12144 | password, and which needs to access the @file{/etc/passwd} and | |
0ae8c15a LC |
12145 | @file{/etc/shadow} files---something normally restricted to root, for |
12146 | obvious security reasons. To address that, these executables are | |
12147 | @dfn{setuid-root}, meaning that they always run with root privileges | |
12148 | (@pxref{How Change Persona,,, libc, The GNU C Library Reference Manual}, | |
f7e4ae7f | 12149 | for more info about the setuid mechanism.) |
0ae8c15a LC |
12150 | |
12151 | The store itself @emph{cannot} contain setuid programs: that would be a | |
12152 | security issue since any user on the system can write derivations that | |
12153 | populate the store (@pxref{The Store}). Thus, a different mechanism is | |
12154 | used: instead of changing the setuid bit directly on files that are in | |
12155 | the store, we let the system administrator @emph{declare} which programs | |
12156 | should be setuid root. | |
12157 | ||
12158 | The @code{setuid-programs} field of an @code{operating-system} | |
12159 | declaration contains a list of G-expressions denoting the names of | |
12160 | programs to be setuid-root (@pxref{Using the Configuration System}). | |
12161 | For instance, the @command{passwd} program, which is part of the Shadow | |
12162 | package, can be designated by this G-expression (@pxref{G-Expressions}): | |
12163 | ||
12164 | @example | |
12165 | #~(string-append #$shadow "/bin/passwd") | |
12166 | @end example | |
12167 | ||
12168 | A default set of setuid programs is defined by the | |
12169 | @code{%setuid-programs} variable of the @code{(gnu system)} module. | |
12170 | ||
12171 | @defvr {Scheme Variable} %setuid-programs | |
12172 | A list of G-expressions denoting common programs that are setuid-root. | |
12173 | ||
12174 | The list includes commands such as @command{passwd}, @command{ping}, | |
12175 | @command{su}, and @command{sudo}. | |
12176 | @end defvr | |
12177 | ||
12178 | Under the hood, the actual setuid programs are created in the | |
12179 | @file{/run/setuid-programs} directory at system activation time. The | |
12180 | files in this directory refer to the ``real'' binaries, which are in the | |
12181 | store. | |
12182 | ||
efb5e833 LC |
12183 | @node X.509 Certificates |
12184 | @subsection X.509 Certificates | |
12185 | ||
12186 | @cindex HTTPS, certificates | |
12187 | @cindex X.509 certificates | |
12188 | @cindex TLS | |
12189 | Web servers available over HTTPS (that is, HTTP over the transport-layer | |
12190 | security mechanism, TLS) send client programs an @dfn{X.509 certificate} | |
12191 | that the client can then use to @emph{authenticate} the server. To do | |
12192 | that, clients verify that the server's certificate is signed by a | |
12193 | so-called @dfn{certificate authority} (CA). But to verify the CA's | |
12194 | signature, clients must have first acquired the CA's certificate. | |
12195 | ||
12196 | Web browsers such as GNU@tie{}IceCat include their own set of CA | |
12197 | certificates, such that they are able to verify CA signatures | |
12198 | out-of-the-box. | |
12199 | ||
12200 | However, most other programs that can talk HTTPS---@command{wget}, | |
12201 | @command{git}, @command{w3m}, etc.---need to be told where CA | |
12202 | certificates can be found. | |
12203 | ||
12204 | @cindex @code{nss-certs} | |
12205 | In GuixSD, this is done by adding a package that provides certificates | |
12206 | to the @code{packages} field of the @code{operating-system} declaration | |
12207 | (@pxref{operating-system Reference}). GuixSD includes one such package, | |
12208 | @code{nss-certs}, which is a set of CA certificates provided as part of | |
12209 | Mozilla's Network Security Services. | |
12210 | ||
12211 | Note that it is @emph{not} part of @var{%base-packages}, so you need to | |
12212 | explicitly add it. The @file{/etc/ssl/certs} directory, which is where | |
12213 | most applications and libraries look for certificates by default, points | |
12214 | to the certificates installed globally. | |
12215 | ||
b3129f2b LC |
12216 | Unprivileged users, including users of Guix on a foreign distro, |
12217 | can also install their own certificate package in | |
efb5e833 LC |
12218 | their profile. A number of environment variables need to be defined so |
12219 | that applications and libraries know where to find them. Namely, the | |
12220 | OpenSSL library honors the @code{SSL_CERT_DIR} and @code{SSL_CERT_FILE} | |
12221 | variables. Some applications add their own environment variables; for | |
12222 | instance, the Git version control system honors the certificate bundle | |
b3129f2b LC |
12223 | pointed to by the @code{GIT_SSL_CAINFO} environment variable. Thus, you |
12224 | would typically run something like: | |
efb5e833 | 12225 | |
b3129f2b LC |
12226 | @example |
12227 | $ guix package -i nss-certs | |
12228 | $ export SSL_CERT_DIR="$HOME/.guix-profile/etc/ssl/certs" | |
12229 | $ export SSL_CERT_FILE="$HOME/.guix-profile/etc/ssl/certs/ca-certificates.crt" | |
12230 | $ export GIT_SSL_CAINFO="$SSL_CERT_FILE" | |
12231 | @end example | |
efb5e833 | 12232 | |
996ed739 LC |
12233 | @node Name Service Switch |
12234 | @subsection Name Service Switch | |
12235 | ||
12236 | @cindex name service switch | |
12237 | @cindex NSS | |
12238 | The @code{(gnu system nss)} module provides bindings to the | |
1068f26b | 12239 | configuration file of the libc @dfn{name service switch} or @dfn{NSS} |
996ed739 LC |
12240 | (@pxref{NSS Configuration File,,, libc, The GNU C Library Reference |
12241 | Manual}). In a nutshell, the NSS is a mechanism that allows libc to be | |
12242 | extended with new ``name'' lookup methods for system databases, which | |
12243 | includes host names, service names, user accounts, and more (@pxref{Name | |
12244 | Service Switch, System Databases and Name Service Switch,, libc, The GNU | |
12245 | C Library Reference Manual}). | |
12246 | ||
12247 | The NSS configuration specifies, for each system database, which lookup | |
12248 | method is to be used, and how the various methods are chained | |
12249 | together---for instance, under which circumstances NSS should try the | |
12250 | next method in the list. The NSS configuration is given in the | |
12251 | @code{name-service-switch} field of @code{operating-system} declarations | |
12252 | (@pxref{operating-system Reference, @code{name-service-switch}}). | |
12253 | ||
4c9050c6 LC |
12254 | @cindex nss-mdns |
12255 | @cindex .local, host name lookup | |
996ed739 | 12256 | As an example, the declaration below configures the NSS to use the |
4c9050c6 LC |
12257 | @uref{http://0pointer.de/lennart/projects/nss-mdns/, @code{nss-mdns} |
12258 | back-end}, which supports host name lookups over multicast DNS (mDNS) | |
12259 | for host names ending in @code{.local}: | |
996ed739 LC |
12260 | |
12261 | @example | |
12262 | (name-service-switch | |
12263 | (hosts (list %files ;first, check /etc/hosts | |
12264 | ||
12265 | ;; If the above did not succeed, try | |
12266 | ;; with 'mdns_minimal'. | |
12267 | (name-service | |
12268 | (name "mdns_minimal") | |
12269 | ||
12270 | ;; 'mdns_minimal' is authoritative for | |
12271 | ;; '.local'. When it returns "not found", | |
12272 | ;; no need to try the next methods. | |
12273 | (reaction (lookup-specification | |
12274 | (not-found => return)))) | |
12275 | ||
12276 | ;; Then fall back to DNS. | |
12277 | (name-service | |
12278 | (name "dns")) | |
12279 | ||
12280 | ;; Finally, try with the "full" 'mdns'. | |
12281 | (name-service | |
12282 | (name "mdns"))))) | |
12283 | @end example | |
12284 | ||
1068f26b AE |
12285 | Do not worry: the @code{%mdns-host-lookup-nss} variable (see below) |
12286 | contains this configuration, so you will not have to type it if all you | |
15137a29 LC |
12287 | want is to have @code{.local} host lookup working. |
12288 | ||
4c9050c6 LC |
12289 | Note that, in this case, in addition to setting the |
12290 | @code{name-service-switch} of the @code{operating-system} declaration, | |
cc9c1f39 LC |
12291 | you also need to use @code{avahi-service} (@pxref{Networking Services, |
12292 | @code{avahi-service}}), or @var{%desktop-services}, which includes it | |
12293 | (@pxref{Desktop Services}). Doing this makes @code{nss-mdns} accessible | |
12294 | to the name service cache daemon (@pxref{Base Services, | |
12295 | @code{nscd-service}}). | |
15137a29 LC |
12296 | |
12297 | For convenience, the following variables provide typical NSS | |
12298 | configurations. | |
12299 | ||
12300 | @defvr {Scheme Variable} %default-nss | |
12301 | This is the default name service switch configuration, a | |
12302 | @code{name-service-switch} object. | |
12303 | @end defvr | |
12304 | ||
12305 | @defvr {Scheme Variable} %mdns-host-lookup-nss | |
12306 | This is the name service switch configuration with support for host name | |
12307 | lookup over multicast DNS (mDNS) for host names ending in @code{.local}. | |
12308 | @end defvr | |
4c9050c6 | 12309 | |
996ed739 | 12310 | The reference for name service switch configuration is given below. It |
1068f26b | 12311 | is a direct mapping of the configuration file format of the C library , so |
996ed739 LC |
12312 | please refer to the C library manual for more information (@pxref{NSS |
12313 | Configuration File,,, libc, The GNU C Library Reference Manual}). | |
1068f26b | 12314 | Compared to the configuration file format of libc NSS, it has the advantage |
996ed739 | 12315 | not only of adding this warm parenthetic feel that we like, but also |
1068f26b | 12316 | static checks: you will know about syntax errors and typos as soon as you |
996ed739 LC |
12317 | run @command{guix system}. |
12318 | ||
996ed739 LC |
12319 | @deftp {Data Type} name-service-switch |
12320 | ||
12321 | This is the data type representation the configuration of libc's name | |
12322 | service switch (NSS). Each field below represents one of the supported | |
12323 | system databases. | |
12324 | ||
12325 | @table @code | |
12326 | @item aliases | |
12327 | @itemx ethers | |
12328 | @itemx group | |
12329 | @itemx gshadow | |
12330 | @itemx hosts | |
12331 | @itemx initgroups | |
12332 | @itemx netgroup | |
12333 | @itemx networks | |
12334 | @itemx password | |
12335 | @itemx public-key | |
12336 | @itemx rpc | |
12337 | @itemx services | |
12338 | @itemx shadow | |
12339 | The system databases handled by the NSS. Each of these fields must be a | |
1068f26b | 12340 | list of @code{<name-service>} objects (see below). |
996ed739 LC |
12341 | @end table |
12342 | @end deftp | |
12343 | ||
12344 | @deftp {Data Type} name-service | |
12345 | ||
12346 | This is the data type representing an actual name service and the | |
12347 | associated lookup action. | |
12348 | ||
12349 | @table @code | |
12350 | @item name | |
12351 | A string denoting the name service (@pxref{Services in the NSS | |
12352 | configuration,,, libc, The GNU C Library Reference Manual}). | |
12353 | ||
4aee6e60 LC |
12354 | Note that name services listed here must be visible to nscd. This is |
12355 | achieved by passing the @code{#:name-services} argument to | |
12356 | @code{nscd-service} the list of packages providing the needed name | |
12357 | services (@pxref{Base Services, @code{nscd-service}}). | |
12358 | ||
996ed739 LC |
12359 | @item reaction |
12360 | An action specified using the @code{lookup-specification} macro | |
12361 | (@pxref{Actions in the NSS configuration,,, libc, The GNU C Library | |
12362 | Reference Manual}). For example: | |
12363 | ||
12364 | @example | |
12365 | (lookup-specification (unavailable => continue) | |
12366 | (success => return)) | |
12367 | @end example | |
12368 | @end table | |
12369 | @end deftp | |
0ae8c15a | 12370 | |
fd1b1fa2 LC |
12371 | @node Initial RAM Disk |
12372 | @subsection Initial RAM Disk | |
12373 | ||
e32171ee JD |
12374 | @cindex initrd |
12375 | @cindex initial RAM disk | |
fd1b1fa2 LC |
12376 | For bootstrapping purposes, the Linux-Libre kernel is passed an |
12377 | @dfn{initial RAM disk}, or @dfn{initrd}. An initrd contains a temporary | |
1068f26b | 12378 | root file system as well as an initialization script. The latter is |
fd1b1fa2 LC |
12379 | responsible for mounting the real root file system, and for loading any |
12380 | kernel modules that may be needed to achieve that. | |
12381 | ||
12382 | The @code{initrd} field of an @code{operating-system} declaration allows | |
12383 | you to specify which initrd you would like to use. The @code{(gnu | |
12384 | system linux-initrd)} module provides two ways to build an initrd: the | |
12385 | high-level @code{base-initrd} procedure, and the low-level | |
12386 | @code{expression->initrd} procedure. | |
12387 | ||
12388 | The @code{base-initrd} procedure is intended to cover most common uses. | |
12389 | For example, if you want to add a bunch of kernel modules to be loaded | |
12390 | at boot time, you can define the @code{initrd} field of the operating | |
12391 | system declaration like this: | |
12392 | ||
12393 | @example | |
52ac153e | 12394 | (initrd (lambda (file-systems . rest) |
027981d6 LC |
12395 | ;; Create a standard initrd that has modules "foo.ko" |
12396 | ;; and "bar.ko", as well as their dependencies, in | |
12397 | ;; addition to the modules available by default. | |
52ac153e | 12398 | (apply base-initrd file-systems |
027981d6 | 12399 | #:extra-modules '("foo" "bar") |
52ac153e | 12400 | rest))) |
fd1b1fa2 LC |
12401 | @end example |
12402 | ||
52ac153e | 12403 | The @code{base-initrd} procedure also handles common use cases that |
1068f26b AE |
12404 | involves using the system as a QEMU guest, or as a ``live'' system with |
12405 | volatile root file system. | |
fd1b1fa2 | 12406 | |
e90cf6c1 LC |
12407 | The initial RAM disk produced by @code{base-initrd} honors several |
12408 | options passed on the Linux kernel command line (that is, arguments | |
1068f26b | 12409 | passed @i{via} the @code{linux} command of GRUB, or the |
4af2fafd | 12410 | @code{-append} option of QEMU), notably: |
e90cf6c1 LC |
12411 | |
12412 | @table @code | |
12413 | @item --load=@var{boot} | |
12414 | Tell the initial RAM disk to load @var{boot}, a file containing a Scheme | |
12415 | program, once it has mounted the root file system. | |
12416 | ||
12417 | GuixSD uses this option to yield control to a boot program that runs the | |
dd17bc38 | 12418 | service activation programs and then spawns the GNU@tie{}Shepherd, the |
e90cf6c1 LC |
12419 | initialization system. |
12420 | ||
12421 | @item --root=@var{root} | |
1068f26b | 12422 | Mount @var{root} as the root file system. @var{root} can be a |
e90cf6c1 LC |
12423 | device name like @code{/dev/sda1}, a partition label, or a partition |
12424 | UUID. | |
12425 | ||
12426 | @item --system=@var{system} | |
12427 | Have @file{/run/booted-system} and @file{/run/current-system} point to | |
12428 | @var{system}. | |
12429 | ||
12430 | @item modprobe.blacklist=@var{modules}@dots{} | |
12431 | @cindex module, black-listing | |
12432 | @cindex black list, of kernel modules | |
12433 | Instruct the initial RAM disk as well as the @command{modprobe} command | |
12434 | (from the kmod package) to refuse to load @var{modules}. @var{modules} | |
12435 | must be a comma-separated list of module names---e.g., | |
12436 | @code{usbkbd,9pnet}. | |
12437 | ||
12438 | @item --repl | |
12439 | Start a read-eval-print loop (REPL) from the initial RAM disk before it | |
12440 | tries to load kernel modules and to mount the root file system. Our | |
12441 | marketing team calls it @dfn{boot-to-Guile}. The Schemer in you will | |
12442 | love it. @xref{Using Guile Interactively,,, guile, GNU Guile Reference | |
12443 | Manual}, for more information on Guile's REPL. | |
12444 | ||
12445 | @end table | |
12446 | ||
12447 | Now that you know all the features that initial RAM disks produced by | |
12448 | @code{base-initrd} provide, here is how to use it and customize it | |
12449 | further. | |
12450 | ||
e32171ee JD |
12451 | @cindex initrd |
12452 | @cindex initial RAM disk | |
fd1b1fa2 | 12453 | @deffn {Monadic Procedure} base-initrd @var{file-systems} @ |
9059b97d | 12454 | [#:qemu-networking? #f] [#:virtio? #t] [#:volatile-root? #f] @ |
52ac153e | 12455 | [#:extra-modules '()] [#:mapped-devices '()] |
fd1b1fa2 | 12456 | Return a monadic derivation that builds a generic initrd. @var{file-systems} is |
1068f26b | 12457 | a list of file systems to be mounted by the initrd, possibly in addition to |
fd1b1fa2 | 12458 | the root file system specified on the kernel command line via @code{--root}. |
52ac153e LC |
12459 | @var{mapped-devices} is a list of device mappings to realize before |
12460 | @var{file-systems} are mounted (@pxref{Mapped Devices}). | |
fd1b1fa2 LC |
12461 | |
12462 | When @var{qemu-networking?} is true, set up networking with the standard QEMU | |
1068f26b AE |
12463 | parameters. When @var{virtio?} is true, load additional modules so that the |
12464 | initrd can be used as a QEMU guest with para-virtualized I/O drivers. | |
fd1b1fa2 LC |
12465 | |
12466 | When @var{volatile-root?} is true, the root file system is writable but any changes | |
12467 | to it are lost. | |
12468 | ||
12469 | The initrd is automatically populated with all the kernel modules necessary | |
12470 | for @var{file-systems} and for the given options. However, additional kernel | |
12471 | modules can be listed in @var{extra-modules}. They will be added to the initrd, and | |
12472 | loaded at boot time in the order in which they appear. | |
12473 | @end deffn | |
12474 | ||
12475 | Needless to say, the initrds we produce and use embed a | |
12476 | statically-linked Guile, and the initialization program is a Guile | |
12477 | program. That gives a lot of flexibility. The | |
12478 | @code{expression->initrd} procedure builds such an initrd, given the | |
12479 | program to run in that initrd. | |
12480 | ||
12481 | @deffn {Monadic Procedure} expression->initrd @var{exp} @ | |
4ee96a79 | 12482 | [#:guile %guile-static-stripped] [#:name "guile-initrd"] |
fd1b1fa2 LC |
12483 | Return a derivation that builds a Linux initrd (a gzipped cpio archive) |
12484 | containing @var{guile} and that evaluates @var{exp}, a G-expression, | |
df650fa8 LC |
12485 | upon booting. All the derivations referenced by @var{exp} are |
12486 | automatically copied to the initrd. | |
fd1b1fa2 LC |
12487 | @end deffn |
12488 | ||
88faf933 LC |
12489 | @node GRUB Configuration |
12490 | @subsection GRUB Configuration | |
12491 | ||
12492 | @cindex GRUB | |
12493 | @cindex boot loader | |
12494 | ||
12495 | The operating system uses GNU@tie{}GRUB as its boot loader | |
12496 | (@pxref{Overview, overview of GRUB,, grub, GNU GRUB Manual}). It is | |
1068f26b AE |
12497 | configured using a @code{grub-configuration} declaration. This data type |
12498 | is exported by the @code{(gnu system grub)} module and described below. | |
88faf933 LC |
12499 | |
12500 | @deftp {Data Type} grub-configuration | |
12501 | The type of a GRUB configuration declaration. | |
12502 | ||
12503 | @table @asis | |
12504 | ||
12505 | @item @code{device} | |
12506 | This is a string denoting the boot device. It must be a device name | |
12507 | understood by the @command{grub-install} command, such as | |
12508 | @code{/dev/sda} or @code{(hd0)} (@pxref{Invoking grub-install,,, grub, | |
12509 | GNU GRUB Manual}). | |
12510 | ||
12511 | @item @code{menu-entries} (default: @code{()}) | |
12512 | A possibly empty list of @code{menu-entry} objects (see below), denoting | |
12513 | entries to appear in the GRUB boot menu, in addition to the current | |
12514 | system entry and the entry pointing to previous system generations. | |
12515 | ||
12516 | @item @code{default-entry} (default: @code{0}) | |
1068f26b AE |
12517 | The index of the default boot menu entry. Index 0 is for the entry of the |
12518 | current system. | |
88faf933 LC |
12519 | |
12520 | @item @code{timeout} (default: @code{5}) | |
12521 | The number of seconds to wait for keyboard input before booting. Set to | |
12522 | 0 to boot immediately, and to -1 to wait indefinitely. | |
12523 | ||
12524 | @item @code{theme} (default: @var{%default-theme}) | |
12525 | The @code{grub-theme} object describing the theme to use. | |
12526 | @end table | |
12527 | ||
12528 | @end deftp | |
12529 | ||
44d5f54e LC |
12530 | @cindex dual boot |
12531 | @cindex boot menu | |
88faf933 LC |
12532 | Should you want to list additional boot menu entries @i{via} the |
12533 | @code{menu-entries} field above, you will need to create them with the | |
44d5f54e LC |
12534 | @code{menu-entry} form. For example, imagine you want to be able to |
12535 | boot another distro (hard to imagine!), you can define a menu entry | |
12536 | along these lines: | |
12537 | ||
12538 | @example | |
12539 | (menu-entry | |
12540 | (label "The Other Distro") | |
12541 | (linux "/boot/old/vmlinux-2.6.32") | |
12542 | (linux-arguments '("root=/dev/sda2")) | |
12543 | (initrd "/boot/old/initrd")) | |
12544 | @end example | |
12545 | ||
12546 | Details below. | |
88faf933 LC |
12547 | |
12548 | @deftp {Data Type} menu-entry | |
12549 | The type of an entry in the GRUB boot menu. | |
12550 | ||
12551 | @table @asis | |
12552 | ||
12553 | @item @code{label} | |
35ed9306 | 12554 | The label to show in the menu---e.g., @code{"GNU"}. |
88faf933 LC |
12555 | |
12556 | @item @code{linux} | |
44d5f54e LC |
12557 | The Linux kernel image to boot, for example: |
12558 | ||
12559 | @example | |
12560 | (file-append linux-libre "/bzImage") | |
12561 | @end example | |
88faf933 | 12562 | |
1ef8b72a CM |
12563 | It is also possible to specify a device explicitly in the file path |
12564 | using GRUB's device naming convention (@pxref{Naming convention,,, grub, | |
12565 | GNU GRUB manual}), for example: | |
12566 | ||
12567 | @example | |
12568 | "(hd0,msdos1)/boot/vmlinuz" | |
12569 | @end example | |
12570 | ||
12571 | If the device is specified explicitly as above, then the @code{device} | |
12572 | field is ignored entirely. | |
12573 | ||
88faf933 LC |
12574 | @item @code{linux-arguments} (default: @code{()}) |
12575 | The list of extra Linux kernel command-line arguments---e.g., | |
12576 | @code{("console=ttyS0")}. | |
12577 | ||
12578 | @item @code{initrd} | |
12579 | A G-Expression or string denoting the file name of the initial RAM disk | |
12580 | to use (@pxref{G-Expressions}). | |
12581 | ||
1ef8b72a CM |
12582 | @item @code{device} (default: @code{#f}) |
12583 | The device where the kernel and initrd are to be found---i.e., the GRUB | |
12584 | @dfn{root} for this menu entry (@pxref{root,,, grub, GNU GRUB manual}). | |
12585 | ||
12586 | This may be a file system label (a string), a file system UUID (a | |
12587 | bytevector, @pxref{File Systems}), or @code{#f}, in which case GRUB will | |
12588 | search the device containing the file specified by the @code{linux} | |
12589 | field (@pxref{search,,, grub, GNU GRUB manual}). It must @emph{not} be | |
12590 | an OS device name such as @file{/dev/sda1}. | |
12591 | ||
12592 | @item @code{device-mount-point} (default: @code{"/"}) | |
12593 | The mount point of the above device on the system. You probably do not | |
12594 | need to change the default value. GuixSD uses it to strip the prefix of | |
12595 | store file names for systems where @file{/gnu} or @file{/gnu/store} is | |
12596 | on a separate partition. | |
12597 | ||
88faf933 LC |
12598 | @end table |
12599 | @end deftp | |
12600 | ||
12601 | @c FIXME: Write documentation once it's stable. | |
12602 | Themes are created using the @code{grub-theme} form, which is not | |
12603 | documented yet. | |
12604 | ||
12605 | @defvr {Scheme Variable} %default-theme | |
12606 | This is the default GRUB theme used by the operating system, with a | |
12607 | fancy background image displaying the GNU and Guix logos. | |
12608 | @end defvr | |
12609 | ||
12610 | ||
cf4a9129 LC |
12611 | @node Invoking guix system |
12612 | @subsection Invoking @code{guix system} | |
0918e64a | 12613 | |
1068f26b | 12614 | Once you have written an operating system declaration as seen in the |
cf4a9129 LC |
12615 | previous section, it can be @dfn{instantiated} using the @command{guix |
12616 | system} command. The synopsis is: | |
4af2447e | 12617 | |
cf4a9129 LC |
12618 | @example |
12619 | guix system @var{options}@dots{} @var{action} @var{file} | |
12620 | @end example | |
4af2447e | 12621 | |
cf4a9129 LC |
12622 | @var{file} must be the name of a file containing an |
12623 | @code{operating-system} declaration. @var{action} specifies how the | |
a40424bd | 12624 | operating system is instantiated. Currently the following values are |
cf4a9129 | 12625 | supported: |
4af2447e | 12626 | |
cf4a9129 LC |
12627 | @table @code |
12628 | @item reconfigure | |
12629 | Build the operating system described in @var{file}, activate it, and | |
8074b330 CM |
12630 | switch to it@footnote{This action (and the related actions |
12631 | @code{switch-generation} and @code{roll-back}) are usable only on | |
12632 | systems already running GuixSD.}. | |
4af2447e | 12633 | |
cf4a9129 LC |
12634 | This effects all the configuration specified in @var{file}: user |
12635 | accounts, system services, global package list, setuid programs, etc. | |
240b57f0 LC |
12636 | The command starts system services specified in @var{file} that are not |
12637 | currently running; if a service is currently running, it does not | |
1068f26b | 12638 | attempt to upgrade it since this would not be possible without stopping it |
240b57f0 | 12639 | first. |
4af2447e | 12640 | |
067a2e2d CM |
12641 | This command creates a new generation whose number is one greater than |
12642 | the current generation (as reported by @command{guix system | |
12643 | list-generations}). If that generation already exists, it will be | |
12644 | overwritten. This behavior mirrors that of @command{guix package} | |
12645 | (@pxref{Invoking guix package}). | |
12646 | ||
cf4a9129 LC |
12647 | It also adds a GRUB menu entry for the new OS configuration, and moves |
12648 | entries for older configurations to a submenu---unless | |
12649 | @option{--no-grub} is passed. | |
4af2447e | 12650 | |
240b57f0 | 12651 | @quotation Note |
bf2479c7 LC |
12652 | @c The paragraph below refers to the problem discussed at |
12653 | @c <http://lists.gnu.org/archive/html/guix-devel/2014-08/msg00057.html>. | |
12654 | It is highly recommended to run @command{guix pull} once before you run | |
12655 | @command{guix system reconfigure} for the first time (@pxref{Invoking | |
12656 | guix pull}). Failing to do that you would see an older version of Guix | |
12657 | once @command{reconfigure} has completed. | |
240b57f0 | 12658 | @end quotation |
bf2479c7 | 12659 | |
8074b330 | 12660 | @item switch-generation |
e32171ee | 12661 | @cindex generations |
8074b330 CM |
12662 | Switch to an existing system generation. This action atomically |
12663 | switches the system profile to the specified system generation. It also | |
12664 | rearranges the system's existing GRUB menu entries. It makes the menu | |
12665 | entry for the specified system generation the default, and it moves the | |
12666 | entries for the other generations to a submenu. The next time the | |
12667 | system boots, it will use the specified system generation. | |
12668 | ||
12669 | The target generation can be specified explicitly by its generation | |
12670 | number. For example, the following invocation would switch to system | |
12671 | generation 7: | |
12672 | ||
12673 | @example | |
12674 | guix system switch-generation 7 | |
12675 | @end example | |
12676 | ||
12677 | The target generation can also be specified relative to the current | |
12678 | generation with the form @code{+N} or @code{-N}, where @code{+3} means | |
12679 | ``3 generations ahead of the current generation,'' and @code{-1} means | |
12680 | ``1 generation prior to the current generation.'' When specifying a | |
12681 | negative value such as @code{-1}, you must precede it with @code{--} to | |
12682 | prevent it from being parsed as an option. For example: | |
12683 | ||
12684 | @example | |
12685 | guix system switch-generation -- -1 | |
12686 | @end example | |
12687 | ||
12688 | Currently, the effect of invoking this action is @emph{only} to switch | |
12689 | the system profile to an existing generation and rearrange the GRUB menu | |
12690 | entries. To actually start using the target system generation, you must | |
12691 | reboot after running this action. In the future, it will be updated to | |
12692 | do the same things as @command{reconfigure}, like activating and | |
12693 | deactivating services. | |
12694 | ||
12695 | This action will fail if the specified generation does not exist. | |
12696 | ||
12697 | @item roll-back | |
e32171ee | 12698 | @cindex rolling back |
8074b330 CM |
12699 | Switch to the preceding system generation. The next time the system |
12700 | boots, it will use the preceding system generation. This is the inverse | |
12701 | of @command{reconfigure}, and it is exactly the same as invoking | |
12702 | @command{switch-generation} with an argument of @code{-1}. | |
12703 | ||
12704 | Currently, as with @command{switch-generation}, you must reboot after | |
12705 | running this action to actually start using the preceding system | |
12706 | generation. | |
12707 | ||
cf4a9129 | 12708 | @item build |
1068f26b | 12709 | Build the derivation of the operating system, which includes all the |
cf4a9129 LC |
12710 | configuration files and programs needed to boot and run the system. |
12711 | This action does not actually install anything. | |
113daf62 | 12712 | |
cf4a9129 LC |
12713 | @item init |
12714 | Populate the given directory with all the files necessary to run the | |
12715 | operating system specified in @var{file}. This is useful for first-time | |
4705641f | 12716 | installations of GuixSD. For instance: |
113daf62 LC |
12717 | |
12718 | @example | |
cf4a9129 | 12719 | guix system init my-os-config.scm /mnt |
113daf62 LC |
12720 | @end example |
12721 | ||
cf4a9129 LC |
12722 | copies to @file{/mnt} all the store items required by the configuration |
12723 | specified in @file{my-os-config.scm}. This includes configuration | |
12724 | files, packages, and so on. It also creates other essential files | |
12725 | needed for the system to operate correctly---e.g., the @file{/etc}, | |
12726 | @file{/var}, and @file{/run} directories, and the @file{/bin/sh} file. | |
113daf62 | 12727 | |
cf4a9129 LC |
12728 | This command also installs GRUB on the device specified in |
12729 | @file{my-os-config}, unless the @option{--no-grub} option was passed. | |
113daf62 | 12730 | |
cf4a9129 LC |
12731 | @item vm |
12732 | @cindex virtual machine | |
0276f697 | 12733 | @cindex VM |
f535dcbe | 12734 | @anchor{guix system vm} |
1068f26b | 12735 | Build a virtual machine that contains the operating system declared in |
cf4a9129 | 12736 | @var{file}, and return a script to run that virtual machine (VM). |
1068f26b | 12737 | Arguments given to the script are passed to QEMU. |
113daf62 | 12738 | |
cf4a9129 | 12739 | The VM shares its store with the host system. |
113daf62 | 12740 | |
0276f697 LC |
12741 | Additional file systems can be shared between the host and the VM using |
12742 | the @code{--share} and @code{--expose} command-line options: the former | |
12743 | specifies a directory to be shared with write access, while the latter | |
12744 | provides read-only access to the shared directory. | |
12745 | ||
12746 | The example below creates a VM in which the user's home directory is | |
12747 | accessible read-only, and where the @file{/exchange} directory is a | |
1068f26b | 12748 | read-write mapping of @file{$HOME/tmp} on the host: |
0276f697 LC |
12749 | |
12750 | @example | |
12751 | guix system vm my-config.scm \ | |
12752 | --expose=$HOME --share=$HOME/tmp=/exchange | |
12753 | @end example | |
12754 | ||
6aa260af LC |
12755 | On GNU/Linux, the default is to boot directly to the kernel; this has |
12756 | the advantage of requiring only a very tiny root disk image since the | |
1068f26b | 12757 | store of the host can then be mounted. |
6aa260af LC |
12758 | |
12759 | The @code{--full-boot} option forces a complete boot sequence, starting | |
12760 | with the bootloader. This requires more disk space since a root image | |
12761 | containing at least the kernel, initrd, and bootloader data files must | |
12762 | be created. The @code{--image-size} option can be used to specify the | |
1068f26b | 12763 | size of the image. |
ab11f0be | 12764 | |
cf4a9129 LC |
12765 | @item vm-image |
12766 | @itemx disk-image | |
12767 | Return a virtual machine or disk image of the operating system declared | |
12768 | in @var{file} that stands alone. Use the @option{--image-size} option | |
12769 | to specify the size of the image. | |
113daf62 | 12770 | |
cf4a9129 | 12771 | When using @code{vm-image}, the returned image is in qcow2 format, which |
97d76250 LF |
12772 | the QEMU emulator can efficiently use. @xref{Running GuixSD in a VM}, |
12773 | for more information on how to run the image in a virtual machine. | |
113daf62 | 12774 | |
cf4a9129 LC |
12775 | When using @code{disk-image}, a raw disk image is produced; it can be |
12776 | copied as is to a USB stick, for instance. Assuming @code{/dev/sdc} is | |
1068f26b | 12777 | the device corresponding to a USB stick, one can copy the image to it |
cf4a9129 | 12778 | using the following command: |
113daf62 | 12779 | |
cf4a9129 LC |
12780 | @example |
12781 | # dd if=$(guix system disk-image my-os.scm) of=/dev/sdc | |
12782 | @end example | |
113daf62 | 12783 | |
1c8a81b1 DT |
12784 | @item container |
12785 | Return a script to run the operating system declared in @var{file} | |
12786 | within a container. Containers are a set of lightweight isolation | |
12787 | mechanisms provided by the kernel Linux-libre. Containers are | |
12788 | substantially less resource-demanding than full virtual machines since | |
12789 | the kernel, shared objects, and other resources can be shared with the | |
12790 | host system; this also means they provide thinner isolation. | |
12791 | ||
12792 | Currently, the script must be run as root in order to support more than | |
12793 | a single user and group. The container shares its store with the host | |
12794 | system. | |
12795 | ||
12796 | As with the @code{vm} action (@pxref{guix system vm}), additional file | |
12797 | systems to be shared between the host and container can be specified | |
12798 | using the @option{--share} and @option{--expose} options: | |
12799 | ||
12800 | @example | |
12801 | guix system container my-config.scm \ | |
12802 | --expose=$HOME --share=$HOME/tmp=/exchange | |
12803 | @end example | |
12804 | ||
0f252e26 | 12805 | @quotation Note |
cfd35b4e | 12806 | This option requires Linux-libre 3.19 or newer. |
0f252e26 DT |
12807 | @end quotation |
12808 | ||
cf4a9129 | 12809 | @end table |
113daf62 | 12810 | |
ccd7158d LC |
12811 | @var{options} can contain any of the common build options (@pxref{Common |
12812 | Build Options}). In addition, @var{options} can contain one of the | |
12813 | following: | |
113daf62 | 12814 | |
cf4a9129 LC |
12815 | @table @option |
12816 | @item --system=@var{system} | |
12817 | @itemx -s @var{system} | |
1068f26b | 12818 | Attempt to build for @var{system} instead of the host system type. |
cf4a9129 | 12819 | This works as per @command{guix build} (@pxref{Invoking guix build}). |
113daf62 | 12820 | |
f3f427c2 LC |
12821 | @item --derivation |
12822 | @itemx -d | |
12823 | Return the derivation file name of the given operating system without | |
12824 | building anything. | |
12825 | ||
cf4a9129 LC |
12826 | @item --image-size=@var{size} |
12827 | For the @code{vm-image} and @code{disk-image} actions, create an image | |
12828 | of the given @var{size}. @var{size} may be a number of bytes, or it may | |
4a44d7bb LC |
12829 | include a unit as a suffix (@pxref{Block size, size specifications,, |
12830 | coreutils, GNU Coreutils}). | |
db030303 LC |
12831 | |
12832 | @item --on-error=@var{strategy} | |
12833 | Apply @var{strategy} when an error occurs when reading @var{file}. | |
12834 | @var{strategy} may be one of the following: | |
12835 | ||
12836 | @table @code | |
12837 | @item nothing-special | |
12838 | Report the error concisely and exit. This is the default strategy. | |
12839 | ||
12840 | @item backtrace | |
12841 | Likewise, but also display a backtrace. | |
12842 | ||
12843 | @item debug | |
12844 | Report the error and enter Guile's debugger. From there, you can run | |
12845 | commands such as @code{,bt} to get a backtrace, @code{,locals} to | |
1068f26b AE |
12846 | display local variable values, and more generally inspect the state of the |
12847 | program. @xref{Debug Commands,,, guile, GNU Guile Reference Manual}, for | |
db030303 LC |
12848 | a list of available debugging commands. |
12849 | @end table | |
113daf62 | 12850 | @end table |
113daf62 | 12851 | |
eca69fc0 LC |
12852 | @quotation Note |
12853 | All the actions above, except @code{build} and @code{init}, | |
12854 | can use KVM support in the Linux-libre kernel. Specifically, if the | |
12855 | machine has hardware virtualization support, the corresponding | |
cf4a9129 | 12856 | KVM kernel module should be loaded, and the @file{/dev/kvm} device node |
1068f26b | 12857 | must exist and be readable and writable by the user and by the |
eca69fc0 LC |
12858 | build users of the daemon (@pxref{Build Environment Setup}). |
12859 | @end quotation | |
8451a568 | 12860 | |
65797bff LC |
12861 | Once you have built, configured, re-configured, and re-re-configured |
12862 | your GuixSD installation, you may find it useful to list the operating | |
12863 | system generations available on disk---and that you can choose from the | |
12864 | GRUB boot menu: | |
12865 | ||
12866 | @table @code | |
12867 | ||
12868 | @item list-generations | |
12869 | List a summary of each generation of the operating system available on | |
12870 | disk, in a human-readable way. This is similar to the | |
12871 | @option{--list-generations} option of @command{guix package} | |
12872 | (@pxref{Invoking guix package}). | |
12873 | ||
12874 | Optionally, one can specify a pattern, with the same syntax that is used | |
12875 | in @command{guix package --list-generations}, to restrict the list of | |
12876 | generations displayed. For instance, the following command displays | |
1068f26b | 12877 | generations that are up to 10 days old: |
65797bff LC |
12878 | |
12879 | @example | |
12880 | $ guix system list-generations 10d | |
12881 | @end example | |
12882 | ||
12883 | @end table | |
12884 | ||
d6c3267a LC |
12885 | The @command{guix system} command has even more to offer! The following |
12886 | sub-commands allow you to visualize how your system services relate to | |
12887 | each other: | |
12888 | ||
12889 | @anchor{system-extension-graph} | |
12890 | @table @code | |
12891 | ||
12892 | @item extension-graph | |
12893 | Emit in Dot/Graphviz format to standard output the @dfn{service | |
12894 | extension graph} of the operating system defined in @var{file} | |
12895 | (@pxref{Service Composition}, for more information on service | |
12896 | extensions.) | |
12897 | ||
12898 | The command: | |
12899 | ||
12900 | @example | |
12901 | $ guix system extension-graph @var{file} | dot -Tpdf > services.pdf | |
12902 | @end example | |
12903 | ||
12904 | produces a PDF file showing the extension relations among services. | |
12905 | ||
710fa231 AK |
12906 | @anchor{system-shepherd-graph} |
12907 | @item shepherd-graph | |
6f305ea5 | 12908 | Emit in Dot/Graphviz format to standard output the @dfn{dependency |
dd17bc38 AK |
12909 | graph} of shepherd services of the operating system defined in |
12910 | @var{file}. @xref{Shepherd Services}, for more information and for an | |
12911 | example graph. | |
6f305ea5 | 12912 | |
d6c3267a LC |
12913 | @end table |
12914 | ||
97d76250 | 12915 | @node Running GuixSD in a VM |
70ac09a5 | 12916 | @subsection Running GuixSD in a Virtual Machine |
97d76250 | 12917 | |
e32171ee | 12918 | @cindex virtual machine |
97d76250 LF |
12919 | One way to run GuixSD in a virtual machine (VM) is to build a GuixSD |
12920 | virtual machine image using @command{guix system vm-image} | |
12921 | (@pxref{Invoking guix system}). The returned image is in qcow2 format, | |
12922 | which the @uref{http://qemu.org/, QEMU emulator} can efficiently use. | |
12923 | ||
e32171ee | 12924 | @cindex QEMU |
97d76250 LF |
12925 | To run the image in QEMU, copy it out of the store (@pxref{The Store}) |
12926 | and give yourself permission to write to the copy. When invoking QEMU, | |
12927 | you must choose a system emulator that is suitable for your hardware | |
12928 | platform. Here is a minimal QEMU invocation that will boot the result | |
12929 | of @command{guix system vm-image} on x86_64 hardware: | |
12930 | ||
12931 | @example | |
12932 | $ qemu-system-x86_64 \ | |
12933 | -net user -net nic,model=virtio \ | |
12934 | -enable-kvm -m 256 /tmp/qemu-image | |
12935 | @end example | |
12936 | ||
12937 | Here is what each of these options means: | |
12938 | ||
12939 | @table @code | |
12940 | @item qemu-system-x86_64 | |
12941 | This specifies the hardware platform to emulate. This should match the | |
12942 | host. | |
12943 | ||
12944 | @item -net user | |
12945 | Enable the unprivileged user-mode network stack. The guest OS can | |
12946 | access the host but not vice versa. This is the simplest way to get the | |
58806e6f | 12947 | guest OS online. |
97d76250 LF |
12948 | |
12949 | @item -net nic,model=virtio | |
1068f26b | 12950 | You must create a network interface of a given model. If you do not |
97d76250 LF |
12951 | create a NIC, the boot will fail. Assuming your hardware platform is |
12952 | x86_64, you can get a list of available NIC models by running | |
12953 | @command{qemu-system-x86_64 -net nic,model=help}. | |
12954 | ||
12955 | @item -enable-kvm | |
12956 | If your system has hardware virtualization extensions, enabling the | |
1068f26b | 12957 | virtual machine support (KVM) of the Linux kernel will make things run |
97d76250 LF |
12958 | faster. |
12959 | ||
12960 | @item -m 256 | |
12961 | RAM available to the guest OS, in mebibytes. Defaults to 128@tie{}MiB, | |
7414de0a | 12962 | which may be insufficient for some operations. |
97d76250 LF |
12963 | |
12964 | @item /tmp/qemu-image | |
12965 | The file name of the qcow2 image. | |
12966 | @end table | |
d6c3267a | 12967 | |
3ddc50db DC |
12968 | The default @command{run-vm.sh} script that is returned by an invokation of |
12969 | @command{guix system vm} does not add a @command{-net user} flag by default. | |
12970 | To get network access from within the vm add the @code{(dhcp-client-service)} | |
12971 | to your system definition and start the VM using | |
12972 | @command{`guix system vm config.scm` -net user}. An important caveat of using | |
12973 | @command{-net user} for networking is that @command{ping} will not work, because | |
12974 | it uses the ICMP protocol. You'll have to use a different command to check for | |
12975 | network connectivity, like for example @command{curl}. | |
12976 | ||
12977 | @subsubsection Connecting Through SSH | |
12978 | ||
e32171ee JD |
12979 | @cindex SSH |
12980 | @cindex SSH server | |
3ddc50db DC |
12981 | To enable SSH inside a VM you need to add a SSH server like @code{(dropbear-service)} |
12982 | or @code{(lsh-service)} to your VM. The @code{(lsh-service}) doesn't currently | |
12983 | boot unsupervised. It requires you to type some characters to initialize the | |
12984 | randomness generator. In addition you need to forward the SSH port, 22 by | |
12985 | default, to the host. You can do this with | |
12986 | ||
12987 | @example | |
12988 | `guix system vm config.scm` -net user,hostfwd=tcp::10022-:22 | |
12989 | @end example | |
12990 | ||
12991 | To connect to the VM you can run | |
12992 | ||
12993 | @example | |
12994 | ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 10022 | |
12995 | @end example | |
12996 | ||
12997 | The @command{-p} tells @command{ssh} the port you want to connect to. | |
12998 | @command{-o UserKnownHostsFile=/dev/null} prevents @command{ssh} from complaining | |
12999 | every time you modify your @command{config.scm} file and the | |
13000 | @command{-o StrictHostKeyChecking=no} prevents you from having to allow a | |
13001 | connection to an unknown host every time you connect. | |
13002 | ||
13003 | @subsubsection Using @command{virt-viewer} with Spice | |
13004 | ||
13005 | As an alternative to the default @command{qemu} graphical client you can | |
13006 | use the @command{remote-viewer} from the @command{virt-viewer} package. To | |
13007 | connect pass the @command{-spice port=5930,disable-ticketing} flag to | |
13008 | @command{qemu}. See previous section for further information on how to do this. | |
13009 | ||
13010 | Spice also allows you to do some nice stuff like share your clipboard with your | |
13011 | VM. To enable that you'll also have to pass the following flags to @command{qemu}: | |
13012 | ||
13013 | @example | |
13014 | -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 | |
13015 | -chardev spicevmc,name=vdagent,id=vdagent | |
13016 | -device virtserialport,nr=1,bus=virtio-serial0.0,chardev=vdagent, | |
13017 | name=com.redhat.spice.0 | |
13018 | @end example | |
13019 | ||
13020 | You'll also need to add the @pxref{Miscellaneous Services, Spice service}. | |
13021 | ||
cf4a9129 LC |
13022 | @node Defining Services |
13023 | @subsection Defining Services | |
8451a568 | 13024 | |
eb524192 | 13025 | The previous sections show the available services and how one can combine |
0adfe95a LC |
13026 | them in an @code{operating-system} declaration. But how do we define |
13027 | them in the first place? And what is a service anyway? | |
8451a568 | 13028 | |
0adfe95a LC |
13029 | @menu |
13030 | * Service Composition:: The model for composing services. | |
13031 | * Service Types and Services:: Types and services. | |
13032 | * Service Reference:: API reference. | |
dd17bc38 | 13033 | * Shepherd Services:: A particular type of service. |
0adfe95a LC |
13034 | @end menu |
13035 | ||
13036 | @node Service Composition | |
13037 | @subsubsection Service Composition | |
13038 | ||
13039 | @cindex services | |
13040 | @cindex daemons | |
13041 | Here we define a @dfn{service} as, broadly, something that extends the | |
1068f26b | 13042 | functionality of the operating system. Often a service is a process---a |
0adfe95a LC |
13043 | @dfn{daemon}---started when the system boots: a secure shell server, a |
13044 | Web server, the Guix build daemon, etc. Sometimes a service is a daemon | |
13045 | whose execution can be triggered by another daemon---e.g., an FTP server | |
13046 | started by @command{inetd} or a D-Bus service activated by | |
13047 | @command{dbus-daemon}. Occasionally, a service does not map to a | |
13048 | daemon. For instance, the ``account'' service collects user accounts | |
13049 | and makes sure they exist when the system runs; the ``udev'' service | |
13050 | collects device management rules and makes them available to the eudev | |
1068f26b AE |
13051 | daemon; the @file{/etc} service populates the @file{/etc} directory |
13052 | of the system. | |
0adfe95a | 13053 | |
d6c3267a | 13054 | @cindex service extensions |
0adfe95a | 13055 | GuixSD services are connected by @dfn{extensions}. For instance, the |
1068f26b | 13056 | secure shell service @emph{extends} the Shepherd---the GuixSD |
dd17bc38 AK |
13057 | initialization system, running as PID@tie{}1---by giving it the command |
13058 | lines to start and stop the secure shell daemon (@pxref{Networking | |
13059 | Services, @code{lsh-service}}); the UPower service extends the D-Bus | |
13060 | service by passing it its @file{.service} specification, and extends the | |
13061 | udev service by passing it device management rules (@pxref{Desktop | |
13062 | Services, @code{upower-service}}); the Guix daemon service extends the | |
13063 | Shepherd by passing it the command lines to start and stop the daemon, | |
13064 | and extends the account service by passing it a list of required build | |
13065 | user accounts (@pxref{Base Services}). | |
0adfe95a LC |
13066 | |
13067 | All in all, services and their ``extends'' relations form a directed | |
13068 | acyclic graph (DAG). If we represent services as boxes and extensions | |
13069 | as arrows, a typical system might provide something like this: | |
13070 | ||
13071 | @image{images/service-graph,,5in,Typical service extension graph.} | |
13072 | ||
d62e201c LC |
13073 | @cindex system service |
13074 | At the bottom, we see the @dfn{system service}, which produces the | |
13075 | directory containing everything to run and boot the system, as returned | |
13076 | by the @command{guix system build} command. @xref{Service Reference}, | |
13077 | to learn about the other service types shown here. | |
d6c3267a LC |
13078 | @xref{system-extension-graph, the @command{guix system extension-graph} |
13079 | command}, for information on how to generate this representation for a | |
13080 | particular operating system definition. | |
0adfe95a LC |
13081 | |
13082 | @cindex service types | |
13083 | Technically, developers can define @dfn{service types} to express these | |
13084 | relations. There can be any number of services of a given type on the | |
13085 | system---for instance, a system running two instances of the GNU secure | |
13086 | shell server (lsh) has two instances of @var{lsh-service-type}, with | |
13087 | different parameters. | |
13088 | ||
13089 | The following section describes the programming interface for service | |
13090 | types and services. | |
13091 | ||
13092 | @node Service Types and Services | |
13093 | @subsubsection Service Types and Services | |
13094 | ||
13095 | A @dfn{service type} is a node in the DAG described above. Let us start | |
13096 | with a simple example, the service type for the Guix build daemon | |
13097 | (@pxref{Invoking guix-daemon}): | |
13098 | ||
13099 | @example | |
13100 | (define guix-service-type | |
13101 | (service-type | |
13102 | (name 'guix) | |
13103 | (extensions | |
d4053c71 | 13104 | (list (service-extension shepherd-root-service-type guix-shepherd-service) |
0adfe95a LC |
13105 | (service-extension account-service-type guix-accounts) |
13106 | (service-extension activation-service-type guix-activation))))) | |
13107 | @end example | |
8451a568 | 13108 | |
cf4a9129 | 13109 | @noindent |
1068f26b | 13110 | It defines two things: |
0adfe95a LC |
13111 | |
13112 | @enumerate | |
13113 | @item | |
13114 | A name, whose sole purpose is to make inspection and debugging easier. | |
13115 | ||
13116 | @item | |
13117 | A list of @dfn{service extensions}, where each extension designates the | |
1068f26b AE |
13118 | target service type and a procedure that, given the parameters of the |
13119 | service, returns a list of objects to extend the service of that type. | |
0adfe95a LC |
13120 | |
13121 | Every service type has at least one service extension. The only | |
13122 | exception is the @dfn{boot service type}, which is the ultimate service. | |
13123 | @end enumerate | |
13124 | ||
13125 | In this example, @var{guix-service-type} extends three services: | |
13126 | ||
13127 | @table @var | |
d4053c71 AK |
13128 | @item shepherd-root-service-type |
13129 | The @var{guix-shepherd-service} procedure defines how the Shepherd | |
13130 | service is extended. Namely, it returns a @code{<shepherd-service>} | |
13131 | object that defines how @command{guix-daemon} is started and stopped | |
13132 | (@pxref{Shepherd Services}). | |
0adfe95a LC |
13133 | |
13134 | @item account-service-type | |
13135 | This extension for this service is computed by @var{guix-accounts}, | |
13136 | which returns a list of @code{user-group} and @code{user-account} | |
13137 | objects representing the build user accounts (@pxref{Invoking | |
13138 | guix-daemon}). | |
13139 | ||
13140 | @item activation-service-type | |
13141 | Here @var{guix-activation} is a procedure that returns a gexp, which is | |
13142 | a code snippet to run at ``activation time''---e.g., when the service is | |
13143 | booted. | |
13144 | @end table | |
13145 | ||
13146 | A service of this type is instantiated like this: | |
13147 | ||
13148 | @example | |
13149 | (service guix-service-type | |
13150 | (guix-configuration | |
13151 | (build-accounts 5) | |
13152 | (use-substitutes? #f))) | |
13153 | @end example | |
13154 | ||
13155 | The second argument to the @code{service} form is a value representing | |
13156 | the parameters of this specific service instance. | |
13157 | @xref{guix-configuration-type, @code{guix-configuration}}, for | |
13158 | information about the @code{guix-configuration} data type. | |
13159 | ||
13160 | @var{guix-service-type} is quite simple because it extends other | |
13161 | services but is not extensible itself. | |
13162 | ||
13163 | @c @subsubsubsection Extensible Service Types | |
13164 | ||
13165 | The service type for an @emph{extensible} service looks like this: | |
13166 | ||
13167 | @example | |
13168 | (define udev-service-type | |
13169 | (service-type (name 'udev) | |
13170 | (extensions | |
d4053c71 AK |
13171 | (list (service-extension shepherd-root-service-type |
13172 | udev-shepherd-service))) | |
0adfe95a LC |
13173 | |
13174 | (compose concatenate) ;concatenate the list of rules | |
13175 | (extend (lambda (config rules) | |
13176 | (match config | |
13177 | (($ <udev-configuration> udev initial-rules) | |
13178 | (udev-configuration | |
13179 | (udev udev) ;the udev package to use | |
13180 | (rules (append initial-rules rules))))))))) | |
13181 | @end example | |
13182 | ||
13183 | This is the service type for the | |
13184 | @uref{https://wiki.gentoo.org/wiki/Project:Eudev, eudev device | |
13185 | management daemon}. Compared to the previous example, in addition to an | |
d4053c71 | 13186 | extension of @var{shepherd-root-service-type}, we see two new fields: |
0adfe95a LC |
13187 | |
13188 | @table @code | |
13189 | @item compose | |
13190 | This is the procedure to @dfn{compose} the list of extensions to | |
13191 | services of this type. | |
13192 | ||
13193 | Services can extend the udev service by passing it lists of rules; we | |
13194 | compose those extensions simply by concatenating them. | |
13195 | ||
13196 | @item extend | |
1068f26b | 13197 | This procedure defines how the value of the service is @dfn{extended} with |
0adfe95a LC |
13198 | the composition of the extensions. |
13199 | ||
13200 | Udev extensions are composed into a list of rules, but the udev service | |
13201 | value is itself a @code{<udev-configuration>} record. So here, we | |
a40424bd | 13202 | extend that record by appending the list of rules it contains to the |
0adfe95a LC |
13203 | list of contributed rules. |
13204 | @end table | |
13205 | ||
13206 | There can be only one instance of an extensible service type such as | |
13207 | @var{udev-service-type}. If there were more, the | |
13208 | @code{service-extension} specifications would be ambiguous. | |
13209 | ||
13210 | Still here? The next section provides a reference of the programming | |
13211 | interface for services. | |
13212 | ||
13213 | @node Service Reference | |
13214 | @subsubsection Service Reference | |
13215 | ||
13216 | We have seen an overview of service types (@pxref{Service Types and | |
13217 | Services}). This section provides a reference on how to manipulate | |
13218 | services and service types. This interface is provided by the | |
13219 | @code{(gnu services)} module. | |
13220 | ||
13221 | @deffn {Scheme Procedure} service @var{type} @var{value} | |
13222 | Return a new service of @var{type}, a @code{<service-type>} object (see | |
13223 | below.) @var{value} can be any object; it represents the parameters of | |
13224 | this particular service instance. | |
13225 | @end deffn | |
13226 | ||
13227 | @deffn {Scheme Procedure} service? @var{obj} | |
13228 | Return true if @var{obj} is a service. | |
13229 | @end deffn | |
8451a568 | 13230 | |
0adfe95a LC |
13231 | @deffn {Scheme Procedure} service-kind @var{service} |
13232 | Return the type of @var{service}---i.e., a @code{<service-type>} object. | |
13233 | @end deffn | |
13234 | ||
13235 | @deffn {Scheme Procedure} service-parameters @var{service} | |
13236 | Return the value associated with @var{service}. It represents its | |
13237 | parameters. | |
13238 | @end deffn | |
13239 | ||
13240 | Here is an example of how a service is created and manipulated: | |
13241 | ||
13242 | @example | |
13243 | (define s | |
13244 | (service nginx-service-type | |
13245 | (nginx-configuration | |
13246 | (nginx nginx) | |
13247 | (log-directory log-directory) | |
13248 | (run-directory run-directory) | |
13249 | (file config-file)))) | |
13250 | ||
13251 | (service? s) | |
13252 | @result{} #t | |
13253 | ||
13254 | (eq? (service-kind s) nginx-service-type) | |
13255 | @result{} #t | |
13256 | @end example | |
13257 | ||
cd6f6c22 LC |
13258 | The @code{modify-services} form provides a handy way to change the |
13259 | parameters of some of the services of a list such as | |
4d343a14 | 13260 | @var{%base-services} (@pxref{Base Services, @code{%base-services}}). It |
7414de0a | 13261 | evaluates to a list of services. Of course, you could always use |
4d343a14 CM |
13262 | standard list combinators such as @code{map} and @code{fold} to do that |
13263 | (@pxref{SRFI-1, List Library,, guile, GNU Guile Reference Manual}); | |
13264 | @code{modify-services} simply provides a more concise form for this | |
13265 | common pattern. | |
cd6f6c22 LC |
13266 | |
13267 | @deffn {Scheme Syntax} modify-services @var{services} @ | |
13268 | (@var{type} @var{variable} => @var{body}) @dots{} | |
13269 | ||
13270 | Modify the services listed in @var{services} according to the given | |
13271 | clauses. Each clause has the form: | |
13272 | ||
13273 | @example | |
13274 | (@var{type} @var{variable} => @var{body}) | |
13275 | @end example | |
13276 | ||
4d343a14 CM |
13277 | where @var{type} is a service type---e.g., |
13278 | @code{guix-service-type}---and @var{variable} is an identifier that is | |
13279 | bound within the @var{body} to the service parameters---e.g., a | |
13280 | @code{guix-configuration} instance---of the original service of that | |
13281 | @var{type}. | |
cd6f6c22 | 13282 | |
4d343a14 CM |
13283 | The @var{body} should evaluate to the new service parameters, which will |
13284 | be used to configure the new service. This new service will replace the | |
13285 | original in the resulting list. Because a service's service parameters | |
7414de0a | 13286 | are created using @code{define-record-type*}, you can write a succinct |
4d343a14 CM |
13287 | @var{body} that evaluates to the new service parameters by using the |
13288 | @code{inherit} feature that @code{define-record-type*} provides. | |
13289 | ||
b53daad0 | 13290 | @xref{Using the Configuration System}, for example usage. |
cd6f6c22 | 13291 | |
cd6f6c22 LC |
13292 | @end deffn |
13293 | ||
13294 | Next comes the programming interface for service types. This is | |
13295 | something you want to know when writing new service definitions, but not | |
13296 | necessarily when simply looking for ways to customize your | |
13297 | @code{operating-system} declaration. | |
13298 | ||
0adfe95a LC |
13299 | @deftp {Data Type} service-type |
13300 | @cindex service type | |
13301 | This is the representation of a @dfn{service type} (@pxref{Service Types | |
13302 | and Services}). | |
13303 | ||
13304 | @table @asis | |
13305 | @item @code{name} | |
13306 | This is a symbol, used only to simplify inspection and debugging. | |
13307 | ||
13308 | @item @code{extensions} | |
1068f26b | 13309 | A non-empty list of @code{<service-extension>} objects (see below). |
0adfe95a LC |
13310 | |
13311 | @item @code{compose} (default: @code{#f}) | |
13312 | If this is @code{#f}, then the service type denotes services that cannot | |
13313 | be extended---i.e., services that do not receive ``values'' from other | |
13314 | services. | |
13315 | ||
13316 | Otherwise, it must be a one-argument procedure. The procedure is called | |
13317 | by @code{fold-services} and is passed a list of values collected from | |
13318 | extensions. It must return a value that is a valid parameter value for | |
13319 | the service instance. | |
13320 | ||
13321 | @item @code{extend} (default: @code{#f}) | |
13322 | If this is @code{#f}, services of this type cannot be extended. | |
13323 | ||
13324 | Otherwise, it must be a two-argument procedure: @code{fold-services} | |
1068f26b | 13325 | calls it, passing it the initial value of the service as the first argument |
0adfe95a LC |
13326 | and the result of applying @code{compose} to the extension values as the |
13327 | second argument. | |
13328 | @end table | |
13329 | ||
13330 | @xref{Service Types and Services}, for examples. | |
13331 | @end deftp | |
13332 | ||
13333 | @deffn {Scheme Procedure} service-extension @var{target-type} @ | |
13334 | @var{compute} | |
13335 | Return a new extension for services of type @var{target-type}. | |
13336 | @var{compute} must be a one-argument procedure: @code{fold-services} | |
13337 | calls it, passing it the value associated with the service that provides | |
13338 | the extension; it must return a valid value for the target service. | |
13339 | @end deffn | |
13340 | ||
13341 | @deffn {Scheme Procedure} service-extension? @var{obj} | |
13342 | Return true if @var{obj} is a service extension. | |
13343 | @end deffn | |
13344 | ||
71654dfd LC |
13345 | Occasionally, you might want to simply extend an existing service. This |
13346 | involves creating a new service type and specifying the extension of | |
13347 | interest, which can be verbose; the @code{simple-service} procedure | |
13348 | provides a shorthand for this. | |
13349 | ||
13350 | @deffn {Scheme Procedure} simple-service @var{name} @var{target} @var{value} | |
13351 | Return a service that extends @var{target} with @var{value}. This works | |
13352 | by creating a singleton service type @var{name}, of which the returned | |
13353 | service is an instance. | |
13354 | ||
13355 | For example, this extends mcron (@pxref{Scheduled Job Execution}) with | |
13356 | an additional job: | |
13357 | ||
13358 | @example | |
13359 | (simple-service 'my-mcron-job mcron-service-type | |
13360 | #~(job '(next-hour (3)) "guix gc -F 2G")) | |
13361 | @end example | |
13362 | @end deffn | |
13363 | ||
0adfe95a LC |
13364 | At the core of the service abstraction lies the @code{fold-services} |
13365 | procedure, which is responsible for ``compiling'' a list of services | |
d62e201c LC |
13366 | down to a single directory that contains everything needed to boot and |
13367 | run the system---the directory shown by the @command{guix system build} | |
13368 | command (@pxref{Invoking guix system}). In essence, it propagates | |
13369 | service extensions down the service graph, updating each node parameters | |
13370 | on the way, until it reaches the root node. | |
0adfe95a LC |
13371 | |
13372 | @deffn {Scheme Procedure} fold-services @var{services} @ | |
d62e201c | 13373 | [#:target-type @var{system-service-type}] |
0adfe95a LC |
13374 | Fold @var{services} by propagating their extensions down to the root of |
13375 | type @var{target-type}; return the root service adjusted accordingly. | |
13376 | @end deffn | |
13377 | ||
13378 | Lastly, the @code{(gnu services)} module also defines several essential | |
13379 | service types, some of which are listed below. | |
13380 | ||
d62e201c LC |
13381 | @defvr {Scheme Variable} system-service-type |
13382 | This is the root of the service graph. It produces the system directory | |
13383 | as returned by the @command{guix system build} command. | |
13384 | @end defvr | |
13385 | ||
0adfe95a | 13386 | @defvr {Scheme Variable} boot-service-type |
d62e201c LC |
13387 | The type of the ``boot service'', which produces the @dfn{boot script}. |
13388 | The boot script is what the initial RAM disk runs when booting. | |
0adfe95a LC |
13389 | @end defvr |
13390 | ||
13391 | @defvr {Scheme Variable} etc-service-type | |
13392 | The type of the @file{/etc} service. This service can be extended by | |
13393 | passing it name/file tuples such as: | |
13394 | ||
13395 | @example | |
13396 | (list `("issue" ,(plain-file "issue" "Welcome!\n"))) | |
13397 | @end example | |
13398 | ||
13399 | In this example, the effect would be to add an @file{/etc/issue} file | |
13400 | pointing to the given file. | |
13401 | @end defvr | |
13402 | ||
13403 | @defvr {Scheme Variable} setuid-program-service-type | |
13404 | Type for the ``setuid-program service''. This service collects lists of | |
13405 | executable file names, passed as gexps, and adds them to the set of | |
13406 | setuid-root programs on the system (@pxref{Setuid Programs}). | |
13407 | @end defvr | |
13408 | ||
af4c3fd5 LC |
13409 | @defvr {Scheme Variable} profile-service-type |
13410 | Type of the service that populates the @dfn{system profile}---i.e., the | |
13411 | programs under @file{/run/current-system/profile}. Other services can | |
13412 | extend it by passing it lists of packages to add to the system profile. | |
13413 | @end defvr | |
13414 | ||
0adfe95a | 13415 | |
dd17bc38 AK |
13416 | @node Shepherd Services |
13417 | @subsubsection Shepherd Services | |
0adfe95a | 13418 | |
e32171ee | 13419 | @cindex shepherd services |
0adfe95a LC |
13420 | @cindex PID 1 |
13421 | @cindex init system | |
a40424bd CM |
13422 | The @code{(gnu services shepherd)} module provides a way to define |
13423 | services managed by the GNU@tie{}Shepherd, which is the GuixSD | |
13424 | initialization system---the first process that is started when the | |
1068f26b AE |
13425 | system boots, also known as PID@tie{}1 |
13426 | (@pxref{Introduction,,, shepherd, The GNU Shepherd Manual}). | |
6f305ea5 | 13427 | |
dd17bc38 AK |
13428 | Services in the Shepherd can depend on each other. For instance, the |
13429 | SSH daemon may need to be started after the syslog daemon has been | |
13430 | started, which in turn can only happen once all the file systems have | |
13431 | been mounted. The simple operating system defined earlier (@pxref{Using | |
13432 | the Configuration System}) results in a service graph like this: | |
6f305ea5 | 13433 | |
710fa231 | 13434 | @image{images/shepherd-graph,,5in,Typical shepherd service graph.} |
6f305ea5 LC |
13435 | |
13436 | You can actually generate such a graph for any operating system | |
710fa231 AK |
13437 | definition using the @command{guix system shepherd-graph} command |
13438 | (@pxref{system-shepherd-graph, @command{guix system shepherd-graph}}). | |
6f305ea5 | 13439 | |
d4053c71 AK |
13440 | The @var{%shepherd-root-service} is a service object representing |
13441 | PID@tie{}1, of type @var{shepherd-root-service-type}; it can be extended | |
13442 | by passing it lists of @code{<shepherd-service>} objects. | |
0adfe95a | 13443 | |
d4053c71 | 13444 | @deftp {Data Type} shepherd-service |
dd17bc38 | 13445 | The data type representing a service managed by the Shepherd. |
0adfe95a LC |
13446 | |
13447 | @table @asis | |
13448 | @item @code{provision} | |
13449 | This is a list of symbols denoting what the service provides. | |
13450 | ||
dd17bc38 AK |
13451 | These are the names that may be passed to @command{herd start}, |
13452 | @command{herd status}, and similar commands (@pxref{Invoking herd,,, | |
13453 | shepherd, The GNU Shepherd Manual}). @xref{Slots of services, the | |
13454 | @code{provides} slot,, shepherd, The GNU Shepherd Manual}, for details. | |
0adfe95a LC |
13455 | |
13456 | @item @code{requirements} (default: @code{'()}) | |
dd17bc38 | 13457 | List of symbols denoting the Shepherd services this one depends on. |
0adfe95a LC |
13458 | |
13459 | @item @code{respawn?} (default: @code{#t}) | |
13460 | Whether to restart the service when it stops, for instance when the | |
13461 | underlying process dies. | |
13462 | ||
13463 | @item @code{start} | |
13464 | @itemx @code{stop} (default: @code{#~(const #f)}) | |
dd17bc38 AK |
13465 | The @code{start} and @code{stop} fields refer to the Shepherd's |
13466 | facilities to start and stop processes (@pxref{Service De- and | |
13467 | Constructors,,, shepherd, The GNU Shepherd Manual}). They are given as | |
13468 | G-expressions that get expanded in the Shepherd configuration file | |
13469 | (@pxref{G-Expressions}). | |
0adfe95a LC |
13470 | |
13471 | @item @code{documentation} | |
13472 | A documentation string, as shown when running: | |
13473 | ||
13474 | @example | |
dd17bc38 | 13475 | herd doc @var{service-name} |
0adfe95a LC |
13476 | @end example |
13477 | ||
13478 | where @var{service-name} is one of the symbols in @var{provision} | |
dd17bc38 | 13479 | (@pxref{Invoking herd,,, shepherd, The GNU Shepherd Manual}). |
fae685b9 LC |
13480 | |
13481 | @item @code{modules} (default: @var{%default-modules}) | |
13482 | This is the list of modules that must be in scope when @code{start} and | |
13483 | @code{stop} are evaluated. | |
13484 | ||
0adfe95a LC |
13485 | @end table |
13486 | @end deftp | |
13487 | ||
d4053c71 | 13488 | @defvr {Scheme Variable} shepherd-root-service-type |
dd17bc38 | 13489 | The service type for the Shepherd ``root service''---i.e., PID@tie{}1. |
0adfe95a LC |
13490 | |
13491 | This is the service type that extensions target when they want to create | |
dd17bc38 | 13492 | shepherd services (@pxref{Service Types and Services}, for an example). |
d4053c71 | 13493 | Each extension must pass a list of @code{<shepherd-service>}. |
0adfe95a LC |
13494 | @end defvr |
13495 | ||
d4053c71 | 13496 | @defvr {Scheme Variable} %shepherd-root-service |
0adfe95a LC |
13497 | This service represents PID@tie{}1. |
13498 | @end defvr | |
8451a568 | 13499 | |
8451a568 | 13500 | |
cf4a9129 LC |
13501 | @node Installing Debugging Files |
13502 | @section Installing Debugging Files | |
8451a568 | 13503 | |
cf4a9129 LC |
13504 | @cindex debugging files |
13505 | Program binaries, as produced by the GCC compilers for instance, are | |
13506 | typically written in the ELF format, with a section containing | |
13507 | @dfn{debugging information}. Debugging information is what allows the | |
13508 | debugger, GDB, to map binary code to source code; it is required to | |
13509 | debug a compiled program in good conditions. | |
8451a568 | 13510 | |
cf4a9129 LC |
13511 | The problem with debugging information is that is takes up a fair amount |
13512 | of disk space. For example, debugging information for the GNU C Library | |
13513 | weighs in at more than 60 MiB. Thus, as a user, keeping all the | |
13514 | debugging info of all the installed programs is usually not an option. | |
13515 | Yet, space savings should not come at the cost of an impediment to | |
13516 | debugging---especially in the GNU system, which should make it easier | |
13517 | for users to exert their computing freedom (@pxref{GNU Distribution}). | |
8451a568 | 13518 | |
cf4a9129 LC |
13519 | Thankfully, the GNU Binary Utilities (Binutils) and GDB provide a |
13520 | mechanism that allows users to get the best of both worlds: debugging | |
13521 | information can be stripped from the binaries and stored in separate | |
13522 | files. GDB is then able to load debugging information from those files, | |
13523 | when they are available (@pxref{Separate Debug Files,,, gdb, Debugging | |
13524 | with GDB}). | |
8451a568 | 13525 | |
cf4a9129 LC |
13526 | The GNU distribution takes advantage of this by storing debugging |
13527 | information in the @code{lib/debug} sub-directory of a separate package | |
13528 | output unimaginatively called @code{debug} (@pxref{Packages with | |
13529 | Multiple Outputs}). Users can choose to install the @code{debug} output | |
13530 | of a package when they need it. For instance, the following command | |
13531 | installs the debugging information for the GNU C Library and for GNU | |
13532 | Guile: | |
8451a568 LC |
13533 | |
13534 | @example | |
cf4a9129 | 13535 | guix package -i glibc:debug guile:debug |
8451a568 LC |
13536 | @end example |
13537 | ||
cf4a9129 LC |
13538 | GDB must then be told to look for debug files in the user's profile, by |
13539 | setting the @code{debug-file-directory} variable (consider setting it | |
13540 | from the @file{~/.gdbinit} file, @pxref{Startup,,, gdb, Debugging with | |
13541 | GDB}): | |
8451a568 | 13542 | |
cf4a9129 LC |
13543 | @example |
13544 | (gdb) set debug-file-directory ~/.guix-profile/lib/debug | |
13545 | @end example | |
8451a568 | 13546 | |
cf4a9129 LC |
13547 | From there on, GDB will pick up debugging information from the |
13548 | @code{.debug} files under @file{~/.guix-profile/lib/debug}. | |
8451a568 | 13549 | |
cf4a9129 LC |
13550 | In addition, you will most likely want GDB to be able to show the source |
13551 | code being debugged. To do that, you will have to unpack the source | |
13552 | code of the package of interest (obtained with @code{guix build | |
13553 | --source}, @pxref{Invoking guix build}), and to point GDB to that source | |
13554 | directory using the @code{directory} command (@pxref{Source Path, | |
13555 | @code{directory},, gdb, Debugging with GDB}). | |
8451a568 | 13556 | |
cf4a9129 LC |
13557 | @c XXX: keep me up-to-date |
13558 | The @code{debug} output mechanism in Guix is implemented by the | |
13559 | @code{gnu-build-system} (@pxref{Build Systems}). Currently, it is | |
1068f26b AE |
13560 | opt-in---debugging information is available only for the packages |
13561 | with definitions explicitly declaring a @code{debug} output. This may be | |
13562 | changed to opt-out in the future if our build farm servers can handle | |
cf4a9129 LC |
13563 | the load. To check whether a package has a @code{debug} output, use |
13564 | @command{guix package --list-available} (@pxref{Invoking guix package}). | |
8451a568 | 13565 | |
8451a568 | 13566 | |
05962f29 LC |
13567 | @node Security Updates |
13568 | @section Security Updates | |
13569 | ||
09866b39 LC |
13570 | @cindex security updates |
13571 | @cindex security vulnerabilities | |
13572 | Occasionally, important security vulnerabilities are discovered in software | |
13573 | packages and must be patched. Guix developers try hard to keep track of | |
13574 | known vulnerabilities and to apply fixes as soon as possible in the | |
13575 | @code{master} branch of Guix (we do not yet provide a ``stable'' branch | |
13576 | containing only security updates.) The @command{guix lint} tool helps | |
13577 | developers find out about vulnerable versions of software packages in the | |
13578 | distribution: | |
13579 | ||
13580 | @smallexample | |
13581 | $ guix lint -c cve | |
13582 | gnu/packages/base.scm:652:2: glibc-2.21: probably vulnerable to CVE-2015-1781, CVE-2015-7547 | |
13583 | gnu/packages/gcc.scm:334:2: gcc-4.9.3: probably vulnerable to CVE-2015-5276 | |
13584 | gnu/packages/image.scm:312:2: openjpeg-2.1.0: probably vulnerable to CVE-2016-1923, CVE-2016-1924 | |
13585 | @dots{} | |
13586 | @end smallexample | |
13587 | ||
13588 | @xref{Invoking guix lint}, for more information. | |
13589 | ||
843858b8 | 13590 | @quotation Note |
09866b39 LC |
13591 | As of version @value{VERSION}, the feature described below is considered |
13592 | ``beta''. | |
843858b8 | 13593 | @end quotation |
05962f29 | 13594 | |
09866b39 | 13595 | Guix follows a functional |
05962f29 LC |
13596 | package management discipline (@pxref{Introduction}), which implies |
13597 | that, when a package is changed, @emph{every package that depends on it} | |
13598 | must be rebuilt. This can significantly slow down the deployment of | |
13599 | fixes in core packages such as libc or Bash, since basically the whole | |
13600 | distribution would need to be rebuilt. Using pre-built binaries helps | |
13601 | (@pxref{Substitutes}), but deployment may still take more time than | |
13602 | desired. | |
13603 | ||
13604 | @cindex grafts | |
1068f26b | 13605 | To address this, Guix implements @dfn{grafts}, a mechanism that allows |
05962f29 LC |
13606 | for fast deployment of critical updates without the costs associated |
13607 | with a whole-distribution rebuild. The idea is to rebuild only the | |
13608 | package that needs to be patched, and then to ``graft'' it onto packages | |
13609 | explicitly installed by the user and that were previously referring to | |
13610 | the original package. The cost of grafting is typically very low, and | |
13611 | order of magnitudes lower than a full rebuild of the dependency chain. | |
13612 | ||
13613 | @cindex replacements of packages, for grafts | |
13614 | For instance, suppose a security update needs to be applied to Bash. | |
13615 | Guix developers will provide a package definition for the ``fixed'' | |
13616 | Bash, say @var{bash-fixed}, in the usual way (@pxref{Defining | |
13617 | Packages}). Then, the original package definition is augmented with a | |
13618 | @code{replacement} field pointing to the package containing the bug fix: | |
13619 | ||
13620 | @example | |
13621 | (define bash | |
13622 | (package | |
13623 | (name "bash") | |
13624 | ;; @dots{} | |
13625 | (replacement bash-fixed))) | |
13626 | @end example | |
13627 | ||
c22a1324 LC |
13628 | From there on, any package depending directly or indirectly on Bash---as |
13629 | reported by @command{guix gc --requisites} (@pxref{Invoking guix | |
13630 | gc})---that is installed is automatically ``rewritten'' to refer to | |
05962f29 | 13631 | @var{bash-fixed} instead of @var{bash}. This grafting process takes |
1068f26b | 13632 | time proportional to the size of the package, usually less than a |
c22a1324 LC |
13633 | minute for an ``average'' package on a recent machine. Grafting is |
13634 | recursive: when an indirect dependency requires grafting, then grafting | |
13635 | ``propagates'' up to the package that the user is installing. | |
05962f29 | 13636 | |
57bdd79e LC |
13637 | Currently, the length of the name and version of the graft and that of |
13638 | the package it replaces (@var{bash-fixed} and @var{bash} in the example | |
13639 | above) must be equal. This restriction mostly comes from the fact that | |
13640 | grafting works by patching files, including binary files, directly. | |
05962f29 LC |
13641 | Other restrictions may apply: for instance, when adding a graft to a |
13642 | package providing a shared library, the original shared library and its | |
13643 | replacement must have the same @code{SONAME} and be binary-compatible. | |
13644 | ||
59a4dd50 LC |
13645 | The @option{--no-grafts} command-line option allows you to forcefully |
13646 | avoid grafting (@pxref{Common Build Options, @option{--no-grafts}}). | |
13647 | Thus, the command: | |
13648 | ||
13649 | @example | |
13650 | guix build bash --no-grafts | |
13651 | @end example | |
13652 | ||
13653 | @noindent | |
13654 | returns the store file name of the original Bash, whereas: | |
13655 | ||
13656 | @example | |
13657 | guix build bash | |
13658 | @end example | |
13659 | ||
13660 | @noindent | |
13661 | returns the store file name of the ``fixed'', replacement Bash. This | |
13662 | allows you to distinguish between the two variants of Bash. | |
13663 | ||
13664 | To verify which Bash your whole profile refers to, you can run | |
13665 | (@pxref{Invoking guix gc}): | |
13666 | ||
13667 | @example | |
13668 | guix gc -R `readlink -f ~/.guix-profile` | grep bash | |
13669 | @end example | |
13670 | ||
13671 | @noindent | |
13672 | @dots{} and compare the store file names that you get with those above. | |
13673 | Likewise for a complete GuixSD system generation: | |
13674 | ||
13675 | @example | |
13676 | guix gc -R `guix system build my-config.scm` | grep bash | |
13677 | @end example | |
13678 | ||
13679 | Lastly, to check which Bash running processes are using, you can use the | |
13680 | @command{lsof} command: | |
13681 | ||
13682 | @example | |
13683 | lsof | grep /gnu/store/.*bash | |
13684 | @end example | |
13685 | ||
05962f29 | 13686 | |
cf4a9129 LC |
13687 | @node Package Modules |
13688 | @section Package Modules | |
8451a568 | 13689 | |
cf4a9129 LC |
13690 | From a programming viewpoint, the package definitions of the |
13691 | GNU distribution are provided by Guile modules in the @code{(gnu packages | |
13692 | @dots{})} name space@footnote{Note that packages under the @code{(gnu | |
13693 | packages @dots{})} module name space are not necessarily ``GNU | |
13694 | packages''. This module naming scheme follows the usual Guile module | |
13695 | naming convention: @code{gnu} means that these modules are distributed | |
13696 | as part of the GNU system, and @code{packages} identifies modules that | |
13697 | define packages.} (@pxref{Modules, Guile modules,, guile, GNU Guile | |
13698 | Reference Manual}). For instance, the @code{(gnu packages emacs)} | |
13699 | module exports a variable named @code{emacs}, which is bound to a | |
13700 | @code{<package>} object (@pxref{Defining Packages}). | |
113daf62 | 13701 | |
300868ba | 13702 | The @code{(gnu packages @dots{})} module name space is |
cf4a9129 LC |
13703 | automatically scanned for packages by the command-line tools. For |
13704 | instance, when running @code{guix package -i emacs}, all the @code{(gnu | |
13705 | packages @dots{})} modules are scanned until one that exports a package | |
13706 | object whose name is @code{emacs} is found. This package search | |
13707 | facility is implemented in the @code{(gnu packages)} module. | |
113daf62 | 13708 | |
300868ba | 13709 | @cindex customization, of packages |
8689901f | 13710 | @cindex package module search path |
cf4a9129 | 13711 | Users can store package definitions in modules with different |
60142854 | 13712 | names---e.g., @code{(my-packages emacs)}@footnote{Note that the file |
c95ded7e LC |
13713 | name and module name must match. For instance, the @code{(my-packages |
13714 | emacs)} module must be stored in a @file{my-packages/emacs.scm} file | |
13715 | relative to the load path specified with @option{--load-path} or | |
13716 | @code{GUIX_PACKAGE_PATH}. @xref{Modules and the File System,,, | |
13717 | guile, GNU Guile Reference Manual}, for details.}. These package definitions | |
1068f26b AE |
13718 | will not be visible by default. Users can invoke commands such as |
13719 | @command{guix package} and @command{guix build} with the | |
c95ded7e LC |
13720 | @code{-e} option so that they know where to find the package. Better |
13721 | yet, they can use the | |
300868ba | 13722 | @code{-L} option of these commands to make those modules visible |
8689901f LC |
13723 | (@pxref{Invoking guix build, @code{--load-path}}), or define the |
13724 | @code{GUIX_PACKAGE_PATH} environment variable. This environment | |
13725 | variable makes it easy to extend or customize the distribution and is | |
13726 | honored by all the user interfaces. | |
13727 | ||
13728 | @defvr {Environment Variable} GUIX_PACKAGE_PATH | |
1068f26b AE |
13729 | This is a colon-separated list of directories to search for additional |
13730 | package modules. Directories listed in this variable take precedence | |
13731 | over the own modules of the distribution. | |
8689901f | 13732 | @end defvr |
ef5dd60a | 13733 | |
cf4a9129 LC |
13734 | The distribution is fully @dfn{bootstrapped} and @dfn{self-contained}: |
13735 | each package is built based solely on other packages in the | |
13736 | distribution. The root of this dependency graph is a small set of | |
13737 | @dfn{bootstrap binaries}, provided by the @code{(gnu packages | |
13738 | bootstrap)} module. For more information on bootstrapping, | |
081145cf | 13739 | @pxref{Bootstrapping}. |
ef5dd60a | 13740 | |
cf4a9129 LC |
13741 | @node Packaging Guidelines |
13742 | @section Packaging Guidelines | |
ef5dd60a | 13743 | |
e32171ee | 13744 | @cindex packages, creating |
cf4a9129 LC |
13745 | The GNU distribution is nascent and may well lack some of your favorite |
13746 | packages. This section describes how you can help make the distribution | |
13747 | grow. @xref{Contributing}, for additional information on how you can | |
13748 | help. | |
ef5dd60a | 13749 | |
cf4a9129 LC |
13750 | Free software packages are usually distributed in the form of |
13751 | @dfn{source code tarballs}---typically @file{tar.gz} files that contain | |
13752 | all the source files. Adding a package to the distribution means | |
13753 | essentially two things: adding a @dfn{recipe} that describes how to | |
13754 | build the package, including a list of other packages required to build | |
f97c9175 | 13755 | it, and adding @dfn{package metadata} along with that recipe, such as a |
cf4a9129 | 13756 | description and licensing information. |
ef5dd60a | 13757 | |
cf4a9129 LC |
13758 | In Guix all this information is embodied in @dfn{package definitions}. |
13759 | Package definitions provide a high-level view of the package. They are | |
13760 | written using the syntax of the Scheme programming language; in fact, | |
13761 | for each package we define a variable bound to the package definition, | |
13762 | and export that variable from a module (@pxref{Package Modules}). | |
13763 | However, in-depth Scheme knowledge is @emph{not} a prerequisite for | |
13764 | creating packages. For more information on package definitions, | |
081145cf | 13765 | @pxref{Defining Packages}. |
ef5dd60a | 13766 | |
cf4a9129 LC |
13767 | Once a package definition is in place, stored in a file in the Guix |
13768 | source tree, it can be tested using the @command{guix build} command | |
13769 | (@pxref{Invoking guix build}). For example, assuming the new package is | |
c71979f4 LC |
13770 | called @code{gnew}, you may run this command from the Guix build tree |
13771 | (@pxref{Running Guix Before It Is Installed}): | |
ef5dd60a LC |
13772 | |
13773 | @example | |
cf4a9129 | 13774 | ./pre-inst-env guix build gnew --keep-failed |
ef5dd60a | 13775 | @end example |
ef5dd60a | 13776 | |
cf4a9129 LC |
13777 | Using @code{--keep-failed} makes it easier to debug build failures since |
13778 | it provides access to the failed build tree. Another useful | |
13779 | command-line option when debugging is @code{--log-file}, to access the | |
13780 | build log. | |
ef5dd60a | 13781 | |
cf4a9129 LC |
13782 | If the package is unknown to the @command{guix} command, it may be that |
13783 | the source file contains a syntax error, or lacks a @code{define-public} | |
13784 | clause to export the package variable. To figure it out, you may load | |
13785 | the module from Guile to get more information about the actual error: | |
ef5dd60a | 13786 | |
cf4a9129 LC |
13787 | @example |
13788 | ./pre-inst-env guile -c '(use-modules (gnu packages gnew))' | |
13789 | @end example | |
ef5dd60a | 13790 | |
cf4a9129 LC |
13791 | Once your package builds correctly, please send us a patch |
13792 | (@pxref{Contributing}). Well, if you need help, we will be happy to | |
13793 | help you too. Once the patch is committed in the Guix repository, the | |
13794 | new package automatically gets built on the supported platforms by | |
2b1cee21 | 13795 | @url{http://hydra.gnu.org/jobset/gnu/master, our continuous integration |
cf4a9129 | 13796 | system}. |
ef5dd60a | 13797 | |
cf4a9129 LC |
13798 | @cindex substituter |
13799 | Users can obtain the new package definition simply by running | |
13800 | @command{guix pull} (@pxref{Invoking guix pull}). When | |
13801 | @code{hydra.gnu.org} is done building the package, installing the | |
13802 | package automatically downloads binaries from there | |
13803 | (@pxref{Substitutes}). The only place where human intervention is | |
13804 | needed is to review and apply the patch. | |
ef5dd60a | 13805 | |
ef5dd60a | 13806 | |
cf4a9129 | 13807 | @menu |
ec0339cd LC |
13808 | * Software Freedom:: What may go into the distribution. |
13809 | * Package Naming:: What's in a name? | |
13810 | * Version Numbers:: When the name is not enough. | |
cbd02397 | 13811 | * Synopses and Descriptions:: Helping users find the right package. |
ec0339cd LC |
13812 | * Python Modules:: Taming the snake. |
13813 | * Perl Modules:: Little pearls. | |
e1c963bf | 13814 | * Java Packages:: Coffee break. |
ec0339cd | 13815 | * Fonts:: Fond of fonts. |
cf4a9129 | 13816 | @end menu |
ef5dd60a | 13817 | |
cf4a9129 LC |
13818 | @node Software Freedom |
13819 | @subsection Software Freedom | |
ef5dd60a | 13820 | |
cf4a9129 | 13821 | @c Adapted from http://www.gnu.org/philosophy/philosophy.html. |
e32171ee | 13822 | @cindex free software |
cf4a9129 LC |
13823 | The GNU operating system has been developed so that users can have |
13824 | freedom in their computing. GNU is @dfn{free software}, meaning that | |
13825 | users have the @url{http://www.gnu.org/philosophy/free-sw.html,four | |
13826 | essential freedoms}: to run the program, to study and change the program | |
13827 | in source code form, to redistribute exact copies, and to distribute | |
13828 | modified versions. Packages found in the GNU distribution provide only | |
13829 | software that conveys these four freedoms. | |
c11a6eb1 | 13830 | |
cf4a9129 LC |
13831 | In addition, the GNU distribution follow the |
13832 | @url{http://www.gnu.org/distros/free-system-distribution-guidelines.html,free | |
13833 | software distribution guidelines}. Among other things, these guidelines | |
13834 | reject non-free firmware, recommendations of non-free software, and | |
13835 | discuss ways to deal with trademarks and patents. | |
ef5dd60a | 13836 | |
1068f26b AE |
13837 | Some otherwise free upstream package sources contain a small and optional |
13838 | subset that violates the above guidelines, for instance because this subset | |
13839 | is itself non-free code. When that happens, the offending items are removed | |
13840 | with appropriate patches or code snippets in the @code{origin} form of the | |
13841 | package (@pxref{Defining Packages}). This way, @code{guix | |
cf4a9129 LC |
13842 | build --source} returns the ``freed'' source rather than the unmodified |
13843 | upstream source. | |
ef5dd60a | 13844 | |
ef5dd60a | 13845 | |
cf4a9129 LC |
13846 | @node Package Naming |
13847 | @subsection Package Naming | |
ef5dd60a | 13848 | |
e32171ee | 13849 | @cindex package name |
cf4a9129 LC |
13850 | A package has actually two names associated with it: |
13851 | First, there is the name of the @emph{Scheme variable}, the one following | |
13852 | @code{define-public}. By this name, the package can be made known in the | |
13853 | Scheme code, for instance as input to another package. Second, there is | |
13854 | the string in the @code{name} field of a package definition. This name | |
13855 | is used by package management commands such as | |
13856 | @command{guix package} and @command{guix build}. | |
ef5dd60a | 13857 | |
cf4a9129 LC |
13858 | Both are usually the same and correspond to the lowercase conversion of |
13859 | the project name chosen upstream, with underscores replaced with | |
13860 | hyphens. For instance, GNUnet is available as @code{gnunet}, and | |
13861 | SDL_net as @code{sdl-net}. | |
927097ef | 13862 | |
cf4a9129 | 13863 | We do not add @code{lib} prefixes for library packages, unless these are |
081145cf | 13864 | already part of the official project name. But @pxref{Python |
cf4a9129 LC |
13865 | Modules} and @ref{Perl Modules} for special rules concerning modules for |
13866 | the Python and Perl languages. | |
927097ef | 13867 | |
1b366ee4 | 13868 | Font package names are handled differently, @pxref{Fonts}. |
7fec52b7 | 13869 | |
ef5dd60a | 13870 | |
cf4a9129 LC |
13871 | @node Version Numbers |
13872 | @subsection Version Numbers | |
ef5dd60a | 13873 | |
e32171ee | 13874 | @cindex package version |
cf4a9129 LC |
13875 | We usually package only the latest version of a given free software |
13876 | project. But sometimes, for instance for incompatible library versions, | |
13877 | two (or more) versions of the same package are needed. These require | |
13878 | different Scheme variable names. We use the name as defined | |
13879 | in @ref{Package Naming} | |
13880 | for the most recent version; previous versions use the same name, suffixed | |
13881 | by @code{-} and the smallest prefix of the version number that may | |
13882 | distinguish the two versions. | |
ef5dd60a | 13883 | |
cf4a9129 LC |
13884 | The name inside the package definition is the same for all versions of a |
13885 | package and does not contain any version number. | |
ef5dd60a | 13886 | |
cf4a9129 | 13887 | For instance, the versions 2.24.20 and 3.9.12 of GTK+ may be packaged as follows: |
ef5dd60a | 13888 | |
cf4a9129 LC |
13889 | @example |
13890 | (define-public gtk+ | |
13891 | (package | |
17d8e33f ML |
13892 | (name "gtk+") |
13893 | (version "3.9.12") | |
13894 | ...)) | |
cf4a9129 LC |
13895 | (define-public gtk+-2 |
13896 | (package | |
17d8e33f ML |
13897 | (name "gtk+") |
13898 | (version "2.24.20") | |
13899 | ...)) | |
cf4a9129 LC |
13900 | @end example |
13901 | If we also wanted GTK+ 3.8.2, this would be packaged as | |
13902 | @example | |
13903 | (define-public gtk+-3.8 | |
13904 | (package | |
17d8e33f ML |
13905 | (name "gtk+") |
13906 | (version "3.8.2") | |
13907 | ...)) | |
cf4a9129 | 13908 | @end example |
ef5dd60a | 13909 | |
880d647d LC |
13910 | @c See <https://lists.gnu.org/archive/html/guix-devel/2016-01/msg00425.html>, |
13911 | @c for a discussion of what follows. | |
13912 | @cindex version number, for VCS snapshots | |
13913 | Occasionally, we package snapshots of upstream's version control system | |
13914 | (VCS) instead of formal releases. This should remain exceptional, | |
13915 | because it is up to upstream developers to clarify what the stable | |
13916 | release is. Yet, it is sometimes necessary. So, what should we put in | |
13917 | the @code{version} field? | |
13918 | ||
13919 | Clearly, we need to make the commit identifier of the VCS snapshot | |
13920 | visible in the version string, but we also need to make sure that the | |
13921 | version string is monotonically increasing so that @command{guix package | |
13922 | --upgrade} can determine which version is newer. Since commit | |
13923 | identifiers, notably with Git, are not monotonically increasing, we add | |
13924 | a revision number that we increase each time we upgrade to a newer | |
13925 | snapshot. The resulting version string looks like this: | |
13926 | ||
13927 | @example | |
13928 | 2.0.11-3.cabba9e | |
13929 | ^ ^ ^ | |
13930 | | | `-- upstream commit ID | |
13931 | | | | |
13932 | | `--- Guix package revision | |
13933 | | | |
13934 | latest upstream version | |
13935 | @end example | |
13936 | ||
13937 | It is a good idea to strip commit identifiers in the @code{version} | |
13938 | field to, say, 7 digits. It avoids an aesthetic annoyance (assuming | |
13939 | aesthetics have a role to play here) as well as problems related to OS | |
13940 | limits such as the maximum shebang length (127 bytes for the Linux | |
13941 | kernel.) It is best to use the full commit identifiers in | |
561360a5 LC |
13942 | @code{origin}s, though, to avoid ambiguities. A typical package |
13943 | definition may look like this: | |
13944 | ||
13945 | @example | |
13946 | (define my-package | |
6e42660b | 13947 | (let ((commit "c3f29bc928d5900971f65965feaae59e1272a3f7") |
13948 | (revision "1")) ;Guix package revision | |
561360a5 | 13949 | (package |
6e42660b | 13950 | (version (string-append "0.9-" revision "." |
561360a5 LC |
13951 | (string-take commit 7))) |
13952 | (source (origin | |
13953 | (method git-fetch) | |
13954 | (uri (git-reference | |
13955 | (url "git://example.org/my-package.git") | |
13956 | (commit commit))) | |
13957 | (sha256 (base32 "1mbikn@dots{}")) | |
13958 | (file-name (string-append "my-package-" version | |
13959 | "-checkout")))) | |
13960 | ;; @dots{} | |
13961 | ))) | |
13962 | @end example | |
880d647d | 13963 | |
cbd02397 LC |
13964 | @node Synopses and Descriptions |
13965 | @subsection Synopses and Descriptions | |
13966 | ||
e32171ee JD |
13967 | @cindex package description |
13968 | @cindex package synopsis | |
cbd02397 LC |
13969 | As we have seen before, each package in GNU@tie{}Guix includes a |
13970 | synopsis and a description (@pxref{Defining Packages}). Synopses and | |
13971 | descriptions are important: They are what @command{guix package | |
13972 | --search} searches, and a crucial piece of information to help users | |
13973 | determine whether a given package suits their needs. Consequently, | |
13974 | packagers should pay attention to what goes into them. | |
13975 | ||
13976 | Synopses must start with a capital letter and must not end with a | |
13977 | period. They must not start with ``a'' or ``the'', which usually does | |
13978 | not bring anything; for instance, prefer ``File-frobbing tool'' over ``A | |
13979 | tool that frobs files''. The synopsis should say what the package | |
13980 | is---e.g., ``Core GNU utilities (file, text, shell)''---or what it is | |
13981 | used for---e.g., the synopsis for GNU@tie{}grep is ``Print lines | |
13982 | matching a pattern''. | |
13983 | ||
13984 | Keep in mind that the synopsis must be meaningful for a very wide | |
13985 | audience. For example, ``Manipulate alignments in the SAM format'' | |
13986 | might make sense for a seasoned bioinformatics researcher, but might be | |
13987 | fairly unhelpful or even misleading to a non-specialized audience. It | |
13988 | is a good idea to come up with a synopsis that gives an idea of the | |
13989 | application domain of the package. In this example, this might give | |
13990 | something like ``Manipulate nucleotide sequence alignments'', which | |
13991 | hopefully gives the user a better idea of whether this is what they are | |
13992 | looking for. | |
13993 | ||
cbd02397 LC |
13994 | Descriptions should take between five and ten lines. Use full |
13995 | sentences, and avoid using acronyms without first introducing them. | |
762e54b7 LC |
13996 | Please avoid marketing phrases such as ``world-leading'', |
13997 | ``industrial-strength'', and ``next-generation'', and avoid superlatives | |
13998 | like ``the most advanced''---they are not helpful to users looking for a | |
13999 | package and may even sound suspicious. Instead, try to be factual, | |
14000 | mentioning use cases and features. | |
14001 | ||
14002 | @cindex Texinfo markup, in package descriptions | |
cbd02397 LC |
14003 | Descriptions can include Texinfo markup, which is useful to introduce |
14004 | ornaments such as @code{@@code} or @code{@@dfn}, bullet lists, or | |
ba7d6c76 ML |
14005 | hyperlinks (@pxref{Overview,,, texinfo, GNU Texinfo}). However you |
14006 | should be careful when using some characters for example @samp{@@} and | |
14007 | curly braces which are the basic special characters in Texinfo | |
14008 | (@pxref{Special Characters,,, texinfo, GNU Texinfo}). User interfaces | |
14009 | such as @command{guix package --show} take care of rendering it | |
14010 | appropriately. | |
cbd02397 LC |
14011 | |
14012 | Synopses and descriptions are translated by volunteers | |
14013 | @uref{http://translationproject.org/domain/guix-packages.html, at the | |
14014 | Translation Project} so that as many users as possible can read them in | |
14015 | their native language. User interfaces search them and display them in | |
14016 | the language specified by the current locale. | |
14017 | ||
14018 | Translation is a lot of work so, as a packager, please pay even more | |
14019 | attention to your synopses and descriptions as every change may entail | |
ba7d6c76 | 14020 | additional work for translators. In order to help them, it is possible |
36743e71 | 14021 | to make recommendations or instructions visible to them by inserting |
ba7d6c76 ML |
14022 | special comments like this (@pxref{xgettext Invocation,,, gettext, GNU |
14023 | Gettext}): | |
14024 | ||
14025 | @example | |
14026 | ;; TRANSLATORS: "X11 resize-and-rotate" should not be translated. | |
14027 | (description "ARandR is designed to provide a simple visual front end | |
14028 | for the X11 resize-and-rotate (RandR) extension. @dots{}") | |
14029 | @end example | |
cbd02397 | 14030 | |
ef5dd60a | 14031 | |
cf4a9129 LC |
14032 | @node Python Modules |
14033 | @subsection Python Modules | |
ef5dd60a | 14034 | |
e32171ee | 14035 | @cindex python |
cf4a9129 LC |
14036 | We currently package Python 2 and Python 3, under the Scheme variable names |
14037 | @code{python-2} and @code{python} as explained in @ref{Version Numbers}. | |
14038 | To avoid confusion and naming clashes with other programming languages, it | |
14039 | seems desirable that the name of a package for a Python module contains | |
14040 | the word @code{python}. | |
ef5dd60a | 14041 | |
cf4a9129 LC |
14042 | Some modules are compatible with only one version of Python, others with both. |
14043 | If the package Foo compiles only with Python 3, we name it | |
14044 | @code{python-foo}; if it compiles only with Python 2, we name it | |
14045 | @code{python2-foo}. If it is compatible with both versions, we create two | |
14046 | packages with the corresponding names. | |
ef5dd60a | 14047 | |
cf4a9129 LC |
14048 | If a project already contains the word @code{python}, we drop this; |
14049 | for instance, the module python-dateutil is packaged under the names | |
99c866a0 HG |
14050 | @code{python-dateutil} and @code{python2-dateutil}. If the project name |
14051 | starts with @code{py} (e.g. @code{pytz}), we keep it and prefix it as | |
14052 | described above. | |
113daf62 | 14053 | |
e940a271 HG |
14054 | @subsubsection Specifying Dependencies |
14055 | @cindex inputs, for Python packages | |
14056 | ||
14057 | Dependency information for Python packages is usually available in the | |
14058 | package source tree, with varying degrees of accuracy: in the | |
14059 | @file{setup.py} file, in @file{requirements.txt}, or in @file{tox.ini}. | |
14060 | ||
14061 | Your mission, when writing a recipe for a Python package, is to map | |
14062 | these dependencies to the appropriate type of ``input'' (@pxref{package | |
14063 | Reference, inputs}). Although the @code{pypi} importer normally does a | |
14064 | good job (@pxref{Invoking guix import}), you may want to check the | |
14065 | following check list to determine which dependency goes where. | |
14066 | ||
14067 | @itemize | |
14068 | ||
aaf75c89 HG |
14069 | @item |
14070 | We currently package Python 2 with @code{setuptools} and @code{pip} | |
14071 | installed like Python 3.4 has per default. Thus you don't need to | |
891a843d HG |
14072 | specify either of these as an input. @command{guix lint} will warn you |
14073 | if you do. | |
aaf75c89 | 14074 | |
e940a271 HG |
14075 | @item |
14076 | Python dependencies required at run time go into | |
14077 | @code{propagated-inputs}. They are typically defined with the | |
14078 | @code{install_requires} keyword in @file{setup.py}, or in the | |
14079 | @file{requirements.txt} file. | |
14080 | ||
14081 | @item | |
14082 | Python packages required only at build time---e.g., those listed with | |
14083 | the @code{setup_requires} keyword in @file{setup.py}---or only for | |
14084 | testing---e.g., those in @code{tests_require}---go into | |
14085 | @code{native-inputs}. The rationale is that (1) they do not need to be | |
14086 | propagated because they are not needed at run time, and (2) in a | |
14087 | cross-compilation context, it's the ``native'' input that we'd want. | |
14088 | ||
aaf75c89 | 14089 | Examples are the @code{pytest}, @code{mock}, and @code{nose} test |
e940a271 HG |
14090 | frameworks. Of course if any of these packages is also required at |
14091 | run-time, it needs to go to @code{propagated-inputs}. | |
14092 | ||
14093 | @item | |
14094 | Anything that does not fall in the previous categories goes to | |
14095 | @code{inputs}, for example programs or C libraries required for building | |
14096 | Python packages containing C extensions. | |
14097 | ||
14098 | @item | |
14099 | If a Python package has optional dependencies (@code{extras_require}), | |
14100 | it is up to you to decide whether to add them or not, based on their | |
14101 | usefulness/overhead ratio (@pxref{Submitting Patches, @command{guix | |
14102 | size}}). | |
14103 | ||
14104 | @end itemize | |
14105 | ||
14106 | ||
cf4a9129 LC |
14107 | @node Perl Modules |
14108 | @subsection Perl Modules | |
523e4896 | 14109 | |
e32171ee | 14110 | @cindex perl |
cf4a9129 LC |
14111 | Perl programs standing for themselves are named as any other package, |
14112 | using the lowercase upstream name. | |
14113 | For Perl packages containing a single class, we use the lowercase class name, | |
14114 | replace all occurrences of @code{::} by dashes and prepend the prefix | |
14115 | @code{perl-}. | |
14116 | So the class @code{XML::Parser} becomes @code{perl-xml-parser}. | |
14117 | Modules containing several classes keep their lowercase upstream name and | |
14118 | are also prepended by @code{perl-}. Such modules tend to have the word | |
14119 | @code{perl} somewhere in their name, which gets dropped in favor of the | |
14120 | prefix. For instance, @code{libwww-perl} becomes @code{perl-libwww}. | |
523e4896 | 14121 | |
523e4896 | 14122 | |
e1c963bf HG |
14123 | @node Java Packages |
14124 | @subsection Java Packages | |
14125 | ||
e32171ee | 14126 | @cindex java |
e1c963bf HG |
14127 | Java programs standing for themselves are named as any other package, |
14128 | using the lowercase upstream name. | |
14129 | ||
14130 | To avoid confusion and naming clashes with other programming languages, | |
14131 | it is desirable that the name of a package for a Java package is | |
14132 | prefixed with @code{java-}. If a project already contains the word | |
14133 | @code{java}, we drop this; for instance, the package @code{ngsjava} is | |
14134 | packaged under the name @code{java-ngs}. | |
14135 | ||
14136 | For Java packages containing a single class or a small class hierarchy, | |
14137 | we use the lowercase class name, replace all occurrences of @code{.} by | |
14138 | dashes and prepend the prefix @code{java-}. So the class | |
14139 | @code{apache.commons.cli} becomes package | |
14140 | @code{java-apache-commons-cli}. | |
14141 | ||
14142 | ||
7fec52b7 AE |
14143 | @node Fonts |
14144 | @subsection Fonts | |
14145 | ||
e32171ee | 14146 | @cindex fonts |
7fec52b7 AE |
14147 | For fonts that are in general not installed by a user for typesetting |
14148 | purposes, or that are distributed as part of a larger software package, | |
14149 | we rely on the general packaging rules for software; for instance, this | |
14150 | applies to the fonts delivered as part of the X.Org system or fonts that | |
14151 | are part of TeX Live. | |
14152 | ||
14153 | To make it easier for a user to search for fonts, names for other packages | |
14154 | containing only fonts are constructed as follows, independently of the | |
14155 | upstream package name. | |
14156 | ||
14157 | The name of a package containing only one font family starts with | |
14158 | @code{font-}; it is followed by the foundry name and a dash @code{-} | |
14159 | if the foundry is known, and the font family name, in which spaces are | |
14160 | replaced by dashes (and as usual, all upper case letters are transformed | |
14161 | to lower case). | |
14162 | For example, the Gentium font family by SIL is packaged under the name | |
14163 | @code{font-sil-gentium}. | |
14164 | ||
14165 | For a package containing several font families, the name of the collection | |
14166 | is used in the place of the font family name. | |
14167 | For instance, the Liberation fonts consist of three families, | |
14168 | Liberation Sans, Liberation Serif and Liberation Mono. | |
14169 | These could be packaged separately under the names | |
14170 | @code{font-liberation-sans} and so on; but as they are distributed together | |
14171 | under a common name, we prefer to package them together as | |
14172 | @code{font-liberation}. | |
14173 | ||
14174 | In the case where several formats of the same font family or font collection | |
14175 | are packaged separately, a short form of the format, prepended by a dash, | |
14176 | is added to the package name. We use @code{-ttf} for TrueType fonts, | |
1b366ee4 | 14177 | @code{-otf} for OpenType fonts and @code{-type1} for PostScript Type 1 |
7fec52b7 AE |
14178 | fonts. |
14179 | ||
14180 | ||
b25937e3 | 14181 | |
cf4a9129 LC |
14182 | @node Bootstrapping |
14183 | @section Bootstrapping | |
b25937e3 | 14184 | |
cf4a9129 | 14185 | @c Adapted from the ELS 2013 paper. |
b25937e3 | 14186 | |
cf4a9129 | 14187 | @cindex bootstrapping |
7889394e | 14188 | |
cf4a9129 LC |
14189 | Bootstrapping in our context refers to how the distribution gets built |
14190 | ``from nothing''. Remember that the build environment of a derivation | |
14191 | contains nothing but its declared inputs (@pxref{Introduction}). So | |
14192 | there's an obvious chicken-and-egg problem: how does the first package | |
14193 | get built? How does the first compiler get compiled? Note that this is | |
14194 | a question of interest only to the curious hacker, not to the regular | |
14195 | user, so you can shamelessly skip this section if you consider yourself | |
14196 | a ``regular user''. | |
72b9d60d | 14197 | |
cf4a9129 LC |
14198 | @cindex bootstrap binaries |
14199 | The GNU system is primarily made of C code, with libc at its core. The | |
14200 | GNU build system itself assumes the availability of a Bourne shell and | |
14201 | command-line tools provided by GNU Coreutils, Awk, Findutils, `sed', and | |
14202 | `grep'. Furthermore, build programs---programs that run | |
14203 | @code{./configure}, @code{make}, etc.---are written in Guile Scheme | |
14204 | (@pxref{Derivations}). Consequently, to be able to build anything at | |
14205 | all, from scratch, Guix relies on pre-built binaries of Guile, GCC, | |
14206 | Binutils, libc, and the other packages mentioned above---the | |
14207 | @dfn{bootstrap binaries}. | |
72b9d60d | 14208 | |
cf4a9129 LC |
14209 | These bootstrap binaries are ``taken for granted'', though we can also |
14210 | re-create them if needed (more on that later). | |
72b9d60d | 14211 | |
cf4a9129 | 14212 | @unnumberedsubsec Preparing to Use the Bootstrap Binaries |
c79d54fe | 14213 | |
cf4a9129 LC |
14214 | @c As of Emacs 24.3, Info-mode displays the image, but since it's a |
14215 | @c large image, it's hard to scroll. Oh well. | |
14216 | @image{images/bootstrap-graph,6in,,Dependency graph of the early bootstrap derivations} | |
523e4896 | 14217 | |
cf4a9129 LC |
14218 | The figure above shows the very beginning of the dependency graph of the |
14219 | distribution, corresponding to the package definitions of the @code{(gnu | |
d33fa0c7 LC |
14220 | packages bootstrap)} module. A similar figure can be generated with |
14221 | @command{guix graph} (@pxref{Invoking guix graph}), along the lines of: | |
14222 | ||
14223 | @example | |
14224 | guix graph -t derivation \ | |
14225 | -e '(@@@@ (gnu packages bootstrap) %bootstrap-gcc)' \ | |
14226 | | dot -Tps > t.ps | |
14227 | @end example | |
14228 | ||
14229 | At this level of detail, things are | |
cf4a9129 LC |
14230 | slightly complex. First, Guile itself consists of an ELF executable, |
14231 | along with many source and compiled Scheme files that are dynamically | |
14232 | loaded when it runs. This gets stored in the @file{guile-2.0.7.tar.xz} | |
14233 | tarball shown in this graph. This tarball is part of Guix's ``source'' | |
14234 | distribution, and gets inserted into the store with @code{add-to-store} | |
14235 | (@pxref{The Store}). | |
2e7b5cea | 14236 | |
cf4a9129 LC |
14237 | But how do we write a derivation that unpacks this tarball and adds it |
14238 | to the store? To solve this problem, the @code{guile-bootstrap-2.0.drv} | |
14239 | derivation---the first one that gets built---uses @code{bash} as its | |
14240 | builder, which runs @code{build-bootstrap-guile.sh}, which in turn calls | |
14241 | @code{tar} to unpack the tarball. Thus, @file{bash}, @file{tar}, | |
14242 | @file{xz}, and @file{mkdir} are statically-linked binaries, also part of | |
14243 | the Guix source distribution, whose sole purpose is to allow the Guile | |
14244 | tarball to be unpacked. | |
fb729425 | 14245 | |
cf4a9129 LC |
14246 | Once @code{guile-bootstrap-2.0.drv} is built, we have a functioning |
14247 | Guile that can be used to run subsequent build programs. Its first task | |
14248 | is to download tarballs containing the other pre-built binaries---this | |
14249 | is what the @code{.tar.xz.drv} derivations do. Guix modules such as | |
14250 | @code{ftp-client.scm} are used for this purpose. The | |
14251 | @code{module-import.drv} derivations import those modules in a directory | |
14252 | in the store, using the original layout. The | |
14253 | @code{module-import-compiled.drv} derivations compile those modules, and | |
14254 | write them in an output directory with the right layout. This | |
14255 | corresponds to the @code{#:modules} argument of | |
14256 | @code{build-expression->derivation} (@pxref{Derivations}). | |
fb729425 | 14257 | |
cf4a9129 LC |
14258 | Finally, the various tarballs are unpacked by the |
14259 | derivations @code{gcc-bootstrap-0.drv}, @code{glibc-bootstrap-0.drv}, | |
14260 | etc., at which point we have a working C tool chain. | |
fb729425 | 14261 | |
fb729425 | 14262 | |
cf4a9129 | 14263 | @unnumberedsubsec Building the Build Tools |
523e4896 | 14264 | |
cf4a9129 LC |
14265 | Bootstrapping is complete when we have a full tool chain that does not |
14266 | depend on the pre-built bootstrap tools discussed above. This | |
14267 | no-dependency requirement is verified by checking whether the files of | |
14268 | the final tool chain contain references to the @file{/gnu/store} | |
14269 | directories of the bootstrap inputs. The process that leads to this | |
14270 | ``final'' tool chain is described by the package definitions found in | |
1f6f57df | 14271 | the @code{(gnu packages commencement)} module. |
df2ce343 | 14272 | |
d33fa0c7 LC |
14273 | The @command{guix graph} command allows us to ``zoom out'' compared to |
14274 | the graph above, by looking at the level of package objects instead of | |
14275 | individual derivations---remember that a package may translate to | |
14276 | several derivations, typically one derivation to download its source, | |
14277 | one to build the Guile modules it needs, and one to actually build the | |
14278 | package from source. The command: | |
14279 | ||
14280 | @example | |
14281 | guix graph -t bag \ | |
14282 | -e '(@@@@ (gnu packages commencement) | |
14283 | glibc-final-with-bootstrap-bash)' | dot -Tps > t.ps | |
14284 | @end example | |
14285 | ||
14286 | @noindent | |
14287 | produces the dependency graph leading to the ``final'' C | |
14288 | library@footnote{You may notice the @code{glibc-intermediate} label, | |
14289 | suggesting that it is not @emph{quite} final, but as a good | |
14290 | approximation, we will consider it final.}, depicted below. | |
14291 | ||
14292 | @image{images/bootstrap-packages,6in,,Dependency graph of the early packages} | |
14293 | ||
cf4a9129 LC |
14294 | @c See <http://lists.gnu.org/archive/html/gnu-system-discuss/2012-10/msg00000.html>. |
14295 | The first tool that gets built with the bootstrap binaries is | |
d33fa0c7 LC |
14296 | GNU@tie{}Make---noted @code{make-boot0} above---which is a prerequisite |
14297 | for all the following packages. From there Findutils and Diffutils get | |
14298 | built. | |
523e4896 | 14299 | |
cf4a9129 LC |
14300 | Then come the first-stage Binutils and GCC, built as pseudo cross |
14301 | tools---i.e., with @code{--target} equal to @code{--host}. They are | |
14302 | used to build libc. Thanks to this cross-build trick, this libc is | |
14303 | guaranteed not to hold any reference to the initial tool chain. | |
4af2447e | 14304 | |
d33fa0c7 LC |
14305 | From there the final Binutils and GCC (not shown above) are built. |
14306 | GCC uses @code{ld} | |
cf4a9129 LC |
14307 | from the final Binutils, and links programs against the just-built libc. |
14308 | This tool chain is used to build the other packages used by Guix and by | |
14309 | the GNU Build System: Guile, Bash, Coreutils, etc. | |
4af2447e | 14310 | |
cf4a9129 LC |
14311 | And voilà! At this point we have the complete set of build tools that |
14312 | the GNU Build System expects. These are in the @code{%final-inputs} | |
dd164244 MW |
14313 | variable of the @code{(gnu packages commencement)} module, and are |
14314 | implicitly used by any package that uses @code{gnu-build-system} | |
1f6f57df | 14315 | (@pxref{Build Systems, @code{gnu-build-system}}). |
4af2447e | 14316 | |
4af2447e | 14317 | |
cf4a9129 | 14318 | @unnumberedsubsec Building the Bootstrap Binaries |
4af2447e | 14319 | |
e32171ee | 14320 | @cindex bootstrap binaries |
cf4a9129 LC |
14321 | Because the final tool chain does not depend on the bootstrap binaries, |
14322 | those rarely need to be updated. Nevertheless, it is useful to have an | |
14323 | automated way to produce them, should an update occur, and this is what | |
14324 | the @code{(gnu packages make-bootstrap)} module provides. | |
4af2447e | 14325 | |
cf4a9129 LC |
14326 | The following command builds the tarballs containing the bootstrap |
14327 | binaries (Guile, Binutils, GCC, libc, and a tarball containing a mixture | |
14328 | of Coreutils and other basic command-line tools): | |
4b2615e1 | 14329 | |
cf4a9129 LC |
14330 | @example |
14331 | guix build bootstrap-tarballs | |
14332 | @end example | |
14333 | ||
14334 | The generated tarballs are those that should be referred to in the | |
14335 | @code{(gnu packages bootstrap)} module mentioned at the beginning of | |
14336 | this section. | |
14337 | ||
14338 | Still here? Then perhaps by now you've started to wonder: when do we | |
14339 | reach a fixed point? That is an interesting question! The answer is | |
14340 | unknown, but if you would like to investigate further (and have | |
14341 | significant computational and storage resources to do so), then let us | |
14342 | know. | |
14343 | ||
14344 | @node Porting | |
14345 | @section Porting to a New Platform | |
14346 | ||
14347 | As discussed above, the GNU distribution is self-contained, and | |
14348 | self-containment is achieved by relying on pre-built ``bootstrap | |
14349 | binaries'' (@pxref{Bootstrapping}). These binaries are specific to an | |
14350 | operating system kernel, CPU architecture, and application binary | |
14351 | interface (ABI). Thus, to port the distribution to a platform that is | |
14352 | not yet supported, one must build those bootstrap binaries, and update | |
14353 | the @code{(gnu packages bootstrap)} module to use them on that platform. | |
14354 | ||
14355 | Fortunately, Guix can @emph{cross compile} those bootstrap binaries. | |
14356 | When everything goes well, and assuming the GNU tool chain supports the | |
14357 | target platform, this can be as simple as running a command like this | |
14358 | one: | |
14359 | ||
14360 | @example | |
14361 | guix build --target=armv5tel-linux-gnueabi bootstrap-tarballs | |
14362 | @end example | |
14363 | ||
1c0c417d LC |
14364 | For this to work, the @code{glibc-dynamic-linker} procedure in |
14365 | @code{(gnu packages bootstrap)} must be augmented to return the right | |
14366 | file name for libc's dynamic linker on that platform; likewise, | |
14367 | @code{system->linux-architecture} in @code{(gnu packages linux)} must be | |
14368 | taught about the new platform. | |
14369 | ||
cf4a9129 | 14370 | Once these are built, the @code{(gnu packages bootstrap)} module needs |
1c0c417d LC |
14371 | to be updated to refer to these binaries on the target platform. That |
14372 | is, the hashes and URLs of the bootstrap tarballs for the new platform | |
14373 | must be added alongside those of the currently supported platforms. The | |
14374 | bootstrap Guile tarball is treated specially: it is expected to be | |
03d0e2d2 | 14375 | available locally, and @file{gnu/local.mk} has rules do download it for |
1c0c417d LC |
14376 | the supported architectures; a rule for the new platform must be added |
14377 | as well. | |
cf4a9129 LC |
14378 | |
14379 | In practice, there may be some complications. First, it may be that the | |
14380 | extended GNU triplet that specifies an ABI (like the @code{eabi} suffix | |
14381 | above) is not recognized by all the GNU tools. Typically, glibc | |
14382 | recognizes some of these, whereas GCC uses an extra @code{--with-abi} | |
14383 | configure flag (see @code{gcc.scm} for examples of how to handle this). | |
14384 | Second, some of the required packages could fail to build for that | |
14385 | platform. Lastly, the generated binaries could be broken for some | |
14386 | reason. | |
4af2447e | 14387 | |
9bf3c1a7 | 14388 | @c ********************************************************************* |
8c01b9d0 | 14389 | @include contributing.texi |
c78bd12b | 14390 | |
568717fd LC |
14391 | @c ********************************************************************* |
14392 | @node Acknowledgments | |
14393 | @chapter Acknowledgments | |
14394 | ||
136787cb LC |
14395 | Guix is based on the @uref{http://nixos.org/nix/, Nix package manager}, |
14396 | which was designed and | |
4c7ac9aa LC |
14397 | implemented by Eelco Dolstra, with contributions from other people (see |
14398 | the @file{nix/AUTHORS} file in Guix.) Nix pioneered functional package | |
568717fd LC |
14399 | management, and promoted unprecedented features, such as transactional |
14400 | package upgrades and rollbacks, per-user profiles, and referentially | |
14401 | transparent build processes. Without this work, Guix would not exist. | |
14402 | ||
14403 | The Nix-based software distributions, Nixpkgs and NixOS, have also been | |
14404 | an inspiration for Guix. | |
14405 | ||
4c7ac9aa LC |
14406 | GNU@tie{}Guix itself is a collective work with contributions from a |
14407 | number of people. See the @file{AUTHORS} file in Guix for more | |
14408 | information on these fine people. The @file{THANKS} file lists people | |
14409 | who have helped by reporting bugs, taking care of the infrastructure, | |
14410 | providing artwork and themes, making suggestions, and more---thank you! | |
14411 | ||
14412 | ||
568717fd LC |
14413 | @c ********************************************************************* |
14414 | @node GNU Free Documentation License | |
14415 | @appendix GNU Free Documentation License | |
e32171ee | 14416 | @cindex license, GNU Free Documentation License |
568717fd LC |
14417 | @include fdl-1.3.texi |
14418 | ||
14419 | @c ********************************************************************* | |
14420 | @node Concept Index | |
14421 | @unnumbered Concept Index | |
14422 | @printindex cp | |
14423 | ||
a85b83d2 LC |
14424 | @node Programming Index |
14425 | @unnumbered Programming Index | |
14426 | @syncodeindex tp fn | |
14427 | @syncodeindex vr fn | |
568717fd LC |
14428 | @printindex fn |
14429 | ||
14430 | @bye | |
14431 | ||
14432 | @c Local Variables: | |
14433 | @c ispell-local-dictionary: "american"; | |
14434 | @c End: |