···181181 </section>
182182<!--============================================================-->
183183<!--
184184-<section>
184184+<section xml:id="sec-package-notes-gnome">
185185 <title>Gnome</title>
186186 <para>* Expression is auto-generated</para>
187187 <para>* How to update</para>
···189189-->
190190<!--============================================================-->
191191<!--
192192-<section>
192192+<section xml:id="sec-package-notes-gcc">
193193 <title>GCC</title>
194194 <para>…</para>
195195</section>
+8-8
doc/release-notes.xml
···22<article xmlns="http://docbook.org/ns/docbook"
33 xmlns:xlink="http://www.w3.org/1999/xlink">
44 <title>Nixpkgs Release Notes</title>
55- <section>
55+ <section xml:id="release-notes-0.14">
66 <title>Release 0.14 (June 4, 2012)</title>
7788 <para>
···1717 packages by numerous contributors. For details, see the commit logs.
1818 </para>
1919 </section>
2020- <section>
2020+ <section xml:id="release-notes-0.13">
2121 <title>Release 0.13 (February 5, 2010)</title>
22222323 <para>
···5151 </itemizedlist>
5252 </para>
5353 </section>
5454- <section>
5454+ <section xml:id="release-notes-0.12">
5555 <title>Release 0.12 (April 24, 2009)</title>
56565757 <para>
···145145 <literal>nix-dev</literal> mailing list.
146146 </para>
147147 </section>
148148- <section>
148148+ <section xml:id="release-notes-0.11">
149149 <title>Release 0.11 (September 11, 2007)</title>
150150151151 <para>
···344344 Bravenboer, Michael Raskin, Wouter den Breejen and Yury G. Kudryashov.
345345 </para>
346346 </section>
347347- <section>
347347+ <section xml:id="release-notes-0.10">
348348 <title>Release 0.10 (October 12, 2006)</title>
349349350350 <note>
···547547 Bravenboer, Merijn de Jonge, Rob Vermaas and Roy van den Broek.
548548 </para>
549549 </section>
550550- <section>
550550+ <section xml:id="release-notes-0.9">
551551 <title>Release 0.9 (January 31, 2006)</title>
552552553553 <para>
···676676 Martin Bravenboer, Rob Vermaas and Roy van den Broek.
677677 </para>
678678 </section>
679679- <section>
679679+ <section xml:id="release-notes-0.8">
680680 <title>Release 0.8 (April 11, 2005)</title>
681681682682 <para>
···700700 </itemizedlist>
701701 </para>
702702 </section>
703703- <section>
703703+ <section xml:id="release-notes-0.7">
704704 <title>Release 0.7 (March 14, 2005)</title>
705705706706 <itemizedlist>
+10-10
doc/reviewing-contributions.xml
···5656 meant as examples. Their usage is optional and the reviewer is free to adapt
5757 them to their liking.
5858 </para>
5959- <section>
5959+ <section xml:id="reviewing-contributions-package-updates">
6060 <title>Package updates</title>
61616262 <para>
···208208 </listitem>
209209 </itemizedlist>
210210211211- <example>
211211+ <example xml:id="reviewing-contributions-sample-package-update">
212212 <title>Sample template for a package update review</title>
213213<screen>
214214##### Reviewed points
···226226</screen>
227227 </example>
228228 </section>
229229- <section>
229229+ <section xml:id="reviewing-contributions-new-packages">
230230 <title>New packages</title>
231231232232 <para>
···320320 </listitem>
321321 </itemizedlist>
322322323323- <example>
323323+ <example xml:id="reviewing-contributions-sample-new-package">
324324 <title>Sample template for a new package review</title>
325325<screen>
326326##### Reviewed points
···346346</screen>
347347 </example>
348348 </section>
349349- <section>
349349+ <section xml:id="reviewing-contributions-module-updates">
350350 <title>Module updates</title>
351351352352 <para>
···443443 </listitem>
444444 </itemizedlist>
445445446446- <example>
446446+ <example xml:id="reviewing-contributions-sample-module-update">
447447 <title>Sample template for a module update review</title>
448448<screen>
449449##### Reviewed points
···464464</screen>
465465 </example>
466466 </section>
467467- <section>
467467+ <section xml:id="reviewing-contributions-new-modules">
468468 <title>New modules</title>
469469470470 <para>
···542542 </listitem>
543543 </itemizedlist>
544544545545- <example>
545545+ <example xml:id="reviewing-contributions-sample-new-module">
546546 <title>Sample template for a new module review</title>
547547<screen>
548548##### Reviewed points
···564564</screen>
565565 </example>
566566 </section>
567567- <section>
567567+ <section xml:id="reviewing-contributions-other-submissions">
568568 <title>Other submissions</title>
569569570570 <para>
···585585 pull requests fitting this category.
586586 </para>
587587 </section>
588588- <section>
588588+ <section xml:id="reviewing-contributions--merging-pull-requests">
589589 <title>Merging pull-requests</title>
590590591591 <para>
+7-7
doc/stdenv.xml
···212212 platforms relative to the new derivation's, and whether they are propagated.
213213 The platform distinctions are motivated by cross compilation; see
214214 <xref linkend="chap-cross"/> for exactly what each platform means.
215215- <footnote>
215215+ <footnote xml:id="footnote-stdenv-ignored-build-platform">
216216 <para>
217217 The build platform is ignored because it is a mere implementation detail
218218 of the package satisfying the dependency: As a general programming
···233233 out only for dependencies whose host platform matches the new derivation's
234234 build platform–i.e. which run on the platform where the new derivation
235235 will be built.
236236- <footnote>
236236+ <footnote xml:id="footnote-stdenv-native-dependencies-in-path">
237237 <para>
238238 Currently, that means for native builds all dependencies are put on the
239239 <envar>PATH</envar>. But in the future that may not be the case for sake
···280280 <link xlink:href="https://en.wikipedia.org/wiki/Natural_deduction">Natural
281281 Deduction</link> using the inference rules. This probably seems a bit
282282 obtuse, but so is the bash code that actually implements it!
283283- <footnote>
283283+ <footnote xml:id="footnote-stdenv-find-inputs-location">
284284 <para>
285285 The <function>findInputs</function> function, currently residing in
286286 <filename>pkgs/stdenv/generic/setup.sh</filename>, implements the
···11121112 By default, the configure phase applies some special hackery to all
11131113 files called <filename>ltmain.sh</filename> before running the configure
11141114 script in order to improve the purity of Libtool-based packages
11151115- <footnote>
11151115+ <footnote xml:id="footnote-stdenv-sys-lib-search-path">
11161116 <para>
11171117 It clears the
11181118 <varname>sys_lib_<replaceable>*</replaceable>search_path</varname>
···11511151 or a subset to control exactly which platform flags are passed.
11521152 Compilers and other tools should use this to also pass the target
11531153 platform, for example.
11541154- <footnote>
11541154+ <footnote xml:id="footnote-stdenv-build-time-guessing-impurity">
11551155 <para>
11561156 Eventually these will be passed when in native builds too, to improve
11571157 determinism: build-time guessing, as is done today, is a risk of
···17321732 Controls whether the installCheck phase is executed. By default it is
17331733 skipped, but if <varname>doInstallCheck</varname> is set to true, the
17341734 installCheck phase is usually executed. Thus you should set
17351735- <programlisting>doInstallCheck = true;</programlisting>
17351735+<programlisting>doInstallCheck = true;</programlisting>
17361736 in the derivation to enable install checks. The exception is cross
17371737 compilation. Cross compiled builds never run tests, no matter how
17381738 <varname>doInstallCheck</varname> is set, as the newly-built program
···22132213 <command>clang</command> is to be used. Secondly, this helps packages
22142214 not get confused when cross-compiling, in which case multiple Bintools
22152215 Wrappers may simultaneously be in use.
22162216- <footnote>
22162216+ <footnote xml:id="footnote-stdenv-per-platform-wrapper">
22172217 <para>
22182218 Each wrapper targets a single platform, so if binaries for multiple
22192219 platforms are needed, the underlying binaries must be wrapped multiple
···6666 sets the kernel’s TCP keepalive time to 120 seconds. To see the available
6767 parameters, run <command>sysctl -a</command>.
6868 </para>
6969- <section>
6969+ <section xml:id="sec-linux-config-customizing">
7070 <title>Customize your kernel</title>
71717272 <para>
7373 The first step before compiling the kernel is to generate an appropriate
7474- <literal>.config</literal> configuration. Either you pass your own config via
7575- the <literal>configfile</literal> setting of <literal>linuxManualConfig</literal>:
7676- <screen><![CDATA[
7474+ <literal>.config</literal> configuration. Either you pass your own config
7575+ via the <literal>configfile</literal> setting of
7676+ <literal>linuxManualConfig</literal>:
7777+<screen><![CDATA[
7778 custom-kernel = super.linuxManualConfig {
7879 inherit (super) stdenv hostPlatform;
7980 inherit (linux_4_9) src;
···117118 ]]></screen>
118119 </para>
119120 </section>
120120- <section>
121121+ <section xml:id="sec-linux-config-developing-modules">
121122 <title>Developing kernel modules</title>
122123123124 <para>
+1-1
nixos/doc/manual/configuration/modularity.xml
···7474 argument is for: it contains the complete, merged system configuration. That
7575 is, <varname>config</varname> is the result of combining the configurations
7676 returned by every module
7777- <footnote>
7777+ <footnote xml:id="footnote-nix-is-lazy">
7878 <para>
7979 If you’re wondering how it’s possible that the (indirect)
8080 <emphasis>result</emphasis> of a function is passed as an
···1010 sources and presenting it in an accessible style would be a worthy
1111 contribution to the project.
1212 </para>
1313- <section>
1313+ <section xml:id="sec-writing-docs-building-the-manual">
1414 <title>Building the Manual</title>
15151616 <para>
···4242 <filename>./result/share/doc/nixos/index.html</filename>.
4343 </para>
4444 </section>
4545- <section>
4545+ <section xml:id="sec-writing-docs-editing-docbook-xml">
4646 <title>Editing DocBook XML</title>
47474848 <para>
···7676 Issue</link> and someone will handle the conversion to XML for you.
7777 </para>
7878 </section>
7979- <section>
7979+ <section xml:id="sec-writing-docs-creating-a-topic">
8080 <title>Creating a Topic</title>
81818282 <para>
···128128 </itemizedlist>
129129 </para>
130130 </section>
131131- <section>
131131+ <section xml:id="sec-writing-docs-adding-a-topic">
132132 <title>Adding a Topic to the Book</title>
133133134134 <para>
+1-1
nixos/doc/manual/installation/upgrading.xml
···109109 so in that case you will not be able to go back to your original channel.
110110 </para>
111111 </warning>
112112- <section>
112112+ <section xml:id="sec-upgrading-automatic">
113113 <title>Automatic Upgrades</title>
114114115115 <para>
+1-1
nixos/doc/manual/manual.xml
···88 <subtitle>Version <xi:include href="./generated/version" parse="text" />
99 </subtitle>
1010 </info>
1111- <preface>
1111+ <preface xml:id="preface">
1212 <title>Preface</title>
1313 <para>
1414 This manual describes how to install, use and extend NixOS, a Linux
···2323 bridge.</para></listitem>
2424</itemizedlist>
25252626-<section><title>IBus</title>
2626+<section xml:id="module-services-input-methods-ibus"><title>IBus</title>
27272828<para>IBus is an Intelligent Input Bus. It provides full featured and user
2929 friendly input method user interface.</para>
···8282</simplesect>
8383</section>
84848585-<section><title>Fcitx</title>
8585+<section xml:id="module-services-input-methods-fcitx"><title>Fcitx</title>
86868787<para>Fcitx is an input method framework with extension support. It has three
8888 built-in Input Method Engine, Pinyin, QuWei and Table-based input
···122122</itemizedlist>
123123</section>
124124125125-<section><title>Nabi</title>
125125+<section xml:id="module-services-input-methods-nabi"><title>Nabi</title>
126126127127<para>Nabi is an easy to use Korean X input method. It allows you to enter
128128 phonetic Korean characters (hangul) and pictographic Korean characters
···136136</programlisting>
137137</section>
138138139139-<section><title>Uim</title>
139139+<section xml:id="module-services-input-methods-uim"><title>Uim</title>
140140141141<para>Uim (short for "universal input method") is a multilingual input method
142142 framework. Applications can use it through so-called bridges.</para>
+1-1
nixos/modules/installer/cd-dvd/iso-image.nix
···233233 "
234234 # Make our own efi program, we can't rely on "grub-install" since it seems to
235235 # probe for devices, even with --skip-fs-probe.
236236- ${pkgs.grub2_efi}/bin/grub-mkimage -o $out/EFI/boot/bootx64.efi -p /EFI/boot -O x86_64-efi \
236236+ ${pkgs.grub2_efi}/bin/grub-mkimage -o $out/EFI/boot/${if targetArch == "x64" then "bootx64" else "bootx32"}.efi -p /EFI/boot -O ${if targetArch == "x64" then "x86_64" else "i386"}-efi \
237237 $MODULES
238238 cp ${pkgs.grub2_efi}/share/grub/unicode.pf2 $out/EFI/boot/
239239
···1010to manage your <link xlink:href="https://www.zsh.org/">ZSH</link> configuration
1111including completion scripts for several CLI tools or custom prompt themes.</para>
12121313-<section><title>Basic usage</title>
1313+<section xml:id="module-programs-oh-my-zsh-usage"><title>Basic usage</title>
1414<para>The module uses the <literal>oh-my-zsh</literal> package with all available features. The
1515initial setup using Nix expressions is fairly similar to the configuration format
1616of <literal>oh-my-zsh</literal>.
···3232configuration and writes it into your <literal>/etc/zshrc</literal>.
3333</para></section>
34343535-<section><title>Custom additions</title>
3535+<section xml:id="module-programs-oh-my-zsh-additions"><title>Custom additions</title>
36363737<para>Sometimes third-party or custom scripts such as a modified theme may be needed.
3838<literal>oh-my-zsh</literal> provides the
···4848</programlisting>
4949</para></section>
50505151-<section><title>Custom environments</title>
5151+<section xml:id="module-programs-oh-my-zsh-environments"><title>Custom environments</title>
52525353<para>There are several extensions for <literal>oh-my-zsh</literal> packaged in <literal>nixpkgs</literal>.
5454One of them is <link xlink:href="https://github.com/spwhitt/nix-zsh-completions">nix-zsh-completions</link>
···7777will be thrown if both <literal>custom</literal> and <literal>customPkgs</literal> are set.</emphasis>
7878</para></section>
79798080-<section><title>Package your own customizations</title>
8080+<section xml:id="module-programs-oh-my-zsh-packaging-customizations"><title>Package your own customizations</title>
81818282<para>If third-party customizations (e.g. new themes) are supposed to be added to <literal>oh-my-zsh</literal>
8383there are several pitfalls to keep in mind:</para>
+3-3
nixos/modules/security/acme.xml
···1111implemented by and for Let's Encrypt. The alternative ACME client
1212<literal>simp_le</literal> is used under the hood.</para>
13131414-<section><title>Prerequisites</title>
1414+<section xml:id="module-security-acme-prerequisites"><title>Prerequisites</title>
15151616<para>You need to have a running HTTP server for verification. The server must
1717have a webroot defined that can serve
···41414242</section>
43434444-<section><title>Configuring</title>
4444+<section xml:id="module-security-acme-configuring"><title>Configuring</title>
45454646<para>To enable ACME certificate retrieval & renewal for a certificate for
4747<literal>foo.example.com</literal>, add the following in your
···66666767</section>
68686969-<section><title>Using ACME certificates in Nginx</title>
6969+<section xml:id="module-security-acme-nginx"><title>Using ACME certificates in Nginx</title>
7070<para>NixOS supports fetching ACME certificates for you by setting
7171 <literal><link linkend="opt-services.nginx.virtualHosts._name_.enableACME">enableACME</link> = true;</literal> in a virtualHost config. We
7272first create self-signed placeholder certificates in place of the
+9-9
nixos/modules/services/databases/foundationdb.xml
···1717<para>FoundationDB (or "FDB") is an open source, distributed, transactional
1818key-value store.</para>
19192020-<section><title>Configuring and basic setup</title>
2020+<section xml:id="module-services-foundationdb-configuring"><title>Configuring and basic setup</title>
21212222<para>To enable FoundationDB, add the following to your
2323<filename>configuration.nix</filename>:
···133133134134</section>
135135136136-<section><title>Scaling processes and backup agents</title>
136136+<section xml:id="module-services-foundationdb-scaling"><title>Scaling processes and backup agents</title>
137137138138<para>Scaling the number of server processes is quite easy; simply specify
139139<option>services.foundationdb.serverProcesses</option> to be the number of
···151151152152</section>
153153154154-<section><title>Clustering</title>
154154+<section xml:id="module-services-foundationdb-clustering"><title>Clustering</title>
155155156156<para>FoundationDB on NixOS works similarly to other Linux systems, so this
157157section will be brief. Please refer to the full FoundationDB documentation for
···221221222222</section>
223223224224-<section><title>Client connectivity</title>
224224+<section xml:id="module-services-foundationdb-connectivity"><title>Client connectivity</title>
225225226226<para>By default, all clients must use the current
227227<command>fdb.cluster</command> file to access a given FoundationDB cluster.
···232232233233</section>
234234235235-<section><title>Client authorization and TLS</title>
235235+<section xml:id="module-services-foundationdb-authorization"><title>Client authorization and TLS</title>
236236237237<para>By default, any user who can connect to a FoundationDB process with the
238238correct cluster configuration can access anything. FoundationDB uses a
···270270271271</section>
272272273273-<section><title>Backups and Disaster Recovery</title>
273273+<section xml:id="module-services-foundationdb-disaster-recovery"><title>Backups and Disaster Recovery</title>
274274275275<para>The usual rules for doing FoundationDB backups apply on NixOS as written
276276in the FoundationDB manual. However, one important difference is the security
···316316317317</section>
318318319319-<section><title>Known limitations</title>
319319+<section xml:id="module-services-foundationdb-limitations"><title>Known limitations</title>
320320321321<para>The FoundationDB setup for NixOS should currently be considered beta.
322322FoundationDB is not new software, but the NixOS compilation and integration has
···333333334334</section>
335335336336-<section><title>Options</title>
336336+<section xml:id="module-services-foundationdb-options"><title>Options</title>
337337338338<para>NixOS's FoundationDB module allows you to configure all of the most
339339relevant configuration options for <command>fdbmonitor</command>, matching it
···343343344344</section>
345345346346-<section><title>Full documentation</title>
346346+<section xml:id="module-services-foundationdb-full-docs"><title>Full documentation</title>
347347348348<para>FoundationDB is a complex piece of software, and requires careful
349349administration to properly use. Full documentation for administration can be
+3-3
nixos/modules/services/databases/postgresql.xml
···17171818<para>PostgreSQL is an advanced, free relational database.<!-- MORE --></para>
19192020-<section><title>Configuring</title>
2020+<section xml:id="module-services-postgres-configuring"><title>Configuring</title>
21212222<para>To enable PostgreSQL, add the following to your
2323<filename>configuration.nix</filename>:
···6060</section>
616162626363-<section><title>Upgrading</title>
6363+<section xml:id="module-services-postgres-upgrading"><title>Upgrading</title>
64646565<para>FIXME: document dump/upgrade/load cycle.</para>
66666767</section>
686869697070-<section><title>Options</title>
7070+<section xml:id="module-services-postgres-options"><title>Options</title>
71717272 <para>A complete list of options for the PostgreSQL module may be found <link linkend="opt-services.postgresql.enable">here</link>.</para>
7373
+12-12
nixos/modules/services/editors/emacs.xml
···3939 starting the Emacs daemon.
4040 </para>
41414242- <section>
4242+ <section xml:id="module-services-emacs-installing">
4343 <title>Installing <application>Emacs</application></title>
44444545 <para>
···4949 can be enabled.
5050 </para>
51515252- <section>
5252+ <section xml:id="module-services-emacs-releases">
5353 <title>The Different Releases of Emacs</title>
54545555 <para>
···100100 </para>
101101102102 </section>
103103- <section>
103103+ <section xml:id="module-services-emacs-adding-packages">
104104 <title>Adding Packages to Emacs</title>
105105 <para>
106106 Emacs includes an entire ecosystem of functionality beyond
···339339 </para>
340340 </section>
341341342342- <section>
342342+ <section xml:id="module-services-emacs-advanced">
343343 <title>Advanced Emacs Configuration</title>
344344345345 <para>
···380380 </section>
381381 </section>
382382383383-<section>
383383+<section xml:id="module-services-emacs-running">
384384 <title>Running Emacs as a Service</title>
385385 <para>
386386 <productname>NixOS</productname> provides an optional
···396396 <filename>modules/services/editors/emacs.nix</filename>
397397 </para>
398398399399- <section>
399399+ <section xml:id="module-services-emacs-enabling">
400400 <title>Enabling the Service</title>
401401402402 <para>
···438438439439 </section>
440440441441- <section>
441441+ <section xml:id="module-services-emacs-starting-client">
442442 <title>Starting the client</title>
443443 <para>
444444 Ensure that the emacs server is enabled, either by customizing
···457457 </para>
458458 </section>
459459460460- <section>
460460+ <section xml:id="module-services-emacs-editor-variable">
461461 <title>Configuring the <varname>EDITOR</varname> variable</title>
462462 <!--<title><command>emacsclient</command> as the Default Editor</title>-->
463463···487487 </para>
488488 </section>
489489490490- <section>
490490+ <section xml:id="module-services-emacs-per-user">
491491 <title>Per-User Enabling of the Service</title>
492492493493 <para>
···515515 </section>
516516</section>
517517518518-<section>
518518+<section xml:id="module-services-emacs-configuring">
519519 <title>Configuring Emacs</title>
520520521521 <para>
···548548 server-switch-hook, server-done-hook?
549549 -->
550550551551- <section>
551551+ <section xml:id="module-services-emacs-major-mode">
552552 <title>A Major Mode for Nix Expressions</title>
553553554554 <para>
···558558 </para>
559559 </section>
560560561561- <section>
561561+ <section xml:id="module-services-emacs-man-pages">
562562 <title>Accessing man pages</title>
563563 <para>
564564 You can use <function>woman</function> to get completion of all
+3-3
nixos/modules/services/misc/gitlab.xml
···8899<para>Gitlab is a feature-rich git hosting service.</para>
10101111-<section><title>Prerequisites</title>
1111+<section xml:id="module-services-gitlab-prerequisites"><title>Prerequisites</title>
12121313<para>The gitlab service exposes only an Unix socket at
1414<literal>/run/gitlab/gitlab-workhorse.socket</literal>. You need to configure a
···35353636</section>
37373838-<section><title>Configuring</title>
3838+<section xml:id="module-services-gitlab-configuring"><title>Configuring</title>
39394040<para>Gitlab depends on both PostgreSQL and Redis and will automatically enable
4141both services. In the case of PostgreSQL, a database and a role will be created.
···119119120120</section>
121121122122-<section><title>Maintenance</title>
122122+<section xml:id="module-services-gitlab-maintenance"><title>Maintenance</title>
123123124124<para>You can run Gitlab's rake tasks with <literal>gitlab-rake</literal>
125125which will be available on the system when gitlab is enabled. You will
···8899<para>Prometheus exporters provide metrics for the <link xlink:href="https://prometheus.io">prometheus monitoring system</link>.</para>
10101111-<section><title>Configuration</title>
1111+<section xml:id="module-services-prometheus-exporters-configuration"><title>Configuration</title>
1212 <para>One of the most common exporters is the <link xlink:href="https://github.com/prometheus/node_exporter">node exporter</link>, it provides hardware and OS metrics from the host it's running on. The exporter could be configured as follows:
1313<programlisting>
1414 services.promtheus.exporters.node = {
···3333search through the <link xlink:href="https://nixos.org/nixos/options.html#prometheus.exporters">available options</link>.
3434</para>
3535</section>
3636-<section><title>Adding a new exporter</title>
3636+<section xml:id="module-services-prometheus-exporters-new-exporter"><title>Adding a new exporter</title>
3737 <para>To add a new exporter, it has to be packaged first (see <literal>nixpkgs/pkgs/servers/monitoring/prometheus/</literal> for examples), then a module can be added. The postfix exporter is used in this example:</para>
3838<itemizedlist>
3939 <listitem>
···1414 upstream is trustworthy).
1515 </para>
16161717- <sect1><title>Basic configuration</title>
1717+ <sect1 xml:id="sec-dnscrypt-proxy-configuration"><title>Basic configuration</title>
18181919 <para>
2020 To enable the client proxy, set
···31313232 </sect1>
33333434- <sect1><title>As a forwarder for another DNS client</title>
3434+ <sect1 xml:id="sec-dnscrypt-proxy-forwarder"><title>As a forwarder for another DNS client</title>
35353636 <para>
3737 To run the DNSCrypt proxy client as a forwarder for another
···4242 </programlisting>
4343 </para>
44444545- <sect2><title>dnsmasq</title>
4545+ <sect2 xml:id="sec-dnscrypt-proxy-forwarder-dsnmasq"><title>dnsmasq</title>
4646 <para>
4747 <programlisting>
4848{
···5353 </para>
5454 </sect2>
55555656- <sect2><title>unbound</title>
5656+ <sect2 xml:id="sec-dnscrypt-proxy-forwarder-unbound"><title>unbound</title>
5757 <para>
5858 <programlisting>
5959{
···289289 source = mkOption {
290290 type = types.path;
291291 description = ''
292292- A script.
292292+ Path to the hook script.
293293 '';
294294 };
295295···297297 type = types.enum (attrNames dispatcherTypesSubdirMap);
298298 default = "basic";
299299 description = ''
300300- Dispatcher hook type. Only basic hooks are currently available.
300300+ Dispatcher hook type. Look up the hooks described at
301301+ <link xlink:href="https://developer.gnome.org/NetworkManager/stable/NetworkManager.html">https://developer.gnome.org/NetworkManager/stable/NetworkManager.html</link>
302302+ and choose the type depending on the output folder.
303303+ You should then filter the event type (e.g., "up"/"down") from within your script.
301304 '';
302305 };
303306 };
304307 });
305308 default = [];
309309+ example = literalExample ''
310310+ [ {
311311+ source = pkgs.writeText "upHook" '''
312312+313313+ if [ "$2" != "up" ]; then
314314+ logger "exit: event $2 != up"
315315+ fi
316316+317317+ # coreutils and iproute are in PATH too
318318+ logger "Device $DEVICE_IFACE coming up"
319319+ ''';
320320+ type = "basic";
321321+ } ]'';
306322 description = ''
307323 A list of scripts which will be executed in response to network events.
308324 '';
···418434 ++ lib.imap1 (i: s: {
419435 inherit (s) source;
420436 target = "NetworkManager/dispatcher.d/${dispatcherTypesSubdirMap.${s.type}}03userscript${lib.fixedWidthNumber 4 i}";
437437+ mode = "0544";
421438 }) cfg.dispatcherScripts
422439 ++ optional (dynamicHostsEnabled)
423440 { target = "NetworkManager/dnsmasq.d/dyndns.conf";
···473490 Type = "oneshot";
474491 RemainAfterExist = true;
475492 };
493493+ };
494494+495495+ systemd.services."NetworkManager-dispatcher" = {
496496+ wantedBy = [ "network.target" ];
497497+ restartTriggers = [ configFile ];
498498+499499+ # useful binaries for user-specified hooks
500500+ path = [ pkgs.iproute pkgs.utillinux pkgs.coreutils ];
476501 };
477502478503 # Turn off NixOS' network management
+4-4
nixos/modules/services/web-apps/matomo-doc.xml
···1515 </para>
161617171818- <section>
1818+ <section xml:id="module-services-matomo-database-setup">
1919 <title>Database Setup</title>
20202121 <para>
···5151 </section>
525253535454- <section>
5454+ <section xml:id="module-services-matomo-backups">
5555 <title>Backup</title>
5656 <para>
5757 You only need to take backups of your MySQL database and the
···6262 </section>
636364646565- <section>
6565+ <section xml:id="module-services-matomo-issues">
6666 <title>Issues</title>
6767 <itemizedlist>
6868 <listitem>
···8383 </section>
848485858686- <section>
8686+ <section xml:id="module-services-matomo-other-web-servers">
8787 <title>Using other Web Servers than nginx</title>
88888989 <para>
···473473 # Remove Dead Interfaces
474474 ip link show "${n}" >/dev/null 2>&1 && ip link delete "${n}"
475475 ip link add link "${v.interface}" name "${n}" type vlan id "${toString v.id}"
476476- ip link set "${n}" up
476476+477477+ # We try to bring up the logical VLAN interface. If the master
478478+ # interface the logical interface is dependent upon is not up yet we will
479479+ # fail to immediately bring up the logical interface. The resulting logical
480480+ # interface will brought up later when the master interface is up.
481481+ ip link set "${n}" up || true
477482 '';
478483 postStop = ''
479484 ip link delete "${n}" || true
···15151616 cargoSha256 = "14x8pbjgkz0g724lnvd9mi2alqd6fipjljw6xsraf9gqwijn1kn0";
17171818- meta = {
1818+ meta = with stdenv.lib; {
1919 description = "Directly run Ethereum bytecode";
2020 homepage = https://github.com/dapphub/ethrun/;
2121- maintainers = [stdenv.lib.maintainers.dbrock];
2121+ maintainers = [ maintainers.dbrock ];
2222+ license = licenses.gpl3;
2223 broken = true; # mark temporary as broken
2324 inherit version;
2425 };
+1-1
pkgs/applications/audio/axoloti/dfu-util.nix
···2323 phones. With dfu-util you are able to download firmware to your device or
2424 upload firmware from it.
2525 '';
2626- homepage = http://dfu-util.gnumonks.org/;
2626+ homepage = http://dfu-util.sourceforge.net;
2727 license = licenses.gpl2Plus;
2828 platforms = platforms.unix;
2929 maintainers = [ ];
+3-3
pkgs/applications/audio/axoloti/libusb1.nix
···2929 sed 's,-ludev,-L${systemd.lib}/lib -ludev,' -i $out/lib/libusb-1.0.la
3030 '';
31313232- meta = {
3232+ meta = with stdenv.lib; {
3333 homepage = http://www.libusb.info;
3434 description = "User-space USB library";
3535- platforms = stdenv.lib.platforms.unix;
3636- maintainers = [ ];
3535+ platforms = platforms.unix;
3636+ license = licenses.lgpl21;
3737 };
3838}
···16161717 meta = {
1818 description = "A C++ platform for building dynamic and reflexive systems with an emphasis on audio and media";
1919- homepage = https://jamoma.org;
1919+ homepage = http://www.jamoma.org;
2020 license = stdenv.lib.licenses.bsd3;
2121 maintainers = [ stdenv.lib.maintainers.magnetophon ];
2222 platforms = stdenv.lib.platforms.linux;
···281281 inherit (buildPackages)
282282 makeWrapper;
283283 inherit (pkgs)
284284- lib hostPlatform targetPlatform
284284+ lib stdenv
285285 runCommand wrapBintoolsWith wrapCCWith;
286286 # buildPackages.foo rather than buildPackages.buildPackages.foo would work,
287287 # but for splicing messing up on infinite recursion for the variants we
···297297 inherit (buildPackages)
298298 makeWrapper;
299299 inherit (pkgs)
300300- lib hostPlatform targetPlatform
300300+ lib stdenv
301301 runCommand wrapBintoolsWith wrapCCWith;
302302 # buildPackages.foo rather than buildPackages.buildPackages.foo would work,
303303 # but for splicing messing up on infinite recursion for the variants we