···181 </section>
182<!--============================================================-->
183<!--
184-<section>
185 <title>Gnome</title>
186 <para>* Expression is auto-generated</para>
187 <para>* How to update</para>
···189-->
190<!--============================================================-->
191<!--
192-<section>
193 <title>GCC</title>
194 <para>…</para>
195</section>
···181 </section>
182<!--============================================================-->
183<!--
184+<section xml:id="sec-package-notes-gnome">
185 <title>Gnome</title>
186 <para>* Expression is auto-generated</para>
187 <para>* How to update</para>
···189-->
190<!--============================================================-->
191<!--
192+<section xml:id="sec-package-notes-gcc">
193 <title>GCC</title>
194 <para>…</para>
195</section>
+8-8
doc/release-notes.xml
···2<article xmlns="http://docbook.org/ns/docbook"
3 xmlns:xlink="http://www.w3.org/1999/xlink">
4 <title>Nixpkgs Release Notes</title>
5- <section>
6 <title>Release 0.14 (June 4, 2012)</title>
78 <para>
···17 packages by numerous contributors. For details, see the commit logs.
18 </para>
19 </section>
20- <section>
21 <title>Release 0.13 (February 5, 2010)</title>
2223 <para>
···51 </itemizedlist>
52 </para>
53 </section>
54- <section>
55 <title>Release 0.12 (April 24, 2009)</title>
5657 <para>
···145 <literal>nix-dev</literal> mailing list.
146 </para>
147 </section>
148- <section>
149 <title>Release 0.11 (September 11, 2007)</title>
150151 <para>
···344 Bravenboer, Michael Raskin, Wouter den Breejen and Yury G. Kudryashov.
345 </para>
346 </section>
347- <section>
348 <title>Release 0.10 (October 12, 2006)</title>
349350 <note>
···547 Bravenboer, Merijn de Jonge, Rob Vermaas and Roy van den Broek.
548 </para>
549 </section>
550- <section>
551 <title>Release 0.9 (January 31, 2006)</title>
552553 <para>
···676 Martin Bravenboer, Rob Vermaas and Roy van den Broek.
677 </para>
678 </section>
679- <section>
680 <title>Release 0.8 (April 11, 2005)</title>
681682 <para>
···700 </itemizedlist>
701 </para>
702 </section>
703- <section>
704 <title>Release 0.7 (March 14, 2005)</title>
705706 <itemizedlist>
···2<article xmlns="http://docbook.org/ns/docbook"
3 xmlns:xlink="http://www.w3.org/1999/xlink">
4 <title>Nixpkgs Release Notes</title>
5+ <section xml:id="release-notes-0.14">
6 <title>Release 0.14 (June 4, 2012)</title>
78 <para>
···17 packages by numerous contributors. For details, see the commit logs.
18 </para>
19 </section>
20+ <section xml:id="release-notes-0.13">
21 <title>Release 0.13 (February 5, 2010)</title>
2223 <para>
···51 </itemizedlist>
52 </para>
53 </section>
54+ <section xml:id="release-notes-0.12">
55 <title>Release 0.12 (April 24, 2009)</title>
5657 <para>
···145 <literal>nix-dev</literal> mailing list.
146 </para>
147 </section>
148+ <section xml:id="release-notes-0.11">
149 <title>Release 0.11 (September 11, 2007)</title>
150151 <para>
···344 Bravenboer, Michael Raskin, Wouter den Breejen and Yury G. Kudryashov.
345 </para>
346 </section>
347+ <section xml:id="release-notes-0.10">
348 <title>Release 0.10 (October 12, 2006)</title>
349350 <note>
···547 Bravenboer, Merijn de Jonge, Rob Vermaas and Roy van den Broek.
548 </para>
549 </section>
550+ <section xml:id="release-notes-0.9">
551 <title>Release 0.9 (January 31, 2006)</title>
552553 <para>
···676 Martin Bravenboer, Rob Vermaas and Roy van den Broek.
677 </para>
678 </section>
679+ <section xml:id="release-notes-0.8">
680 <title>Release 0.8 (April 11, 2005)</title>
681682 <para>
···700 </itemizedlist>
701 </para>
702 </section>
703+ <section xml:id="release-notes-0.7">
704 <title>Release 0.7 (March 14, 2005)</title>
705706 <itemizedlist>
+10-10
doc/reviewing-contributions.xml
···56 meant as examples. Their usage is optional and the reviewer is free to adapt
57 them to their liking.
58 </para>
59- <section>
60 <title>Package updates</title>
6162 <para>
···208 </listitem>
209 </itemizedlist>
210211- <example>
212 <title>Sample template for a package update review</title>
213<screen>
214##### Reviewed points
···226</screen>
227 </example>
228 </section>
229- <section>
230 <title>New packages</title>
231232 <para>
···320 </listitem>
321 </itemizedlist>
322323- <example>
324 <title>Sample template for a new package review</title>
325<screen>
326##### Reviewed points
···346</screen>
347 </example>
348 </section>
349- <section>
350 <title>Module updates</title>
351352 <para>
···443 </listitem>
444 </itemizedlist>
445446- <example>
447 <title>Sample template for a module update review</title>
448<screen>
449##### Reviewed points
···464</screen>
465 </example>
466 </section>
467- <section>
468 <title>New modules</title>
469470 <para>
···542 </listitem>
543 </itemizedlist>
544545- <example>
546 <title>Sample template for a new module review</title>
547<screen>
548##### Reviewed points
···564</screen>
565 </example>
566 </section>
567- <section>
568 <title>Other submissions</title>
569570 <para>
···585 pull requests fitting this category.
586 </para>
587 </section>
588- <section>
589 <title>Merging pull-requests</title>
590591 <para>
···56 meant as examples. Their usage is optional and the reviewer is free to adapt
57 them to their liking.
58 </para>
59+ <section xml:id="reviewing-contributions-package-updates">
60 <title>Package updates</title>
6162 <para>
···208 </listitem>
209 </itemizedlist>
210211+ <example xml:id="reviewing-contributions-sample-package-update">
212 <title>Sample template for a package update review</title>
213<screen>
214##### Reviewed points
···226</screen>
227 </example>
228 </section>
229+ <section xml:id="reviewing-contributions-new-packages">
230 <title>New packages</title>
231232 <para>
···320 </listitem>
321 </itemizedlist>
322323+ <example xml:id="reviewing-contributions-sample-new-package">
324 <title>Sample template for a new package review</title>
325<screen>
326##### Reviewed points
···346</screen>
347 </example>
348 </section>
349+ <section xml:id="reviewing-contributions-module-updates">
350 <title>Module updates</title>
351352 <para>
···443 </listitem>
444 </itemizedlist>
445446+ <example xml:id="reviewing-contributions-sample-module-update">
447 <title>Sample template for a module update review</title>
448<screen>
449##### Reviewed points
···464</screen>
465 </example>
466 </section>
467+ <section xml:id="reviewing-contributions-new-modules">
468 <title>New modules</title>
469470 <para>
···542 </listitem>
543 </itemizedlist>
544545+ <example xml:id="reviewing-contributions-sample-new-module">
546 <title>Sample template for a new module review</title>
547<screen>
548##### Reviewed points
···564</screen>
565 </example>
566 </section>
567+ <section xml:id="reviewing-contributions-other-submissions">
568 <title>Other submissions</title>
569570 <para>
···585 pull requests fitting this category.
586 </para>
587 </section>
588+ <section xml:id="reviewing-contributions--merging-pull-requests">
589 <title>Merging pull-requests</title>
590591 <para>
+7-7
doc/stdenv.xml
···212 platforms relative to the new derivation's, and whether they are propagated.
213 The platform distinctions are motivated by cross compilation; see
214 <xref linkend="chap-cross"/> for exactly what each platform means.
215- <footnote>
216 <para>
217 The build platform is ignored because it is a mere implementation detail
218 of the package satisfying the dependency: As a general programming
···233 out only for dependencies whose host platform matches the new derivation's
234 build platform–i.e. which run on the platform where the new derivation
235 will be built.
236- <footnote>
237 <para>
238 Currently, that means for native builds all dependencies are put on the
239 <envar>PATH</envar>. But in the future that may not be the case for sake
···280 <link xlink:href="https://en.wikipedia.org/wiki/Natural_deduction">Natural
281 Deduction</link> using the inference rules. This probably seems a bit
282 obtuse, but so is the bash code that actually implements it!
283- <footnote>
284 <para>
285 The <function>findInputs</function> function, currently residing in
286 <filename>pkgs/stdenv/generic/setup.sh</filename>, implements the
···1112 By default, the configure phase applies some special hackery to all
1113 files called <filename>ltmain.sh</filename> before running the configure
1114 script in order to improve the purity of Libtool-based packages
1115- <footnote>
1116 <para>
1117 It clears the
1118 <varname>sys_lib_<replaceable>*</replaceable>search_path</varname>
···1151 or a subset to control exactly which platform flags are passed.
1152 Compilers and other tools should use this to also pass the target
1153 platform, for example.
1154- <footnote>
1155 <para>
1156 Eventually these will be passed when in native builds too, to improve
1157 determinism: build-time guessing, as is done today, is a risk of
···1732 Controls whether the installCheck phase is executed. By default it is
1733 skipped, but if <varname>doInstallCheck</varname> is set to true, the
1734 installCheck phase is usually executed. Thus you should set
1735- <programlisting>doInstallCheck = true;</programlisting>
1736 in the derivation to enable install checks. The exception is cross
1737 compilation. Cross compiled builds never run tests, no matter how
1738 <varname>doInstallCheck</varname> is set, as the newly-built program
···2213 <command>clang</command> is to be used. Secondly, this helps packages
2214 not get confused when cross-compiling, in which case multiple Bintools
2215 Wrappers may simultaneously be in use.
2216- <footnote>
2217 <para>
2218 Each wrapper targets a single platform, so if binaries for multiple
2219 platforms are needed, the underlying binaries must be wrapped multiple
···212 platforms relative to the new derivation's, and whether they are propagated.
213 The platform distinctions are motivated by cross compilation; see
214 <xref linkend="chap-cross"/> for exactly what each platform means.
215+ <footnote xml:id="footnote-stdenv-ignored-build-platform">
216 <para>
217 The build platform is ignored because it is a mere implementation detail
218 of the package satisfying the dependency: As a general programming
···233 out only for dependencies whose host platform matches the new derivation's
234 build platform–i.e. which run on the platform where the new derivation
235 will be built.
236+ <footnote xml:id="footnote-stdenv-native-dependencies-in-path">
237 <para>
238 Currently, that means for native builds all dependencies are put on the
239 <envar>PATH</envar>. But in the future that may not be the case for sake
···280 <link xlink:href="https://en.wikipedia.org/wiki/Natural_deduction">Natural
281 Deduction</link> using the inference rules. This probably seems a bit
282 obtuse, but so is the bash code that actually implements it!
283+ <footnote xml:id="footnote-stdenv-find-inputs-location">
284 <para>
285 The <function>findInputs</function> function, currently residing in
286 <filename>pkgs/stdenv/generic/setup.sh</filename>, implements the
···1112 By default, the configure phase applies some special hackery to all
1113 files called <filename>ltmain.sh</filename> before running the configure
1114 script in order to improve the purity of Libtool-based packages
1115+ <footnote xml:id="footnote-stdenv-sys-lib-search-path">
1116 <para>
1117 It clears the
1118 <varname>sys_lib_<replaceable>*</replaceable>search_path</varname>
···1151 or a subset to control exactly which platform flags are passed.
1152 Compilers and other tools should use this to also pass the target
1153 platform, for example.
1154+ <footnote xml:id="footnote-stdenv-build-time-guessing-impurity">
1155 <para>
1156 Eventually these will be passed when in native builds too, to improve
1157 determinism: build-time guessing, as is done today, is a risk of
···1732 Controls whether the installCheck phase is executed. By default it is
1733 skipped, but if <varname>doInstallCheck</varname> is set to true, the
1734 installCheck phase is usually executed. Thus you should set
1735+<programlisting>doInstallCheck = true;</programlisting>
1736 in the derivation to enable install checks. The exception is cross
1737 compilation. Cross compiled builds never run tests, no matter how
1738 <varname>doInstallCheck</varname> is set, as the newly-built program
···2213 <command>clang</command> is to be used. Secondly, this helps packages
2214 not get confused when cross-compiling, in which case multiple Bintools
2215 Wrappers may simultaneously be in use.
2216+ <footnote xml:id="footnote-stdenv-per-platform-wrapper">
2217 <para>
2218 Each wrapper targets a single platform, so if binaries for multiple
2219 platforms are needed, the underlying binaries must be wrapped multiple
+15-15
doc/submitting-changes.xml
···2 xmlns:xlink="http://www.w3.org/1999/xlink"
3 xml:id="chap-submitting-changes">
4 <title>Submitting changes</title>
5- <section>
6 <title>Making patches</title>
78 <itemizedlist>
···205 </listitem>
206 </itemizedlist>
207 </section>
208- <section>
209 <title>Submitting changes</title>
210211 <itemizedlist>
···253 </listitem>
254 </itemizedlist>
255 </section>
256- <section>
257 <title>Pull Request Template</title>
258259 <para>
···269 below:
270 </para>
271272- <section>
273 <title>Tested using sandboxing</title>
274275 <para>
···322 </para>
323 </section>
324325- <section>
326 <title>Built on platform(s)</title>
327328 <para>
···334 </para>
335 </section>
336337- <section>
338 <title>Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)</title>
339340 <para>
···350 </para>
351 </section>
352353- <section>
354 <title>Tested compilation of all pkgs that depend on this change using <command>nox-review</command></title>
355356 <para>
···373 </para>
374 </section>
375376- <section>
377 <title>Tested execution of all binary files (usually in <filename>./result/bin/</filename>)</title>
378379 <para>
···387 </para>
388 </section>
389390- <section>
391- <title>Meets nixpkgs contribution standards</title>
392393 <para>
394 The last checkbox is fits
···402 </para>
403 </section>
404 </section>
405- <section>
406 <title>Hotfixing pull requests</title>
407408 <itemizedlist>
···430 </listitem>
431 </itemizedlist>
432 </section>
433- <section>
434 <title>Commit policy</title>
435436 <itemizedlist>
···456 </listitem>
457 </itemizedlist>
458459- <section>
460 <title>Master branch</title>
461462 <itemizedlist>
···468 </itemizedlist>
469 </section>
470471- <section>
472 <title>Staging branch</title>
473474 <itemizedlist>
···493 </itemizedlist>
494 </section>
495496- <section>
497 <title>Stable release branches</title>
498499 <itemizedlist>
···66 sets the kernel’s TCP keepalive time to 120 seconds. To see the available
67 parameters, run <command>sysctl -a</command>.
68 </para>
69- <section>
70 <title>Customize your kernel</title>
7172 <para>
73 The first step before compiling the kernel is to generate an appropriate
74- <literal>.config</literal> configuration. Either you pass your own config via
75- the <literal>configfile</literal> setting of <literal>linuxManualConfig</literal>:
76- <screen><![CDATA[
077 custom-kernel = super.linuxManualConfig {
78 inherit (super) stdenv hostPlatform;
79 inherit (linux_4_9) src;
···117 ]]></screen>
118 </para>
119 </section>
120- <section>
121 <title>Developing kernel modules</title>
122123 <para>
···66 sets the kernel’s TCP keepalive time to 120 seconds. To see the available
67 parameters, run <command>sysctl -a</command>.
68 </para>
69+ <section xml:id="sec-linux-config-customizing">
70 <title>Customize your kernel</title>
7172 <para>
73 The first step before compiling the kernel is to generate an appropriate
74+ <literal>.config</literal> configuration. Either you pass your own config
75+ via the <literal>configfile</literal> setting of
76+ <literal>linuxManualConfig</literal>:
77+<screen><![CDATA[
78 custom-kernel = super.linuxManualConfig {
79 inherit (super) stdenv hostPlatform;
80 inherit (linux_4_9) src;
···118 ]]></screen>
119 </para>
120 </section>
121+ <section xml:id="sec-linux-config-developing-modules">
122 <title>Developing kernel modules</title>
123124 <para>
+1-1
nixos/doc/manual/configuration/modularity.xml
···74 argument is for: it contains the complete, merged system configuration. That
75 is, <varname>config</varname> is the result of combining the configurations
76 returned by every module
77- <footnote>
78 <para>
79 If you’re wondering how it’s possible that the (indirect)
80 <emphasis>result</emphasis> of a function is passed as an
···74 argument is for: it contains the complete, merged system configuration. That
75 is, <varname>config</varname> is the result of combining the configurations
76 returned by every module
77+ <footnote xml:id="footnote-nix-is-lazy">
78 <para>
79 If you’re wondering how it’s possible that the (indirect)
80 <emphasis>result</emphasis> of a function is passed as an
···11 value definitions.
12 </para>
1314- <section>
15 <title>Basic Types</title>
1617 <para>
···196 </variablelist>
197 </section>
198199- <section>
200 <title>Value Types</title>
201202 <para>
···257 </variablelist>
258 </section>
259260- <section>
261 <title>Composed Types</title>
262263 <para>
···483 </example>
484 </section>
485486- <section>
487 <title>Extending types</title>
488489 <para>
···543 </variablelist>
544 </section>
545546- <section>
547 <title>Custom Types</title>
548549 <para>
550 Custom types can be created with the <literal>mkOptionType</literal>
551 function. As type creation includes some more complex topics such as
552 submodule handling, it is recommended to get familiar with
553- <filename
554 xlink:href="https://github.com/NixOS/nixpkgs/blob/master/lib/types.nix">types.nix</filename>
555 code before creating a new type.
556 </para>
···11 value definitions.
12 </para>
1314+ <section xml:id="sec-option-types-basic">
15 <title>Basic Types</title>
1617 <para>
···196 </variablelist>
197 </section>
198199+ <section xml:id="sec-option-types-value">
200 <title>Value Types</title>
201202 <para>
···257 </variablelist>
258 </section>
259260+ <section xml:id="sec-option-types-composed">
261 <title>Composed Types</title>
262263 <para>
···483 </example>
484 </section>
485486+ <section xml:id="sec-option-types-extending">
487 <title>Extending types</title>
488489 <para>
···543 </variablelist>
544 </section>
545546+ <section xml:id="sec-option-types-custom">
547 <title>Custom Types</title>
548549 <para>
550 Custom types can be created with the <literal>mkOptionType</literal>
551 function. As type creation includes some more complex topics such as
552 submodule handling, it is recommended to get familiar with
553+ <filename
554 xlink:href="https://github.com/NixOS/nixpkgs/blob/master/lib/types.nix">types.nix</filename>
555 code before creating a new type.
556 </para>
···10 sources and presenting it in an accessible style would be a worthy
11 contribution to the project.
12 </para>
13- <section>
14 <title>Building the Manual</title>
1516 <para>
···42 <filename>./result/share/doc/nixos/index.html</filename>.
43 </para>
44 </section>
45- <section>
46 <title>Editing DocBook XML</title>
4748 <para>
···76 Issue</link> and someone will handle the conversion to XML for you.
77 </para>
78 </section>
79- <section>
80 <title>Creating a Topic</title>
8182 <para>
···128 </itemizedlist>
129 </para>
130 </section>
131- <section>
132 <title>Adding a Topic to the Book</title>
133134 <para>
···10 sources and presenting it in an accessible style would be a worthy
11 contribution to the project.
12 </para>
13+ <section xml:id="sec-writing-docs-building-the-manual">
14 <title>Building the Manual</title>
1516 <para>
···42 <filename>./result/share/doc/nixos/index.html</filename>.
43 </para>
44 </section>
45+ <section xml:id="sec-writing-docs-editing-docbook-xml">
46 <title>Editing DocBook XML</title>
4748 <para>
···76 Issue</link> and someone will handle the conversion to XML for you.
77 </para>
78 </section>
79+ <section xml:id="sec-writing-docs-creating-a-topic">
80 <title>Creating a Topic</title>
8182 <para>
···128 </itemizedlist>
129 </para>
130 </section>
131+ <section xml:id="sec-writing-docs-adding-a-topic">
132 <title>Adding a Topic to the Book</title>
133134 <para>
+1-1
nixos/doc/manual/installation/upgrading.xml
···109 so in that case you will not be able to go back to your original channel.
110 </para>
111 </warning>
112- <section>
113 <title>Automatic Upgrades</title>
114115 <para>
···109 so in that case you will not be able to go back to your original channel.
110 </para>
111 </warning>
112+ <section xml:id="sec-upgrading-automatic">
113 <title>Automatic Upgrades</title>
114115 <para>
+1-1
nixos/doc/manual/manual.xml
···8 <subtitle>Version <xi:include href="./generated/version" parse="text" />
9 </subtitle>
10 </info>
11- <preface>
12 <title>Preface</title>
13 <para>
14 This manual describes how to install, use and extend NixOS, a Linux
···8 <subtitle>Version <xi:include href="./generated/version" parse="text" />
9 </subtitle>
10 </info>
11+ <preface xml:id="preface">
12 <title>Preface</title>
13 <para>
14 This manual describes how to install, use and extend NixOS, a Linux
···23 bridge.</para></listitem>
24</itemizedlist>
2526-<section><title>IBus</title>
2728<para>IBus is an Intelligent Input Bus. It provides full featured and user
29 friendly input method user interface.</para>
···82</simplesect>
83</section>
8485-<section><title>Fcitx</title>
8687<para>Fcitx is an input method framework with extension support. It has three
88 built-in Input Method Engine, Pinyin, QuWei and Table-based input
···122</itemizedlist>
123</section>
124125-<section><title>Nabi</title>
126127<para>Nabi is an easy to use Korean X input method. It allows you to enter
128 phonetic Korean characters (hangul) and pictographic Korean characters
···136</programlisting>
137</section>
138139-<section><title>Uim</title>
140141<para>Uim (short for "universal input method") is a multilingual input method
142 framework. Applications can use it through so-called bridges.</para>
···23 bridge.</para></listitem>
24</itemizedlist>
2526+<section xml:id="module-services-input-methods-ibus"><title>IBus</title>
2728<para>IBus is an Intelligent Input Bus. It provides full featured and user
29 friendly input method user interface.</para>
···82</simplesect>
83</section>
8485+<section xml:id="module-services-input-methods-fcitx"><title>Fcitx</title>
8687<para>Fcitx is an input method framework with extension support. It has three
88 built-in Input Method Engine, Pinyin, QuWei and Table-based input
···122</itemizedlist>
123</section>
124125+<section xml:id="module-services-input-methods-nabi"><title>Nabi</title>
126127<para>Nabi is an easy to use Korean X input method. It allows you to enter
128 phonetic Korean characters (hangul) and pictographic Korean characters
···136</programlisting>
137</section>
138139+<section xml:id="module-services-input-methods-uim"><title>Uim</title>
140141<para>Uim (short for "universal input method") is a multilingual input method
142 framework. Applications can use it through so-called bridges.</para>
+1-1
nixos/modules/installer/cd-dvd/iso-image.nix
···233 "
234 # Make our own efi program, we can't rely on "grub-install" since it seems to
235 # probe for devices, even with --skip-fs-probe.
236- ${pkgs.grub2_efi}/bin/grub-mkimage -o $out/EFI/boot/bootx64.efi -p /EFI/boot -O x86_64-efi \
237 $MODULES
238 cp ${pkgs.grub2_efi}/share/grub/unicode.pf2 $out/EFI/boot/
239
···233 "
234 # Make our own efi program, we can't rely on "grub-install" since it seems to
235 # probe for devices, even with --skip-fs-probe.
236+ ${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 \
237 $MODULES
238 cp ${pkgs.grub2_efi}/share/grub/unicode.pf2 $out/EFI/boot/
239
···10to manage your <link xlink:href="https://www.zsh.org/">ZSH</link> configuration
11including completion scripts for several CLI tools or custom prompt themes.</para>
1213-<section><title>Basic usage</title>
14<para>The module uses the <literal>oh-my-zsh</literal> package with all available features. The
15initial setup using Nix expressions is fairly similar to the configuration format
16of <literal>oh-my-zsh</literal>.
···32configuration and writes it into your <literal>/etc/zshrc</literal>.
33</para></section>
3435-<section><title>Custom additions</title>
3637<para>Sometimes third-party or custom scripts such as a modified theme may be needed.
38<literal>oh-my-zsh</literal> provides the
···48</programlisting>
49</para></section>
5051-<section><title>Custom environments</title>
5253<para>There are several extensions for <literal>oh-my-zsh</literal> packaged in <literal>nixpkgs</literal>.
54One of them is <link xlink:href="https://github.com/spwhitt/nix-zsh-completions">nix-zsh-completions</link>
···77will be thrown if both <literal>custom</literal> and <literal>customPkgs</literal> are set.</emphasis>
78</para></section>
7980-<section><title>Package your own customizations</title>
8182<para>If third-party customizations (e.g. new themes) are supposed to be added to <literal>oh-my-zsh</literal>
83there are several pitfalls to keep in mind:</para>
···10to manage your <link xlink:href="https://www.zsh.org/">ZSH</link> configuration
11including completion scripts for several CLI tools or custom prompt themes.</para>
1213+<section xml:id="module-programs-oh-my-zsh-usage"><title>Basic usage</title>
14<para>The module uses the <literal>oh-my-zsh</literal> package with all available features. The
15initial setup using Nix expressions is fairly similar to the configuration format
16of <literal>oh-my-zsh</literal>.
···32configuration and writes it into your <literal>/etc/zshrc</literal>.
33</para></section>
3435+<section xml:id="module-programs-oh-my-zsh-additions"><title>Custom additions</title>
3637<para>Sometimes third-party or custom scripts such as a modified theme may be needed.
38<literal>oh-my-zsh</literal> provides the
···48</programlisting>
49</para></section>
5051+<section xml:id="module-programs-oh-my-zsh-environments"><title>Custom environments</title>
5253<para>There are several extensions for <literal>oh-my-zsh</literal> packaged in <literal>nixpkgs</literal>.
54One of them is <link xlink:href="https://github.com/spwhitt/nix-zsh-completions">nix-zsh-completions</link>
···77will be thrown if both <literal>custom</literal> and <literal>customPkgs</literal> are set.</emphasis>
78</para></section>
7980+<section xml:id="module-programs-oh-my-zsh-packaging-customizations"><title>Package your own customizations</title>
8182<para>If third-party customizations (e.g. new themes) are supposed to be added to <literal>oh-my-zsh</literal>
83there are several pitfalls to keep in mind:</para>
+3-3
nixos/modules/security/acme.xml
···11implemented by and for Let's Encrypt. The alternative ACME client
12<literal>simp_le</literal> is used under the hood.</para>
1314-<section><title>Prerequisites</title>
1516<para>You need to have a running HTTP server for verification. The server must
17have a webroot defined that can serve
···4142</section>
4344-<section><title>Configuring</title>
4546<para>To enable ACME certificate retrieval & renewal for a certificate for
47<literal>foo.example.com</literal>, add the following in your
···6667</section>
6869-<section><title>Using ACME certificates in Nginx</title>
70<para>NixOS supports fetching ACME certificates for you by setting
71 <literal><link linkend="opt-services.nginx.virtualHosts._name_.enableACME">enableACME</link> = true;</literal> in a virtualHost config. We
72first create self-signed placeholder certificates in place of the
···11implemented by and for Let's Encrypt. The alternative ACME client
12<literal>simp_le</literal> is used under the hood.</para>
1314+<section xml:id="module-security-acme-prerequisites"><title>Prerequisites</title>
1516<para>You need to have a running HTTP server for verification. The server must
17have a webroot defined that can serve
···4142</section>
4344+<section xml:id="module-security-acme-configuring"><title>Configuring</title>
4546<para>To enable ACME certificate retrieval & renewal for a certificate for
47<literal>foo.example.com</literal>, add the following in your
···6667</section>
6869+<section xml:id="module-security-acme-nginx"><title>Using ACME certificates in Nginx</title>
70<para>NixOS supports fetching ACME certificates for you by setting
71 <literal><link linkend="opt-services.nginx.virtualHosts._name_.enableACME">enableACME</link> = true;</literal> in a virtualHost config. We
72first create self-signed placeholder certificates in place of the
+9-9
nixos/modules/services/databases/foundationdb.xml
···17<para>FoundationDB (or "FDB") is an open source, distributed, transactional
18key-value store.</para>
1920-<section><title>Configuring and basic setup</title>
2122<para>To enable FoundationDB, add the following to your
23<filename>configuration.nix</filename>:
···133134</section>
135136-<section><title>Scaling processes and backup agents</title>
137138<para>Scaling the number of server processes is quite easy; simply specify
139<option>services.foundationdb.serverProcesses</option> to be the number of
···151152</section>
153154-<section><title>Clustering</title>
155156<para>FoundationDB on NixOS works similarly to other Linux systems, so this
157section will be brief. Please refer to the full FoundationDB documentation for
···221222</section>
223224-<section><title>Client connectivity</title>
225226<para>By default, all clients must use the current
227<command>fdb.cluster</command> file to access a given FoundationDB cluster.
···232233</section>
234235-<section><title>Client authorization and TLS</title>
236237<para>By default, any user who can connect to a FoundationDB process with the
238correct cluster configuration can access anything. FoundationDB uses a
···270271</section>
272273-<section><title>Backups and Disaster Recovery</title>
274275<para>The usual rules for doing FoundationDB backups apply on NixOS as written
276in the FoundationDB manual. However, one important difference is the security
···316317</section>
318319-<section><title>Known limitations</title>
320321<para>The FoundationDB setup for NixOS should currently be considered beta.
322FoundationDB is not new software, but the NixOS compilation and integration has
···333334</section>
335336-<section><title>Options</title>
337338<para>NixOS's FoundationDB module allows you to configure all of the most
339relevant configuration options for <command>fdbmonitor</command>, matching it
···343344</section>
345346-<section><title>Full documentation</title>
347348<para>FoundationDB is a complex piece of software, and requires careful
349administration to properly use. Full documentation for administration can be
···17<para>FoundationDB (or "FDB") is an open source, distributed, transactional
18key-value store.</para>
1920+<section xml:id="module-services-foundationdb-configuring"><title>Configuring and basic setup</title>
2122<para>To enable FoundationDB, add the following to your
23<filename>configuration.nix</filename>:
···133134</section>
135136+<section xml:id="module-services-foundationdb-scaling"><title>Scaling processes and backup agents</title>
137138<para>Scaling the number of server processes is quite easy; simply specify
139<option>services.foundationdb.serverProcesses</option> to be the number of
···151152</section>
153154+<section xml:id="module-services-foundationdb-clustering"><title>Clustering</title>
155156<para>FoundationDB on NixOS works similarly to other Linux systems, so this
157section will be brief. Please refer to the full FoundationDB documentation for
···221222</section>
223224+<section xml:id="module-services-foundationdb-connectivity"><title>Client connectivity</title>
225226<para>By default, all clients must use the current
227<command>fdb.cluster</command> file to access a given FoundationDB cluster.
···232233</section>
234235+<section xml:id="module-services-foundationdb-authorization"><title>Client authorization and TLS</title>
236237<para>By default, any user who can connect to a FoundationDB process with the
238correct cluster configuration can access anything. FoundationDB uses a
···270271</section>
272273+<section xml:id="module-services-foundationdb-disaster-recovery"><title>Backups and Disaster Recovery</title>
274275<para>The usual rules for doing FoundationDB backups apply on NixOS as written
276in the FoundationDB manual. However, one important difference is the security
···316317</section>
318319+<section xml:id="module-services-foundationdb-limitations"><title>Known limitations</title>
320321<para>The FoundationDB setup for NixOS should currently be considered beta.
322FoundationDB is not new software, but the NixOS compilation and integration has
···333334</section>
335336+<section xml:id="module-services-foundationdb-options"><title>Options</title>
337338<para>NixOS's FoundationDB module allows you to configure all of the most
339relevant configuration options for <command>fdbmonitor</command>, matching it
···343344</section>
345346+<section xml:id="module-services-foundationdb-full-docs"><title>Full documentation</title>
347348<para>FoundationDB is a complex piece of software, and requires careful
349administration to properly use. Full documentation for administration can be
+3-3
nixos/modules/services/databases/postgresql.xml
···1718<para>PostgreSQL is an advanced, free relational database.<!-- MORE --></para>
1920-<section><title>Configuring</title>
2122<para>To enable PostgreSQL, add the following to your
23<filename>configuration.nix</filename>:
···60</section>
616263-<section><title>Upgrading</title>
6465<para>FIXME: document dump/upgrade/load cycle.</para>
6667</section>
686970-<section><title>Options</title>
7172 <para>A complete list of options for the PostgreSQL module may be found <link linkend="opt-services.postgresql.enable">here</link>.</para>
73
···1718<para>PostgreSQL is an advanced, free relational database.<!-- MORE --></para>
1920+<section xml:id="module-services-postgres-configuring"><title>Configuring</title>
2122<para>To enable PostgreSQL, add the following to your
23<filename>configuration.nix</filename>:
···60</section>
616263+<section xml:id="module-services-postgres-upgrading"><title>Upgrading</title>
6465<para>FIXME: document dump/upgrade/load cycle.</para>
6667</section>
686970+<section xml:id="module-services-postgres-options"><title>Options</title>
7172 <para>A complete list of options for the PostgreSQL module may be found <link linkend="opt-services.postgresql.enable">here</link>.</para>
73
+12-12
nixos/modules/services/editors/emacs.xml
···39 starting the Emacs daemon.
40 </para>
4142- <section>
43 <title>Installing <application>Emacs</application></title>
4445 <para>
···49 can be enabled.
50 </para>
5152- <section>
53 <title>The Different Releases of Emacs</title>
5455 <para>
···100 </para>
101102 </section>
103- <section>
104 <title>Adding Packages to Emacs</title>
105 <para>
106 Emacs includes an entire ecosystem of functionality beyond
···339 </para>
340 </section>
341342- <section>
343 <title>Advanced Emacs Configuration</title>
344345 <para>
···380 </section>
381 </section>
382383-<section>
384 <title>Running Emacs as a Service</title>
385 <para>
386 <productname>NixOS</productname> provides an optional
···396 <filename>modules/services/editors/emacs.nix</filename>
397 </para>
398399- <section>
400 <title>Enabling the Service</title>
401402 <para>
···438439 </section>
440441- <section>
442 <title>Starting the client</title>
443 <para>
444 Ensure that the emacs server is enabled, either by customizing
···457 </para>
458 </section>
459460- <section>
461 <title>Configuring the <varname>EDITOR</varname> variable</title>
462 <!--<title><command>emacsclient</command> as the Default Editor</title>-->
463···487 </para>
488 </section>
489490- <section>
491 <title>Per-User Enabling of the Service</title>
492493 <para>
···515 </section>
516</section>
517518-<section>
519 <title>Configuring Emacs</title>
520521 <para>
···548 server-switch-hook, server-done-hook?
549 -->
550551- <section>
552 <title>A Major Mode for Nix Expressions</title>
553554 <para>
···558 </para>
559 </section>
560561- <section>
562 <title>Accessing man pages</title>
563 <para>
564 You can use <function>woman</function> to get completion of all
···39 starting the Emacs daemon.
40 </para>
4142+ <section xml:id="module-services-emacs-installing">
43 <title>Installing <application>Emacs</application></title>
4445 <para>
···49 can be enabled.
50 </para>
5152+ <section xml:id="module-services-emacs-releases">
53 <title>The Different Releases of Emacs</title>
5455 <para>
···100 </para>
101102 </section>
103+ <section xml:id="module-services-emacs-adding-packages">
104 <title>Adding Packages to Emacs</title>
105 <para>
106 Emacs includes an entire ecosystem of functionality beyond
···339 </para>
340 </section>
341342+ <section xml:id="module-services-emacs-advanced">
343 <title>Advanced Emacs Configuration</title>
344345 <para>
···380 </section>
381 </section>
382383+<section xml:id="module-services-emacs-running">
384 <title>Running Emacs as a Service</title>
385 <para>
386 <productname>NixOS</productname> provides an optional
···396 <filename>modules/services/editors/emacs.nix</filename>
397 </para>
398399+ <section xml:id="module-services-emacs-enabling">
400 <title>Enabling the Service</title>
401402 <para>
···438439 </section>
440441+ <section xml:id="module-services-emacs-starting-client">
442 <title>Starting the client</title>
443 <para>
444 Ensure that the emacs server is enabled, either by customizing
···457 </para>
458 </section>
459460+ <section xml:id="module-services-emacs-editor-variable">
461 <title>Configuring the <varname>EDITOR</varname> variable</title>
462 <!--<title><command>emacsclient</command> as the Default Editor</title>-->
463···487 </para>
488 </section>
489490+ <section xml:id="module-services-emacs-per-user">
491 <title>Per-User Enabling of the Service</title>
492493 <para>
···515 </section>
516</section>
517518+<section xml:id="module-services-emacs-configuring">
519 <title>Configuring Emacs</title>
520521 <para>
···548 server-switch-hook, server-done-hook?
549 -->
550551+ <section xml:id="module-services-emacs-major-mode">
552 <title>A Major Mode for Nix Expressions</title>
553554 <para>
···558 </para>
559 </section>
560561+ <section xml:id="module-services-emacs-man-pages">
562 <title>Accessing man pages</title>
563 <para>
564 You can use <function>woman</function> to get completion of all
+3-3
nixos/modules/services/misc/gitlab.xml
···89<para>Gitlab is a feature-rich git hosting service.</para>
1011-<section><title>Prerequisites</title>
1213<para>The gitlab service exposes only an Unix socket at
14<literal>/run/gitlab/gitlab-workhorse.socket</literal>. You need to configure a
···3536</section>
3738-<section><title>Configuring</title>
3940<para>Gitlab depends on both PostgreSQL and Redis and will automatically enable
41both services. In the case of PostgreSQL, a database and a role will be created.
···119120</section>
121122-<section><title>Maintenance</title>
123124<para>You can run Gitlab's rake tasks with <literal>gitlab-rake</literal>
125which will be available on the system when gitlab is enabled. You will
···89<para>Gitlab is a feature-rich git hosting service.</para>
1011+<section xml:id="module-services-gitlab-prerequisites"><title>Prerequisites</title>
1213<para>The gitlab service exposes only an Unix socket at
14<literal>/run/gitlab/gitlab-workhorse.socket</literal>. You need to configure a
···3536</section>
3738+<section xml:id="module-services-gitlab-configuring"><title>Configuring</title>
3940<para>Gitlab depends on both PostgreSQL and Redis and will automatically enable
41both services. In the case of PostgreSQL, a database and a role will be created.
···119120</section>
121122+<section xml:id="module-services-gitlab-maintenance"><title>Maintenance</title>
123124<para>You can run Gitlab's rake tasks with <literal>gitlab-rake</literal>
125which will be available on the system when gitlab is enabled. You will
···89<para>Prometheus exporters provide metrics for the <link xlink:href="https://prometheus.io">prometheus monitoring system</link>.</para>
1011-<section><title>Configuration</title>
12 <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:
13<programlisting>
14 services.promtheus.exporters.node = {
···33search through the <link xlink:href="https://nixos.org/nixos/options.html#prometheus.exporters">available options</link>.
34</para>
35</section>
36-<section><title>Adding a new exporter</title>
37 <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>
38<itemizedlist>
39 <listitem>
···89<para>Prometheus exporters provide metrics for the <link xlink:href="https://prometheus.io">prometheus monitoring system</link>.</para>
1011+<section xml:id="module-services-prometheus-exporters-configuration"><title>Configuration</title>
12 <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:
13<programlisting>
14 services.promtheus.exporters.node = {
···33search through the <link xlink:href="https://nixos.org/nixos/options.html#prometheus.exporters">available options</link>.
34</para>
35</section>
36+<section xml:id="module-services-prometheus-exporters-new-exporter"><title>Adding a new exporter</title>
37 <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>
38<itemizedlist>
39 <listitem>
···14 upstream is trustworthy).
15 </para>
1617- <sect1><title>Basic configuration</title>
1819 <para>
20 To enable the client proxy, set
···3132 </sect1>
3334- <sect1><title>As a forwarder for another DNS client</title>
3536 <para>
37 To run the DNSCrypt proxy client as a forwarder for another
···42 </programlisting>
43 </para>
4445- <sect2><title>dnsmasq</title>
46 <para>
47 <programlisting>
48{
···53 </para>
54 </sect2>
5556- <sect2><title>unbound</title>
57 <para>
58 <programlisting>
59{
···14 upstream is trustworthy).
15 </para>
1617+ <sect1 xml:id="sec-dnscrypt-proxy-configuration"><title>Basic configuration</title>
1819 <para>
20 To enable the client proxy, set
···3132 </sect1>
3334+ <sect1 xml:id="sec-dnscrypt-proxy-forwarder"><title>As a forwarder for another DNS client</title>
3536 <para>
37 To run the DNSCrypt proxy client as a forwarder for another
···42 </programlisting>
43 </para>
4445+ <sect2 xml:id="sec-dnscrypt-proxy-forwarder-dsnmasq"><title>dnsmasq</title>
46 <para>
47 <programlisting>
48{
···53 </para>
54 </sect2>
5556+ <sect2 xml:id="sec-dnscrypt-proxy-forwarder-unbound"><title>unbound</title>
57 <para>
58 <programlisting>
59{
···289 source = mkOption {
290 type = types.path;
291 description = ''
292- A script.
293 '';
294 };
295···297 type = types.enum (attrNames dispatcherTypesSubdirMap);
298 default = "basic";
299 description = ''
300- Dispatcher hook type. Only basic hooks are currently available.
000301 '';
302 };
303 };
304 });
305 default = [];
0000000000000306 description = ''
307 A list of scripts which will be executed in response to network events.
308 '';
···418 ++ lib.imap1 (i: s: {
419 inherit (s) source;
420 target = "NetworkManager/dispatcher.d/${dispatcherTypesSubdirMap.${s.type}}03userscript${lib.fixedWidthNumber 4 i}";
0421 }) cfg.dispatcherScripts
422 ++ optional (dynamicHostsEnabled)
423 { target = "NetworkManager/dnsmasq.d/dyndns.conf";
···473 Type = "oneshot";
474 RemainAfterExist = true;
475 };
00000000476 };
477478 # Turn off NixOS' network management
···289 source = mkOption {
290 type = types.path;
291 description = ''
292+ Path to the hook script.
293 '';
294 };
295···297 type = types.enum (attrNames dispatcherTypesSubdirMap);
298 default = "basic";
299 description = ''
300+ Dispatcher hook type. Look up the hooks described at
301+ <link xlink:href="https://developer.gnome.org/NetworkManager/stable/NetworkManager.html">https://developer.gnome.org/NetworkManager/stable/NetworkManager.html</link>
302+ and choose the type depending on the output folder.
303+ You should then filter the event type (e.g., "up"/"down") from within your script.
304 '';
305 };
306 };
307 });
308 default = [];
309+ example = literalExample ''
310+ [ {
311+ source = pkgs.writeText "upHook" '''
312+313+ if [ "$2" != "up" ]; then
314+ logger "exit: event $2 != up"
315+ fi
316+317+ # coreutils and iproute are in PATH too
318+ logger "Device $DEVICE_IFACE coming up"
319+ ''';
320+ type = "basic";
321+ } ]'';
322 description = ''
323 A list of scripts which will be executed in response to network events.
324 '';
···434 ++ lib.imap1 (i: s: {
435 inherit (s) source;
436 target = "NetworkManager/dispatcher.d/${dispatcherTypesSubdirMap.${s.type}}03userscript${lib.fixedWidthNumber 4 i}";
437+ mode = "0544";
438 }) cfg.dispatcherScripts
439 ++ optional (dynamicHostsEnabled)
440 { target = "NetworkManager/dnsmasq.d/dyndns.conf";
···490 Type = "oneshot";
491 RemainAfterExist = true;
492 };
493+ };
494+495+ systemd.services."NetworkManager-dispatcher" = {
496+ wantedBy = [ "network.target" ];
497+ restartTriggers = [ configFile ];
498+499+ # useful binaries for user-specified hooks
500+ path = [ pkgs.iproute pkgs.utillinux pkgs.coreutils ];
501 };
502503 # Turn off NixOS' network management
+4-4
nixos/modules/services/web-apps/matomo-doc.xml
···15 </para>
161718- <section>
19 <title>Database Setup</title>
2021 <para>
···51 </section>
525354- <section>
55 <title>Backup</title>
56 <para>
57 You only need to take backups of your MySQL database and the
···62 </section>
636465- <section>
66 <title>Issues</title>
67 <itemizedlist>
68 <listitem>
···83 </section>
848586- <section>
87 <title>Using other Web Servers than nginx</title>
8889 <para>
···15 </para>
161718+ <section xml:id="module-services-matomo-database-setup">
19 <title>Database Setup</title>
2021 <para>
···51 </section>
525354+ <section xml:id="module-services-matomo-backups">
55 <title>Backup</title>
56 <para>
57 You only need to take backups of your MySQL database and the
···62 </section>
636465+ <section xml:id="module-services-matomo-issues">
66 <title>Issues</title>
67 <itemizedlist>
68 <listitem>
···83 </section>
848586+ <section xml:id="module-services-matomo-other-web-servers">
87 <title>Using other Web Servers than nginx</title>
8889 <para>
···473 # Remove Dead Interfaces
474 ip link show "${n}" >/dev/null 2>&1 && ip link delete "${n}"
475 ip link add link "${v.interface}" name "${n}" type vlan id "${toString v.id}"
476- ip link set "${n}" up
00000477 '';
478 postStop = ''
479 ip link delete "${n}" || true
···473 # Remove Dead Interfaces
474 ip link show "${n}" >/dev/null 2>&1 && ip link delete "${n}"
475 ip link add link "${v.interface}" name "${n}" type vlan id "${toString v.id}"
476+477+ # We try to bring up the logical VLAN interface. If the master
478+ # interface the logical interface is dependent upon is not up yet we will
479+ # fail to immediately bring up the logical interface. The resulting logical
480+ # interface will brought up later when the master interface is up.
481+ ip link set "${n}" up || true
482 '';
483 postStop = ''
484 ip link delete "${n}" || true
···1516 cargoSha256 = "14x8pbjgkz0g724lnvd9mi2alqd6fipjljw6xsraf9gqwijn1kn0";
1718- meta = {
19 description = "Directly run Ethereum bytecode";
20 homepage = https://github.com/dapphub/ethrun/;
21- maintainers = [stdenv.lib.maintainers.dbrock];
022 broken = true; # mark temporary as broken
23 inherit version;
24 };
···1516 cargoSha256 = "14x8pbjgkz0g724lnvd9mi2alqd6fipjljw6xsraf9gqwijn1kn0";
1718+ meta = with stdenv.lib; {
19 description = "Directly run Ethereum bytecode";
20 homepage = https://github.com/dapphub/ethrun/;
21+ maintainers = [ maintainers.dbrock ];
22+ license = licenses.gpl3;
23 broken = true; # mark temporary as broken
24 inherit version;
25 };
+1-1
pkgs/applications/audio/axoloti/dfu-util.nix
···23 phones. With dfu-util you are able to download firmware to your device or
24 upload firmware from it.
25 '';
26- homepage = http://dfu-util.gnumonks.org/;
27 license = licenses.gpl2Plus;
28 platforms = platforms.unix;
29 maintainers = [ ];
···23 phones. With dfu-util you are able to download firmware to your device or
24 upload firmware from it.
25 '';
26+ homepage = http://dfu-util.sourceforge.net;
27 license = licenses.gpl2Plus;
28 platforms = platforms.unix;
29 maintainers = [ ];
···2122 meta = {
23 description = "Bitmap paint program inspired by the Amiga programs Deluxe Paint and Brilliance";
24- homepage = http://code.google.co/p/grafx2/;
25 license = stdenv.lib.licenses.gpl2;
26 platforms = [ "x86_64-linux" "i686-linux" ];
27 maintainers = [ stdenv.lib.maintainers.zoomulator ];
···2122 meta = {
23 description = "Bitmap paint program inspired by the Amiga programs Deluxe Paint and Brilliance";
24+ homepage = http://pulkomandy.tk/projects/GrafX2;
25 license = stdenv.lib.licenses.gpl2;
26 platforms = [ "x86_64-linux" "i686-linux" ];
27 maintainers = [ stdenv.lib.maintainers.zoomulator ];
+4-5
pkgs/applications/graphics/k3d/default.nix
···3940 #doCheck = false;
4142- meta = {
43 description = "A 3D editor with support for procedural editing";
44 homepage = http://www.k-3d.org/;
45- platforms = with stdenv.lib.platforms;
46- linux;
47- maintainers = with stdenv.lib.maintainers;
48- [raskin];
49 };
50}
···3940 #doCheck = false;
4142+ meta = with stdenv.lib; {
43 description = "A 3D editor with support for procedural editing";
44 homepage = http://www.k-3d.org/;
45+ platforms = platforms.linux;
46+ maintainers = [ maintainers.raskin ];
47+ license = licenses.gpl2;
048 };
49}
···32 "$out/lib:${neon}/lib:${libusb.out}/lib:${avahi}/lib:${freeipmi}/lib"
33 '';
3435- meta = {
36 description = "Network UPS Tools";
37 longDescription = ''
38 Network UPS Tools is a collection of programs which provide a common
···41 '';
42 homepage = http://www.networkupstools.org/;
43 repositories.git = https://github.com/networkupstools/nut.git;
44- platforms = with stdenv.lib.platforms; linux;
45- maintainers = with stdenv.lib.maintainers; [ pierron ];
046 priority = 10;
47 };
48}
···32 "$out/lib:${neon}/lib:${libusb.out}/lib:${avahi}/lib:${freeipmi}/lib"
33 '';
3435+ meta = with stdenv.lib; {
36 description = "Network UPS Tools";
37 longDescription = ''
38 Network UPS Tools is a collection of programs which provide a common
···41 '';
42 homepage = http://www.networkupstools.org/;
43 repositories.git = https://github.com/networkupstools/nut.git;
44+ platforms = platforms.linux;
45+ maintainers = [ maintainers.pierron ];
46+ license = with licenses; [ gpl1Plus gpl2Plus gpl3Plus ];
47 priority = 10;
48 };
49}
+1-1
pkgs/applications/misc/orpie/default.nix
···12 buildInputs = [ ncurses gsl ] ++ (with ocamlPackages; [ ocaml camlp4 ]);
1314 meta = {
15- homepage = http://pessimization.com/software/orpie/;
16 description = "A fullscreen RPN calculator for the console";
17 license = stdenv.lib.licenses.gpl2;
18 platforms = stdenv.lib.platforms.all;
···12 buildInputs = [ ncurses gsl ] ++ (with ocamlPackages; [ ocaml camlp4 ]);
1314 meta = {
15+ homepage = https://github.com/pelzlpj/orpie;
16 description = "A fullscreen RPN calculator for the console";
17 license = stdenv.lib.licenses.gpl2;
18 platforms = stdenv.lib.platforms.all;
+1
pkgs/applications/misc/pdf-quench/default.nix
···31 homepage = https://github.com/linuxerwang/pdf-quench;
32 description = "A visual tool for cropping pdf files";
33 platforms = platforms.linux;
034 maintainers = with maintainers; [ flokli ];
35 };
36}
···31 homepage = https://github.com/linuxerwang/pdf-quench;
32 description = "A visual tool for cropping pdf files";
33 platforms = platforms.linux;
34+ license = licenses.gpl2;
35 maintainers = with maintainers; [ flokli ];
36 };
37}
+1-1
pkgs/applications/misc/pdfshuffler/default.nix
···32 doCheck = false; # no tests
3334 meta = with stdenv.lib; {
35- homepage = https://gna.org/projects/pdfshuffler/;
36 description = "Merge or split pdf documents and rotate, crop and rearrange their pages";
37 platforms = platforms.linux;
38 maintainers = with maintainers; [ mic92 ];
···32 doCheck = false; # no tests
3334 meta = with stdenv.lib; {
35+ homepage = https://sourceforge.net/p/pdfshuffler/wiki/Home;
36 description = "Merge or split pdf documents and rotate, crop and rearrange their pages";
37 platforms = platforms.linux;
38 maintainers = with maintainers; [ mic92 ];
-1
pkgs/applications/misc/pinfo/default.nix
···1718 meta = with stdenv.lib; {
19 description = "A viewer for info files";
20- homepage = https://alioth.debian.org/projects/pinfo/;
21 license = licenses.gpl2Plus;
22 platforms = platforms.unix;
23 };
···1718 meta = with stdenv.lib; {
19 description = "A viewer for info files";
020 license = licenses.gpl2Plus;
21 platforms = platforms.unix;
22 };
+4-3
pkgs/applications/misc/posterazor/default.nix
···28 cp PosteRazor $out/bin
29 '';
3031- meta = {
32 homepage = http://posterazor.sourceforge.net/;
33 description = "Cuts a raster image into pieces which can afterwards be printed out and assembled to a poster";
34- maintainers = [ stdenv.lib.maintainers.madjar ];
35- platforms = stdenv.lib.platforms.linux;
036 };
37}
···28 cp PosteRazor $out/bin
29 '';
3031+ meta = with stdenv.lib; {
32 homepage = http://posterazor.sourceforge.net/;
33 description = "Cuts a raster image into pieces which can afterwards be printed out and assembled to a poster";
34+ maintainers = [ maintainers.madjar ];
35+ license = licenses.gpl3Plus;
36+ platforms = platforms.linux;
37 };
38}
···23 addToSearchPath PATH .bin
24 '';
2526+ meta = with stdenv.lib; {
27+ description = "Autoclicker application, which enables you to automatically click the left mousebutton";
28+ homepage = http://xautoclick.sourceforge.net;
29+ license = licenses.gpl2;
30+ platforms = platforms.linux;
31 };
32}
+3-2
pkgs/applications/misc/xchm/default.nix
···13 echo $NIX_LDFLAGS
14 '';
1516- meta = {
17 description = "A viewer for Microsoft HTML Help files";
18 homepage = http://xchm.sourceforge.net;
19- platforms = stdenv.lib.platforms.linux;
020 };
21}
···13 echo $NIX_LDFLAGS
14 '';
1516+ meta = with stdenv.lib; {
17 description = "A viewer for Microsoft HTML Help files";
18 homepage = http://xchm.sourceforge.net;
19+ license = licenses.gpl2;
20+ platforms = platforms.linux;
21 };
22}
···1617 meta = {
18 description = "A C++ platform for building dynamic and reflexive systems with an emphasis on audio and media";
19- homepage = https://jamoma.org;
20 license = stdenv.lib.licenses.bsd3;
21 maintainers = [ stdenv.lib.maintainers.magnetophon ];
22 platforms = stdenv.lib.platforms.linux;
···1617 meta = {
18 description = "A C++ platform for building dynamic and reflexive systems with an emphasis on audio and media";
19+ homepage = http://www.jamoma.org;
20 license = stdenv.lib.licenses.bsd3;
21 maintainers = [ stdenv.lib.maintainers.magnetophon ];
22 platforms = stdenv.lib.platforms.linux;
+1-1
pkgs/development/libraries/bwidget/default.nix
···23 buildInputs = [ tcl ];
2425 meta = {
26- homepage = http://tcl.activestate.com/software/tcllib/;
27 description = "High-level widget set for Tcl/Tk";
28 license = stdenv.lib.licenses.tcltk;
29 platforms = stdenv.lib.platforms.linux;
···23 buildInputs = [ tcl ];
2425 meta = {
26+ homepage = https://sourceforge.net/projects/tcllib;
27 description = "High-level widget set for Tcl/Tk";
28 license = stdenv.lib.licenses.tcltk;
29 platforms = stdenv.lib.platforms.linux;
+1-1
pkgs/development/libraries/clipper/default.nix
···19 The Clipper library performs line & polygon clipping - intersection, union, difference & exclusive-or,
20 and line & polygon offsetting. The library is based on Vatti's clipping algorithm.
21 '';
22- homepage = https://www.angusj.com/delphi/clipper.php;
23 license = licenses.boost;
24 maintainers = with maintainers; [ mpickering ];
25 platforms = with platforms; unix;
···19 The Clipper library performs line & polygon clipping - intersection, union, difference & exclusive-or,
20 and line & polygon offsetting. The library is based on Vatti's clipping algorithm.
21 '';
22+ homepage = https://sourceforge.net/projects/polyclipping;
23 license = licenses.boost;
24 maintainers = with maintainers; [ mpickering ];
25 platforms = with platforms; unix;
···281 inherit (buildPackages)
282 makeWrapper;
283 inherit (pkgs)
284- lib hostPlatform targetPlatform
285 runCommand wrapBintoolsWith wrapCCWith;
286 # buildPackages.foo rather than buildPackages.buildPackages.foo would work,
287 # but for splicing messing up on infinite recursion for the variants we
···297 inherit (buildPackages)
298 makeWrapper;
299 inherit (pkgs)
300- lib hostPlatform targetPlatform
301 runCommand wrapBintoolsWith wrapCCWith;
302 # buildPackages.foo rather than buildPackages.buildPackages.foo would work,
303 # but for splicing messing up on infinite recursion for the variants we
···281 inherit (buildPackages)
282 makeWrapper;
283 inherit (pkgs)
284+ lib stdenv
285 runCommand wrapBintoolsWith wrapCCWith;
286 # buildPackages.foo rather than buildPackages.buildPackages.foo would work,
287 # but for splicing messing up on infinite recursion for the variants we
···297 inherit (buildPackages)
298 makeWrapper;
299 inherit (pkgs)
300+ lib stdenv
301 runCommand wrapBintoolsWith wrapCCWith;
302 # buildPackages.foo rather than buildPackages.buildPackages.foo would work,
303 # but for splicing messing up on infinite recursion for the variants we