git.iko.soy/typeable/nixpkgs
on master help sign in
Merge remote-tracking branch 'upstream/master' into racket-full-darwin
commitd3c2ec6f1d9aa2500cf35eb2767306c250a0ed3a authorClaes Wallin (韋嘉誠) <claes.wallin@greatsinodevelopment.com> dateFri 16 Nov 2018, 15:41 (8 years ago) parent2f8f189db0abe9
12435 files changed+539251−314113
.editorconfig+2−2 .gitattributes+16 .github/CODEOWNERS+41−9 .github/CONTRIBUTING.md+3−1 .github/PULL_REQUEST_TEMPLATE.md+2−1 .version+1−1 COPYING−9 README.md+12−6 default.nix+10−1 doc/.gitignore+7 doc/Makefile+104 doc/coding-conventions.xml+759−538 doc/configuration.xml+329−284 doc/contributing.xml+28−13 doc/cross-compilation.xml+434−267 doc/default.nix+38−106 doc/functions.xml+15−704 doc/functions/debug.xml+21 doc/functions/dockertools.xml+564 doc/functions/fhs-environments.xml+142 doc/functions/generators.xml+89 doc/functions/library.xml+15 doc/functions/library/asserts.xml+117 doc/functions/library/attrsets.xml+1731 doc/functions/overrides.xml+212 doc/functions/shell.xml+26 doc/introduction.chapter.md+51 doc/introduction.md−51 doc/languages-frameworks/beam.xml+277−223 doc/languages-frameworks/bower.xml+137−152 doc/languages-frameworks/coq.xml+30−29 doc/languages-frameworks/emscripten.section.md+185 doc/languages-frameworks/go.xml+84−90 doc/languages-frameworks/haskell.md−955 doc/languages-frameworks/haskell.section.md+1091 doc/languages-frameworks/idris.section.md+115 doc/languages-frameworks/index.xml+28−31 doc/languages-frameworks/java.xml+50−50 doc/languages-frameworks/lua.xml+20−23 doc/languages-frameworks/node.section.md+51 doc/languages-frameworks/ocaml.xml+99 doc/languages-frameworks/perl.xml+117−106 doc/languages-frameworks/python.md−1024 doc/languages-frameworks/python.section.md+1109 doc/languages-frameworks/qt.xml+62−46 doc/languages-frameworks/r.section.md+120 doc/languages-frameworks/ruby.xml+47−45 doc/languages-frameworks/rust.md−309 doc/languages-frameworks/rust.section.md+395 doc/languages-frameworks/texlive.xml+72−33 doc/languages-frameworks/vim.md−135 doc/languages-frameworks/vim.section.md+235 doc/lib-function-locations.nix+85 doc/manual.xml+21−26 doc/meta.xml+366−256 doc/multiple-output.xml+300−80 doc/old/cross.txt+2−2 doc/overlays.xml+172−111 doc/overrides.css+9 doc/package-notes.xml+653−485 doc/platform-notes.xml+68−46 doc/quick-start.xml+185−189 doc/release-notes.xml+710−643 doc/reviewing-contributions.xml+488−263 doc/shell.md−20 doc/shell.nix+5 doc/stdenv.xml+2515−1850 doc/style.css+23−7 doc/submitting-changes.xml+463−399 lib/asserts.nix+44 lib/attrsets.nix+16−11 lib/composable-derivation.nix+1−1 lib/customisation.nix+5−15 lib/debug.nix+194−66 lib/default.nix+40−34 lib/generators.nix+106−16 lib/kernel.nix+57 lib/licenses.nix+94−1 lib/lists.nix+195−48 lib/maintainers.nix−799 lib/meta.nix+19 lib/minver.nix+1−1 lib/modules.nix+86−49 lib/options.nix+99−26 lib/sources.nix+7−3 lib/strings.nix+215−59 lib/systems/default.nix+41−6 lib/systems/doubles.nix+11−7 lib/systems/examples.nix+114−23 lib/systems/for-meta.nix+37 lib/systems/inspect.nix+46−33 lib/systems/parse.nix+105−31 lib/systems/platforms.nix+149−235 lib/tests/check-eval.nix+7 lib/tests/misc.nix+89−8 lib/tests/modules.sh+12−1 lib/tests/modules/declare-coerced-value-unsound.nix+10 lib/tests/modules/define-value-string-arbitrary.nix+3 lib/tests/modules/define-value-string-bigint.nix+3 lib/tests/modules/loaOf-with-long-list.nix+19 lib/tests/modules/loaOf-with-many-list-merges.nix+19 lib/tests/release.nix+1−2 lib/tests/systems.nix+15−14 lib/trivial.nix+174−47 lib/types.nix+52−22 lib/versions.nix+47 lib/zip-int-bits.nix+39 maintainers/maintainer-list.nix+4895 maintainers/scripts/all-tarballs.nix+3−5 maintainers/scripts/check-maintainer-github-handles.sh+66 maintainers/scripts/copy-tarballs.pl+8−2 maintainers/scripts/gnome.sh−192 maintainers/scripts/hydra-eval-failures.py+20−15 maintainers/scripts/nix-generate-from-cpan.nix+1−1 maintainers/scripts/nixpkgs-lint.pl+2−1 maintainers/scripts/update-python-libraries+3−3 maintainers/scripts/update.nix+45−17 maintainers/scripts/vanity.sh+1−1 nixos/doc/manual/.gitignore+2 nixos/doc/manual/Makefile+29 nixos/doc/manual/administration/boot-problems.xml+83−58 nixos/doc/manual/administration/cleaning-store.xml+40−39 nixos/doc/manual/administration/container-networking.xml+39−38 nixos/doc/manual/administration/containers.xml+28−28 nixos/doc/manual/administration/control-groups.xml+38−46 nixos/doc/manual/administration/declarative-containers.xml+44−44 nixos/doc/manual/administration/imperative-containers.xml+66−83 nixos/doc/manual/administration/logging.xml+21−30 nixos/doc/manual/administration/maintenance-mode.xml+7−9 nixos/doc/manual/administration/network-problems.xml+14−20 nixos/doc/manual/administration/rebooting.xml+20−29 nixos/doc/manual/administration/rollback.xml+23−30 nixos/doc/manual/administration/running.xml+15−18 nixos/doc/manual/administration/service-mgmt.xml+31−42 nixos/doc/manual/administration/store-corruption.xml+23−24 nixos/doc/manual/administration/troubleshooting.xml+10−12 nixos/doc/manual/administration/user-sessions.xml+15−23 nixos/doc/manual/configuration/abstractions.xml+57−67 nixos/doc/manual/configuration/ad-hoc-network-config.xml+8−12 nixos/doc/manual/configuration/ad-hoc-packages.xml+38−40 nixos/doc/manual/configuration/adding-custom-packages.xml+28−39 nixos/doc/manual/configuration/config-file.xml+131−138 nixos/doc/manual/configuration/config-syntax.xml+18−20 nixos/doc/manual/configuration/configuration.xml+20−26 nixos/doc/manual/configuration/customizing-packages.xml+61−68 nixos/doc/manual/configuration/declarative-packages.xml+26−26 nixos/doc/manual/configuration/file-systems.xml+35−35 nixos/doc/manual/configuration/firewall.xml+21−35 nixos/doc/manual/configuration/ipv4-config.xml+30−31 nixos/doc/manual/configuration/ipv6-config.xml+29−25 nixos/doc/manual/configuration/linux-kernel.xml+99−51 nixos/doc/manual/configuration/luks-file-systems.xml+15−21 nixos/doc/manual/configuration/modularity.xml+81−93 nixos/doc/manual/configuration/network-manager.xml+32−29 nixos/doc/manual/configuration/networking.xml+12−15 nixos/doc/manual/configuration/package-mgmt.xml+25−28 nixos/doc/manual/configuration/profiles.xml+39 nixos/doc/manual/configuration/profiles/all-hardware.xml+20 nixos/doc/manual/configuration/profiles/base.xml+15 nixos/doc/manual/configuration/profiles/clone-config.xml+14 nixos/doc/manual/configuration/profiles/demo.xml+13 nixos/doc/manual/configuration/profiles/docker-container.xml+15 nixos/doc/manual/configuration/profiles/graphical.xml+21 nixos/doc/manual/configuration/profiles/hardened.xml+22 nixos/doc/manual/configuration/profiles/headless.xml+18 nixos/doc/manual/configuration/profiles/installation-device.xml+35 nixos/doc/manual/configuration/profiles/minimal.xml+17 nixos/doc/manual/configuration/profiles/qemu-guest.xml+16 nixos/doc/manual/configuration/ssh.xml+14−19 nixos/doc/manual/configuration/summary.xml+202−167 nixos/doc/manual/configuration/user-mgmt.xml+64−76 nixos/doc/manual/configuration/wireless.xml+24−32 nixos/doc/manual/configuration/x-windows.xml+101−105 nixos/doc/manual/configuration/xfce.xml+57−79 nixos/doc/manual/default.nix+40−23 nixos/doc/manual/development/assertions.xml+29−35 nixos/doc/manual/development/building-nixos.xml+15−20 nixos/doc/manual/development/building-parts.xml+87−79 nixos/doc/manual/development/debugging-nixos-tests.xml+37 nixos/doc/manual/development/development.xml+14−17 nixos/doc/manual/development/importing-modules.xml+56 nixos/doc/manual/development/meta-attributes.xml+28−27 nixos/doc/manual/development/nixos-tests.xml+13−13 nixos/doc/manual/development/option-declarations.xml+146−113 nixos/doc/manual/development/option-def.xml+49−62 nixos/doc/manual/development/option-types.xml+681−421 nixos/doc/manual/development/releases.xml+215−209 nixos/doc/manual/development/replace-modules.xml+26−22 nixos/doc/manual/development/running-nixos-tests-interactively.xml+22−21 nixos/doc/manual/development/running-nixos-tests.xml+13−18 nixos/doc/manual/development/sources.xml+50−67 nixos/doc/manual/development/testing-installer.xml+11−16 nixos/doc/manual/development/writing-documentation.xml+140−138 nixos/doc/manual/development/writing-modules.xml+95−94 nixos/doc/manual/development/writing-nixos-tests.xml+366−253 nixos/doc/manual/installation/changing-config.xml+58−75 nixos/doc/manual/installation/installation.xml+11−15 nixos/doc/manual/installation/installing-behind-a-proxy.xml+48 nixos/doc/manual/installation/installing-from-other-distro.xml+356 nixos/doc/manual/installation/installing-pxe.xml+33−31 nixos/doc/manual/installation/installing-usb.xml+22−41 nixos/doc/manual/installation/installing-virtualbox-guest.xml+61−43 nixos/doc/manual/installation/installing.xml+490−337 nixos/doc/manual/installation/obtaining.xml+45−39 nixos/doc/manual/installation/upgrading.xml+102−109 nixos/doc/manual/man-configuration.xml+26−33 nixos/doc/manual/man-nixos-build-vms.xml+86−76 nixos/doc/manual/man-nixos-enter.xml+138 nixos/doc/manual/man-nixos-generate-config.xml+152−146 nixos/doc/manual/man-nixos-install.xml+230−186 nixos/doc/manual/man-nixos-option.xml+101−98 nixos/doc/manual/man-nixos-rebuild.xml+423−354 nixos/doc/manual/man-nixos-version.xml+97−82 nixos/doc/manual/man-pages.xml+16−28 nixos/doc/manual/manual.xml+41−40 nixos/doc/manual/options-to-docbook.xsl+11−8 nixos/doc/manual/postprocess-option-descriptions.xsl+115 nixos/doc/manual/release-notes/release-notes.xml+16−16 nixos/doc/manual/release-notes/rl-1310.xml+4−4 nixos/doc/manual/release-notes/rl-1404.xml+150−131 nixos/doc/manual/release-notes/rl-1412.xml+454−164 nixos/doc/manual/release-notes/rl-1509.xml+640−381 nixos/doc/manual/release-notes/rl-1603.xml+529−311 nixos/doc/manual/release-notes/rl-1609.xml+205−167 nixos/doc/manual/release-notes/rl-1703.xml+685−382 nixos/doc/manual/release-notes/rl-1709.xml+732−444 nixos/doc/manual/release-notes/rl-1803.xml+777−306 nixos/doc/manual/release-notes/rl-1809.xml+932 nixos/doc/manual/release-notes/rl-1903.xml+265 nixos/doc/manual/shell.nix+8 nixos/doc/manual/style.css−267 nixos/doc/varlistentry-fixer.rb+124 nixos/doc/xmlformat.conf+73 nixos/lib/build-vms.nix+14−6 nixos/lib/eval-config.nix+9−4 nixos/lib/make-channel.nix+4 nixos/lib/make-disk-image.nix+26−25 nixos/lib/make-ext4-fs.nix+20−10 nixos/lib/make-iso9660-image.nix+4−5 nixos/lib/make-iso9660-image.sh+3−4 nixos/lib/make-squashfs.nix+5−37 nixos/lib/make-system-tarball.nix+12−4 nixos/lib/make-system-tarball.sh+2−3 nixos/lib/qemu-flags.nix+10−6 nixos/lib/test-driver/Machine.pm+19−6 nixos/lib/testing.nix+22−9 pkgs/development/libraries/javascript/jquery-ui/default.nix → nixos/lib/testing/jquery-ui.nix pkgs/development/libraries/javascript/jquery/default.nix → nixos/lib/testing/jquery.nix nixos/maintainers/option-usages.nix+5−5 nixos/maintainers/scripts/azure/create-azure.sh+1−1 nixos/maintainers/scripts/ec2/amazon-image.nix+5 nixos/maintainers/scripts/ec2/create-amis.sh+3−2 nixos/maintainers/scripts/gce/create-gce.sh+2−2 nixos/modules/config/fonts/fontconfig-ultimate.nix+1−3 nixos/modules/config/gnu.nix+2−2 nixos/modules/config/gtk/gtk-icon-cache.nix+86 nixos/modules/config/i18n.nix+1−1 nixos/modules/config/iproute2.nix+32 nixos/modules/config/krb5/default.nix+1−1 nixos/modules/config/ldap.nix+2−2 nixos/modules/config/networking.nix+47−32 nixos/modules/config/no-x-libs.nix+12−12 nixos/modules/config/nsswitch.nix+10−10 nixos/modules/config/power-management.nix+1−1 nixos/modules/config/pulseaudio.nix+34−8 nixos/modules/config/shells-environment.nix+29−13 nixos/modules/config/sysctl.nix+1−1 nixos/modules/config/system-path.nix+11−26 nixos/modules/config/unix-odbc-drivers.nix+1−1 nixos/modules/config/users-groups.nix+34−33 nixos/modules/config/vpnc.nix+1−1 nixos/modules/config/xdg/autostart.nix+22 nixos/modules/config/xdg/icons.nix+27 nixos/modules/config/xdg/menus.nix+25 nixos/modules/config/xdg/mime.nix+36 nixos/modules/config/zram.nix+5−5 nixos/modules/hardware/all-firmware.nix+2−1 nixos/modules/hardware/brightnessctl.nix+30 nixos/modules/hardware/ckb-next.nix+49 nixos/modules/hardware/ckb.nix−40 nixos/modules/hardware/digitalbitbox.nix+30 nixos/modules/hardware/network/smc-2632w/default.nix+1−1 nixos/modules/hardware/network/zydas-zd1211.nix+1−1 nixos/modules/hardware/nitrokey.nix+1−1 nixos/modules/hardware/onlykey.nix+33 nixos/modules/hardware/onlykey.udev+4 nixos/modules/hardware/opengl.nix+98−89 nixos/modules/hardware/steam-hardware.nix+25 nixos/modules/hardware/video/amdgpu-pro.nix+17−3 nixos/modules/hardware/video/ati.nix+2−2 nixos/modules/hardware/video/capture/mwprocapture.nix+1−1 nixos/modules/hardware/video/nvidia.nix+129−22 nixos/modules/hardware/video/uvcvideo/default.nix+64 nixos/modules/hardware/video/uvcvideo/uvcdynctrl-udev-rules.nix+44 nixos/modules/i18n/input-method/default.nix+1−1 nixos/modules/i18n/input-method/default.xml+210−109 nixos/modules/installer/cd-dvd/channel.nix+2 nixos/modules/installer/cd-dvd/installation-cd-base.nix+2−3 nixos/modules/installer/cd-dvd/installation-cd-graphical-base.nix+49 nixos/modules/installer/cd-dvd/installation-cd-graphical-gnome.nix+3−60 nixos/modules/installer/cd-dvd/installation-cd-graphical-kde-new-kernel.nix+1−1 nixos/modules/installer/cd-dvd/installation-cd-graphical-kde.nix+10−39 nixos/modules/installer/cd-dvd/installation-cd-minimal-new-kernel.nix+1−1 nixos/modules/installer/cd-dvd/installation-cd-minimal.nix+3−1 nixos/modules/installer/cd-dvd/iso-image.nix+270−54 nixos/modules/installer/cd-dvd/sd-image-aarch64.nix+2−7 nixos/modules/installer/cd-dvd/sd-image-armv7l-multiplatform.nix+2−7 nixos/modules/installer/cd-dvd/sd-image-raspberrypi.nix+21−13 nixos/modules/installer/cd-dvd/sd-image.nix+54−15 nixos/modules/installer/cd-dvd/system-tarball-fuloong2f.nix+1−1 nixos/modules/installer/cd-dvd/system-tarball-sheevaplug.nix+1−1 nixos/modules/installer/netboot/netboot-base.nix+1−4 nixos/modules/installer/netboot/netboot-minimal.nix+1−1 nixos/modules/installer/netboot/netboot.nix+3−4 nixos/modules/installer/scan/detected.nix+1−1 nixos/modules/installer/scan/not-detected.nix+3−6 nixos/modules/installer/tools/nix-fallback-paths.nix+4−4 nixos/modules/installer/tools/nixos-build-vms/build-vms.nix+5−1 nixos/modules/installer/tools/nixos-enter.sh+61 nixos/modules/installer/tools/nixos-generate-config.pl+15−6 nixos/modules/installer/tools/nixos-install.sh+69−131 nixos/modules/installer/tools/nixos-option.sh+12−4 nixos/modules/installer/tools/nixos-prepare-root.sh−104 nixos/modules/installer/tools/nixos-rebuild.sh+1−1 nixos/modules/installer/tools/tools.nix+11−23 nixos/modules/installer/virtualbox-demo.nix+43−2 nixos/modules/misc/assertions.nix+1−1 nixos/modules/misc/documentation.nix+199 nixos/modules/misc/extra-arguments.nix+1−1 nixos/modules/misc/ids.nix+74−18 nixos/modules/misc/label.nix+1−1 nixos/modules/misc/lib.nix+1−1 nixos/modules/misc/locate.nix+17−4 nixos/modules/misc/meta.nix+1−1 nixos/modules/misc/nixpkgs.nix+112−20 nixos/modules/misc/passthru.nix+1−1 nixos/modules/misc/version.nix+6−11 nixos/modules/module-list.nix+98−24 nixos/modules/profiles/all-hardware.nix+2−2 nixos/modules/profiles/base.nix+7−4 nixos/modules/profiles/clone-config.nix+9−1 nixos/modules/profiles/demo.nix+8−2 nixos/modules/profiles/docker-container.nix+1−3 nixos/modules/profiles/graphical.nix+6−3 nixos/modules/profiles/hardened.nix+7−13 nixos/modules/profiles/headless.nix+1−1 nixos/modules/profiles/installation-device.nix+14−5 nixos/modules/profiles/minimal.nix+2−4 nixos/modules/profiles/qemu-guest.nix+1−1 nixos/modules/programs/adb.nix+2−2 nixos/modules/programs/atop.nix+1−1 nixos/modules/programs/bash/bash.nix+20−12 nixos/modules/programs/bcc.nix+1−1 nixos/modules/programs/chromium.nix+5 nixos/modules/programs/dconf.nix+3−1 nixos/modules/programs/digitalbitbox/default.nix+39 nixos/modules/programs/digitalbitbox/doc.xml+74 nixos/modules/programs/dmrconfig.nix+38 nixos/modules/programs/environment.nix+1−4 nixos/modules/programs/firejail.nix+48 nixos/modules/programs/fish.nix+18−14 nixos/modules/programs/gphoto2.nix+2−2 nixos/modules/programs/iftop.nix+18 nixos/modules/programs/info.nix−30 nixos/modules/programs/less.nix+15−2 nixos/modules/programs/light.nix+3−2 nixos/modules/programs/man.nix−31 nixos/modules/programs/mosh.nix+18 nixos/modules/programs/npm.nix+3−1 nixos/modules/programs/nylas-mail.nix−1 nixos/modules/programs/plotinus.xml+22−17 nixos/modules/programs/rootston.nix−103 nixos/modules/programs/screen.nix+3−1 nixos/modules/programs/sedutil.nix+18 nixos/modules/programs/shell.nix+19−31 nixos/modules/programs/singularity.nix+20 nixos/modules/programs/ssh.nix+26−5 nixos/modules/programs/sway-beta.nix+79 nixos/modules/programs/sway.nix+1−1 nixos/modules/programs/systemtap.nix+1−1 nixos/modules/programs/thefuck.nix+3−3 nixos/modules/programs/tmux.nix+1−1 nixos/modules/programs/udevil.nix+14 nixos/modules/programs/wavemon.nix+28 nixos/modules/programs/wireshark.nix+1−1 nixos/modules/programs/xonsh.nix−2 nixos/modules/programs/xss-lock.nix+26 nixos/modules/programs/yabar.nix+15−2 nixos/modules/programs/zsh/oh-my-zsh.nix+47−5 nixos/modules/programs/zsh/oh-my-zsh.xml+155 nixos/modules/programs/zsh/zsh-autosuggestions.nix+60 nixos/modules/programs/zsh/zsh.nix+27−19 nixos/modules/rename.nix+72−14 nixos/modules/security/acme.nix+85−43 nixos/modules/security/acme.xml+63−57 nixos/modules/security/apparmor-suid.nix+1−1 nixos/modules/security/audit.nix+3−3 nixos/modules/security/dhparams.nix+149−81 nixos/modules/security/duosec.nix+2−2 nixos/modules/security/hidepid.nix+1−1 nixos/modules/security/hidepid.xml+22−27 nixos/modules/security/lock-kernel-modules.nix+4 nixos/modules/security/misc.nix+39 nixos/modules/security/oath.nix+1−1 nixos/modules/security/pam.nix+23−5 nixos/modules/security/pam_mount.nix+1−1 nixos/modules/security/pam_usb.nix−2 nixos/modules/security/polkit.nix+6−6 nixos/modules/security/rngd.nix+1−3 nixos/modules/security/rtkit.nix+1−1 nixos/modules/security/sudo.nix+7−4 nixos/modules/security/wrappers/default.nix−29 nixos/modules/security/wrappers/wrapper.c+1−1 nixos/modules/services/admin/oxidized.nix+116 nixos/modules/services/admin/salt/master.nix+3 nixos/modules/services/admin/salt/minion.nix+16−5 nixos/modules/services/amqp/activemq/default.nix+2−2 nixos/modules/services/amqp/rabbitmq.nix+92−21 nixos/modules/services/audio/alsa.nix+8−7 nixos/modules/services/audio/liquidsoap.nix+2−2 nixos/modules/services/audio/mopidy.nix+2−2 nixos/modules/services/audio/mpd.nix+10−7 nixos/modules/services/audio/slimserver.nix+2−1 nixos/modules/services/audio/squeezelite.nix+1−1 nixos/modules/services/backup/almir.nix−173 nixos/modules/services/backup/bacula.nix+22−21 nixos/modules/services/backup/borgbackup.nix+616 nixos/modules/services/backup/crashplan-small-business.nix−1 nixos/modules/services/backup/crashplan.nix−1 nixos/modules/services/backup/duplicati.nix+57 nixos/modules/services/backup/mysql-backup.nix+1−1 nixos/modules/services/backup/postgresql-backup.nix+47−17 nixos/modules/services/backup/restic-rest-server.nix+107 nixos/modules/services/backup/restic.nix+160 nixos/modules/services/backup/tarsnap.nix+60−7 nixos/modules/services/backup/znapzend.nix+1−8 nixos/modules/services/cluster/fleet.nix−150 nixos/modules/services/cluster/hadoop/conf.nix+31 nixos/modules/services/cluster/hadoop/default.nix+60 nixos/modules/services/cluster/hadoop/hdfs.nix+73 nixos/modules/services/cluster/hadoop/yarn.nix+74 nixos/modules/services/cluster/kubernetes/dashboard.nix+200−39 nixos/modules/services/cluster/kubernetes/default.nix+100−47 nixos/modules/services/cluster/kubernetes/dns.nix+196−187 nixos/modules/services/cluster/panamax.nix−156 nixos/modules/services/computing/boinc/client.nix+45−1 nixos/modules/services/computing/slurm/slurm.nix+188−19 nixos/modules/services/continuous-integration/buildbot/master.nix+51−20 nixos/modules/services/continuous-integration/buildbot/worker.nix+68−13 nixos/modules/services/continuous-integration/buildkite-agent.nix+3−3 nixos/modules/services/continuous-integration/gitlab-runner.nix+2−2 nixos/modules/services/continuous-integration/gocd-agent/default.nix+2−2 nixos/modules/services/continuous-integration/gocd-server/default.nix+4−4 nixos/modules/services/continuous-integration/hydra/default.nix+4−4 nixos/modules/services/continuous-integration/jenkins/default.nix+10−3 nixos/modules/services/continuous-integration/jenkins/slave.nix+3−3 nixos/modules/services/databases/4store-endpoint.nix+2−2 nixos/modules/services/databases/4store.nix+2−2 nixos/modules/services/databases/aerospike.nix+155 nixos/modules/services/databases/cassandra.nix+243−400 nixos/modules/services/databases/clickhouse.nix+2−2 nixos/modules/services/databases/couchdb.nix+2−2 nixos/modules/services/databases/firebird.nix+2−2 nixos/modules/services/databases/foundationdb.nix+416 nixos/modules/services/databases/foundationdb.xml+443 nixos/modules/services/databases/hbase.nix+2−2 nixos/modules/services/databases/influxdb.nix+2−2 nixos/modules/services/databases/memcached.nix+1−1 nixos/modules/services/databases/monetdb.nix+100 nixos/modules/services/databases/mongodb.nix+1−1 nixos/modules/services/databases/mysql.nix+19−17 nixos/modules/services/databases/neo4j.nix+590−87 nixos/modules/services/databases/openldap.nix+48−8 nixos/modules/services/databases/opentsdb.nix+2−2 nixos/modules/services/databases/pgmanage.nix+28−44 nixos/modules/services/databases/postgresql.nix+13−15 nixos/modules/services/databases/postgresql.xml+50−50 nixos/modules/services/databases/redis.nix+1−1 nixos/modules/services/databases/rethinkdb.nix+2−2 nixos/modules/services/databases/riak-cs.nix+1−1 nixos/modules/services/databases/riak.nix+2−2 nixos/modules/services/databases/stanchion.nix+2−2 nixos/modules/services/databases/virtuoso.nix+1−1 nixos/modules/services/desktops/accountsservice.nix+8−2 nixos/modules/services/desktops/bamf.nix+23 nixos/modules/services/desktops/flatpak.nix+52 nixos/modules/services/desktops/flatpak.xml+56 nixos/modules/services/desktops/geoclue2.nix+32−7 nixos/modules/services/desktops/gnome3/at-spi2-core.nix+3−3 nixos/modules/services/desktops/gnome3/evolution-data-server.nix+3−3 nixos/modules/services/desktops/gnome3/gnome-keyring.nix+2−2 nixos/modules/services/desktops/gnome3/gnome-online-accounts.nix+2−2 nixos/modules/services/desktops/gnome3/gnome-terminal-server.nix+3−3 nixos/modules/services/desktops/gnome3/rygel.nix+30 nixos/modules/services/desktops/gsignond.nix+43 nixos/modules/services/desktops/pipewire.nix+18−4 nixos/modules/services/desktops/profile-sync-daemon.nix+34−102 nixos/modules/services/desktops/telepathy.nix+2−2 nixos/modules/services/desktops/zeitgeist.nix+26 nixos/modules/services/development/bloop.nix+37 nixos/modules/services/development/hoogle.nix+7−1 nixos/modules/services/development/jupyter/default.nix+185 nixos/modules/services/development/jupyter/kernel-options.nix+60 nixos/modules/services/editors/emacs.nix+21−2 nixos/modules/services/editors/emacs.xml+409−442 nixos/modules/services/editors/infinoted.nix+6−6 nixos/modules/services/games/minecraft-server.nix+1−1 nixos/modules/services/games/minetest-server.nix+4−1 nixos/modules/services/games/terraria.nix+15−5 nixos/modules/services/hardware/actkbd.nix+1−1 nixos/modules/services/hardware/bluetooth.nix+11−1 nixos/modules/services/hardware/fwupd.nix+9−6 nixos/modules/services/hardware/lcd.nix+172 nixos/modules/services/hardware/lirc.nix+89 nixos/modules/services/hardware/nvidia-optimus.nix+1−1 nixos/modules/services/hardware/pcscd.nix+2−2 nixos/modules/services/hardware/ratbagd.nix+32 nixos/modules/services/hardware/sane.nix+2−2 nixos/modules/services/hardware/sane_extra_backends/brscan4.nix+1−1 nixos/modules/services/hardware/tcsd.nix+2−2 nixos/modules/services/hardware/thermald.nix+29−7 nixos/modules/services/hardware/thinkfan.nix+46−9 nixos/modules/services/hardware/trezord.nix+9−3 nixos/modules/services/hardware/triggerhappy.nix+114 nixos/modules/services/hardware/udev.nix+1−3 nixos/modules/services/hardware/udisks2.nix+2−9 nixos/modules/services/hardware/undervolt.nix+134 nixos/modules/services/hardware/upower.nix+26 nixos/modules/services/hardware/usbmuxd.nix+3−3 nixos/modules/services/logging/graylog.nix+2−2 nixos/modules/services/logging/journaldriver.nix+112 nixos/modules/services/logging/journalwatch.nix+3−3 nixos/modules/services/logging/logcheck.nix+1−1 nixos/modules/services/logging/logstash.nix+6−37 nixos/modules/services/logging/syslog-ng.nix+2 nixos/modules/services/mail/clamsmtp.nix+2 nixos/modules/services/mail/dkimproxy-out.nix+2 nixos/modules/services/mail/dovecot.nix+15−8 nixos/modules/services/mail/dspam.nix+2−2 nixos/modules/services/mail/exim.nix+17−6 nixos/modules/services/mail/mail.nix+1−1 nixos/modules/services/mail/mailhog.nix+1−1 nixos/modules/services/mail/mlmmj.nix+2−2 nixos/modules/services/mail/nullmailer.nix+2−2 nixos/modules/services/mail/opendkim.nix+2−2 nixos/modules/services/mail/opensmtpd.nix+12−5 nixos/modules/services/mail/postfix.nix+19−3 nixos/modules/services/mail/postgrey.nix+2−2 nixos/modules/services/mail/postsrsd.nix+2−2 nixos/modules/services/mail/rmilter.nix+9−6 nixos/modules/services/mail/rspamd.nix+161−94 nixos/modules/services/mail/spamassassin.nix+2−2 nixos/modules/services/misc/airsonic.nix+20−1 nixos/modules/services/misc/apache-kafka.nix+1−1 nixos/modules/services/misc/autorandr.nix+21−3 nixos/modules/services/misc/bepasty.nix+2−2 nixos/modules/services/misc/calibre-server.nix+2−2 nixos/modules/services/misc/cfdyndns.nix+2−2 nixos/modules/services/misc/cgminer.nix+1−1 nixos/modules/services/misc/clipmenu.nix+31 nixos/modules/services/misc/couchpotato.nix+2−2 nixos/modules/services/misc/defaultUnicornConfig.rb+52−188 nixos/modules/services/misc/dictd.nix+2−2 nixos/modules/services/misc/disnix.nix+11−15 nixos/modules/services/misc/docker-registry.nix+92−10 nixos/modules/services/misc/dysnomia.nix+25−28 nixos/modules/services/misc/emby.nix+16−10 nixos/modules/services/misc/errbot.nix+2−2 nixos/modules/services/misc/etcd.nix+1−1 nixos/modules/services/misc/exhibitor.nix+4−2 nixos/modules/services/misc/felix.nix+2−2 nixos/modules/services/misc/folding-at-home.nix+2−2 nixos/modules/services/misc/gammu-smsd.nix+1−1 nixos/modules/services/misc/geoip-updater.nix+2−2 nixos/modules/services/misc/gitea.nix+140−13 nixos/modules/services/misc/gitit.nix+7−7 nixos/modules/services/misc/gitlab.nix+120−141 nixos/modules/services/misc/gitlab.xml+93−88 nixos/modules/services/misc/gitolite.nix+2−2 nixos/modules/services/misc/gitweb.nix+59 nixos/modules/services/misc/gogs.nix+5−2 nixos/modules/services/misc/gollum.nix+2−2 nixos/modules/services/misc/gpsd.nix+12−3 nixos/modules/services/misc/home-assistant.nix+61−11 nixos/modules/services/misc/ihaskell.nix+6−6 nixos/modules/services/misc/jackett.nix+3−3 nixos/modules/services/misc/leaps.nix+1−1 nixos/modules/services/misc/lidarr.nix+46 nixos/modules/services/misc/logkeys.nix+8−1 nixos/modules/services/misc/mathics.nix+5−5 nixos/modules/services/misc/matrix-synapse.nix+11−11 nixos/modules/services/misc/mediatomb.nix+2−3 nixos/modules/services/misc/mesos-slave.nix+3−3 nixos/modules/services/misc/nix-daemon.nix+42−21 nixos/modules/services/misc/nix-gc.nix+1−1 nixos/modules/services/misc/nix-optimise.nix+3−1 nixos/modules/services/misc/nix-ssh-serve.nix+19−9 nixos/modules/services/misc/nixos-manual.nix+29−100 nixos/modules/services/misc/nzbget.nix+3−3 nixos/modules/services/misc/octoprint.nix+2−2 nixos/modules/services/misc/osrm.nix+1−1 nixos/modules/services/misc/packagekit.nix−3 nixos/modules/services/misc/parsoid.nix+3−1 nixos/modules/services/misc/plex.nix+2−3 nixos/modules/services/misc/plexpy.nix+1−1 nixos/modules/services/misc/pykms.nix+2−2 nixos/modules/services/misc/radarr.nix+3−3 nixos/modules/services/misc/redmine.nix+241−121 nixos/modules/services/misc/ripple-data-api.nix+1−1 nixos/modules/services/misc/rippled.nix+1−1 nixos/modules/services/misc/safeeyes.nix+50 nixos/modules/services/misc/serviio.nix+92 nixos/modules/services/misc/sickbeard.nix+92 nixos/modules/services/misc/siproxd.nix+1−1 nixos/modules/services/misc/sonarr.nix+3−3 nixos/modules/services/misc/ssm-agent.nix+1−1 nixos/modules/services/misc/subsonic.nix+3−3 nixos/modules/services/misc/synergy.nix+6−6 nixos/modules/services/misc/sysprof.nix+19 nixos/modules/services/misc/taskserver/default.nix+1−11 nixos/modules/services/misc/taskserver/doc.xml+104−113 nixos/modules/services/misc/uhub.nix+2−2 nixos/modules/services/misc/weechat.nix+58 nixos/modules/services/misc/weechat.xml+66 nixos/modules/services/misc/xmr-stak.nix+40−20 nixos/modules/services/misc/zookeeper.nix+1−1 nixos/modules/services/monitoring/alerta.nix+116 nixos/modules/services/monitoring/apcupsd.nix+1−1 nixos/modules/services/monitoring/bosun.nix+2−2 nixos/modules/services/monitoring/collectd.nix+1−1 nixos/modules/services/monitoring/datadog-agent.nix+271 nixos/modules/services/monitoring/dd-agent/dd-agent.nix+49−47 nixos/modules/services/monitoring/fusion-inventory.nix+1−1 nixos/modules/services/monitoring/grafana-reporter.nix+66 nixos/modules/services/monitoring/grafana.nix+127−10 nixos/modules/services/monitoring/graphite.nix+15−23 nixos/modules/services/monitoring/heapster.nix+1−1 nixos/modules/services/monitoring/incron.nix+98 nixos/modules/services/monitoring/kapacitor.nix+192 nixos/modules/services/monitoring/monit.nix+20−27 nixos/modules/services/monitoring/munin.nix+8−8 nixos/modules/services/monitoring/nagios.nix+1−1 nixos/modules/services/monitoring/netdata.nix+6−2 nixos/modules/services/monitoring/prometheus/alertmanager.nix+18−5 nixos/modules/services/monitoring/prometheus/blackbox-exporter.nix−68 nixos/modules/services/monitoring/prometheus/collectd-exporter.nix−128 nixos/modules/services/monitoring/prometheus/default.nix+36−8 nixos/modules/services/monitoring/prometheus/exporters.nix+178 nixos/modules/services/monitoring/prometheus/exporters.xml+187 nixos/modules/services/monitoring/prometheus/exporters/blackbox.nix+31 nixos/modules/services/monitoring/prometheus/exporters/collectd.nix+78 nixos/modules/services/monitoring/prometheus/exporters/dnsmasq.nix+39 nixos/modules/services/monitoring/prometheus/exporters/dovecot.nix+50 nixos/modules/services/monitoring/prometheus/exporters/fritzbox.nix+39 nixos/modules/services/monitoring/prometheus/exporters/json.nix+36 nixos/modules/services/monitoring/prometheus/exporters/minio.nix+65 nixos/modules/services/monitoring/prometheus/exporters/nginx.nix+47 nixos/modules/services/monitoring/prometheus/exporters/node.nix+40 nixos/modules/services/monitoring/prometheus/exporters/postfix.nix+81 nixos/modules/services/monitoring/prometheus/exporters/snmp.nix+71 nixos/modules/services/monitoring/prometheus/exporters/surfboard.nix+32 nixos/modules/services/monitoring/prometheus/exporters/tor.nix+40 nixos/modules/services/monitoring/prometheus/exporters/unifi.nix+67 nixos/modules/services/monitoring/prometheus/exporters/varnish.nix+88 nixos/modules/services/monitoring/prometheus/fritzbox-exporter.nix−76 nixos/modules/services/monitoring/prometheus/json-exporter.nix−74 nixos/modules/services/monitoring/prometheus/minio-exporter.nix−117 nixos/modules/services/monitoring/prometheus/nginx-exporter.nix−78 nixos/modules/services/monitoring/prometheus/node-exporter.nix−87 nixos/modules/services/monitoring/prometheus/snmp-exporter.nix−127 nixos/modules/services/monitoring/prometheus/unifi-exporter.nix−105 nixos/modules/services/monitoring/prometheus/varnish-exporter.nix−61 nixos/modules/services/monitoring/riemann-dash.nix+2−2 nixos/modules/services/monitoring/riemann-tools.nix+2−2 nixos/modules/services/monitoring/riemann.nix+20−6 nixos/modules/services/monitoring/scollector.nix+2−2 nixos/modules/services/monitoring/smartd.nix+2−2 nixos/modules/services/monitoring/statsd.nix+1−1 nixos/modules/services/monitoring/telegraf.nix+1−1 nixos/modules/services/monitoring/ups.nix+2−2 nixos/modules/services/monitoring/uptime.nix+1−1 nixos/modules/services/monitoring/vnstat.nix+1−1 nixos/modules/services/monitoring/zabbix-agent.nix+15−3 nixos/modules/services/monitoring/zabbix-server.nix+3−3 nixos/modules/services/network-filesystems/beegfs.nix+13−2 nixos/modules/services/network-filesystems/ceph.nix+371 nixos/modules/services/network-filesystems/davfs2.nix+2−2 nixos/modules/services/network-filesystems/glusterfs.nix+4−3 nixos/modules/services/network-filesystems/ipfs.nix+17−3 nixos/modules/services/network-filesystems/openafs/client.nix+21−7 nixos/modules/services/network-filesystems/openafs/lib.nix+7−2 nixos/modules/services/network-filesystems/openafs/server.nix+23−14 nixos/modules/services/network-filesystems/samba.nix+4−6 nixos/modules/services/network-filesystems/tahoe.nix+2−2 nixos/modules/services/network-filesystems/xtreemfs.nix+3−3 nixos/modules/services/network-filesystems/yandex-disk.nix+3−3 nixos/modules/services/networking/amuled.nix+3−3 nixos/modules/services/networking/aria2.nix+2−2 nixos/modules/services/networking/asterisk.nix+2−2 nixos/modules/services/networking/avahi-daemon.nix+12−3 nixos/modules/services/networking/bind.nix+11−1 nixos/modules/services/networking/bird.nix+3−2 nixos/modules/services/networking/bitlbee.nix+29−14 nixos/modules/services/networking/btsync.nix+2−2 nixos/modules/services/networking/charybdis.nix+3−3 nixos/modules/services/networking/chrony.nix+25−37 nixos/modules/services/networking/cjdns.nix+3−2 nixos/modules/services/networking/cntlm.nix+1−1 nixos/modules/services/networking/consul.nix+5−4 nixos/modules/services/networking/coturn.nix+2−2 nixos/modules/services/networking/dante.nix+7−6 nixos/modules/services/networking/ddclient.nix+60−53 nixos/modules/services/networking/dhcpcd.nix+3−2 nixos/modules/services/networking/dhcpd.nix+2−1 nixos/modules/services/networking/dnscache.nix+25−8 nixos/modules/services/networking/dnschain.nix+1−1 nixos/modules/services/networking/dnscrypt-proxy.nix+7 nixos/modules/services/networking/dnscrypt-proxy.xml+43−46 nixos/modules/services/networking/dnsdist.nix+61 nixos/modules/services/networking/dnsmasq.nix+1−1 nixos/modules/services/networking/ejabberd.nix+2−2 nixos/modules/services/networking/epmd.nix+56 nixos/modules/services/networking/eternal-terminal.nix+89 nixos/modules/services/networking/firewall.nix+235−211 nixos/modules/services/networking/flashpolicyd.nix+1−1 nixos/modules/services/networking/freenet.nix+2−2 nixos/modules/services/networking/freeradius.nix+1−1 nixos/modules/services/networking/gale.nix+2−2 nixos/modules/services/networking/gateone.nix+2−2 nixos/modules/services/networking/gdomap.nix−3 nixos/modules/services/networking/git-daemon.nix+2−2 nixos/modules/services/networking/gnunet.nix+13−5 nixos/modules/services/networking/hans.nix+145 nixos/modules/services/networking/haproxy.nix+2−2 nixos/modules/services/networking/hostapd.nix+4−9 nixos/modules/services/networking/hylafax/default.nix+29 nixos/modules/services/networking/hylafax/faxq-default.nix+12 nixos/modules/services/networking/hylafax/faxq-wait.sh+29 nixos/modules/services/networking/hylafax/hfaxd-default.nix+10 nixos/modules/services/networking/hylafax/modem-default.nix+22 nixos/modules/services/networking/hylafax/options.nix+375 nixos/modules/services/networking/hylafax/spool.sh+111 nixos/modules/services/networking/hylafax/systemd.nix+249 nixos/modules/services/networking/i2p.nix+2−2 nixos/modules/services/networking/i2pd.nix+405−207 nixos/modules/services/networking/iodine.nix+19−7 nixos/modules/services/networking/iperf3.nix+87 nixos/modules/services/networking/ircd-hybrid/default.nix+2−2 nixos/modules/services/networking/iwd.nix+7−8 nixos/modules/services/networking/keepalived/default.nix+60−2 nixos/modules/services/networking/keepalived/vrrp-instance-options.nix+135 nixos/modules/services/networking/keepalived/vrrp-options.nix−121 nixos/modules/services/networking/keepalived/vrrp-script-options.nix+64 nixos/modules/services/networking/kippo.nix+2−2 nixos/modules/services/networking/kresd.nix+2−2 nixos/modules/services/networking/lambdabot.nix+2−2 nixos/modules/services/networking/lldpd.nix+2−2 nixos/modules/services/networking/mailpile.nix+2−2 nixos/modules/services/networking/matterbridge.nix+53−31 nixos/modules/services/networking/minidlna.nix+31−16 nixos/modules/services/networking/miniupnpd.nix+2−22 nixos/modules/services/networking/mjpg-streamer.nix+1−1 nixos/modules/services/networking/monero.nix+2−2 nixos/modules/services/networking/morty.nix+96 nixos/modules/services/networking/mosquitto.nix+2−2 nixos/modules/services/networking/murmur.nix+5−4 nixos/modules/services/networking/namecoind.nix+2−2 nixos/modules/services/networking/nat.nix+15−5 nixos/modules/services/networking/ndppd.nix+47 nixos/modules/services/networking/networkmanager.nix+200−39 nixos/modules/services/networking/nftables.nix+1−1 nixos/modules/services/networking/nghttpx/nghttpx-options.nix+1−1 nixos/modules/services/networking/ngircd.nix+1−1 nixos/modules/services/networking/nix-serve.nix+3−1 nixos/modules/services/networking/nntp-proxy.nix+1−1 nixos/modules/services/networking/nsd.nix+143−10 nixos/modules/services/networking/ntpd.nix+3−1 nixos/modules/services/networking/nullidentdmod.nix+34 nixos/modules/services/networking/nylon.nix+3−3 nixos/modules/services/networking/ocserv.nix+99 nixos/modules/services/networking/oidentd.nix+2−2 nixos/modules/services/networking/openntpd.nix+7−5 nixos/modules/services/networking/openvpn.nix+4−1 nixos/modules/services/networking/owamp.nix+47 nixos/modules/services/networking/pdns-recursor.nix+1−1 nixos/modules/services/networking/pdnsd.nix+2−2 nixos/modules/services/networking/polipo.nix+2−2 nixos/modules/services/networking/pptpd.nix+2−2 nixos/modules/services/networking/prayer.nix+2−2 nixos/modules/services/networking/prosody.nix+221−29 nixos/modules/services/networking/quagga.nix+17−18 nixos/modules/services/networking/quassel.nix+2−2 nixos/modules/services/networking/radicale.nix+2−2 nixos/modules/services/networking/radvd.nix+1−1 nixos/modules/services/networking/rdnssd.nix+2−2 nixos/modules/services/networking/redsocks.nix+2 nixos/modules/services/networking/resilio.nix+3−8 nixos/modules/services/networking/rpcbind.nix+1−1 nixos/modules/services/networking/sabnzbd.nix+2−2 nixos/modules/services/networking/searx.nix+2−2 nixos/modules/services/networking/seeks.nix+2−2 nixos/modules/services/networking/shadowsocks.nix+112 nixos/modules/services/networking/shairport-sync.nix+3−2 nixos/modules/services/networking/shout.nix+2−2 nixos/modules/services/networking/smokeping.nix+1−1 nixos/modules/services/networking/sniproxy.nix+2−2 nixos/modules/services/networking/spiped.nix+2−2 nixos/modules/services/networking/ssh/sshd.nix+117−17 nixos/modules/services/networking/sslh.nix+95−19 nixos/modules/services/networking/strongswan-swanctl/module.nix+82 nixos/modules/services/networking/strongswan-swanctl/param-constructors.nix+162 nixos/modules/services/networking/strongswan-swanctl/param-lib.nix+82 nixos/modules/services/networking/strongswan-swanctl/swanctl-params.nix+1254 nixos/modules/services/networking/strongswan.nix+19−4 nixos/modules/services/networking/stubby.nix+214 nixos/modules/services/networking/supplicant.nix+1−1 nixos/modules/services/networking/supybot.nix+2−2 nixos/modules/services/networking/syncthing.nix+36−27 nixos/modules/services/networking/tcpcrypt.nix+6−6 nixos/modules/services/networking/teamspeak3.nix+1−1 nixos/modules/services/networking/tinc.nix+6−16 nixos/modules/services/networking/tinydns.nix+1−1 nixos/modules/services/networking/tox-bootstrapd.nix+1−1 nixos/modules/services/networking/toxvpn.nix+2−2 nixos/modules/services/networking/tvheadend.nix+3−3 nixos/modules/services/networking/unbound.nix+8−3 nixos/modules/services/networking/unifi.nix+33−6 nixos/modules/services/networking/vsftpd.nix+3−3 nixos/modules/services/networking/wireguard.nix+55−53 nixos/modules/services/networking/wpa_supplicant.nix+12 nixos/modules/services/networking/xl2tpd.nix+2−2 nixos/modules/services/networking/xrdp.nix+9−4 nixos/modules/services/networking/zerobin.nix+1−1 nixos/modules/services/networking/zeronet.nix+114 nixos/modules/services/networking/zerotierone.nix+31−7 nixos/modules/services/networking/znc.nix−421 nixos/modules/services/networking/znc/default.nix+306 nixos/modules/services/networking/znc/options.nix+270 nixos/modules/services/printing/cupsd.nix+35−8 nixos/modules/services/scheduling/atd.nix+2−2 nixos/modules/services/scheduling/chronos.nix+1−1 nixos/modules/services/scheduling/fcron.nix+2−1 nixos/modules/services/scheduling/marathon.nix+1−1 nixos/modules/services/search/elasticsearch-curator.nix+93 nixos/modules/services/search/elasticsearch.nix+47−49 nixos/modules/services/search/hound.nix+2−2 nixos/modules/services/search/kibana.nix+2−38 nixos/modules/services/search/solr.nix+72−109 nixos/modules/services/security/certmgr.nix+194 nixos/modules/services/security/cfssl.nix+209 nixos/modules/services/security/clamav.nix+6−5 nixos/modules/services/security/fprot.nix+2−2 nixos/modules/services/security/hologram-server.nix+33−5 nixos/modules/services/security/munge.nix+14−2 nixos/modules/services/security/oauth2_proxy.nix+108−61 nixos/modules/services/security/oauth2_proxy_nginx.nix+64 nixos/modules/services/security/sks.nix+67−33 nixos/modules/services/security/sshguard.nix+1 nixos/modules/services/security/tor.nix+58−25 nixos/modules/services/security/torify.nix+1−1 nixos/modules/services/security/torsocks.nix+1−1 nixos/modules/services/security/usbguard.nix+5−2 nixos/modules/services/security/vault.nix+20−6 nixos/modules/services/system/cloud-init.nix+33−9 nixos/modules/services/system/dbus.nix+3−2 nixos/modules/services/system/kerberos.nix+5−5 nixos/modules/services/system/localtime.nix+2−8 nixos/modules/services/system/nscd.nix+1−3 nixos/modules/services/system/saslauthd.nix+1−2 nixos/modules/services/system/uptimed.nix+1−1 nixos/modules/services/torrent/deluge.nix+4−14 nixos/modules/services/torrent/flexget.nix+1−1 nixos/modules/services/torrent/peerflix.nix+1−1 nixos/modules/services/torrent/transmission.nix+20−13 nixos/modules/services/ttys/kmscon.nix+13−2 nixos/modules/services/web-apps/atlassian/confluence.nix+2−2 nixos/modules/services/web-apps/atlassian/crowd.nix+5−4 nixos/modules/services/web-apps/atlassian/jira.nix+3−3 nixos/modules/services/web-apps/codimd.nix+920 nixos/modules/services/web-apps/frab.nix+2−3 nixos/modules/services/web-apps/matomo-doc.xml+90 nixos/modules/services/web-apps/matomo.nix+253 nixos/modules/services/web-apps/mattermost.nix+6−6 nixos/modules/services/web-apps/nextcloud.nix+487 nixos/modules/services/web-apps/nexus.nix+44−10 nixos/modules/services/web-apps/nixbot.nix−149 nixos/modules/services/web-apps/piwik-doc.xml−95 nixos/modules/services/web-apps/piwik.nix−227 nixos/modules/services/web-apps/pump.io-configure.js−23 nixos/modules/services/web-apps/pump.io.nix−438 nixos/modules/services/web-apps/restya-board.nix+2−2 nixos/modules/services/web-apps/selfoss.nix+2−2 nixos/modules/services/web-apps/tt-rss.nix+50−6 nixos/modules/services/web-apps/virtlyst.nix+72 nixos/modules/services/web-apps/youtrack.nix+177 nixos/modules/services/web-servers/apache-httpd/default.nix+3−8 nixos/modules/services/web-servers/apache-httpd/limesurvey.nix+1−1 nixos/modules/services/web-servers/apache-httpd/mercurial.nix+1−1 nixos/modules/services/web-servers/apache-httpd/owncloud.nix+1−12 nixos/modules/services/web-servers/apache-httpd/per-server-options.nix+1−1 nixos/modules/services/web-servers/apache-httpd/trac.nix−2 nixos/modules/services/web-servers/apache-httpd/wordpress.nix+1−1 nixos/modules/services/web-servers/caddy.nix+4−4 nixos/modules/services/web-servers/hitch/default.nix+108 nixos/modules/services/web-servers/hydron.nix+167 nixos/modules/services/web-servers/lighttpd/cgit.nix+22−6 nixos/modules/services/web-servers/lighttpd/default.nix+2−2 nixos/modules/services/web-servers/lighttpd/gitweb.nix+8−27 nixos/modules/services/web-servers/lighttpd/inginious.nix−261 nixos/modules/services/web-servers/meguca.nix+158 nixos/modules/services/web-servers/mighttpd2.nix+2−2 nixos/modules/services/web-servers/minio.nix+3−3 nixos/modules/services/web-servers/nginx/default.nix+76−16 nixos/modules/services/web-servers/nginx/gitweb.nix+61 nixos/modules/services/web-servers/nginx/location-options.nix+10 nixos/modules/services/web-servers/nginx/vhost-options.nix+17−1 nixos/modules/services/web-servers/tomcat.nix+251−194 nixos/modules/services/web-servers/traefik.nix+2−2 nixos/modules/services/web-servers/uwsgi.nix+5−11 nixos/modules/services/web-servers/varnish/default.nix+16−7 nixos/modules/services/web-servers/zope2.nix+2−2 nixos/modules/services/x11/compton.nix+6 nixos/modules/services/x11/desktop-managers/default.nix+9−9 nixos/modules/services/x11/desktop-managers/enlightenment.nix+8−3 nixos/modules/services/x11/desktop-managers/gnome3.nix+36−42 nixos/modules/services/x11/desktop-managers/lumina.nix+1−2 nixos/modules/services/x11/desktop-managers/lxqt.nix+14−5 nixos/modules/services/x11/desktop-managers/mate.nix+3−1 nixos/modules/services/x11/desktop-managers/plasma5.nix+12−8 nixos/modules/services/x11/desktop-managers/xfce.nix+5−15 nixos/modules/services/x11/desktop-managers/xterm.nix+1 nixos/modules/services/x11/display-managers/auto.nix+20−4 nixos/modules/services/x11/display-managers/default.nix+71−56 nixos/modules/services/x11/display-managers/gdm.nix+30−10 nixos/modules/services/x11/display-managers/lightdm-greeters/enso-os.nix+159 nixos/modules/services/x11/display-managers/lightdm-greeters/gtk.nix+5−5 nixos/modules/services/x11/display-managers/lightdm-greeters/mini.nix+100 nixos/modules/services/x11/display-managers/lightdm.nix+53−28 nixos/modules/services/x11/display-managers/sddm.nix+40−20 nixos/modules/services/x11/display-managers/slim.nix+3−3 nixos/modules/services/x11/display-managers/startx.nix+44 nixos/modules/services/x11/display-managers/xpra.nix+20−24 nixos/modules/services/x11/gdk-pixbuf.nix+45 nixos/modules/services/x11/hardware/libinput.nix+2−2 nixos/modules/services/x11/redshift.nix+3 nixos/modules/services/x11/terminal-server.nix+1−1 nixos/modules/services/x11/window-managers/awesome.nix+6−1 nixos/modules/services/x11/window-managers/bspwm.nix+1−1 nixos/modules/services/x11/window-managers/default.nix+3−4 nixos/modules/services/x11/window-managers/metacity.nix+3−9 nixos/modules/services/x11/window-managers/openbox.nix−1 nixos/modules/services/x11/window-managers/stumpwm.nix+2−2 nixos/modules/services/x11/window-managers/wmii.nix+1−2 nixos/modules/services/x11/xserver.nix+42−24 nixos/modules/system/activation/activation-script.nix+64−19 nixos/modules/system/activation/switch-to-configuration.pl+40−10 nixos/modules/system/activation/top-level.nix+49−36 nixos/modules/system/boot/coredump.nix+5−2 nixos/modules/system/boot/grow-partition.nix+10−3 nixos/modules/system/boot/initrd-network.nix+35−5 nixos/modules/system/boot/initrd-ssh.nix+2−2 nixos/modules/system/boot/kernel.nix+2−2 nixos/modules/system/boot/kexec.nix+19−18 nixos/modules/system/boot/loader/generations-dir/generations-dir.nix+1−1 nixos/modules/system/boot/loader/grub/grub.nix+64−16 nixos/modules/system/boot/loader/grub/install-grub.pl+34−21 nixos/modules/system/boot/loader/loader.nix+1−1 nixos/modules/system/boot/loader/raspberrypi/builder.sh−122 nixos/modules/system/boot/loader/raspberrypi/raspberrypi-builder.nix+10 nixos/modules/system/boot/loader/raspberrypi/raspberrypi-builder.sh+132 nixos/modules/system/boot/loader/raspberrypi/raspberrypi.nix+85−25 nixos/modules/system/boot/loader/raspberrypi/uboot-builder.nix+35 nixos/modules/system/boot/loader/raspberrypi/uboot-builder.sh+38 nixos/modules/system/boot/loader/systemd-boot/systemd-boot-builder.py+2−1 nixos/modules/system/boot/loader/systemd-boot/systemd-boot.nix+34 nixos/modules/system/boot/luksroot.nix+246−123 nixos/modules/system/boot/modprobe.nix+1−1 nixos/modules/system/boot/networkd.nix+172−32 nixos/modules/system/boot/plymouth.nix+2−1 nixos/modules/system/boot/resolved.nix+3−1 nixos/modules/system/boot/stage-1-init.sh+36−36 nixos/modules/system/boot/stage-1.nix+65−8 nixos/modules/system/boot/stage-2-init.sh+13−6 nixos/modules/system/boot/stage-2.nix+2−3 nixos/modules/system/boot/systemd-lib.nix+31−10 nixos/modules/system/boot/systemd-nspawn.nix+2−7 nixos/modules/system/boot/systemd-unit-options.nix+2−2 nixos/modules/system/boot/systemd.nix+61−45 nixos/modules/system/boot/timesyncd.nix+4−4 nixos/modules/tasks/bcache.nix+1−1 nixos/modules/tasks/encrypted-devices.nix−1 nixos/modules/tasks/filesystems.nix+5−3 nixos/modules/tasks/filesystems/bcachefs.nix+50−11 nixos/modules/tasks/filesystems/exfat.nix+1−1 nixos/modules/tasks/filesystems/ext.nix+1−1 nixos/modules/tasks/filesystems/zfs.nix+102−52 nixos/modules/tasks/kbd.nix+1−1 nixos/modules/tasks/network-interfaces-scripted.nix+23−8 nixos/modules/tasks/network-interfaces-systemd.nix+1−1 nixos/modules/tasks/network-interfaces.nix+9−54 nixos/modules/tasks/scsi-link-power-management.nix+25−3 nixos/modules/tasks/swraid.nix+2−2 nixos/modules/tasks/trackpoint.nix+13−4 nixos/modules/testing/service-runner.nix+1−1 nixos/modules/testing/test-instrumentation.nix+14−7 nixos/modules/virtualisation/amazon-image.nix+6−9 nixos/modules/virtualisation/amazon-init.nix+1−1 nixos/modules/virtualisation/amazon-options.nix+1−1 nixos/modules/virtualisation/azure-agent.nix+8−4 nixos/modules/virtualisation/azure-common.nix+1−1 nixos/modules/virtualisation/azure-config-user.nix+1−1 nixos/modules/virtualisation/azure-config.nix+1−1 nixos/modules/virtualisation/azure-image.nix+2−2 nixos/modules/virtualisation/azure-qemu-220-no-etc-install.patch−14 nixos/modules/virtualisation/brightbox-config.nix+1−1 nixos/modules/virtualisation/brightbox-image.nix+1−1 nixos/modules/virtualisation/container-config.nix+7 nixos/modules/virtualisation/containers.nix+28−10 nixos/modules/virtualisation/docker-image.nix+1−1 nixos/modules/virtualisation/docker-preloader.nix+135 nixos/modules/virtualisation/docker.nix+1−1 nixos/modules/virtualisation/ec2-amis.nix+35−1 nixos/modules/virtualisation/gce-images.nix+2−1 nixos/modules/virtualisation/google-compute-config.nix+1−1 nixos/modules/virtualisation/google-compute-image.nix+38−32 nixos/modules/virtualisation/hyperv-guest.nix+31−4 nixos/modules/virtualisation/kvmgt.nix+70 nixos/modules/virtualisation/libvirtd.nix+31−13 nixos/modules/virtualisation/lxc-container.nix+2−2 nixos/modules/virtualisation/lxc.nix+4−1 nixos/modules/virtualisation/lxd.nix+35−29 nixos/modules/virtualisation/nova-config.nix+1−1 nixos/modules/virtualisation/openvswitch.nix+1−4 nixos/modules/virtualisation/parallels-guest.nix+24−6 nixos/modules/virtualisation/qemu-guest-agent.nix+36 nixos/modules/virtualisation/qemu-vm.nix+69−25 nixos/modules/virtualisation/rkt.nix+1−1 nixos/modules/virtualisation/virtualbox-guest.nix+2−2 nixos/modules/virtualisation/virtualbox-host.nix+24−5 nixos/modules/virtualisation/virtualbox-image.nix+39−11 nixos/modules/virtualisation/vmware-guest.nix+1−1 nixos/modules/virtualisation/xe-guest-utilities.nix+1−1 nixos/modules/virtualisation/xen-dom0.nix+10−4 nixos/modules/virtualisation/xen-domU.nix+1−1 nixos/release-combined.nix+22−13 nixos/release-small.nix+4 nixos/release.nix+75−201 nixos/tests/acme.nix+5−28 nixos/tests/all-tests.nix+214 nixos/tests/ammonite.nix+1−1 nixos/tests/atd.nix+4−9 nixos/tests/avahi.nix+1−1 nixos/tests/bcachefs.nix+38 nixos/tests/beegfs.nix+3−3 nixos/tests/bind.nix+27 nixos/tests/bittorrent.nix+70−37 nixos/tests/boot.nix+11−2 nixos/tests/borgbackup.nix+152−11 nixos/tests/buildbot.nix+114−105 nixos/tests/cadvisor.nix+2−2 nixos/tests/cassandra.nix+46−43 nixos/tests/ceph.nix+139 nixos/tests/certmgr.nix+151 nixos/tests/cfssl.nix+67 nixos/tests/chromium.nix+35−7 nixos/tests/cjdns.nix+6−15 nixos/tests/cloud-init.nix+6−3 nixos/tests/codimd.nix+54 nixos/tests/common/letsencrypt.nix−446 nixos/tests/common/letsencrypt/common.nix+27 nixos/tests/common/letsencrypt/default.nix+445 nixos/tests/common/letsencrypt/mkcerts.nix+69 nixos/tests/common/letsencrypt/mkcerts.sh+6 nixos/tests/common/letsencrypt/snakeoil-certs.nix+253 nixos/tests/common/resolver.nix+1−1 nixos/tests/common/user-account.nix+3−3 nixos/tests/containers-bridge.nix+1−2 nixos/tests/containers-extra_veth.nix+1−2 nixos/tests/containers-hosts.nix+1−1 nixos/tests/containers-imperative.nix+19−4 nixos/tests/containers-ipv4.nix+2−2 nixos/tests/containers-ipv6.nix+1−2 nixos/tests/containers-macvlans.nix+2−2 nixos/tests/containers-physical_interfaces.nix+6−6 nixos/tests/containers-portforward.nix+1−2 nixos/tests/containers-reloadable.nix+3−4 nixos/tests/containers-restart_networking.nix+4−5 nixos/tests/containers-tmpfs.nix+2−2 nixos/tests/couchdb.nix+2−2 nixos/tests/deluge.nix+29 nixos/tests/dhparams.nix+144 nixos/tests/dnscrypt-proxy.nix+3−2 nixos/tests/docker-edge.nix+1−1 nixos/tests/docker-preloader.nix+27 nixos/tests/docker-registry.nix+24−4 nixos/tests/docker-tools-overlay.nix+32 nixos/tests/docker-tools.nix+33−6 nixos/tests/docker.nix+1−1 nixos/tests/dovecot.nix+16−3 nixos/tests/ec2.nix+8−3 nixos/tests/ecryptfs.nix+2−2 nixos/tests/elk.nix+53−8 nixos/tests/emacs-daemon.nix+1−1 nixos/tests/env.nix+1−1 nixos/tests/etcd-cluster.nix+3−3 nixos/tests/etcd.nix+1−1 nixos/tests/ferm.nix+5−3 nixos/tests/firefox.nix+1−1 nixos/tests/firewall.nix+3−3 nixos/tests/flannel.nix+3−3 nixos/tests/flatpak.nix+26 nixos/tests/fleet.nix−76 nixos/tests/fsck.nix+29 nixos/tests/fwupd.nix+1−1 nixos/tests/gdk-pixbuf.nix+21 nixos/tests/gitea.nix+77 nixos/tests/gitlab.nix+15−6 nixos/tests/gitolite.nix+4−4 nixos/tests/gnome3-gdm.nix+11−5 nixos/tests/gnome3.nix+9−4 nixos/tests/gocd-agent.nix+1−1 nixos/tests/gocd-server.nix+1−1 nixos/tests/grafana.nix+2−2 nixos/tests/graphite.nix+18−9 nixos/tests/hadoop/hdfs.nix+54 nixos/tests/hadoop/yarn.nix+46 nixos/tests/haka.nix+1−1 nixos/tests/handbrake.nix+25 nixos/tests/haproxy.nix+41 nixos/tests/hardened.nix+6−4 nixos/tests/hibernate.nix+3−3 nixos/tests/hitch/default.nix+33 nixos/tests/hitch/example.pem+53 nixos/tests/hitch/example/index.txt+1 nixos/tests/hocker-fetchdocker/default.nix+15 nixos/tests/hocker-fetchdocker/hello-world-container.nix+19 nixos/tests/hocker-fetchdocker/machine.nix+26 nixos/tests/home-assistant.nix+13−10 nixos/tests/hound.nix+2−2 nixos/tests/hydra.nix−32 nixos/tests/hydra/create-trivial-project.sh+57 nixos/tests/hydra/default.nix+77 nixos/tests/i3wm.nix+8−6 nixos/tests/iftop.nix+34 nixos/tests/incron.nix+52 nixos/tests/influxdb.nix+1−1 nixos/tests/initrd-network-ssh/default.nix+3−3 nixos/tests/initrd-network.nix+1−1 nixos/tests/installer.nix+81−60 nixos/tests/ipfs.nix+2−2 nixos/tests/ipv6.nix+3−3 nixos/tests/jenkins.nix+4−4 nixos/tests/kafka.nix+73 nixos/tests/kafka_0_10.nix−48 nixos/tests/kafka_0_11.nix−48 nixos/tests/kafka_0_9.nix−48 nixos/tests/kafka_1_0.nix−48 nixos/tests/kernel-copperhead.nix−19 nixos/tests/kernel-latest.nix+1−1 nixos/tests/kernel-lts.nix+1−1 nixos/tests/kexec.nix+1−1 nixos/tests/keymap.nix+50−86 nixos/tests/krb5/deprecated-config.nix+1−1 nixos/tests/krb5/example-config.nix+1−1 nixos/tests/kubernetes/base.nix+6−3 nixos/tests/kubernetes/certs.nix+54−21 nixos/tests/kubernetes/dns.nix+3−3 nixos/tests/kubernetes/e2e.nix+1−1 nixos/tests/kubernetes/kubernetes-common.nix−1 nixos/tests/kubernetes/rbac.nix+2−2 nixos/tests/ldap.nix+2−2 nixos/tests/lightdm.nix+2−2 nixos/tests/login.nix+1−1 nixos/tests/make-test.nix+6−2 nixos/tests/mathics.nix+1−1 nixos/tests/matrix-synapse.nix+9−8 nixos/tests/memcached.nix+28 nixos/tests/mesos.nix+6−3 nixos/tests/minio.nix+1−1 nixos/tests/misc.nix+15−4 nixos/tests/mongodb.nix+1−1 nixos/tests/morty.nix+32 nixos/tests/mpd.nix+119 nixos/tests/mumble.nix+2−2 nixos/tests/munin.nix+17−7 nixos/tests/mutable-users.nix+2−2 nixos/tests/mysql-backup.nix+13−5 nixos/tests/mysql-replication.nix+12−5 nixos/tests/mysql.nix+1−2 nixos/tests/nat.nix+4−6 nixos/tests/netdata.nix+10−3 nixos/tests/networking-proxy.nix+4−4 nixos/tests/networking.nix+46−38 nixos/tests/nextcloud/basic.nix+56 nixos/tests/nextcloud/default.nix+9 nixos/tests/nextcloud/with-mysql-and-memcached.nix+97 nixos/tests/nextcloud/with-postgresql-and-redis.nix+130 nixos/tests/nexus.nix+9−11 nixos/tests/nfs.nix+4−3 nixos/tests/nginx.nix+1−1 nixos/tests/nix-ssh-serve.nix+39 nixos/tests/novacomd.nix+8−2 nixos/tests/nsd.nix+9 nixos/tests/openldap.nix+35 nixos/tests/opensmtpd.nix+125 nixos/tests/openssh.nix+7−20 nixos/tests/osquery.nix+28 nixos/tests/ostree.nix+21 nixos/tests/owncloud.nix+2−2 nixos/tests/pam-oath-login.nix+3−5 nixos/tests/panamax.nix−21 nixos/tests/partition.nix+1−1 nixos/tests/peerflix.nix+1−1 nixos/tests/pgjwt.nix+1−1 nixos/tests/phabricator.nix+3−3 nixos/tests/php-pcre.nix+3−3 nixos/tests/plasma5.nix+22−19 nixos/tests/plotinus.nix+6−6 nixos/tests/postgis.nix+2−2 nixos/tests/postgresql.nix+16−3 nixos/tests/powerdns.nix+1−1 nixos/tests/predictable-interface-names.nix+24−24 nixos/tests/printing.nix+5−3 nixos/tests/prometheus-exporters.nix+316 nixos/tests/prometheus.nix+1−1 nixos/tests/prosody.nix+78 nixos/tests/proxy.nix+3−3 nixos/tests/pump.io.nix−89 nixos/tests/quagga.nix+5−6 nixos/tests/quake3.nix+2−2 nixos/tests/rabbitmq.nix+1−1 nixos/tests/radicale.nix+1−1 nixos/tests/redmine.nix+40 nixos/tests/riak.nix+1−1 nixos/tests/rspamd.nix+160−46 nixos/tests/rsyslogd.nix+42 nixos/tests/run-in-machine.nix+6−3 nixos/tests/rxe.nix+2−2 nixos/tests/samba.nix+2−2 nixos/tests/sddm.nix+9−6 nixos/tests/simple.nix+1−1 nixos/tests/slim.nix+2−2 nixos/tests/slurm.nix+70−18 nixos/tests/smokeping.nix+1−1 nixos/tests/solr.nix+47 nixos/tests/ssh-keys.nix+15 nixos/tests/statsd.nix−40 nixos/tests/strongswan-swanctl.nix+148 nixos/tests/subversion.nix+2−2 nixos/tests/sudo.nix+2−2 nixos/tests/switch-test.nix+2−2 nixos/tests/systemd.nix+68 nixos/tests/taskserver.nix+4−3 nixos/tests/tomcat.nix+1−1 nixos/tests/tor.nix+28 nixos/tests/trac.nix+4−4 nixos/tests/transmission.nix+21 nixos/tests/udisks2.nix+4−3 nixos/tests/upnp.nix+94 nixos/tests/vault.nix+3−3 nixos/tests/virtualbox.nix+49−10 nixos/tests/wordpress.nix+3−6 nixos/tests/xautolock.nix+24 nixos/tests/xdg-desktop-portal.nix+17 nixos/tests/xfce.nix+1−1 nixos/tests/xmonad.nix+1−1 nixos/tests/xrdp.nix+3−3 nixos/tests/xss-lock.nix+25 nixos/tests/yabar.nix+13−5 nixos/tests/zfs.nix+6−3 nixos/tests/zookeeper.nix+1−1 pkgs/applications/altcoins/aeon/default.nix+19−11 pkgs/applications/altcoins/bitcoin-abc.nix+7−4 pkgs/applications/altcoins/bitcoin-classic.nix+5−2 pkgs/applications/altcoins/bitcoin-unlimited-const-comparators.patch+38 pkgs/applications/altcoins/bitcoin-unlimited.nix+14−6 pkgs/applications/altcoins/bitcoin-xt.nix+10−5 pkgs/applications/altcoins/bitcoin.nix+21−6 pkgs/applications/altcoins/btc1.nix+11−10 pkgs/applications/altcoins/clightning.nix+47 pkgs/applications/altcoins/dapp.nix−33 pkgs/applications/altcoins/dashpay.nix+6−6 pkgs/applications/altcoins/dcrd.nix+34 pkgs/applications/altcoins/dcrwallet.nix+43 pkgs/applications/altcoins/default.nix+58−30 pkgs/applications/altcoins/dero.nix+3−3 pkgs/applications/altcoins/dogecoin.nix+1−1 pkgs/applications/altcoins/ethabi.nix+7−6 pkgs/applications/altcoins/ethrun.nix−25 pkgs/applications/altcoins/ethsign/default.nix−59 pkgs/applications/altcoins/freicoin.nix+2−2 pkgs/applications/altcoins/go-ethereum-classic/default.nix+1−1 pkgs/applications/altcoins/go-ethereum.nix+3−14 pkgs/applications/altcoins/hevm.nix−61 pkgs/applications/altcoins/litecoin.nix+11−4 pkgs/applications/altcoins/masari.nix+27 pkgs/applications/altcoins/memorycoin.nix+1−1 pkgs/applications/altcoins/mist.nix+72 pkgs/applications/altcoins/monero-gui/default.nix+10−7 pkgs/applications/altcoins/monero-gui/move-log-file.patch+22−37 pkgs/applications/altcoins/monero-gui/move-translations-dir.patch+7−8 pkgs/applications/altcoins/monero/build-wallet-rpc.patch−78 pkgs/applications/altcoins/monero/default.nix+24−25 pkgs/applications/altcoins/namecoin.nix+6−3 pkgs/applications/altcoins/nano-wallet/CMakeLists.txt.patch+13 pkgs/applications/altcoins/nano-wallet/default.nix+57 pkgs/applications/altcoins/parity-ui/default.nix+50 pkgs/applications/altcoins/parity-ui/env.nix+19 pkgs/applications/altcoins/parity/beta.nix+9 pkgs/applications/altcoins/parity/default.nix+7 pkgs/applications/altcoins/parity/parity.nix+43 pkgs/applications/altcoins/parity/patches/vendored-sources-2.0.patch+98 pkgs/applications/altcoins/parity/patches/vendored-sources-2.1.patch+83 pkgs/applications/altcoins/particl/particl-core.nix+53 pkgs/applications/altcoins/primecoin.nix−58 pkgs/applications/altcoins/seth.nix−33 pkgs/applications/altcoins/stellar-core.nix+1−1 pkgs/applications/altcoins/wownero.nix+51 pkgs/applications/audio/FIL-plugins/default.nix+37 pkgs/applications/audio/MMA/default.nix+4−4 pkgs/applications/audio/a2jmidid/default.nix+1−1 pkgs/applications/audio/aacgain/default.nix+21−7 pkgs/applications/audio/abcde/abcde.patch−30 pkgs/applications/audio/abcde/default.nix+20−22 pkgs/applications/audio/aeolus/default.nix+3−3 pkgs/applications/audio/airwave/default.nix+1−1 pkgs/applications/audio/aj-snapshot/default.nix+2−2 pkgs/applications/audio/amarok/default.nix+42 pkgs/applications/audio/amarok/kf5.nix−38 pkgs/applications/audio/ams-lv2/default.nix+5−5 pkgs/applications/audio/ario/default.nix+2−2 pkgs/applications/audio/asunder/default.nix+2−2 pkgs/applications/audio/audacious/default.nix+6−6 pkgs/applications/audio/audacious/qt-5.nix+3−3 pkgs/applications/audio/audacity/default.nix+4−4 pkgs/applications/audio/audio-recorder/default.nix+15−27 pkgs/applications/audio/avldrums-lv2/default.nix+30 pkgs/applications/audio/axoloti/default.nix+14−14 pkgs/applications/audio/axoloti/dfu-util.nix+1−1 pkgs/applications/audio/axoloti/libusb1.nix+3−3 pkgs/applications/audio/banshee/default.nix−55 pkgs/applications/audio/baudline/default.nix+3−3 pkgs/applications/audio/beast/default.nix+1−1 pkgs/applications/audio/bitmeter/default.nix+1−1 pkgs/applications/audio/bitwig-studio/bitwig-studio2.nix+2−2 pkgs/applications/audio/bs1770gain/default.nix+2−2 pkgs/applications/audio/cadence/default.nix+65 pkgs/applications/audio/calf/default.nix+11−2 pkgs/applications/audio/cantata/default.nix+2−11 pkgs/applications/audio/caps/default.nix+2−9 pkgs/applications/audio/cava/default.nix+2−2 pkgs/applications/audio/cdparanoia/default.nix+6−4 pkgs/applications/audio/cdparanoia/fix_private_keyword.patch+468 pkgs/applications/audio/chuck/clang.patch+58 pkgs/applications/audio/chuck/default.nix+19−14 pkgs/applications/audio/clementine/default.nix+30−40 pkgs/applications/audio/cmus/default.nix+2−2 pkgs/applications/audio/cmusfm/default.nix+36 pkgs/applications/audio/cozy-audiobooks/default.nix+85 pkgs/applications/audio/crip/default.nix+68 pkgs/applications/audio/csa/default.nix+28 pkgs/applications/audio/csound/default.nix+2−2 pkgs/applications/audio/deadbeef/default.nix+5−5 pkgs/applications/audio/deadbeef/plugins/headerbar-gtk3.nix+30 pkgs/applications/audio/deadbeef/plugins/infobar.nix+33 pkgs/applications/audio/deadbeef/plugins/mpris2.nix+2−2 pkgs/applications/audio/deadbeef/plugins/opus.nix+31 pkgs/applications/audio/deadbeef/wrapper.nix+1−1 pkgs/applications/audio/denemo/default.nix+1−1 pkgs/applications/audio/distrho/default.nix+7−5 pkgs/applications/audio/dr14_tmeter/default.nix+1−1 pkgs/applications/audio/dragonfly-reverb/default.nix+35 pkgs/applications/audio/drumgizmo/default.nix+3−3 pkgs/applications/audio/drumkv1/default.nix+2−2 pkgs/applications/audio/easytag/default.nix+21−17 pkgs/applications/audio/ecasound/default.nix+1−1 pkgs/applications/audio/eflite/buf-overflow.patch−22 pkgs/applications/audio/eflite/cvs-update.patch−98 pkgs/applications/audio/eflite/default.nix+25−6 pkgs/applications/audio/eflite/link.patch−11 pkgs/applications/audio/elisa/default.nix+35 pkgs/applications/audio/eq10q/default.nix+10−1 pkgs/applications/audio/espeak-ng/default.nix+1−1 pkgs/applications/audio/eteroj.lv2/default.nix+24 pkgs/applications/audio/faust/faust1.nix+1−1 pkgs/applications/audio/faust/faust2.nix+11−4 pkgs/applications/audio/faust/faustlive.nix+35 pkgs/applications/audio/flac/default.nix+1−1 pkgs/applications/audio/flacon/default.nix+4−4 pkgs/applications/audio/fldigi/default.nix+2−2 pkgs/applications/audio/fluidsynth/default.nix+2−2 pkgs/applications/audio/fmit/default.nix+3−3 pkgs/applications/audio/fomp/default.nix+1−1 pkgs/applications/audio/freewheeling/default.nix+2−2 pkgs/applications/audio/gigedit/default.nix+1−1 pkgs/applications/audio/gjay/default.nix+2−2 pkgs/applications/audio/gmpc/default.nix+3−3 pkgs/applications/audio/google-musicmanager/default.nix+47−29 pkgs/applications/audio/google-play-music-desktop-player/default.nix+4−3 pkgs/applications/audio/gpodder/default.nix+3−4 pkgs/applications/audio/gradio/default.nix+9−10 pkgs/applications/audio/gtklick/default.nix+2−3 pkgs/applications/audio/gtkpod/default.nix+9−16 pkgs/applications/audio/guitarix/default.nix+8−8 pkgs/applications/audio/gxplugins-lv2/default.nix+29 pkgs/applications/audio/helm/default.nix+2−2 pkgs/applications/audio/hybridreverb2/default.nix+49 pkgs/applications/audio/infamousPlugins/default.nix+1−1 pkgs/applications/audio/ir.lv2/default.nix+3−3 pkgs/applications/audio/jaaa/default.nix+4−4 pkgs/applications/audio/jack-capture/default.nix+1−1 pkgs/applications/audio/jack-oscrolloscope/default.nix+2−2 pkgs/applications/audio/jalv/default.nix+1−1 pkgs/applications/audio/jamin/default.nix+4−6 pkgs/applications/audio/japa/default.nix+3−3 pkgs/applications/audio/kid3/default.nix+11−12 pkgs/applications/audio/ladspa-sdk/default.nix+1−1 pkgs/applications/audio/ladspa-sdk/ladspah.nix+1−1 pkgs/applications/audio/lastfmsubmitd/default.nix+5−5 pkgs/applications/audio/lastwatch/default.nix+1−2 pkgs/applications/audio/lingot/default.nix+1−1 pkgs/applications/audio/linuxsampler/default.nix+1−1 pkgs/applications/audio/lmms/default.nix+5−3 pkgs/applications/audio/lollypop/default.nix+70 pkgs/applications/audio/lsp-plugins/default.nix+160 pkgs/applications/audio/ltc-tools/default.nix+25 pkgs/applications/audio/magnetophonDSP/VoiceOfFaust/default.nix+1−1 pkgs/applications/audio/mda-lv2/default.nix+1−1 pkgs/applications/audio/meterbridge/default.nix+2−2 pkgs/applications/audio/meters_lv2/default.nix+2−2 pkgs/applications/audio/mhwaveedit/default.nix+12−11 pkgs/applications/audio/mi2ly/default.nix+1 pkgs/applications/audio/midas/generic.nix+43 pkgs/applications/audio/midas/m32edit.nix+9 pkgs/applications/audio/midas/x32edit.nix+9 pkgs/applications/audio/midisheetmusic/default.nix+60 pkgs/applications/audio/mikmod/default.nix+2−2 pkgs/applications/audio/milkytracker/decompressor_gzip.patch−20 pkgs/applications/audio/milkytracker/default.nix+12−15 pkgs/applications/audio/mimic/default.nix+35 pkgs/applications/audio/mimms/default.nix+26−26 pkgs/applications/audio/mixxx/default.nix+21−21 pkgs/applications/audio/monkeys-audio/default.nix+1−1 pkgs/applications/audio/mopidy-gmusic/default.nix−28 pkgs/applications/audio/mopidy-iris/default.nix−28 pkgs/applications/audio/mopidy-local-images/default.nix−33 pkgs/applications/audio/mopidy-local-sqlite/default.nix−26 pkgs/applications/audio/mopidy-moped/default.nix−25 pkgs/applications/audio/mopidy-mopify/default.nix−23 pkgs/applications/audio/mopidy-musicbox-webclient/default.nix−24 pkgs/applications/audio/mopidy-soundcloud/default.nix−24 pkgs/applications/audio/mopidy-spotify-tunigo/default.nix−24 pkgs/applications/audio/mopidy-spotify/default.nix−23 pkgs/applications/audio/mopidy-youtube/default.nix−24 pkgs/applications/audio/mopidy/default.nix+5−6 pkgs/applications/audio/mopidy/gmusic.nix+28 pkgs/applications/audio/mopidy/iris.nix+34 pkgs/applications/audio/mopidy/local-images.nix+32 pkgs/applications/audio/mopidy/local-sqlite.nix+25 pkgs/applications/audio/mopidy/moped.nix+26 pkgs/applications/audio/mopidy/mopify.nix+23 pkgs/applications/audio/mopidy/musicbox-webclient.nix+23 pkgs/applications/audio/mopidy/soundcloud.nix+23 pkgs/applications/audio/mopidy/spotify-tunigo.nix+23 pkgs/applications/audio/mopidy/spotify.nix+23 pkgs/applications/audio/mopidy/youtube.nix+23 pkgs/applications/audio/morituri/default.nix−55 pkgs/applications/audio/morituri/paths.patch−87 pkgs/applications/audio/mp3blaster/default.nix+5−2 pkgs/applications/audio/mpc123/default.nix+1−1 pkgs/applications/audio/mpg123/default.nix+5−5 pkgs/applications/audio/mpg321/default.nix+1−1 pkgs/applications/audio/muse/default.nix+76 pkgs/applications/audio/musescore/default.nix+12−34 pkgs/applications/audio/ncmpc/default.nix+2−4 pkgs/applications/audio/ncmpcpp/default.nix+2−2 pkgs/applications/audio/nova-filters/default.nix+1−1 pkgs/applications/audio/opusfile/default.nix+2−2 pkgs/applications/audio/padthv1/default.nix+2−2 pkgs/applications/audio/pamix/default.nix+8−4 pkgs/applications/audio/pamixer/default.nix+13−6 pkgs/applications/audio/paprefs/default.nix+6−11 pkgs/applications/audio/patchage/default.nix+2−2 pkgs/applications/audio/pavucontrol/default.nix+4−3 pkgs/applications/audio/pd-plugins/helmholtz/default.nix+4−1 pkgs/applications/audio/pd-plugins/puremapping/default.nix+1−1 pkgs/applications/audio/pd-plugins/zexy/default.nix+1−1 pkgs/applications/audio/pianobar/default.nix+4−5 pkgs/applications/audio/pianobooster/default.nix+3−3 pkgs/applications/audio/picard/default.nix+13−8 pkgs/applications/audio/pithos/default.nix−1 pkgs/applications/audio/praat/default.nix+2−2 pkgs/applications/audio/puddletag/default.nix+2−13 pkgs/applications/audio/pulseaudio-ctl/default.nix+41 pkgs/applications/audio/pulseaudio-modules-bt/default.nix+82 pkgs/applications/audio/pulseaudio-modules-bt/fix-install-path.patch+20 pkgs/applications/audio/pulseeffects/default.nix+109 pkgs/applications/audio/puredata/default.nix+9−12 pkgs/applications/audio/puredata/wrapper.nix+1−1 pkgs/applications/audio/qjackctl/default.nix+2−2 pkgs/applications/audio/qmidinet/default.nix+2−2 pkgs/applications/audio/qmidiroute/default.nix+2−2 pkgs/applications/audio/qmmp/default.nix+2−2 pkgs/applications/audio/qsampler/default.nix+2−2 pkgs/applications/audio/qsynth/default.nix+3−3 pkgs/applications/audio/quodlibet/default.nix+29−14 pkgs/applications/audio/radiotray-ng/default.nix+13−11 pkgs/applications/audio/reaper/default.nix+81 pkgs/applications/audio/redoflacs/default.nix+39 pkgs/applications/audio/renoise/default.nix+19−11 pkgs/applications/audio/rhvoice/default.nix+48 pkgs/applications/audio/rhvoice/honor_nix_environment.patch+14 pkgs/applications/audio/rhythmbox/default.nix+30−17 pkgs/applications/audio/rkrlv2/default.nix+1−1 pkgs/applications/audio/rosegarden/default.nix+3−3 pkgs/applications/audio/samplv1/default.nix+2−2 pkgs/applications/audio/sayonara/default.nix+3−3 pkgs/applications/audio/schismtracker/default.nix+1−1 pkgs/applications/audio/setbfree/default.nix+4−4 pkgs/applications/audio/sfxr-qt/default.nix+36 pkgs/applications/audio/sidplayfp/default.nix+22 pkgs/applications/audio/sisco.lv2/default.nix+2−2 pkgs/applications/audio/snapcast/default.nix+66 pkgs/applications/audio/snd/default.nix+2−2 pkgs/applications/audio/sonata/default.nix+5−7 pkgs/applications/audio/sonic-pi/default.nix+5−5 pkgs/applications/audio/sonic-visualiser/default.nix+1−1 pkgs/applications/audio/sound-juicer/default.nix+23−29 pkgs/applications/audio/soundscape-renderer/default.nix+4−2 pkgs/applications/audio/spectmorph/default.nix+22 pkgs/applications/audio/spectrojack/default.nix+2−2 pkgs/applications/audio/split2flac/default.nix+62 pkgs/applications/audio/spotify/default.nix+48−16 pkgs/applications/audio/spotify/update.sh+96 pkgs/applications/audio/spotifywm/default.nix+31 pkgs/applications/audio/squishyball/default.nix+2 pkgs/applications/audio/streamripper/default.nix+2−3 pkgs/applications/audio/sunvox/default.nix+1−1 pkgs/applications/audio/swh-lv2/default.nix+1−1 pkgs/applications/audio/synthv1/default.nix+2−2 pkgs/applications/audio/tambura/default.nix+34 pkgs/applications/audio/tetraproc/default.nix+3−3 pkgs/applications/audio/tomahawk/default.nix+4−3 pkgs/applications/audio/transcode/default.nix+5−3 pkgs/applications/audio/transcribe/default.nix+2−2 pkgs/applications/audio/uade123/default.nix+5−2 pkgs/applications/audio/vcv-rack/default.nix+79 pkgs/applications/audio/vimpc/default.nix+1−3 pkgs/applications/audio/vocal/default.nix+53 pkgs/applications/audio/vorbis-tools/default.nix+1−1 pkgs/applications/audio/whipper/default.nix+48 pkgs/applications/audio/whipper/paths.patch+105 pkgs/applications/audio/wolf-shaper/default.nix+47 pkgs/applications/audio/x42-plugins/default.nix+5−5 pkgs/applications/audio/ympd/default.nix+3−2 pkgs/applications/audio/yoshimi/default.nix+4−4 pkgs/applications/audio/zam-plugins/default.nix+2−2 pkgs/applications/audio/zita-njbridge/default.nix+32 pkgs/applications/backup/crashplan/crashplan-small-business.nix+10−10 pkgs/applications/backup/crashplan/default.nix+1−1 pkgs/applications/backup/deja-dup/default.nix+18−22 pkgs/applications/backup/deja-dup/fix-paths.patch+10−11 pkgs/applications/backup/deja-dup/hardcode-gsettings.patch+38 pkgs/applications/display-managers/lightdm-enso-os-greeter/default.nix+71 pkgs/applications/display-managers/lightdm-gtk-greeter/default.nix−49 pkgs/applications/display-managers/lightdm-mini-greeter/default.nix+32 pkgs/applications/display-managers/lightdm/default.nix+53−19 pkgs/applications/display-managers/lightdm/gtk-greeter.nix+51 pkgs/applications/display-managers/lightdm/run-dir.patch+13 pkgs/applications/display-managers/ly/default.nix+29 pkgs/applications/display-managers/sddm/default.nix+10−7 pkgs/applications/display-managers/slim/default.nix+8−4 pkgs/applications/editors/android-studio/common.nix+60−14 pkgs/applications/editors/android-studio/default.nix+38−29 pkgs/applications/editors/aseprite/default.nix+18−6 pkgs/applications/editors/atom/beta.nix−52 pkgs/applications/editors/atom/default.nix+82−46 pkgs/applications/editors/atom/env.nix+3−3 pkgs/applications/editors/bonzomatic/default.nix+30 pkgs/applications/editors/brackets/default.nix+2−2 pkgs/applications/editors/codeblocks/default.nix+4−8 pkgs/applications/editors/dit/default.nix+30 pkgs/applications/editors/eclipse/build-eclipse.nix+5−5 pkgs/applications/editors/eclipse/default.nix+94−43 pkgs/applications/editors/eclipse/plugins.nix+65−23 pkgs/applications/editors/ed/default.nix+1−2 pkgs/applications/editors/edbrowse/default.nix+8−10 pkgs/applications/editors/elvis/default.nix+1−1 pkgs/applications/editors/emacs-modes/bbdb/default.nix+1−1 pkgs/applications/editors/emacs-modes/calfw/default.nix+1−1 pkgs/applications/editors/emacs-modes/cask/default.nix+2−2 pkgs/applications/editors/emacs-modes/cedille/default.nix+30 pkgs/applications/editors/emacs-modes/elpa-generated.nix+830−292 pkgs/applications/editors/emacs-modes/elpa-packages.nix+1−1 pkgs/applications/editors/emacs-modes/emacs-clang-complete-async/default.nix+1−1 pkgs/applications/editors/emacs-modes/emacs-libvterm/default.nix+41 pkgs/applications/editors/emacs-modes/filesets-plus/default.nix+2−2 pkgs/applications/editors/emacs-modes/font-lock-plus/default.nix+2−2 pkgs/applications/editors/emacs-modes/haskell/default.nix+3 pkgs/applications/editors/emacs-modes/header2/default.nix+2−2 pkgs/applications/editors/emacs-modes/hexrgb/default.nix+2−2 pkgs/applications/editors/emacs-modes/icicles/default.nix+14−14 pkgs/applications/editors/emacs-modes/jdee/default.nix+1−1 pkgs/applications/editors/emacs-modes/lib-requires/default.nix+2−2 pkgs/applications/editors/emacs-modes/maude/default.nix+1−1 pkgs/applications/editors/emacs-modes/melpa-generated.nix+46035−20457 pkgs/applications/editors/emacs-modes/melpa-packages.nix+93−62 pkgs/applications/editors/emacs-modes/melpa-stable-generated.nix+22836−9509 pkgs/applications/editors/emacs-modes/melpa-stable-packages.nix+40−7 pkgs/applications/editors/emacs-modes/ocaml/default.nix+1−1 pkgs/applications/editors/emacs-modes/org-generated.nix+14−9 pkgs/applications/editors/emacs-modes/org-packages.nix+1−7 pkgs/applications/editors/emacs-modes/org/default.nix+1−1 pkgs/applications/editors/emacs-modes/scala-mode/v1.nix+1−1 pkgs/applications/editors/emacs-modes/thingatpt-plus/default.nix+2−2 pkgs/applications/editors/emacs/25.nix+139 pkgs/applications/editors/emacs/builder.sh−40 pkgs/applications/editors/emacs/clean-env.patch+2−2 pkgs/applications/editors/emacs/default.nix+36−30 pkgs/applications/editors/emacs/macport.nix+16−16 pkgs/applications/editors/featherpad/default.nix+23 pkgs/applications/editors/flpsed/default.nix+3−3 pkgs/applications/editors/focuswriter/default.nix+3−3 pkgs/applications/editors/geany/default.nix+7−13 pkgs/applications/editors/geany/with-vte.nix+1−1 pkgs/applications/editors/ghostwriter/default.nix+2−2 pkgs/applications/editors/gnome-builder/default.nix+158 pkgs/applications/editors/gnome-latex/default.nix+47 pkgs/applications/editors/gobby/default.nix+12−16 pkgs/applications/editors/hexcurse/default.nix+13−1 pkgs/applications/editors/howl/default.nix+40 pkgs/applications/editors/ht/default.nix+2 pkgs/applications/editors/ht/gcc7.patch+11 pkgs/applications/editors/jetbrains/common.nix+8−6 pkgs/applications/editors/jetbrains/default.nix+80−64 pkgs/applications/editors/jetbrains/update.pl+1−1 pkgs/applications/editors/jucipp/default.nix+4−4 pkgs/applications/editors/jupp/default.nix+1−1 pkgs/applications/editors/jupyter/default.nix+18 pkgs/applications/editors/jupyter/kernel.nix+74 pkgs/applications/editors/kakoune/default.nix+5−4 pkgs/applications/editors/kdevelop5/kdevelop.nix+13−11 pkgs/applications/editors/kdevelop5/kdevplatform.nix−44 pkgs/applications/editors/kile/default.nix+5−7 pkgs/applications/editors/kodestudio/default.nix+11−11 pkgs/applications/editors/leo-editor/default.nix+4−13 pkgs/applications/editors/lighttable/default.nix+4−4 pkgs/applications/editors/manuskript/default.nix+5−5 pkgs/applications/editors/mg/default.nix+2−2 pkgs/applications/editors/micro/default.nix+2−2 pkgs/applications/editors/moe/default.nix+1−1 pkgs/applications/editors/monodevelop/default.nix+5−4 pkgs/applications/editors/music/tuxguitar/default.nix+2−2 pkgs/applications/editors/nano/default.nix+10−10 pkgs/applications/editors/nano/nanorc/default.nix+29 pkgs/applications/editors/ne/default.nix+2−2 pkgs/applications/editors/nedit/default.nix+1 pkgs/applications/editors/neovim/default.nix+11−37 pkgs/applications/editors/neovim/neovim-remote.nix+4−4 pkgs/applications/editors/neovim/qt.nix+14−9 pkgs/applications/editors/neovim/ruby_provider/Gemfile.lock+2−2 pkgs/applications/editors/neovim/ruby_provider/gemset.nix+4−4 pkgs/applications/editors/neovim/wrapper.nix+36−29 pkgs/applications/editors/netbeans/default.nix+1−1 pkgs/applications/editors/notepadqq/default.nix+10−7 pkgs/applications/editors/nvpy/default.nix+2−2 pkgs/applications/editors/okteta/default.nix+34 pkgs/applications/editors/quilter/default.nix+52 pkgs/applications/editors/rednotebook/default.nix+6−4 pkgs/applications/editors/rstudio/clang-location.patch+25 pkgs/applications/editors/rstudio/default.nix+2−2 pkgs/applications/editors/rstudio/fix-cmake.patch+15 pkgs/applications/editors/rstudio/preview.nix+119 pkgs/applications/editors/scite/default.nix+4−4 pkgs/applications/editors/sigil/default.nix+2−2 pkgs/applications/editors/standardnotes/default.nix+48 pkgs/applications/editors/sublime/2/default.nix+59 pkgs/applications/editors/sublime/3/common.nix+118 pkgs/applications/editors/sublime/3/packages.nix+18 pkgs/applications/editors/sublime/default.nix−59 pkgs/applications/editors/sublime3/default.nix−113 pkgs/applications/editors/texmacs/common.nix+68 pkgs/applications/editors/texmacs/darwin.nix+59 pkgs/applications/editors/texmacs/darwin.patch+29 pkgs/applications/editors/texmacs/default.nix+18−73 pkgs/applications/editors/texmaker/default.nix+9−6 pkgs/applications/editors/texstudio/default.nix+8−7 pkgs/applications/editors/textadept/default.nix−1 pkgs/applications/editors/thonny/default.nix+51 pkgs/applications/editors/tiled/default.nix+4−4 pkgs/applications/editors/tweak/default.nix+1−1 pkgs/applications/editors/typora/default.nix+19−10 pkgs/applications/editors/vanubi/default.nix−29 pkgs/applications/editors/vim/common.nix+2−2 pkgs/applications/editors/vim/configurable.nix+132−129 pkgs/applications/editors/vim/default.nix+7−4 pkgs/applications/editors/vim/ft-nix-support.patch+1−70 pkgs/applications/editors/vim/macvim.nix+1−1 pkgs/applications/editors/vim/qvim.nix+82−98 pkgs/applications/editors/vis/default.nix+6−2 pkgs/applications/editors/vscode-with-extensions/default.nix−82 pkgs/applications/editors/vscode/default.nix+21−15 pkgs/applications/editors/vscode/with-extensions.nix+87 pkgs/applications/editors/wxhexeditor/default.nix+19−9 pkgs/applications/editors/yi/wrapper.nix+2−2 pkgs/applications/editors/zed/default.nix−82 pkgs/applications/editors/zed/deps.json−6 pkgs/applications/editors/zed/node-packages.nix−877 pkgs/applications/editors/zed/node.nix−16 pkgs/applications/gis/grass/default.nix+14−3 pkgs/applications/gis/grass/no_symbolic_links.patch+37 pkgs/applications/gis/openorienteering-mapper/default.nix+68 pkgs/applications/gis/qgis/default.nix+61−15 pkgs/applications/gis/saga/clang_patch.patch+19 pkgs/applications/gis/saga/default.nix+19−9 pkgs/applications/gis/saga/finite-6.3.0.patch+55 pkgs/applications/gis/saga/finite.patch+13 pkgs/applications/gis/saga/lts.nix+36 pkgs/applications/gis/whitebox-tools/default.nix+24 pkgs/applications/graphics/ImageMagick/7.0.nix+13−13 pkgs/applications/graphics/ImageMagick/default.nix+15−13 pkgs/applications/graphics/PythonMagick/default.nix+12−4 pkgs/applications/graphics/ahoviewer/default.nix+24−17 pkgs/applications/graphics/animbar/default.nix+40 pkgs/applications/graphics/antimony/default.nix+17−11 pkgs/applications/graphics/ao/default.nix+3−2 pkgs/applications/graphics/avocode/default.nix+104 pkgs/applications/graphics/awesomebump/default.nix+1−1 pkgs/applications/graphics/batik/default.nix+11−2 pkgs/applications/graphics/c3d/default.nix+4−3 pkgs/applications/graphics/cinepaint/default.nix+6−6 pkgs/applications/graphics/darktable/default.nix+22−13 pkgs/applications/graphics/dia/default.nix+15−19 pkgs/applications/graphics/digikam/default.nix+8−7 pkgs/applications/graphics/displaycal/default.nix+6−4 pkgs/applications/graphics/dosage/default.nix+28 pkgs/applications/graphics/draftsight/default.nix+25−14 pkgs/applications/graphics/drawpile/default.nix+44 pkgs/applications/graphics/epeg/default.nix+34 pkgs/applications/graphics/exrdisplay/default.nix+7−9 pkgs/applications/graphics/exrtools/default.nix+2−2 pkgs/applications/graphics/fbida/default.nix+12−9 pkgs/applications/graphics/feh/default.nix+9−9 pkgs/applications/graphics/fig2dev/default.nix+25 pkgs/applications/graphics/freecad/default.nix+19−6 pkgs/applications/graphics/freepv/default.nix+2−2 pkgs/applications/graphics/fstl/default.nix+35 pkgs/applications/graphics/gcolor2/default.nix+5−4 pkgs/applications/graphics/gcolor3/default.nix+17−16 pkgs/applications/graphics/geeqie/default.nix+13−10 pkgs/applications/graphics/geeqie/geeqie-no-changelog.patch+14 pkgs/applications/graphics/gimp/2.8.nix−58 pkgs/applications/graphics/gimp/default.nix+83 pkgs/applications/graphics/gimp/plugins/default.nix+14−58 pkgs/applications/graphics/gimp/remove-cc-reference.patch+13 pkgs/applications/graphics/gimp/wrapper.nix+4−3 pkgs/applications/graphics/giv/default.nix+3−3 pkgs/applications/graphics/glabels/default.nix+6−7 pkgs/applications/graphics/gnuclad/default.nix+22 pkgs/applications/graphics/gocr/default.nix+3−3 pkgs/applications/graphics/goxel/default.nix+6−4 pkgs/applications/graphics/goxel/disable-imgui_ini.patch+13 pkgs/applications/graphics/gqview/default.nix+3−2 pkgs/applications/graphics/grafx2/default.nix+1−1 pkgs/applications/graphics/graphicsmagick/compat.nix+37 pkgs/applications/graphics/graphicsmagick/default.nix+4−5 pkgs/applications/graphics/gthumb/default.nix+29−14 pkgs/applications/graphics/hugin/default.nix+5−5 pkgs/applications/graphics/imagej/default.nix+1−1 pkgs/applications/graphics/imgcat/default.nix+33 pkgs/applications/graphics/imlibsetroot/default.nix+1−1 pkgs/applications/graphics/imv/default.nix+16−9 pkgs/applications/graphics/inkscape/default.nix+20−12 pkgs/applications/graphics/jbrout/default.nix+1 pkgs/applications/graphics/jpegoptim/default.nix+3−3 pkgs/applications/graphics/k3d/default.nix+15−15 pkgs/applications/graphics/kgraphviewer/default.nix+3−3 pkgs/applications/graphics/kipi-plugins/default.nix+3−3 pkgs/applications/graphics/krita/default.nix+11−9 pkgs/applications/graphics/krop/default.nix+40 pkgs/applications/graphics/ktikz/default.nix+2−3 pkgs/applications/graphics/leocad/default.nix+3−3 pkgs/applications/graphics/meshlab/default.nix+13−9 pkgs/applications/graphics/meshlab/fix-2016.02.patch−88 pkgs/applications/graphics/meshlab/fix-20180627-beta.patch+25 pkgs/applications/graphics/mozjpeg/default.nix+8−10 pkgs/applications/graphics/mypaint/default.nix+9−4 pkgs/applications/graphics/nomacs/default.nix+4−7 pkgs/applications/graphics/nomacs/fix-appdata-install.patch−13 pkgs/applications/graphics/ocrad/default.nix+1−1 pkgs/applications/graphics/openimageio/default.nix+4−4 pkgs/applications/graphics/openscad/default.nix+19−9 pkgs/applications/graphics/panotools/default.nix+1−1 pkgs/applications/graphics/paraview/default.nix+25−12 pkgs/applications/graphics/pbrt/default.nix+8−3 pkgs/applications/graphics/pbrt/openexr-cmake-3.12.patch+26 pkgs/applications/graphics/pencil/default.nix+15−15 pkgs/applications/graphics/photivo/default.nix+2−2 pkgs/applications/graphics/photoflow/default.nix+56 pkgs/applications/graphics/photoqt/default.nix−1 pkgs/applications/graphics/phototonic/default.nix+3−5 pkgs/applications/graphics/pinta/default.nix+1−1 pkgs/applications/graphics/pqiv/default.nix+2−2 pkgs/applications/graphics/processing/default.nix−39 pkgs/applications/graphics/processing/use-nixpkgs-jre.patch−88 pkgs/applications/graphics/processing3/default.nix+63 pkgs/applications/graphics/qcomicbook/default.nix+43 pkgs/applications/graphics/qiv/default.nix+4−3 pkgs/applications/graphics/qscreenshot/default.nix+3−2 pkgs/applications/graphics/qtpfsgui/default.nix+1−1 pkgs/applications/graphics/rapcad/default.nix+3−2 pkgs/applications/graphics/rapid-photo-downloader/default.nix+71 pkgs/applications/graphics/rawtherapee/default.nix+5−5 pkgs/applications/graphics/renderdoc/custom_swig.patch−32 pkgs/applications/graphics/renderdoc/default.nix+25−37 pkgs/applications/graphics/sane/backends/brscan4/default.nix+4−4 pkgs/applications/graphics/sane/backends/generic.nix+1−1 pkgs/applications/graphics/sane/xsane.nix+4−4 pkgs/applications/graphics/scantailor/advanced.nix+26 pkgs/applications/graphics/scantailor/default.nix+1−1 pkgs/applications/graphics/screencloud/default.nix+1−1 pkgs/applications/graphics/seg3d/default.nix+3−3 pkgs/applications/graphics/shotwell/default.nix+21−14 pkgs/applications/graphics/shutter/default.nix+14−9 pkgs/applications/graphics/smartdeblur/default.nix+1−1 pkgs/applications/graphics/solvespace/default.nix+6−6 pkgs/applications/graphics/sxiv/default.nix+4−4 pkgs/applications/graphics/synfigstudio/default.nix+2−2 pkgs/applications/graphics/tesseract/default.nix+34−30 pkgs/applications/graphics/ufraw/default.nix+21−5 pkgs/applications/graphics/unigine-valley/default.nix+3−3 pkgs/applications/graphics/viewnior/default.nix+3−3 pkgs/applications/graphics/vimiv/default.nix+2−2 pkgs/applications/graphics/write_stylus/default.nix+65 pkgs/applications/graphics/xara/default.nix+1−1 pkgs/applications/graphics/xfig/builder.sh−28 pkgs/applications/graphics/xfig/default.nix+27−32 pkgs/applications/graphics/yacreader/default.nix+25 pkgs/applications/graphics/yed/default.nix+3−3 pkgs/applications/graphics/zgv/default.nix+1−1 pkgs/applications/inferno/default.nix+1−1 pkgs/applications/kde/akonadi-import-wizard.nix+20 pkgs/applications/kde/akonadi-mime.nix+2−2 pkgs/applications/kde/akonadi/akonadi-paths.patch+60−61 pkgs/applications/kde/akonadi/default.nix+2−2 pkgs/applications/kde/ark/default.nix+1−1 pkgs/applications/kde/default.nix+16−4 pkgs/applications/kde/dolphin.nix+6−2 pkgs/applications/kde/dragon.nix+25 pkgs/applications/kde/eventviews.nix+4−2 pkgs/applications/kde/fetch.sh+1−1 pkgs/applications/kde/grantleetheme/default.nix+3−3 pkgs/applications/kde/grantleetheme/grantlee-merge-theme-dirs.patch+83−81 pkgs/applications/kde/k3b.nix+14−8 pkgs/applications/kde/kalarm.nix+37 pkgs/applications/kde/kalarmcal.nix+2−2 pkgs/applications/kde/kcalutils.nix+2−2 pkgs/applications/kde/kdebugsettings.nix+20 pkgs/applications/kde/kdenlive-cmake-concurrent-module.patch−12 pkgs/applications/kde/kdenlive.nix+2−10 pkgs/applications/kde/kdepim-addons.nix+25 pkgs/applications/kde/kdepim-runtime.nix+2−2 pkgs/applications/kde/kio-extras.nix+2−2 pkgs/applications/kde/kitinerary.nix+19 pkgs/applications/kde/kleopatra.nix+2−2 pkgs/applications/kde/kmail-account-wizard.nix+2−2 pkgs/applications/kde/kmailtransport.nix+4−2 pkgs/applications/kde/konqueror.nix+20 pkgs/applications/kde/konquest.nix+18 pkgs/applications/kde/konsole.nix+2−2 pkgs/applications/kde/kpimtextedit.nix+2−2 pkgs/applications/kde/kpkpass.nix+15 pkgs/applications/kde/krfb.nix+2−2 pkgs/applications/kde/ksystemlog.nix+17 pkgs/applications/kde/libkdegames.nix+26 pkgs/applications/kde/libkgapi.nix+3−2 pkgs/applications/kde/libkomparediff2.nix+1−1 pkgs/applications/kde/marble.nix+6−2 pkgs/applications/kde/mbox-importer.nix−3 pkgs/applications/kde/messagelib.nix+2−2 pkgs/applications/kde/okteta.nix−21 pkgs/applications/kde/okular.nix+16−14 pkgs/applications/kde/pim-data-exporter.nix+1−1 pkgs/applications/kde/pimcommon.nix+1−1 pkgs/applications/kde/spectacle.nix+2−1 pkgs/applications/kde/srcs.nix+876−852 pkgs/applications/misc/1password/default.nix+44 pkgs/applications/misc/acbuild/default.nix+1−1 pkgs/applications/misc/adobe-reader/default.nix+1−1 pkgs/applications/misc/airspy/default.nix+1−1 pkgs/applications/misc/airtame/default.nix+22−42 pkgs/applications/misc/alacritty/default.nix+59−17 pkgs/applications/misc/albert/default.nix+7−4 pkgs/applications/misc/antfs-cli/default.nix+5−4 pkgs/applications/misc/ape/apeclex.nix+8 pkgs/applications/misc/ape/clex.nix+25 pkgs/applications/misc/ape/default.nix+45 pkgs/applications/misc/apvlv/default.nix+9−1 pkgs/applications/misc/archiver/default.nix+28 pkgs/applications/misc/archiver/deps.nix+56 pkgs/applications/misc/artha/default.nix+2−2 pkgs/applications/misc/audio/soxr/default.nix+2−2 pkgs/applications/misc/audio/wavesurfer/default.nix+1−1 pkgs/applications/misc/avrdudess/default.nix+2−2 pkgs/applications/misc/barrier/default.nix+42 pkgs/applications/misc/bashSnippets/default.nix+1−1 pkgs/applications/misc/bb/default.nix+7−3 pkgs/applications/misc/bitcoinarmory/default.nix−1 pkgs/applications/misc/bleachbit/default.nix+2−2 pkgs/applications/misc/blender/default.nix+15−5 pkgs/applications/misc/buku/default.nix+16−8 pkgs/applications/misc/calcurse/default.nix+1−1 pkgs/applications/misc/calibre/default.nix+20−19 pkgs/applications/misc/calibre/disable_plugins.patch+17 pkgs/applications/misc/calibre/no_updates_dialog.patch+15 pkgs/applications/misc/cataract/build.nix+1−1 pkgs/applications/misc/cataract/default.nix+1−10 pkgs/applications/misc/cataract/unstable.nix+1−10 pkgs/applications/misc/cbatticon/default.nix+6−2 pkgs/applications/misc/cgminer/default.nix+1−1 pkgs/applications/misc/cheat/default.nix+2−2 pkgs/applications/misc/cherrytree/default.nix+4−4 pkgs/applications/misc/chirp/default.nix+5−5 pkgs/applications/misc/cli-visualizer/default.nix+3−3 pkgs/applications/misc/clipit/default.nix+2−2 pkgs/applications/misc/clipmenu/default.nix+33 pkgs/applications/misc/cointop/default.nix+31 pkgs/applications/misc/cointop/deps.nix+3 pkgs/applications/misc/confclerk/default.nix+4−4 pkgs/applications/misc/cool-retro-term/default.nix+1−1 pkgs/applications/misc/copyq/default.nix+5−4 pkgs/applications/misc/coursera-dl/default.nix+41 pkgs/applications/misc/cpp-ethereum/default.nix+5−4 pkgs/applications/misc/ctodo/default.nix+1−1 pkgs/applications/misc/cura/default.nix+21−6 pkgs/applications/misc/cura/lulzbot.nix+5−5 pkgs/applications/misc/curabydagoma/default.nix+76 pkgs/applications/misc/curaengine/default.nix+14−6 pkgs/applications/misc/dbeaver/default.nix+4−4 pkgs/applications/misc/dbvisualizer/default.nix+1−1 pkgs/applications/misc/deco/default.nix+2−2 pkgs/applications/misc/deepin-terminal/default.nix−46 pkgs/applications/misc/devilspie2/default.nix+2−2 pkgs/applications/misc/dfilemanager/default.nix+1−2 pkgs/applications/misc/diffpdf/default.nix+3−3 pkgs/applications/misc/digitalbitbox/default.nix+145 pkgs/applications/misc/djvulibre/default.nix+2−4 pkgs/applications/misc/dmenu/default.nix+5−5 pkgs/applications/misc/dmrconfig/default.nix+39 pkgs/applications/misc/doing/Gemfile+2 pkgs/applications/misc/doing/Gemfile.lock+25 pkgs/applications/misc/doing/default.nix+25 pkgs/applications/misc/doing/gemset.nix+60 pkgs/applications/misc/doomseeker/default.nix+13−10 pkgs/applications/misc/doomseeker/fix_paths.patch+40 pkgs/applications/misc/doomseeker/qt_build_fix.patch+47 pkgs/applications/misc/dozenal/default.nix+61 pkgs/applications/misc/dozenal/lua-header.patch+16 pkgs/applications/misc/dunst/default.nix+14−5 pkgs/applications/misc/eaglemode/default.nix+1−1 pkgs/applications/misc/electron-cash/default.nix+14−9 pkgs/applications/misc/electrum-ltc/default.nix−55 pkgs/applications/misc/electrum/dash.nix pkgs/applications/misc/electrum/default.nix+22−17 pkgs/applications/misc/electrum/ltc.nix+55 pkgs/applications/misc/ephemeralpg/default.nix+2−2 pkgs/applications/misc/et/default.nix+2−2 pkgs/applications/misc/eureka-editor/default.nix+39 pkgs/applications/misc/evilvte/default.nix+3 pkgs/applications/misc/evtest/default.nix+1−1 pkgs/applications/misc/exercism/default.nix+5−4 pkgs/applications/misc/exercism/deps.nix+201 pkgs/applications/misc/extract_url/default.nix+42 pkgs/applications/misc/far2l/add-nix-syntax-highlighting.patch−158 pkgs/applications/misc/far2l/default.nix+15−7 pkgs/applications/misc/fbreader/default.nix+50−20 pkgs/applications/misc/fbreader/typecheck.patch+11 pkgs/applications/misc/fetchmail/default.nix+2−1 pkgs/applications/misc/finalterm/default.nix−65 pkgs/applications/misc/fllog/default.nix+34 pkgs/applications/misc/flmsg/default.nix+34 pkgs/applications/misc/flrig/default.nix+34 pkgs/applications/misc/flwrap/default.nix+34 pkgs/applications/misc/font-manager/default.nix+15−14 pkgs/applications/misc/gImageReader/default.nix+71 pkgs/applications/misc/gammu/default.nix+2−2 pkgs/applications/misc/gcal/default.nix+2−2 pkgs/applications/misc/gcalcli/default.nix+17−22 pkgs/applications/misc/get_iplayer/default.nix+4−4 pkgs/applications/misc/girara/default.nix+7−24 pkgs/applications/misc/gkrellm/default.nix+1−1 pkgs/applications/misc/gksu/default.nix+5−5 pkgs/applications/misc/glava/default.nix+81 pkgs/applications/misc/gmtp/default.nix+8−4 pkgs/applications/misc/gnome-usage/default.nix+37 pkgs/applications/misc/gnss-sdr/default.nix+2−1 pkgs/applications/misc/gnuradio-nacl/default.nix−39 pkgs/applications/misc/gnuradio-rds/default.nix−38 pkgs/applications/misc/gnuradio/ais.nix pkgs/applications/misc/gnuradio/default.nix+7−5 pkgs/applications/misc/gnuradio/gsm.nix pkgs/applications/misc/gnuradio/limesdr.nix+38 pkgs/applications/misc/gnuradio/nacl.nix+39 pkgs/applications/misc/gnuradio/osmosdr.nix pkgs/applications/misc/gnuradio/rds.nix+38 pkgs/applications/misc/go-jira/default.nix+22 pkgs/applications/misc/golden-cheetah/default.nix+19−5 pkgs/applications/misc/goldendict/default.nix+11−9 pkgs/applications/misc/gollum/Gemfile.lock+27−19 pkgs/applications/misc/gollum/default.nix+1 pkgs/applications/misc/gollum/gemset.nix+64−29 pkgs/applications/misc/googleearth/default.nix+36−18 pkgs/applications/misc/googler/default.nix+2−2 pkgs/applications/misc/gosmore/default.nix+3 pkgs/applications/misc/gosmore/pointer_int_comparison.patch+11 pkgs/applications/misc/gpa/default.nix+3−3 pkgs/applications/misc/gphoto2/default.nix+2−2 pkgs/applications/misc/gphoto2/gphotofs.nix+5−5 pkgs/applications/misc/gpsprune/default.nix+8−13 pkgs/applications/misc/gpx-viewer/default.nix+3−3 pkgs/applications/misc/gpx/default.nix+23 pkgs/applications/misc/gpxsee/default.nix+12−7 pkgs/applications/misc/gqrx/default.nix+2−2 pkgs/applications/misc/gramps/default.nix+17−18 pkgs/applications/misc/gremlin-console/default.nix+29 pkgs/applications/misc/guake/default.nix+25−57 pkgs/applications/misc/gummi/default.nix+1−1 pkgs/applications/misc/gutenberg/default.nix+35 pkgs/applications/misc/gv/default.nix+14−3 pkgs/applications/misc/gxmessage/default.nix+3−2 pkgs/applications/misc/gxneur/default.nix+11−15 pkgs/applications/misc/hamster-time-tracker/default.nix+4−4 pkgs/applications/misc/haxor-news/default.nix+2−2 pkgs/applications/misc/hdate/default.nix+16 pkgs/applications/misc/hello-unfree/default.nix+23 pkgs/applications/misc/hello/default.nix+6−5 pkgs/applications/misc/houdini/default.nix+1−1 pkgs/applications/misc/houdini/runtime.nix+7−7 pkgs/applications/misc/hovercraft/default.nix+35 pkgs/applications/misc/hr/default.nix+1−1 pkgs/applications/misc/hstr/default.nix+3−3 pkgs/applications/misc/hubstaff/default.nix+2−2 pkgs/applications/misc/hugo/default.nix+8−2 pkgs/applications/misc/hugo/deps.nix+382−95 pkgs/applications/misc/hyper/default.nix+6−7 pkgs/applications/misc/icesl/default.nix+4−4 pkgs/applications/misc/img2pdf/default.nix+27 pkgs/applications/misc/ipmicfg/default.nix+6−5 pkgs/applications/misc/ipmiview/default.nix+4−6 pkgs/applications/misc/jekyll/basic/Gemfile.lock+19−21 pkgs/applications/misc/jekyll/basic/gemset.nix+38−38 pkgs/applications/misc/jekyll/default.nix+2 pkgs/applications/misc/jekyll/full/Gemfile+1−1 pkgs/applications/misc/jekyll/full/Gemfile.lock+27−32 pkgs/applications/misc/jekyll/full/gemset.nix+54−63 pkgs/applications/misc/jekyll/update.sh+15 pkgs/applications/misc/jgmenu/default.nix+3−3 pkgs/applications/misc/jigdo/default.nix+1−1 pkgs/applications/misc/josm/default.nix+5−5 pkgs/applications/misc/jrnl/default.nix+3−5 pkgs/applications/misc/k2pdfopt/default.nix+1−1 pkgs/applications/misc/kdbplus/default.nix+3−3 pkgs/applications/misc/kdeconnect/default.nix+5−4 pkgs/applications/misc/keepass-plugins/keeagent/default.nix+4−4 pkgs/applications/misc/keepass-plugins/keepassrpc/default.nix+3−3 pkgs/applications/misc/keepass/default.nix+25−8 pkgs/applications/misc/keepass/keepass-plugins-load.patch+1 pkgs/applications/misc/keepass/keepass-plugins.patch+13 pkgs/applications/misc/keepassx/cmake.patch−18 pkgs/applications/misc/keepassx/community.nix+62−7 pkgs/applications/misc/keepassx/darwin.patch+14−14 pkgs/applications/misc/keepassx/qt511.patch+15 pkgs/applications/misc/khal/default.nix+15−10 pkgs/applications/misc/khard/default.nix+24−4 pkgs/applications/misc/kitty/default.nix+31−10 pkgs/applications/misc/kitty/fix-paths.patch+27 pkgs/applications/misc/kiwix/default.nix+6−3 pkgs/applications/misc/krename/default.nix+7−7 pkgs/applications/misc/krusader/default.nix+2−2 pkgs/applications/misc/kupfer/default.nix+2−4 pkgs/applications/misc/latte-dock/default.nix+16−13 pkgs/applications/misc/librecad/default.nix+1−1 pkgs/applications/misc/lilyterm/default.nix+8−9 pkgs/applications/misc/limesuite/default.nix+51 pkgs/applications/misc/llpp/default.nix+5−7 pkgs/applications/misc/lxterminal/default.nix+8−7 pkgs/applications/misc/lyx/default.nix+11−4 pkgs/applications/misc/madonctl/default.nix+1−1 pkgs/applications/misc/makeself/Use-rm-from-PATH.patch+43 pkgs/applications/misc/makeself/default.nix+6−3 pkgs/applications/misc/mako/default.nix+25 pkgs/applications/misc/masterpdfeditor/default.nix+53−52 pkgs/applications/misc/mdp/default.nix+3−3 pkgs/applications/misc/mediainfo-gui/default.nix+4−4 pkgs/applications/misc/mediainfo/default.nix+2−2 pkgs/applications/misc/memo/default.nix+22−8 pkgs/applications/misc/menumaker/default.nix+21 pkgs/applications/misc/merkaartor/default.nix+1−1 pkgs/applications/misc/minergate-cli/default.nix+36 pkgs/applications/misc/minergate/default.nix+36 pkgs/applications/misc/mlterm/default.nix+2−2 pkgs/applications/misc/moonlight-embedded/default.nix+10−9 pkgs/applications/misc/mop/default.nix+4−3 pkgs/applications/misc/mucommander/default.nix+84 pkgs/applications/misc/multibootusb/default.nix+59 pkgs/applications/misc/multimon-ng/default.nix+2−2 pkgs/applications/misc/mupdf/darwin.patch+27−32 pkgs/applications/misc/mupdf/default.nix+14−23 pkgs/applications/misc/mupdf/default.upstream+1−1 pkgs/applications/misc/mupdf/mupdf-1.12-shared_libs-1.patch−41 pkgs/applications/misc/mupdf/mupdf-1.14-shared_libs.patch+39 pkgs/applications/misc/mwic/default.nix+3−3 pkgs/applications/misc/mysql-workbench/default.nix+68−91 pkgs/applications/misc/mysql-workbench/fix-gdal-includes.patch+47 pkgs/applications/misc/mysql-workbench/hardcode-paths.patch+187 pkgs/applications/misc/navipowm/default.nix+1−1 pkgs/applications/misc/navit/CMakeLists.txt.patch+13 pkgs/applications/misc/navit/default.nix+77−17 pkgs/applications/misc/neap/default.nix+44 pkgs/applications/misc/netsurf/buildsystem/default.nix+2−2 pkgs/applications/misc/netsurf/libcss/default.nix+2 pkgs/applications/misc/nix-tour/default.nix+4−5 pkgs/applications/misc/nixnote2/default.nix+9−2 pkgs/applications/misc/nnn/default.nix+2−2 pkgs/applications/misc/notejot/default.nix+48 pkgs/applications/misc/notify-osd-customizable/default.nix+47 pkgs/applications/misc/notify-osd/default.nix+4−4 pkgs/applications/misc/nrsc5/default.nix+5−3 pkgs/applications/misc/nut/default.nix+4−3 pkgs/applications/misc/ocropus/default.nix+1−1 pkgs/applications/misc/octoprint/default.nix+42−17 pkgs/applications/misc/octoprint/plugins.nix+1−1 pkgs/applications/misc/ola/default.nix+6−3 pkgs/applications/misc/omegat.nix+40 pkgs/applications/misc/onboard/default.nix+9−8 pkgs/applications/misc/oneko/default.nix+4−5 pkgs/applications/misc/open-pdf-presenter/default.nix−22 pkgs/applications/misc/openbrf/default.nix+2−2 pkgs/applications/misc/opencpn/default.nix+3−3 pkgs/applications/misc/opentx/default.nix+61 pkgs/applications/misc/orca/default.nix+21−15 pkgs/applications/misc/orpie/default.nix+1−1 pkgs/applications/misc/osmctools/default.nix+1 pkgs/applications/misc/osmium-tool/default.nix+23 pkgs/applications/misc/overmind/default.nix+27 pkgs/applications/misc/pbpst/default.nix+49 pkgs/applications/misc/pcmanfm/default.nix+2−2 pkgs/applications/misc/pcmanx-gtk2/default.nix+13−7 pkgs/applications/misc/pdf-quench/default.nix+37 pkgs/applications/misc/pdfdiff/default.nix+1−1 pkgs/applications/misc/pdfmod/default.nix+5−4 pkgs/applications/misc/pdfpc/default.nix+2−2 pkgs/applications/misc/pdfshuffler/default.nix+5−4 pkgs/applications/misc/perkeep/default.nix+13−53 pkgs/applications/misc/pgadmin/default.nix+1−1 pkgs/applications/misc/pgmanage/default.nix+15−6 pkgs/applications/misc/pinfo/default.nix−1 pkgs/applications/misc/plank/default.nix+48 pkgs/applications/misc/plasma-applet-volumewin7mixer/cmake.patch+20 pkgs/applications/misc/plasma-applet-volumewin7mixer/default.nix+26 pkgs/applications/misc/playonlinux/default.nix+5−7 pkgs/applications/misc/plover/default.nix+40−19 pkgs/applications/misc/polar-bookshelf/default.nix+87 pkgs/applications/misc/polybar/default.nix+29−9 pkgs/applications/misc/posterazor/default.nix+4−3 pkgs/applications/misc/projectlibre/default.nix+44 pkgs/applications/misc/pstree/default.nix+1−1 pkgs/applications/misc/pt/default.nix+1−1 pkgs/applications/misc/ptask/default.nix+3−2 pkgs/applications/misc/ptask/json_c_is_error.patch+13 pkgs/applications/misc/pwsafe/default.nix+23−41 pkgs/applications/misc/pytrainer/default.nix+17−8 pkgs/applications/misc/pytrainer/fix-test-tz.patch+24−12 pkgs/applications/misc/qlcplus/default.nix+2−2 pkgs/applications/misc/qmapshack/default.nix+4−4 pkgs/applications/misc/qpdfview/default.nix+14−10 pkgs/applications/misc/qradiolink/default.nix+59 pkgs/applications/misc/qsstv/default.nix+54 pkgs/applications/misc/qsyncthingtray/default.nix+2−3 pkgs/applications/misc/qtbitcointrader/default.nix+2−2 pkgs/applications/misc/ranger/default.nix+14−9 pkgs/applications/misc/redis-desktop-manager/default.nix+8−12 pkgs/applications/misc/redshift/default.nix+37−13 pkgs/applications/misc/regextester/default.nix+58 pkgs/applications/misc/rescuetime/default.nix+1−1 pkgs/applications/misc/robo3t/default.nix+4−3 pkgs/applications/misc/rofi/config.patch+54 pkgs/applications/misc/rofi/default.nix+15−7 pkgs/applications/misc/rofi/wrapper.nix+22 pkgs/applications/misc/roxterm/default.nix+9−9 pkgs/applications/misc/rsibreak/default.nix+28 pkgs/applications/misc/rtl-sdr/default.nix+11−5 pkgs/applications/misc/rtl_433/default.nix+26 pkgs/applications/misc/rtv/default.nix+7−14 pkgs/applications/misc/rxvt_unicode/default.nix+1 pkgs/applications/misc/rxvt_unicode/wrapper.nix+1−1 pkgs/applications/misc/safeeyes/default.nix+71 pkgs/applications/misc/sakura/default.nix+2−2 pkgs/applications/misc/sbagen/default.nix+1−1 pkgs/applications/misc/sc-im/default.nix+2−2 pkgs/applications/misc/sdcv/default.nix+1−2 pkgs/applications/misc/sent/default.nix+6−2 pkgs/applications/misc/sequeler/default.nix+45 pkgs/applications/misc/sigal/default.nix+6−4 pkgs/applications/misc/simplenote/default.nix+9−8 pkgs/applications/misc/slade/default.nix+1−1 pkgs/applications/misc/slade/git.nix+1−1 pkgs/applications/misc/sleepyhead/default.nix+42 pkgs/applications/misc/slic3r-prusa3d/default.nix−98 pkgs/applications/misc/slic3r/default.nix+1 pkgs/applications/misc/slic3r/prusa3d.nix+128 pkgs/applications/misc/slstatus/default.nix+30 pkgs/applications/misc/soapyairspy/default.nix+30 pkgs/applications/misc/soapybladerf/default.nix+31 pkgs/applications/misc/soapyhackrf/default.nix+30 pkgs/applications/misc/soapyremote/default.nix+28 pkgs/applications/misc/soapysdr/default.nix+50 pkgs/applications/misc/soapyuhd/default.nix+34 pkgs/applications/misc/solaar/default.nix+11−9 pkgs/applications/misc/spacefm/default.nix+12−8 pkgs/applications/misc/ssocr/default.nix+24 pkgs/applications/misc/st/default.nix+10−11 pkgs/applications/misc/st/st-fix-deletekey.patch−15 pkgs/applications/misc/stag/default.nix+1−1 pkgs/applications/misc/stog/default.nix+9−8 pkgs/applications/misc/stupidterm/default.nix+3−3 pkgs/applications/misc/subsurface/default.nix+3−3 pkgs/applications/misc/sweethome3d/default.nix+4−4 pkgs/applications/misc/sweethome3d/editors.nix+5−5 pkgs/applications/misc/synapse/default.nix+5−5 pkgs/applications/misc/synergy/default.nix+32−14 pkgs/applications/misc/synergy/respect_macos_arch.patch+61 pkgs/applications/misc/synergy/update_gtest_gmock.patch+158 pkgs/applications/misc/tabula/default.nix+39 pkgs/applications/misc/taskell/default.nix+59 pkgs/applications/misc/taskjuggler/2.x/default.nix+6−6 pkgs/applications/misc/taskjuggler/Gemfile.lock+7−7 pkgs/applications/misc/taskjuggler/default.nix+9−4 pkgs/applications/misc/taskjuggler/gemset.nix+34−26 pkgs/applications/misc/tasknc/default.nix+4−3 pkgs/applications/misc/tasksh/default.nix+3−3 pkgs/applications/misc/taskwarrior/default.nix+4−4 pkgs/applications/misc/termdown/default.nix+3−3 pkgs/applications/misc/terminal-notifier/default.nix+3−1 pkgs/applications/misc/terminator/default.nix+6−10 pkgs/applications/misc/terminus/default.nix+43 pkgs/applications/misc/termite/add_errno_header.patch+24 pkgs/applications/misc/termite/default.nix+32−44 pkgs/applications/misc/termite/remove_ldflags_macos.patch+25 pkgs/applications/misc/termite/wrapper.nix+15 pkgs/applications/misc/teseq/default.nix+22 pkgs/applications/misc/tilda/default.nix+2−2 pkgs/applications/misc/tilix/default.nix+12−6 pkgs/applications/misc/timewarrior/default.nix+4−4 pkgs/applications/misc/tint2/default.nix+9−11 pkgs/applications/misc/tnef/default.nix+2−2 pkgs/applications/misc/todiff/default.nix+25 pkgs/applications/misc/todolist/default.nix+22 pkgs/applications/misc/toggldesktop/TogglDesktop.pro+19 pkgs/applications/misc/toggldesktop/default.nix+148 pkgs/applications/misc/toggldesktop/libtoggl.pro+20 pkgs/applications/misc/toot/default.nix+3−3 pkgs/applications/misc/tootle/default.nix+38 pkgs/applications/misc/tqsl/default.nix+1−8 pkgs/applications/misc/translate-shell/default.nix+18−81 pkgs/applications/misc/truecrypt/default.nix−98 pkgs/applications/misc/truecrypt/gcc6.patch−61 pkgs/applications/misc/tvbrowser/bin.nix+56 pkgs/applications/misc/twmn/default.nix+2−1 pkgs/applications/misc/tzupdate/default.nix+2−3 pkgs/applications/misc/udiskie/default.nix+5−6 pkgs/applications/misc/unixcw/default.nix+37 pkgs/applications/misc/unixcw/remove-use-of-dlopen.patch+677 pkgs/applications/misc/urh/default.nix+5−4 pkgs/applications/misc/urlscan/default.nix+7−4 pkgs/applications/misc/valauncher/default.nix−28 pkgs/applications/misc/valentina/default.nix+67 pkgs/applications/misc/vcal/default.nix+37 pkgs/applications/misc/veracrypt/default.nix+23−28 pkgs/applications/misc/verbiste/default.nix+1−1 pkgs/applications/misc/viking/default.nix+4−4 pkgs/applications/misc/visidata/default.nix+29 pkgs/applications/misc/vit/default.nix+2−2 pkgs/applications/misc/volnoti/default.nix+2−2 pkgs/applications/misc/vym/default.nix+6−6 pkgs/applications/misc/weather/default.nix+1−1 pkgs/applications/misc/wego/default.nix+5−1 pkgs/applications/misc/welle-io/default.nix+8−8 pkgs/applications/misc/wikicurses/default.nix+8−15 pkgs/applications/misc/wmname/default.nix+1−1 pkgs/applications/misc/wordnet/default.nix+9−4 pkgs/applications/misc/worker/default.nix+2−2 pkgs/applications/misc/workrave/default.nix+10−19 pkgs/applications/misc/wsjtx/default.nix+3−3 pkgs/applications/misc/xautoclick/default.nix+5−2 pkgs/applications/misc/xca/default.nix+16−11 pkgs/applications/misc/xchm/default.nix+3−2 pkgs/applications/misc/xdgmenumaker/default.nix+2−2 pkgs/applications/misc/xfe/default.nix+2−2 pkgs/applications/misc/xfontsel/default.nix+2−2 pkgs/applications/misc/xiphos/default.nix+4−4 pkgs/applications/misc/xkbd/default.nix+30 pkgs/applications/misc/xlog/default.nix+29 pkgs/applications/misc/xmind/default.nix+3−3 pkgs/applications/misc/xmove/default.nix+1 pkgs/applications/misc/xmr-stak/default.nix+12−7 pkgs/applications/misc/xmrig/default.nix+34 pkgs/applications/misc/xmrig/proxy.nix+34 pkgs/applications/misc/xneur/0.8.nix−29 pkgs/applications/misc/xneur/default.nix+23−32 pkgs/applications/misc/xneur/src-for-default.nix−9 pkgs/applications/misc/xneur/src-info-for-default.nix−5 pkgs/applications/misc/xpad/default.nix+2−2 pkgs/applications/misc/xpdf/cmake_version.patch+15 pkgs/applications/misc/xpdf/default.nix+18−8 pkgs/applications/misc/xrandr-invert-colors/default.nix+2−2 pkgs/applications/misc/xscope/default.nix+24 pkgs/applications/misc/xterm/default.nix+3−3 pkgs/applications/misc/xtermcontrol/default.nix+3−3 pkgs/applications/misc/yaft/default.nix+1−1 pkgs/applications/misc/yakuake/default.nix+3−2 pkgs/applications/misc/yarssr/default.nix+68 pkgs/applications/misc/yate/default.nix+5−4 pkgs/applications/misc/yubioath-desktop/default.nix+3−3 pkgs/applications/misc/zathura/core/default.nix+17−34 pkgs/applications/misc/zathura/core/icon.xpm−120 pkgs/applications/misc/zathura/djvu/default.nix+7−16 pkgs/applications/misc/zathura/djvu/gtkflags.patch−23 pkgs/applications/misc/zathura/pdf-mupdf/default.nix+17−18 pkgs/applications/misc/zathura/pdf-poppler/default.nix+7−14 pkgs/applications/misc/zathura/ps/default.nix+8−17 pkgs/applications/misc/zathura/ps/gtkflags.patch−23 pkgs/applications/misc/zathura/wrapper.nix+1−1 pkgs/applications/misc/zscroll/default.nix+1−1 pkgs/applications/networking/apache-directory-studio/default.nix+3−3 pkgs/applications/networking/bittorrentsync/generic.nix+4−4 pkgs/applications/networking/browsers/brave/default.nix+144 pkgs/applications/networking/browsers/browsh/default.nix+60 pkgs/applications/networking/browsers/browsh/deps.nix+272 pkgs/applications/networking/browsers/chromium/browser.nix+1 pkgs/applications/networking/browsers/chromium/common.nix+65−59 pkgs/applications/networking/browsers/chromium/default.nix+8−8 pkgs/applications/networking/browsers/chromium/patches/chromium-gcc5-r4.patch−98 pkgs/applications/networking/browsers/chromium/patches/constexpr-fix.patch−98 pkgs/applications/networking/browsers/chromium/patches/fix_network_api_crash.patch−77 pkgs/applications/networking/browsers/chromium/patches/include-math-for-round.patch−34 pkgs/applications/networking/browsers/chromium/patches/nix_plugin_paths_52.patch−70 pkgs/applications/networking/browsers/chromium/patches/nix_plugin_paths_68.patch+61 pkgs/applications/networking/browsers/chromium/patches/remove-webp-include-69.patch+11 pkgs/applications/networking/browsers/chromium/plugins.nix+10−7 pkgs/applications/networking/browsers/chromium/update.sh+1−1 pkgs/applications/networking/browsers/chromium/upstream-info.nix+9−9 pkgs/applications/networking/browsers/conkeror/default.nix+4−4 pkgs/applications/networking/browsers/dillo/default.nix+3−2 pkgs/applications/networking/browsers/dwb/default.nix−35 pkgs/applications/networking/browsers/eolie/0001-Extend-the-python-path-rather-than-replacing-it.patch−35 pkgs/applications/networking/browsers/eolie/0001-Remove-post-install-script-handle-in-nix-config-inst.patch−23 pkgs/applications/networking/browsers/eolie/default.nix+35−42 pkgs/applications/networking/browsers/falkon/default.nix+11−10 pkgs/applications/networking/browsers/firefox-bin/beta_sources.nix+409−389 pkgs/applications/networking/browsers/firefox-bin/default.nix+37−21 pkgs/applications/networking/browsers/firefox-bin/devedition_sources.nix+409−389 pkgs/applications/networking/browsers/firefox-bin/release_sources.nix+415−385 pkgs/applications/networking/browsers/firefox-bin/update.nix+1−1 pkgs/applications/networking/browsers/firefox/common.nix+110−57 pkgs/applications/networking/browsers/firefox/fix-pa-context-connect-retval.patch+26 pkgs/applications/networking/browsers/firefox/no-buildconfig.patch+3−3 pkgs/applications/networking/browsers/firefox/packages.nix+103−68 pkgs/applications/networking/browsers/firefox/update.nix+2−4 pkgs/applications/networking/browsers/firefox/wrapper.nix+43−35 pkgs/applications/networking/browsers/google-chrome/default.nix+12−16 pkgs/applications/networking/browsers/jumanji/default.nix−31 pkgs/applications/networking/browsers/links2/default.nix+3−3 pkgs/applications/networking/browsers/luakit/default.nix+61 pkgs/applications/networking/browsers/lynx/default.nix+7−5 pkgs/applications/networking/browsers/midori/default.nix+5−5 pkgs/applications/networking/browsers/mozilla-plugins/flashplayer/default.nix+12−11 pkgs/applications/networking/browsers/mozilla-plugins/flashplayer/standalone.nix+8−13 pkgs/applications/networking/browsers/mozilla-plugins/google-talk-plugin/default.nix+6−6 pkgs/applications/networking/browsers/mozilla-plugins/trezor/default.nix−47 pkgs/applications/networking/browsers/opera/default.nix+6−3 pkgs/applications/networking/browsers/otter/default.nix+3−3 pkgs/applications/networking/browsers/palemoon/default.nix+10−8 pkgs/applications/networking/browsers/qtchan/default.nix+44 pkgs/applications/networking/browsers/qutebrowser/default.nix+30−18 pkgs/applications/networking/browsers/surf/default.nix+2−2 pkgs/applications/networking/browsers/tor-browser-bundle-bin/default.nix+33−26 pkgs/applications/networking/browsers/tor-browser-bundle/default.nix+29−6 pkgs/applications/networking/browsers/uzbl/default.nix+7−6 pkgs/applications/networking/browsers/vimb/default.nix+4−4 pkgs/applications/networking/browsers/vimprobable2/default.nix+4−4 pkgs/applications/networking/browsers/vivaldi/chromium-gcc-r1.patch−14 pkgs/applications/networking/browsers/vivaldi/chromium-gcc5-r1.patch−66 pkgs/applications/networking/browsers/vivaldi/chromium-gn-bootstrap-r14.patch−27 pkgs/applications/networking/browsers/vivaldi/default.nix+8−8 pkgs/applications/networking/browsers/vivaldi/ffmpeg-codecs.nix+9−14 pkgs/applications/networking/browsers/vivaldi/update.sh+2−1 pkgs/applications/networking/browsers/w3m/default.nix+1 pkgs/applications/networking/c14/default.nix+4−5 pkgs/applications/networking/charles/default.nix+48 pkgs/applications/networking/cloudflared/default.nix+25 pkgs/applications/networking/cloudflared/deps.nix+444 pkgs/applications/networking/cluster/click/default.nix+29 pkgs/applications/networking/cluster/click/fix_cargo_lock_version.patch+13 pkgs/applications/networking/cluster/cni/default.nix+3−6 pkgs/applications/networking/cluster/cni/plugins.nix+33 pkgs/applications/networking/cluster/docker-machine/default.nix+2−2 pkgs/applications/networking/cluster/docker-machine/kvm.nix+2−2 pkgs/applications/networking/cluster/docker-machine/kvm2.nix+31 pkgs/applications/networking/cluster/flink/default.nix+8−12 pkgs/applications/networking/cluster/habitat/default.nix+1−1 pkgs/applications/networking/cluster/hadoop/default.nix+148−44 pkgs/applications/networking/cluster/helm/default.nix+33−34 pkgs/applications/networking/cluster/helm/deps.nix+840 pkgs/applications/networking/cluster/helmfile/default.nix+37 pkgs/applications/networking/cluster/heptio-ark/default.nix+25 pkgs/applications/networking/cluster/hetzner-kube/default.nix+24 pkgs/applications/networking/cluster/kanif/default.nix+1−1 pkgs/applications/networking/cluster/kompose/default.nix+3−3 pkgs/applications/networking/cluster/kontemplate/default.nix+25−16 pkgs/applications/networking/cluster/kontemplate/deps.nix+48−57 pkgs/applications/networking/cluster/kops/default.nix+5−5 pkgs/applications/networking/cluster/ksonnet/default.nix+23 pkgs/applications/networking/cluster/kubernetes/default.nix+14−11 pkgs/applications/networking/cluster/kubetail/default.nix+30 pkgs/applications/networking/cluster/kubeval/default.nix+48 pkgs/applications/networking/cluster/kubeval/deps.nix+174 pkgs/applications/networking/cluster/luigi/default.nix+32 pkgs/applications/networking/cluster/mesos/default.nix+20−14 pkgs/applications/networking/cluster/minikube/default.nix+27−36 pkgs/applications/networking/cluster/minikube/localkube.patch−20 pkgs/applications/networking/cluster/minishift/default.nix+67 pkgs/applications/networking/cluster/nomad/default.nix+2−2 pkgs/applications/networking/cluster/openshift/default.nix+49−18 pkgs/applications/networking/cluster/panamax/api/Gemfile−23 pkgs/applications/networking/cluster/panamax/api/Gemfile.lock−164 pkgs/applications/networking/cluster/panamax/api/default.nix−74 pkgs/applications/networking/cluster/panamax/api/gemset.nix−568 pkgs/applications/networking/cluster/panamax/ui/Gemfile−31 pkgs/applications/networking/cluster/panamax/ui/Gemfile.lock−226 pkgs/applications/networking/cluster/panamax/ui/default.nix−72 pkgs/applications/networking/cluster/panamax/ui/gemset.nix−789 pkgs/applications/networking/cluster/pig/default.nix+2−2 pkgs/applications/networking/cluster/spark/default.nix+11−13 pkgs/applications/networking/cluster/stern/default.nix+25 pkgs/applications/networking/cluster/stern/deps.nix+336 pkgs/applications/networking/cluster/taktuk/default.nix+3−3 pkgs/applications/networking/cluster/terraform-landscape/Gemfile.lock+5−5 pkgs/applications/networking/cluster/terraform-landscape/default.nix+8−9 pkgs/applications/networking/cluster/terraform-landscape/gemset.nix+8−8 pkgs/applications/networking/cluster/terraform-providers/data.nix+654 pkgs/applications/networking/cluster/terraform-providers/default.nix+28 pkgs/applications/networking/cluster/terraform-providers/gandi/default.nix+26 pkgs/applications/networking/cluster/terraform-providers/gandi/deps.nix+21 pkgs/applications/networking/cluster/terraform-providers/ibm/default.nix+38 pkgs/applications/networking/cluster/terraform-providers/libvirt/default.nix+51 pkgs/applications/networking/cluster/terraform-providers/providers.txt+16 pkgs/applications/networking/cluster/terraform-providers/update-all+143 pkgs/applications/networking/cluster/terraform/default.nix+43−9 pkgs/applications/networking/cluster/terraform/providers/data.nix−507 pkgs/applications/networking/cluster/terraform/providers/default.nix−25 pkgs/applications/networking/cluster/terraform/providers/update-all−100 pkgs/applications/networking/cluster/terragrunt/default.nix+5−5 pkgs/applications/networking/cluster/terragrunt/deps.nix+16−16 pkgs/applications/networking/compactor/default.nix+52 pkgs/applications/networking/corebird/default.nix+17−13 pkgs/applications/networking/davmail/default.nix+8−6 pkgs/applications/networking/drive/default.nix+1−1 pkgs/applications/networking/dropbox/cli.nix pkgs/applications/networking/dropbox/default.nix+4−4 pkgs/applications/networking/enhanced-ctorrent/default.nix+14−1 pkgs/applications/networking/errbot/default.nix+5−3 pkgs/applications/networking/esniper/default.nix+6−8 pkgs/applications/networking/feedreaders/canto-curses/default.nix+3−3 pkgs/applications/networking/feedreaders/canto-daemon/default.nix+4−5 pkgs/applications/networking/feedreaders/feedreader/default.nix+50 pkgs/applications/networking/feedreaders/newsbeuter/default.nix−61 pkgs/applications/networking/feedreaders/newsboat/default.nix+6−4 pkgs/applications/networking/feedreaders/rssguard/default.nix+2−8 pkgs/applications/networking/feedreaders/rsstail/default.nix+2−2 pkgs/applications/networking/firehol/default.nix+34−5 pkgs/applications/networking/flent/default.nix+30 pkgs/applications/networking/flent/http-getter.nix+23 pkgs/applications/networking/flexget/default.nix+63−62 pkgs/applications/networking/ftp/filezilla/default.nix+2−2 pkgs/applications/networking/ftp/taxi/default.nix+47 pkgs/applications/networking/gmailieer/default.nix+3−3 pkgs/applications/networking/gns3/default.nix+3−3 pkgs/applications/networking/gns3/server.nix+13 pkgs/applications/networking/google-drive-ocamlfuse/default.nix+6−7 pkgs/applications/networking/gopher/gopherclient/default.nix+1 pkgs/applications/networking/ids/bro/default.nix+3−3 pkgs/applications/networking/ids/daq/default.nix+8−4 pkgs/applications/networking/ids/snort/default.nix+9−4 pkgs/applications/networking/ike/default.nix−2 pkgs/applications/networking/instant-messengers/SkypeExport/default.nix+2−2 pkgs/applications/networking/instant-messengers/amsn/default.nix+6−1 pkgs/applications/networking/instant-messengers/baresip/default.nix+7−9 pkgs/applications/networking/instant-messengers/bitlbee-discord/default.nix+4−3 pkgs/applications/networking/instant-messengers/bitlbee-facebook/default.nix+2−2 pkgs/applications/networking/instant-messengers/bitlbee-steam/default.nix+1−1 pkgs/applications/networking/instant-messengers/bitlbee/default.nix+16−13 pkgs/applications/networking/instant-messengers/blink/default.nix+7−6 pkgs/applications/networking/instant-messengers/bluejeans/default.nix+49 pkgs/applications/networking/instant-messengers/coyim/default.nix+1−1 pkgs/applications/networking/instant-messengers/dino/default.nix+7−7 pkgs/applications/networking/instant-messengers/discord/default.nix+3−3 pkgs/applications/networking/instant-messengers/ekiga/default.nix+8−6 pkgs/applications/networking/instant-messengers/franz/default.nix+13−19 pkgs/applications/networking/instant-messengers/gajim/default.nix+38−97 pkgs/applications/networking/instant-messengers/gitter/default.nix+71 pkgs/applications/networking/instant-messengers/gomuks/default.nix+23 pkgs/applications/networking/instant-messengers/hipchat/default.nix+8−18 pkgs/applications/networking/instant-messengers/jackline/default.nix+4−6 pkgs/applications/networking/instant-messengers/jackline/tls-0.9.0.patch−29 pkgs/applications/networking/instant-messengers/jitsi/default.nix+3−7 pkgs/applications/networking/instant-messengers/linphone/default.nix+8−1 pkgs/applications/networking/instant-messengers/matrique/default.nix+55 pkgs/applications/networking/instant-messengers/mattermost-desktop/default.nix+81 pkgs/applications/networking/instant-messengers/mcabber/default.nix+6−2 pkgs/applications/networking/instant-messengers/messenger-for-desktop/default.nix−104 pkgs/applications/networking/instant-messengers/mikutter/default.nix+1−1 pkgs/applications/networking/instant-messengers/nheko/default.nix+75 pkgs/applications/networking/instant-messengers/pidgin-plugins/pidgin-opensteamworks/default.nix+10−11 pkgs/applications/networking/instant-messengers/pidgin-plugins/pidgin-skypeweb/default.nix+2−2 pkgs/applications/networking/instant-messengers/pidgin-plugins/pidgin-xmpp-receipts/default.nix+2−2 pkgs/applications/networking/instant-messengers/pidgin-plugins/purple-discord/default.nix+31 pkgs/applications/networking/instant-messengers/pidgin-plugins/purple-facebook/default.nix+7−7 pkgs/applications/networking/instant-messengers/pidgin-plugins/purple-hangouts/default.nix+5−5 pkgs/applications/networking/instant-messengers/pidgin-plugins/purple-lurch/default.nix+31 pkgs/applications/networking/instant-messengers/pidgin-plugins/purple-matrix/default.nix+15−13 pkgs/applications/networking/instant-messengers/pidgin-plugins/purple-xmpp-http-upload/default.nix+25 pkgs/applications/networking/instant-messengers/pidgin-plugins/sipe/default.nix+2−2 pkgs/applications/networking/instant-messengers/pidgin-plugins/skype4pidgin/default.nix+2−2 pkgs/applications/networking/instant-messengers/pidgin-plugins/telegram-purple/default.nix+4−4 pkgs/applications/networking/instant-messengers/pidgin-plugins/tox-prpl/default.nix+1−1 pkgs/applications/networking/instant-messengers/pidgin/default.nix+8−9 pkgs/applications/networking/instant-messengers/pidgin/wrapper.nix+1−1 pkgs/applications/networking/instant-messengers/poezio/default.nix+28 pkgs/applications/networking/instant-messengers/pond/default.nix+4−5 pkgs/applications/networking/instant-messengers/profanity/default.nix+27−8 pkgs/applications/networking/instant-messengers/profanity/patches/packages-osx.patch+11 pkgs/applications/networking/instant-messengers/profanity/patches/undefined-macros.patch+40 pkgs/applications/networking/instant-messengers/psi-plus/default.nix+7−6 pkgs/applications/networking/instant-messengers/psi/default.nix+4−3 pkgs/applications/networking/instant-messengers/pybitmessage/default.nix+7−7 pkgs/applications/networking/instant-messengers/qtox/default.nix+20−15 pkgs/applications/networking/instant-messengers/quaternion/default.nix+18−9 pkgs/applications/networking/instant-messengers/rambox/bare.nix+7−8 pkgs/applications/networking/instant-messengers/rambox/default.nix+21−7 pkgs/applications/networking/instant-messengers/rambox/disable-tooltips.patch−19 pkgs/applications/networking/instant-messengers/rambox/hide-check-for-updates.patch−35 pkgs/applications/networking/instant-messengers/rambox/sencha/bare.nix+4−4 pkgs/applications/networking/instant-messengers/ratox/default.nix+10−8 pkgs/applications/networking/instant-messengers/ratox/ldlibs.patch−5 pkgs/applications/networking/instant-messengers/ricochet/default.nix+1−1 pkgs/applications/networking/instant-messengers/ring-daemon/default.nix+4−5 pkgs/applications/networking/instant-messengers/riot/riot-web.nix+5−3 pkgs/applications/networking/instant-messengers/salut-a-toi/default.nix+1−1 pkgs/applications/networking/instant-messengers/signal-desktop/beta.nix−87 pkgs/applications/networking/instant-messengers/signal-desktop/default.nix+70−49 pkgs/applications/networking/instant-messengers/silc-client/default.nix+1−1 pkgs/applications/networking/instant-messengers/skype-call-recorder/default.nix+1−1 pkgs/applications/networking/instant-messengers/skypeforlinux/default.nix+19−15 pkgs/applications/networking/instant-messengers/slack-term/default.nix+23 pkgs/applications/networking/instant-messengers/slack/default.nix+20−12 pkgs/applications/networking/instant-messengers/spectral/default.nix+33 pkgs/applications/networking/instant-messengers/stride/default.nix+2−2 pkgs/applications/networking/instant-messengers/swift-im/default.nix+50 pkgs/applications/networking/instant-messengers/swift-im/qt-5.11.patch+10 pkgs/applications/networking/instant-messengers/swift-im/scons.patch+53 pkgs/applications/networking/instant-messengers/teamspeak/client.nix+5−4 pkgs/applications/networking/instant-messengers/teamspeak/server.nix+4−4 pkgs/applications/networking/instant-messengers/telegram/tdesktop/default.nix+18−124 pkgs/applications/networking/instant-messengers/telegram/tdesktop/fix-internal-compiler-error.patch+68 pkgs/applications/networking/instant-messengers/telegram/tdesktop/generic.nix+151 pkgs/applications/networking/instant-messengers/telepathy/gabble/default.nix+9−8 pkgs/applications/networking/instant-messengers/telepathy/haze/default.nix+4−4 pkgs/applications/networking/instant-messengers/telepathy/idle/default.nix+3−3 pkgs/applications/networking/instant-messengers/telepathy/logger/default.nix+8−8 pkgs/applications/networking/instant-messengers/telepathy/mission-control/default.nix+3−3 pkgs/applications/networking/instant-messengers/telepathy/salut/default.nix+6−6 pkgs/applications/networking/instant-messengers/torchat/default.nix−1 pkgs/applications/networking/instant-messengers/toxic/default.nix+4−4 pkgs/applications/networking/instant-messengers/utox/default.nix+17−10 pkgs/applications/networking/instant-messengers/vacuum/default.nix+1−1 pkgs/applications/networking/instant-messengers/viber/default.nix+4−6 pkgs/applications/networking/instant-messengers/vk-messenger/default.nix+53 pkgs/applications/networking/instant-messengers/wavebox/default.nix+66 pkgs/applications/networking/instant-messengers/weechat-matrix-bridge/default.nix−44 pkgs/applications/networking/instant-messengers/weechat-xmpp/default.nix−35 pkgs/applications/networking/instant-messengers/weechat-xmpp/libpath.patch−16 pkgs/applications/networking/instant-messengers/wire-desktop/default.nix+109 pkgs/applications/networking/instant-messengers/zoom-us/default.nix+82−80 pkgs/applications/networking/instant-messengers/zoom-us/update.sh+7 pkgs/applications/networking/insync/default.nix+4−4 pkgs/applications/networking/ipfs-cluster/default.nix+41 pkgs/applications/networking/ipfs-migrator/default.nix+3−3 pkgs/applications/networking/ipfs-migrator/deps.nix+4−13 pkgs/applications/networking/ipfs/default.nix+3−3 pkgs/applications/networking/irc/bip/default.nix+1−1 pkgs/applications/networking/irc/chatzilla/default.nix+1−1 pkgs/applications/networking/irc/communi/default.nix+1−1 pkgs/applications/networking/irc/hexchat/default.nix+4−4 pkgs/applications/networking/irc/ii/default.nix+4−4 pkgs/applications/networking/irc/irssi/default.nix+4−3 pkgs/applications/networking/irc/irssi/otr/default.nix+1−1 pkgs/applications/networking/irc/konversation/default.nix+3−2 pkgs/applications/networking/irc/quassel/default.nix+2−2 pkgs/applications/networking/irc/quassel/qt5_11.patch+72 pkgs/applications/networking/irc/quassel/source.nix+2−2 pkgs/applications/networking/irc/sic/default.nix+1−1 pkgs/applications/networking/irc/weechat/default.nix+68−35 pkgs/applications/networking/irc/weechat/scripts/default.nix+15 pkgs/applications/networking/irc/weechat/scripts/wee-slack/default.nix+39 pkgs/applications/networking/irc/weechat/scripts/wee-slack/libpath.patch+13 pkgs/applications/networking/irc/weechat/scripts/weechat-matrix-bridge/default.nix+46 pkgs/applications/networking/irc/weechat/scripts/weechat-matrix-bridge/library-path.patch pkgs/applications/networking/irc/weechat/scripts/weechat-xmpp/default.nix+36 pkgs/applications/networking/irc/weechat/scripts/weechat-xmpp/libpath.patch+16 pkgs/applications/networking/jmeter/default.nix+40−12 pkgs/applications/networking/linssid/default.nix+2−2 pkgs/applications/networking/mailreaders/afew/default.nix+11−1 pkgs/applications/networking/mailreaders/alpine/default.nix+1−1 pkgs/applications/networking/mailreaders/astroid/default.nix+24−9 pkgs/applications/networking/mailreaders/balsa/default.nix+61 pkgs/applications/networking/mailreaders/claws-mail/default.nix+26−17 pkgs/applications/networking/mailreaders/imapfilter.nix+2−2 pkgs/applications/networking/mailreaders/inboxer/default.nix+10−7 pkgs/applications/networking/mailreaders/lumail/default.nix+42−10 pkgs/applications/networking/mailreaders/mailnag/default.nix+2−2 pkgs/applications/networking/mailreaders/mailpile/default.nix+1−1 pkgs/applications/networking/mailreaders/mblaze/default.nix+2−2 pkgs/applications/networking/mailreaders/msgviewer/default.nix+1−1 pkgs/applications/networking/mailreaders/mutt/default.nix+2−2 pkgs/applications/networking/mailreaders/neomutt/default.nix+18−5 pkgs/applications/networking/mailreaders/notmuch-bower/default.nix+3−3 pkgs/applications/networking/mailreaders/notmuch/default.nix+32−45 pkgs/applications/networking/mailreaders/nylas-mail-bin/default.nix+8−11 pkgs/applications/networking/mailreaders/realpine/default.nix+1−1 pkgs/applications/networking/mailreaders/sup/default.nix+2−3 pkgs/applications/networking/mailreaders/sylpheed/default.nix+3−3 pkgs/applications/networking/mailreaders/thunderbird-bin/default.nix+12−14 pkgs/applications/networking/mailreaders/thunderbird-bin/release_sources.nix+245−255 pkgs/applications/networking/mailreaders/thunderbird/default.nix+38−24 pkgs/applications/networking/modem-manager-gui/default.nix+50 pkgs/applications/networking/msmtp/default.nix+13−5 pkgs/applications/networking/mumble/default.nix+25−13 pkgs/applications/networking/ndppd/default.nix+17−2 pkgs/applications/networking/netperf/default.nix+13−5 pkgs/applications/networking/newsreaders/liferea/default.nix+8−9 pkgs/applications/networking/newsreaders/pan/default.nix+23−8 pkgs/applications/networking/newsreaders/quiterss/default.nix+11−4 pkgs/applications/networking/newsreaders/slrn/default.nix+4−1 pkgs/applications/networking/nextcloud-client/default.nix+3−3 pkgs/applications/networking/nload/default.nix+14−1 pkgs/applications/networking/offrss/default.nix+1−1 pkgs/applications/networking/ostinato/default.nix+4−4 pkgs/applications/networking/owamp/default.nix+28 pkgs/applications/networking/owncloud-client/default.nix+4−3 pkgs/applications/networking/owncloud-client/find-sql.patch+12 pkgs/applications/networking/p2p/deluge/default.nix+13−3 pkgs/applications/networking/p2p/eiskaltdcpp/default.nix+5−4 pkgs/applications/networking/p2p/frostwire/default.nix+76−13 pkgs/applications/networking/p2p/frostwire/frostwire-bin.nix+31 pkgs/applications/networking/p2p/gnunet/default.nix+2−2 pkgs/applications/networking/p2p/gnunet/git.nix+92 pkgs/applications/networking/p2p/gnunet/svn.nix−93 pkgs/applications/networking/p2p/ktorrent/default.nix+20−2 pkgs/applications/networking/p2p/ncdc/default.nix+1−1 pkgs/applications/networking/p2p/opentracker/default.nix+7−7 pkgs/applications/networking/p2p/qbittorrent/default.nix+18−15 pkgs/applications/networking/p2p/retroshare/default.nix+3−2 pkgs/applications/networking/p2p/soulseekqt/default.nix+73 pkgs/applications/networking/p2p/synapse-bt/default.nix+27 pkgs/applications/networking/p2p/tixati/default.nix+4−4 pkgs/applications/networking/p2p/transmission-remote-gtk/default.nix+16−13 pkgs/applications/networking/p2p/transmission/default.nix+7−23 pkgs/applications/networking/p2p/tribler/default.nix+9−7 pkgs/applications/networking/p2p/twister/default.nix+4−2 pkgs/applications/networking/p2p/zeronet/default.nix+35 pkgs/applications/networking/pjsip/default.nix+3−3 pkgs/applications/networking/protocol/default.nix+20 pkgs/applications/networking/protonmail-bridge/default.nix+85 pkgs/applications/networking/pyload/default.nix+1−2 pkgs/applications/networking/remote/anydesk/default.nix+32−12 pkgs/applications/networking/remote/citrix-receiver/default.nix+57−52 pkgs/applications/networking/remote/citrix-receiver/wrapper.nix+19 pkgs/applications/networking/remote/freerdp/default.nix+7−7 pkgs/applications/networking/remote/freerdp/legacy.nix+1−2 pkgs/applications/networking/remote/putty/default.nix+20−6 pkgs/applications/networking/remote/remmina/default.nix+26−39 pkgs/applications/networking/remote/ssvnc/default.nix+1−1 pkgs/applications/networking/remote/teamviewer/default.nix+16−45 pkgs/applications/networking/remote/x2goclient/default.nix+14−9 pkgs/applications/networking/remote/x2goclient/qt511.patch+15 pkgs/applications/networking/remote/xrdp/default.nix+5−5 pkgs/applications/networking/resilio-sync/default.nix+5−5 pkgs/applications/networking/seafile-client/default.nix+8−6 pkgs/applications/networking/sieve-connect/default.nix+48 pkgs/applications/networking/sipcmd/default.nix+1 pkgs/applications/networking/siproxd/default.nix+1 pkgs/applications/networking/sniffers/etherape/default.nix+9−11 pkgs/applications/networking/sniffers/kismet/default.nix+1−1 pkgs/applications/networking/sniffers/wireshark/default.nix+55−12 pkgs/applications/networking/soapui/default.nix+51 pkgs/applications/networking/spideroak/default.nix+13−13 pkgs/applications/networking/ssb/patchwork-classic/default.nix+106 pkgs/applications/networking/super-productivity/default.nix+105 pkgs/applications/networking/sync/backintime/common.nix+2−2 pkgs/applications/networking/sync/backintime/qt4.nix+5−2 pkgs/applications/networking/sync/casync/default.nix+52 pkgs/applications/networking/sync/desync/default.nix+27 pkgs/applications/networking/sync/desync/deps.nix+129 pkgs/applications/networking/sync/lsyncd/default.nix+14−6 pkgs/applications/networking/sync/rclone/browser.nix+25 pkgs/applications/networking/sync/rclone/default.nix+3−3 pkgs/applications/networking/sync/rsync/base.nix+1−1 pkgs/applications/networking/sync/rsync/default.nix+2−2 pkgs/applications/networking/sync/rsync/rrsync.nix+1−1 pkgs/applications/networking/syncplay/default.nix+8−13 pkgs/applications/networking/syncthing-gtk/default.nix+18−10 pkgs/applications/networking/syncthing-gtk/disable-syncthing-binary-configuration.patch−77 pkgs/applications/networking/syncthing/default.nix+2−2 pkgs/applications/networking/syncthing/inotify-deps.nix−21 pkgs/applications/networking/syncthing/inotify.nix−37 pkgs/applications/networking/tcpkali/default.nix+2−2 pkgs/applications/networking/testssl/default.nix+22−17 pkgs/applications/networking/testssl/testssl.patch−10 pkgs/applications/networking/transporter/default.nix+73 pkgs/applications/networking/tsung/default.nix+50 pkgs/applications/networking/vnstat/default.nix+4−4 pkgs/applications/networking/weather/meteo/default.nix+54 pkgs/applications/networking/znc/default.nix+20−10 pkgs/applications/networking/znc/modules.nix+3−1 pkgs/applications/office/abiword/default.nix+9−12 pkgs/applications/office/aesop/default.nix+50 pkgs/applications/office/atlassian-cli/default.nix+49 pkgs/applications/office/atlassian-cli/wrapper.sh+20 pkgs/applications/office/autokey/default.nix+38 pkgs/applications/office/autokey/remove-requires-dbus-python.patch+11 pkgs/applications/office/beancount/bean-add.nix+1−1 pkgs/applications/office/beancount/default.nix−44 pkgs/applications/office/bookworm/default.nix+77 pkgs/applications/office/calligra/default.nix+7−13 pkgs/applications/office/calligra/qt5_11.patch+98 pkgs/applications/office/cb2bib/default.nix+3−3 pkgs/applications/office/fava/default.nix+3−5 pkgs/applications/office/gnucash/2.4.nix+90 pkgs/applications/office/gnucash/2.6.nix+5−7 pkgs/applications/office/gnucash/default.nix+63−43 pkgs/applications/office/gnumeric/default.nix+9−9 pkgs/applications/office/grisbi/default.nix+4−4 pkgs/applications/office/homebank/default.nix+5−5 pkgs/applications/office/ib/tws/default.nix+1−1 pkgs/applications/office/impressive/default.nix+3−3 pkgs/applications/office/jabref/default.nix+2−2 pkgs/applications/office/jameica/default.nix+75 pkgs/applications/office/keepnote/default.nix+1−1 pkgs/applications/office/kexi/default.nix+10−3 pkgs/applications/office/kmymoney/default.nix+78 pkgs/applications/office/ledger-web/Gemfile.lock+3−3 pkgs/applications/office/ledger-web/gemset.nix+10−2 pkgs/applications/office/ledger/2.6.3.nix+5−1 pkgs/applications/office/ledger/default.nix+6−3 pkgs/applications/office/libreoffice/default-primary-src.nix+6−6 pkgs/applications/office/libreoffice/default.nix+112−93 pkgs/applications/office/libreoffice/generate-libreoffice-srcs.py+8−1 pkgs/applications/office/libreoffice/libreoffice-srcs-still.nix+352−296 pkgs/applications/office/libreoffice/libreoffice-srcs.nix+298−235 pkgs/applications/office/libreoffice/still-primary-src.nix+5−5 pkgs/applications/office/libreoffice/still.nix+121−95 pkgs/applications/office/libreoffice/wrapper.nix+19 pkgs/applications/office/libreoffice/wrapper.sh+18 pkgs/applications/office/marp/default.nix+2−2 pkgs/applications/office/mendeley/default.nix+9−13 pkgs/applications/office/mendeley/update.nix+2−2 pkgs/applications/office/moneyplex/default.nix+6−6 pkgs/applications/office/mytetra/default.nix+9−4 pkgs/applications/office/osmo/default.nix+2−2 pkgs/applications/office/paperwork/backend.nix+14−6 pkgs/applications/office/paperwork/default.nix+11−11 pkgs/applications/office/pinpoint/default.nix+2−2 pkgs/applications/office/planner/default.nix+3−3 pkgs/applications/office/scribus/default.nix+3−3 pkgs/applications/office/scribus/unstable.nix+39 pkgs/applications/office/skrooge/default.nix+14−6 pkgs/applications/office/spice-up/default.nix+15−15 pkgs/applications/office/timetrap/default.nix+1−1 pkgs/applications/office/todo.txt-cli/default.nix+2−2 pkgs/applications/office/todoman/default.nix+65 pkgs/applications/office/treesheets/default.nix+4−4 pkgs/applications/office/tryton/default.nix+30−7 pkgs/applications/office/trytond/default.nix+10−7 pkgs/applications/office/tudu/default.nix+2−2 pkgs/applications/office/wordgrinder/default.nix+1−1 pkgs/applications/office/wpsoffice/default.nix+2−2 pkgs/applications/office/zim/default.nix+3−3 pkgs/applications/office/zotero/default.nix+7−6 pkgs/applications/science/astronomy/astrolabe-generator/default.nix+31 pkgs/applications/science/astronomy/celestia/default.nix+7−10 pkgs/applications/science/astronomy/gildas/aarch64.patch+12 pkgs/applications/science/astronomy/gildas/clang.patch+22 pkgs/applications/science/astronomy/gildas/default.nix+69 pkgs/applications/science/astronomy/gildas/wrapper.patch+19 pkgs/applications/science/astronomy/gpredict/default.nix+11−11 pkgs/applications/science/astronomy/gravit/default.nix+5−4 pkgs/applications/science/astronomy/openspace/assets.patch+100 pkgs/applications/science/astronomy/openspace/config.patch+49 pkgs/applications/science/astronomy/openspace/constexpr.patch+91 pkgs/applications/science/astronomy/openspace/default.nix+89 pkgs/applications/science/astronomy/openspace/vrpn.patch+13 pkgs/applications/science/astronomy/stellarium/default.nix+16−9 pkgs/applications/science/astronomy/xearth/default.nix+32 pkgs/applications/science/biology/EZminc/default.nix+32 pkgs/applications/science/biology/N3/default.nix+38 pkgs/applications/science/biology/bcftools/default.nix+4−6 pkgs/applications/science/biology/bowtie2/default.nix+3−2 pkgs/applications/science/biology/conglomerate/default.nix+34 pkgs/applications/science/biology/diamond/default.nix+1−1 pkgs/applications/science/biology/freebayes/default.nix+1−1 pkgs/applications/science/biology/hisat2/default.nix+49 pkgs/applications/science/biology/hmmer/default.nix+25 pkgs/applications/science/biology/igv/default.nix+3−3 pkgs/applications/science/biology/inormalize/default.nix+39 pkgs/applications/science/biology/inormalize/lgmask-interp.patch+10 pkgs/applications/science/biology/inormalize/nu_correct_norm-interp.patch+10 pkgs/applications/science/biology/iv/default.nix+1−1 pkgs/applications/science/biology/minc-tools/default.nix+17−10 pkgs/applications/science/biology/minc-widgets/default.nix+34 pkgs/applications/science/biology/minimap2/default.nix+31 pkgs/applications/science/biology/mni_autoreg/default.nix+36 pkgs/applications/science/biology/mosdepth/default.nix+45 pkgs/applications/science/biology/ncbi-tools/default.nix+6−1 pkgs/applications/science/biology/neuron/default.nix+1−1 pkgs/applications/science/biology/paml/default.nix+2−2 pkgs/applications/science/biology/picard-tools/default.nix+2−2 pkgs/applications/science/biology/platypus/default.nix+3−3 pkgs/applications/science/biology/raxml/default.nix+2−3 pkgs/applications/science/biology/samtools/default.nix+2−2 pkgs/applications/science/biology/seaview/default.nix+41 pkgs/applications/science/biology/snpeff/default.nix+3−3 pkgs/applications/science/biology/somatic-sniper/default.nix+28 pkgs/applications/science/biology/somatic-sniper/somatic-sniper.patch+26 pkgs/applications/science/biology/star/default.nix+2−2 pkgs/applications/science/biology/strelka/default.nix+37 pkgs/applications/science/biology/vcftools/default.nix+3−3 pkgs/applications/science/chemistry/avogadro/default.nix+3−3 pkgs/applications/science/chemistry/gwyddion/default.nix+3−3 pkgs/applications/science/chemistry/jmol/default.nix+54 pkgs/applications/science/chemistry/molden/default.nix+6−4 pkgs/applications/science/chemistry/molden/dont_register_file_types.patch+29 pkgs/applications/science/chemistry/octopus/default.nix+15−13 pkgs/applications/science/chemistry/openmolcas/default.nix+72 pkgs/applications/science/chemistry/pymol/default.nix+6−6 pkgs/applications/science/chemistry/quantum-espresso/default.nix+49 pkgs/applications/science/chemistry/siesta/default.nix+69 pkgs/applications/science/electronics/adms/default.nix+1−1 pkgs/applications/science/electronics/bitscope/common.nix−6 pkgs/applications/science/electronics/bitscope/packages.nix+1−8 pkgs/applications/science/electronics/eagle/default.nix−97 pkgs/applications/science/electronics/eagle/eagle.nix+83 pkgs/applications/science/electronics/eagle/eagle7.nix+97 pkgs/applications/science/electronics/eagle/eagle7_fixer.c pkgs/applications/science/electronics/geda/default.nix+3−1 pkgs/applications/science/electronics/gtkwave/default.nix+3−3 pkgs/applications/science/electronics/kicad/default.nix+53−53 pkgs/applications/science/electronics/kicad/unstable.nix+13−11 pkgs/applications/science/electronics/librepcb/default.nix+9−7 pkgs/applications/science/electronics/librepcb/fix-2017-12.patch−29 pkgs/applications/science/electronics/ngspice/default.nix+9−7 pkgs/applications/science/electronics/pcb/default.nix+9−2 pkgs/applications/science/electronics/pulseview/default.nix+2−2 pkgs/applications/science/electronics/verilator/default.nix+4−4 pkgs/applications/science/electronics/xcircuit/default.nix+35 pkgs/applications/science/geometry/drgeo/default.nix+4−2 pkgs/applications/science/logic/abc/default.nix+11−10 pkgs/applications/science/logic/abella/default.nix+2−2 pkgs/applications/science/logic/acgtk/default.nix+10−41 pkgs/applications/science/logic/acgtk/install-emacs-to-site-lisp.patch−23 pkgs/applications/science/logic/acgtk/use-nix-ocaml-byteflags.patch−11 pkgs/applications/science/logic/aiger/default.nix+6−4 pkgs/applications/science/logic/alt-ergo/default.nix+4−4 pkgs/applications/science/logic/aspino/default.nix+19−7 pkgs/applications/science/logic/beluga/default.nix+34 pkgs/applications/science/logic/boolector/default.nix+38−29 pkgs/applications/science/logic/btor2tools/default.nix+33 pkgs/applications/science/logic/cedille/default.nix+50 pkgs/applications/science/logic/celf/default.nix+36 pkgs/applications/science/logic/coq/8.3.nix−82 pkgs/applications/science/logic/coq/8.4.nix−97 pkgs/applications/science/logic/coq/configure.8.3.patch−1112 pkgs/applications/science/logic/coq/configure.patch−11 pkgs/applications/science/logic/coq/default.nix+12−7 pkgs/applications/science/logic/coq/no-codesign.patch−19 pkgs/applications/science/logic/coq2html/default.nix+2−2 pkgs/applications/science/logic/cryptoverif/default.nix+2−2 pkgs/applications/science/logic/cvc4/default.nix+7−7 pkgs/applications/science/logic/elan/default.nix+44 pkgs/applications/science/logic/eprover/default.nix+7−8 pkgs/applications/science/logic/hol/default.nix+1−1 pkgs/applications/science/logic/hol_light/default.nix+22−17 pkgs/applications/science/logic/isabelle/default.nix+2−2 pkgs/applications/science/logic/jonprl/default.nix+1−1 pkgs/applications/science/logic/lean/default.nix+2−2 pkgs/applications/science/logic/lean2/default.nix+1−1 pkgs/applications/science/logic/leo2/default.nix+1−1 pkgs/applications/science/logic/lingeling/default.nix+49 pkgs/applications/science/logic/ltl2ba/default.nix+2−2 pkgs/applications/science/logic/matita/130312.nix−65 pkgs/applications/science/logic/matita/Makefile.patch−11 pkgs/applications/science/logic/matita/configure.patch−36 pkgs/applications/science/logic/matita/configure_130312.patch−35 pkgs/applications/science/logic/matita/default.nix−52 pkgs/applications/science/logic/mcrl2/default.nix+4−5 pkgs/applications/science/logic/monosat/default.nix+67 pkgs/applications/science/logic/ott/default.nix+2−2 pkgs/applications/science/logic/picosat/default.nix+3 pkgs/applications/science/logic/poly/default.nix+13−10 pkgs/applications/science/logic/potassco/clingo.nix+9−6 pkgs/applications/science/logic/prooftree/default.nix+12−10 pkgs/applications/science/logic/prover9/default.nix+1−1 pkgs/applications/science/logic/proverif/default.nix+4−4 pkgs/applications/science/logic/sad/default.nix+7−2 pkgs/applications/science/logic/sad/monoid.patch+51 pkgs/applications/science/logic/satallax/default.nix+1−1 pkgs/applications/science/logic/saw-tools/default.nix+2−2 pkgs/applications/science/logic/symbiyosys/default.nix+5−5 pkgs/applications/science/logic/tamarin-prover/default.nix+24−9 pkgs/applications/science/logic/tamarin-prover/ghc-8.4-support-term.patch+109 pkgs/applications/science/logic/tamarin-prover/ghc-8.4-support-theory.patch+130 pkgs/applications/science/logic/tamarin-prover/ghc-8.4-support-utils.patch+140 pkgs/applications/science/logic/tlaplus/default.nix+40 pkgs/applications/science/logic/tlaplus/tlaps.nix+54 pkgs/applications/science/logic/tlaplus/toolbox.nix+77 pkgs/applications/science/logic/tptp/default.nix+5−4 pkgs/applications/science/logic/vampire/default.nix+59 pkgs/applications/science/logic/verifast/default.nix+15−10 pkgs/applications/science/logic/why3/default.nix+4−4 pkgs/applications/science/logic/workcraft/default.nix+33 pkgs/applications/science/logic/yices/default.nix+6−4 pkgs/applications/science/logic/z3/4.5.0.nix−31 pkgs/applications/science/logic/z3/default.nix+16−4 pkgs/applications/science/machine-learning/labelimg/default.nix+23 pkgs/applications/science/machine-learning/shogun/default.nix+19−11 pkgs/applications/science/machine-learning/torch/torch-distro.nix+8−4 pkgs/applications/science/math/R/default.nix+9−7 pkgs/applications/science/math/almonds/default.nix+4−7 pkgs/applications/science/math/bcal/default.nix+6−5 pkgs/applications/science/math/bliss/default.nix+37 pkgs/applications/science/math/caffe/darwin.patch+47 pkgs/applications/science/math/caffe/default.nix+54−14 pkgs/applications/science/math/calc/default.nix+34−32 pkgs/applications/science/math/cbc/default.nix+4−4 pkgs/applications/science/math/clp/default.nix+15−17 pkgs/applications/science/math/cntk/default.nix+11−19 pkgs/applications/science/math/cntk/fix_std_bind.patch+11 pkgs/applications/science/math/colpack/default.nix+2−1 pkgs/applications/science/math/cplex/default.nix+82 pkgs/applications/science/math/csdp/default.nix+1−1 pkgs/applications/science/math/ecm/default.nix+3−3 pkgs/applications/science/math/form/default.nix+22 pkgs/applications/science/math/fricas/default.nix+2−2 pkgs/applications/science/math/gap/default.nix+70−15 pkgs/applications/science/math/geogebra/default.nix+4−8 pkgs/applications/science/math/gfan/default.nix+10−5 pkgs/applications/science/math/giac/default.nix+37−11 pkgs/applications/science/math/ginac/default.nix+4−3 pkgs/applications/science/math/glsurf/default.nix+4−3 pkgs/applications/science/math/gmsh/CMakeLists.txt.patch−37 pkgs/applications/science/math/gmsh/default.nix+9−11 pkgs/applications/science/math/gurobi/default.nix+54 pkgs/applications/science/math/hmetis/default.nix+42 pkgs/applications/science/math/jags/default.nix+7−7 pkgs/applications/science/math/lp_solve/default.nix+2−2 pkgs/applications/science/math/lrcalc/default.nix+41 pkgs/applications/science/math/mathematica/10.nix+2−4 pkgs/applications/science/math/mathematica/9.nix+2−4 pkgs/applications/science/math/mathematica/default.nix+13−21 pkgs/applications/science/math/mathematica/l10ns.nix+33 pkgs/applications/science/math/maxima/default.nix+44−10 pkgs/applications/science/math/maxima/known-ecl-failures.patch+21 pkgs/applications/science/math/mxnet/default.nix+29−17 pkgs/applications/science/math/nasc/default.nix+62 pkgs/applications/science/math/nauty/default.nix+2−2 pkgs/applications/science/math/palp/default.nix+86 pkgs/applications/science/math/pari/default.nix+21−9 pkgs/applications/science/math/pari/gp2c.nix+3−3 pkgs/applications/science/math/pari/unstable.nix−31 pkgs/applications/science/math/pspp/default.nix+13−2 pkgs/applications/science/math/pynac/default.nix+48 pkgs/applications/science/math/qalculate-gtk/default.nix+7−5 pkgs/applications/science/math/ratpoints/default.nix+21−5 pkgs/applications/science/math/ries/default.nix+21 pkgs/applications/science/math/ripser/default.nix+4−3 pkgs/applications/science/math/sage/README.md+117 pkgs/applications/science/math/sage/default.nix+135−210 pkgs/applications/science/math/sage/env-locations.nix+46 pkgs/applications/science/math/sage/env.patch−22 pkgs/applications/science/math/sage/fetch-mirrors.sh−11

9435 more files changed are not listed.

.editorconfig+2−2
@@ -13,8 +13,8 @@ charset = utf-8
1313
1414# see https://nixos.org/nixpkgs/manual/#chap-conventions
1515
16−# Match nix/ruby files, set indent to spaces with width of two
17−[*.{nix,rb}]
16+# Match nix/ruby/docbook files, set indent to spaces with width of two
17+[*.{nix,rb,xml}]
1818indent_style = space
1919indent_size = 2
2020
.gitattributesnew file+16
@@ -0,0 +1,16 @@
1+**/deps.nix linguist-generated
2+**/node-packages.nix linguist-generated
3+
4+pkgs/applications/editors/emacs-modes/*-generated.nix linguist-generated
5+pkgs/development/r-modules/*-packages.nix linguist-generated
6+pkgs/development/haskell-modules/hackage-packages.nix linguist-generated
7+pkgs/development/beam-modules/hex-packages.nix linguist-generated
8+
9+doc/** linguist-documentation
10+doc/default.nix linguist-documentation=false
11+
12+nixos/doc/** linguist-documentation
13+nixos/doc/default.nix linguist-documentation=false
14+
15+nixos/modules/module-list.nix merge=union
16+# pkgs/top-level/all-packages.nix merge=union
.github/CODEOWNERS+41−9
@@ -12,14 +12,19 @@
1212
1313# Libraries
1414/lib @edolstra @nbp
15−/lib/systems @nbp @ericson2314
15+/lib/systems @nbp @ericson2314 @matthewbauer
16+/lib/generators.nix @edolstra @nbp @Profpatsch
17+/lib/debug.nix @edolstra @nbp @Profpatsch
1618
1719# Nixpkgs Internals
1820/default.nix @nbp
1921/pkgs/top-level/default.nix @nbp @Ericson2314
2022/pkgs/top-level/impure.nix @nbp @Ericson2314
21−/pkgs/top-level/stage.nix @nbp @Ericson2314
22−/pkgs/stdenv
23+/pkgs/top-level/stage.nix @nbp @Ericson2314 @matthewbauer
24+/pkgs/top-level/splice.nix @Ericson2314 @matthewbauer
25+/pkgs/top-level/release-cross.nix @Ericson2314 @matthewbauer
26+/pkgs/stdenv/generic @Ericson2314 @matthewbauer
27+/pkgs/stdenv/cross @Ericson2314 @matthewbauer
2328/pkgs/build-support/cc-wrapper @Ericson2314 @orivej
2429/pkgs/build-support/bintools-wrapper @Ericson2314 @orivej
2530/pkgs/build-support/setup-hooks @Ericson2314
@@ -42,18 +47,22 @@
4247/nixos/doc/manual/man-nixos-option.xml @nbp
4348/nixos/modules/installer/tools/nixos-option.sh @nbp
4449
50+# NixOS modules
51+/nixos/modules @Infinisil
52+
4553# Python-related code and docs
54+/maintainers/scripts/update-python-libraries @FRidh
4655/pkgs/top-level/python-packages.nix @FRidh
4756/pkgs/development/interpreters/python @FRidh
4857/pkgs/development/python-modules @FRidh
4958/doc/languages-frameworks/python.md @FRidh
5059
5160# Haskell
52−/pkgs/development/compilers/ghc @peti
53−/pkgs/development/haskell-modules @peti
54−/pkgs/development/haskell-modules/default.nix @peti
55−/pkgs/development/haskell-modules/generic-builder.nix @peti
56−/pkgs/development/haskell-modules/hoogle.nix @peti
61+/pkgs/development/compilers/ghc @peti @ryantm @basvandijk
62+/pkgs/development/haskell-modules @peti @ryantm @basvandijk
63+/pkgs/development/haskell-modules/default.nix @peti @ryantm @basvandijk
64+/pkgs/development/haskell-modules/generic-builder.nix @peti @ryantm @basvandijk
65+/pkgs/development/haskell-modules/hoogle.nix @peti @ryantm @basvandijk
5766
5867# R
5968/pkgs/applications/science/math/R @peti
@@ -63,10 +72,21 @@
6372/pkgs/development/interpreters/ruby @zimbatm
6473/pkgs/development/ruby-modules @zimbatm
6574
75+# Rust
76+/pkgs/development/compilers/rust @Mic92 @LnL7
77+
6678# Darwin-related
6779/pkgs/stdenv/darwin @NixOS/darwin-maintainers
6880/pkgs/os-specific/darwin @NixOS/darwin-maintainers
6981
82+# C compilers
83+/pkgs/development/compilers/gcc @matthewbauer
84+/pkgs/development/compilers/llvm @matthewbauer
85+
86+# Compatibility stuff
87+/pkgs/top-level/unix-tools.nix @matthewbauer
88+/pkgs/development/tools/xcbuild @matthewbauer
89+
7090# Beam-related (Erlang, Elixir, LFE, etc)
7191/pkgs/development/beam-modules @gleber
7292/pkgs/development/interpreters/erlang @gleber
@@ -83,7 +103,6 @@
83103/pkgs/applications/editors/eclipse @rycee
84104
85105# https://github.com/NixOS/nixpkgs/issues/31401
86−/lib/maintainers.nix @ghost
87106/lib/licenses.nix @ghost
88107
89108# Qt / KDE
@@ -91,3 +110,16 @@
91110/pkgs/desktops/plasma-5 @ttuegel
92111/pkgs/development/libraries/kde-frameworks @ttuegel
93112/pkgs/development/libraries/qt-5 @ttuegel
113+
114+# PostgreSQL and related stuff
115+/pkgs/servers/sql/postgresql @thoughtpolice
116+/nixos/modules/services/databases/postgresql.xml @thoughtpolice
117+/nixos/modules/services/databases/postgresql.nix @thoughtpolice
118+/nixos/tests/postgresql.nix @thoughtpolice
119+
120+# Dhall
121+/pkgs/development/dhall-modules @Gabriel439 @Profpatsch
122+/pkgs/development/interpreters/dhall @Gabriel439 @Profpatsch
123+
124+# Idris
125+/pkgs/development/idris-modules @Infinisil
.github/CONTRIBUTING.md+3−1
@@ -20,6 +20,8 @@ under the terms of [COPYING](../COPYING), which is an MIT-like license.
2020 (Motivation for change. Additional information.)
2121 ```
2222
23+ For consistency, there should not be a period at the end of the commit message's summary line (the first line of the commit message).
24+
2325 Examples:
2426
2527 * nginx: init at 2.0.1
@@ -43,7 +45,7 @@ See the nixpkgs manual for more details on [standard meta-attributes](https://ni
4345
4446## Writing good commit messages
4547
46−In addition to writing properly formatted commit messages, it's important to include relevant information so other developers can later understand *why* a change was made. While this information usually can be found by digging code, mailing list archives, pull request discussions or upstream changes, it may require a lot of work.
48+In addition to writing properly formatted commit messages, it's important to include relevant information so other developers can later understand *why* a change was made. While this information usually can be found by digging code, mailing list/Discourse archives, pull request discussions or upstream changes, it may require a lot of work.
4749
4850For package version upgrades and such a one-line commit message is usually sufficient.
4951
.github/PULL_REQUEST_TEMPLATE.md+2−1
@@ -5,7 +5,7 @@
55
66<!-- Please check what applies. Note that these are not hard requirements but merely serve as information for reviewers. -->
77
8−- [ ] Tested using sandboxing ([nix.useSandbox](http://nixos.org/nixos/manual/options.html#opt-nix.useSandbox) on NixOS, or option `build-use-sandbox` in [`nix.conf`](http://nixos.org/nix/manual/#sec-conf-file) on non-NixOS)
8+- [ ] Tested using sandboxing ([nix.useSandbox](http://nixos.org/nixos/manual/options.html#opt-nix.useSandbox) on NixOS, or option `sandbox` in [`nix.conf`](http://nixos.org/nix/manual/#sec-conf-file) on non-NixOS)
99- Built on platform(s)
1010 - [ ] NixOS
1111 - [ ] macOS
@@ -13,6 +13,7 @@
1313- [ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside [nixos/tests](https://github.com/NixOS/nixpkgs/blob/master/nixos/tests))
1414- [ ] Tested compilation of all pkgs that depend on this change using `nix-shell -p nox --run "nox-review wip"`
1515- [ ] Tested execution of all binary files (usually in `./result/bin/`)
16+- [ ] Determined the impact on package closure size (by running `nix path-info -S` before and after)
1617- [ ] Fits [CONTRIBUTING.md](https://github.com/NixOS/nixpkgs/blob/master/.github/CONTRIBUTING.md).
1718
1819---
.version+1−1
@@ -1 +1 @@
1−18.03
1+19.03
COPYING−9
@@ -18,12 +18,3 @@ NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
1818LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
1919OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
2020WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
21−
22−======================================================================
23−
24−Note: the license above does not apply to the packages built by the
25−Nix Packages collection, merely to the package descriptions (i.e., Nix
26−expressions, build scripts, etc.). It also might not apply to patches
27−included in Nixpkgs, which may be derivative works of the packages to
28−which they apply. The aforementioned artifacts are all covered by the
29−licenses of the respective packages.
README.md+12−6
@@ -8,16 +8,16 @@ build daemon as so-called channels. To get channel information via git, add
88[nixpkgs-channels](https://github.com/NixOS/nixpkgs-channels.git) as a remote:
99
1010```
11−% git remote add channels git://github.com/NixOS/nixpkgs-channels.git
11+% git remote add channels https://github.com/NixOS/nixpkgs-channels.git
1212```
1313
1414For stability and maximum binary package support, it is recommended to maintain
15−custom changes on top of one of the channels, e.g. `nixos-17.09` for the latest
15+custom changes on top of one of the channels, e.g. `nixos-18.09` for the latest
1616release and `nixos-unstable` for the latest successful build of master:
1717
1818```
1919% git remote update channels
20−% git rebase channels/nixos-17.09
20+% git rebase channels/nixos-18.09
2121```
2222
2323For pull-requests, please rebase onto nixpkgs `master`.
@@ -31,11 +31,17 @@ For pull-requests, please rebase onto nixpkgs `master`.
3131* [Manual (NixOS)](https://nixos.org/nixos/manual/)
3232* [Community maintained wiki](https://nixos.wiki/)
3333* [Continuous package builds for unstable/master](https://hydra.nixos.org/jobset/nixos/trunk-combined)
34−* [Continuous package builds for 17.09 release](https://hydra.nixos.org/jobset/nixos/release-17.09)
34+* [Continuous package builds for 18.09 release](https://hydra.nixos.org/jobset/nixos/release-18.09)
3535* [Tests for unstable/master](https://hydra.nixos.org/job/nixos/trunk-combined/tested#tabs-constituents)
36−* [Tests for 17.09 release](https://hydra.nixos.org/job/nixos/release-17.09/tested#tabs-constituents)
36+* [Tests for 18.09 release](https://hydra.nixos.org/job/nixos/release-18.09/tested#tabs-constituents)
3737
3838Communication:
3939
40−* [Mailing list](https://groups.google.com/forum/#!forum/nix-devel)
40+* [Discourse Forum](https://discourse.nixos.org/)
4141* [IRC - #nixos on freenode.net](irc://irc.freenode.net/#nixos)
42+
43+Note: MIT license does not apply to the packages built by Nixpkgs, merely to
44+the package descriptions (Nix expressions, build scripts, and so on). It also
45+might not apply to patches included in Nixpkgs, which may be derivative works
46+of the packages to which they apply. The aforementioned artifacts are all
47+covered by the licenses of the respective packages.
default.nix+10−1
@@ -6,12 +6,21 @@ if ! builtins ? nixVersion || builtins.compareVersions requiredVersion builtins.
66
77 This version of Nixpkgs requires Nix >= ${requiredVersion}, please upgrade:
88
9− - If you are running NixOS, use `nixos-rebuild' to upgrade your system.
9+ - If you are running NixOS, `nixos-rebuild' can be used to upgrade your system.
10+
11+ - Alternatively, with Nix > 2.0 `nix upgrade-nix' can be used to imperatively
12+ upgrade Nix. You may use `nix-env --version' to check which version you have.
1013
1114 - If you installed Nix using the install script (https://nixos.org/nix/install),
1215 it is safe to upgrade by running it again:
1316
1417 curl https://nixos.org/nix/install | sh
18+
19+ For more information, please see the NixOS release notes at
20+ https://nixos.org/nixos/manual or locally at
21+ ${toString ./nixos/doc/manual/release-notes}.
22+
23+ If you need further help, see https://nixos.org/nixos/support.html
1524 ''
1625
1726else
doc/.gitignorenew file+7
@@ -0,0 +1,7 @@
1+*.chapter.xml
2+*.section.xml
3+.version
4+out
5+manual-full.xml
6+highlightjs
7+functions/library/locations.xml
doc/Makefilenew file+104
@@ -0,0 +1,104 @@
1+MD_TARGETS=$(addsuffix .xml, $(basename $(wildcard ./*.md ./**/*.md)))
2+
3+.PHONY: all
4+all: validate format out/html/index.html out/epub/manual.epub
5+
6+.PHONY: debug
7+debug:
8+ nix-shell --run "xmloscopy --docbook5 ./manual.xml ./manual-full.xml"
9+
10+.PHONY: format
11+format:
12+ find . -iname '*.xml' -type f -print0 | xargs -0 -I{} -n1 \
13+ xmlformat --config-file "$$XMLFORMAT_CONFIG" -i {}
14+
15+.PHONY: fix-misc-xml
16+fix-misc-xml:
17+ find . -iname '*.xml' -type f \
18+ -exec ../nixos/doc/varlistentry-fixer.rb {} ';'
19+
20+.PHONY: clean
21+clean:
22+ rm -f ${MD_TARGETS} .version manual-full.xml functions/library/locations.xml
23+ rm -rf ./out/ ./highlightjs
24+
25+.PHONY: validate
26+validate: manual-full.xml
27+ jing "$$RNG" manual-full.xml
28+
29+out/html/index.html: manual-full.xml style.css highlightjs
30+ mkdir -p out/html
31+ xsltproc ${xsltFlags} \
32+ --nonet --xinclude \
33+ --output $@ \
34+ "$$XSL/docbook/xhtml/docbook.xsl" \
35+ ./manual-full.xml
36+
37+ mkdir -p out/html/highlightjs/
38+ cp -r highlightjs out/html/
39+
40+ cp ./overrides.css out/html/
41+ cp ./style.css out/html/style.css
42+
43+ mkdir -p out/html/images/callouts
44+ cp "$$XSL/docbook/images/callouts/"*.svg out/html/images/callouts/
45+ chmod u+w -R out/html/
46+
47+out/epub/manual.epub: manual-full.xml
48+ mkdir -p out/epub/scratch
49+ xsltproc ${xsltFlags} --nonet \
50+ --output out/epub/scratch/ \
51+ "$$XSL/docbook/epub/docbook.xsl" \
52+ ./manual-full.xml
53+
54+ cp ./overrides.css out/epub/scratch/OEBPS
55+ cp ./style.css out/epub/scratch/OEBPS
56+ mkdir -p out/epub/scratch/OEBPS/images/callouts/
57+ cp "$$XSL/docbook/images/callouts/"*.svg out/epub/scratch/OEBPS/images/callouts/
58+ echo "application/epub+zip" > mimetype
59+ zip -0Xq "out/epub/manual.epub" mimetype
60+ rm mimetype
61+ cd "out/epub/scratch/" && zip -Xr9D "../manual.epub" *
62+ rm -rf "out/epub/scratch/"
63+
64+highlightjs:
65+ mkdir -p highlightjs
66+ cp -r "$$HIGHLIGHTJS/highlight.pack.js" highlightjs/
67+ cp -r "$$HIGHLIGHTJS/LICENSE" highlightjs/
68+ cp -r "$$HIGHLIGHTJS/mono-blue.css" highlightjs/
69+ cp -r "$$HIGHLIGHTJS/loader.js" highlightjs/
70+
71+
72+manual-full.xml: ${MD_TARGETS} .version functions/library/locations.xml *.xml **/*.xml **/**/*.xml
73+ xmllint --nonet --xinclude --noxincludenode manual.xml --output manual-full.xml
74+
75+.version:
76+ nix-instantiate --eval \
77+ -E '(import ../lib).version' > .version
78+
79+functions/library/locations.xml:
80+ nix-build ./lib-function-locations.nix \
81+ --out-link ./functions/library/locations.xml
82+
83+%.section.xml: %.section.md
84+ pandoc $^ -w docbook+smart \
85+ -f markdown+smart \
86+ | sed -e 's|<ulink url=|<link xlink:href=|' \
87+ -e 's|</ulink>|</link>|' \
88+ -e 's|<sect. id=|<section xml:id=|' \
89+ -e 's|</sect[0-9]>|</section>|' \
90+ -e '1s| id=| xml:id=|' \
91+ -e '1s|\(<[^ ]* \)|\1xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" |' \
92+ | cat > $@
93+
94+%.chapter.xml: %.chapter.md
95+ pandoc $^ -w docbook+smart \
96+ --top-level-division=chapter \
97+ -f markdown+smart \
98+ | sed -e 's|<ulink url=|<link xlink:href=|' \
99+ -e 's|</ulink>|</link>|' \
100+ -e 's|<sect. id=|<section xml:id=|' \
101+ -e 's|</sect[0-9]>|</section>|' \
102+ -e '1s| id=| xml:id=|' \
103+ -e '1s|\(<[^ ]* \)|\1|' \
104+ | cat > $@
doc/coding-conventions.xml+759−538
@@ -1,56 +1,59 @@
11<chapter xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="chap-conventions">
4−
5−<title>Coding conventions</title>
6−
7−
8−<section xml:id="sec-syntax"><title>Syntax</title>
9−
10−<itemizedlist>
11−
12− <listitem><para>Use 2 spaces of indentation per indentation level in
13− Nix expressions, 4 spaces in shell scripts.</para></listitem>
14−
15− <listitem><para>Do not use tab characters, i.e. configure your
16− editor to use soft tabs. For instance, use <literal>(setq-default
17− indent-tabs-mode nil)</literal> in Emacs. Everybody has different
18− tab settings so it’s asking for trouble.</para></listitem>
19−
20− <listitem><para>Use <literal>lowerCamelCase</literal> for variable
21− names, not <literal>UpperCamelCase</literal>. Note, this rule does
22− not apply to package attribute names, which instead follow the rules
23− in <xref linkend="sec-package-naming"/>.</para></listitem>
24−
25− <listitem><para>Function calls with attribute set arguments are
26− written as
27−
4+ <title>Coding conventions</title>
5+ <section xml:id="sec-syntax">
6+ <title>Syntax</title>
7+
8+ <itemizedlist>
9+ <listitem>
10+ <para>
11+ Use 2 spaces of indentation per indentation level in Nix expressions, 4
12+ spaces in shell scripts.
13+ </para>
14+ </listitem>
15+ <listitem>
16+ <para>
17+ Do not use tab characters, i.e. configure your editor to use soft tabs.
18+ For instance, use <literal>(setq-default indent-tabs-mode nil)</literal>
19+ in Emacs. Everybody has different tab settings so it’s asking for
20+ trouble.
21+ </para>
22+ </listitem>
23+ <listitem>
24+ <para>
25+ Use <literal>lowerCamelCase</literal> for variable names, not
26+ <literal>UpperCamelCase</literal>. Note, this rule does not apply to
27+ package attribute names, which instead follow the rules in
28+ <xref linkend="sec-package-naming"/>.
29+ </para>
30+ </listitem>
31+ <listitem>
32+ <para>
33+ Function calls with attribute set arguments are written as
2834<programlisting>
2935foo {
3036 arg = ...;
3137}
3238</programlisting>
33−
34− not
35−
39+ not
3640<programlisting>
3741foo
3842{
3943 arg = ...;
4044}
4145</programlisting>
42−
43− Also fine is
44−
46+ Also fine is
4547<programlisting>
4648foo { arg = ...; }
4749</programlisting>
48−
49− if it's a short call.</para></listitem>
50−
51− <listitem><para>In attribute sets or lists that span multiple lines,
52− the attribute names or list elements should be aligned:
53−
50+ if it's a short call.
51+ </para>
52+ </listitem>
53+ <listitem>
54+ <para>
55+ In attribute sets or lists that span multiple lines, the attribute names
56+ or list elements should be aligned:
5457<programlisting>
5558# A long list.
5659list =
@@ -73,12 +76,11 @@ attrs = {
7376 if true then big_expr else big_expr;
7477};
7578</programlisting>
76−
77− </para></listitem>
78−
79− <listitem><para>Short lists or attribute sets can be written on one
80− line:
81−
79+ </para>
80+ </listitem>
81+ <listitem>
82+ <para>
83+ Short lists or attribute sets can be written on one line:
8284<programlisting>
8385# A short list.
8486list = [ elem1 elem2 elem3 ];
@@ -86,66 +88,58 @@ list = [ elem1 elem2 elem3 ];
8688# A short set.
8789attrs = { x = 1280; y = 1024; };
8890</programlisting>
89−
90− </para></listitem>
91−
92− <listitem><para>Breaking in the middle of a function argument can
93− give hard-to-read code, like
94−
91+ </para>
92+ </listitem>
93+ <listitem>
94+ <para>
95+ Breaking in the middle of a function argument can give hard-to-read code,
96+ like
9597<programlisting>
9698someFunction { x = 1280;
9799 y = 1024; } otherArg
98100 yetAnotherArg
99101</programlisting>
100−
101− (especially if the argument is very large, spanning multiple
102− lines).</para>
103−
104− <para>Better:
105−
102+ (especially if the argument is very large, spanning multiple lines).
103+ </para>
104+ <para>
105+ Better:
106106<programlisting>
107107someFunction
108108 { x = 1280; y = 1024; }
109109 otherArg
110110 yetAnotherArg
111111</programlisting>
112−
113− or
114−
112+ or
115113<programlisting>
116114let res = { x = 1280; y = 1024; };
117115in someFunction res otherArg yetAnotherArg
118116</programlisting>
119−
120− </para></listitem>
121−
122− <listitem><para>The bodies of functions, asserts, and withs are not
123− indented to prevent a lot of superfluous indentation levels, i.e.
124−
117+ </para>
118+ </listitem>
119+ <listitem>
120+ <para>
121+ The bodies of functions, asserts, and withs are not indented to prevent a
122+ lot of superfluous indentation levels, i.e.
125123<programlisting>
126124{ arg1, arg2 }:
127125assert system == "i686-linux";
128126stdenv.mkDerivation { ...
129127</programlisting>
130−
131− not
132−
128+ not
133129<programlisting>
134130{ arg1, arg2 }:
135131 assert system == "i686-linux";
136132 stdenv.mkDerivation { ...
137133</programlisting>
138−
139− </para></listitem>
140−
141− <listitem><para>Function formal arguments are written as:
142−
134+ </para>
135+ </listitem>
136+ <listitem>
137+ <para>
138+ Function formal arguments are written as:
143139<programlisting>
144140{ arg1, arg2, arg3 }:
145141</programlisting>
146−
147− but if they don't fit on one line they're written as:
148−
142+ but if they don't fit on one line they're written as:
149143<programlisting>
150144{ arg1, arg2, arg3
151145, arg4, ...
@@ -153,35 +147,28 @@ stdenv.mkDerivation { ...
153147 argN
154148}:
155149</programlisting>
156−
157− </para></listitem>
158−
159− <listitem><para>Functions should list their expected arguments as
160− precisely as possible. That is, write
161−
150+ </para>
151+ </listitem>
152+ <listitem>
153+ <para>
154+ Functions should list their expected arguments as precisely as possible.
155+ That is, write
162156<programlisting>
163157{ stdenv, fetchurl, perl }: <replaceable>...</replaceable>
164158</programlisting>
165−
166− instead of
167−
159+ instead of
168160<programlisting>
169161args: with args; <replaceable>...</replaceable>
170162</programlisting>
171−
172− or
173−
163+ or
174164<programlisting>
175165{ stdenv, fetchurl, perl, ... }: <replaceable>...</replaceable>
176166</programlisting>
177−
178− </para>
179−
180− <para>For functions that are truly generic in the number of
181− arguments (such as wrappers around <varname>mkDerivation</varname>)
182− that have some required arguments, you should write them using an
183− <literal>@</literal>-pattern:
184−
167+ </para>
168+ <para>
169+ For functions that are truly generic in the number of arguments (such as
170+ wrappers around <varname>mkDerivation</varname>) that have some required
171+ arguments, you should write them using an <literal>@</literal>-pattern:
185172<programlisting>
186173{ stdenv, doCoverageAnalysis ? false, ... } @ args:
187174
@@ -189,9 +176,7 @@ stdenv.mkDerivation (args // {
189176 <replaceable>...</replaceable> if doCoverageAnalysis then "bla" else "" <replaceable>...</replaceable>
190177})
191178</programlisting>
192−
193− instead of
194−
179+ instead of
195180<programlisting>
196181args:
197182
@@ -199,432 +184,635 @@ args.stdenv.mkDerivation (args // {
199184 <replaceable>...</replaceable> if args ? doCoverageAnalysis &amp;&amp; args.doCoverageAnalysis then "bla" else "" <replaceable>...</replaceable>
200185})
201186</programlisting>
187+ </para>
188+ </listitem>
189+ </itemizedlist>
190+ </section>
191+ <section xml:id="sec-package-naming">
192+ <title>Package naming</title>
202193
203− </para></listitem>
204−
205−</itemizedlist>
206−
207−</section>
208−
209−
210−<section xml:id="sec-package-naming"><title>Package naming</title>
211−
212−<para>In Nixpkgs, there are generally three different names associated with a package:
213−
214−<itemizedlist>
215−
216− <listitem><para>The <varname>name</varname> attribute of the
217− derivation (excluding the version part). This is what most users
218− see, in particular when using
219− <command>nix-env</command>.</para></listitem>
220−
221− <listitem><para>The variable name used for the instantiated package
222− in <filename>all-packages.nix</filename>, and when passing it as a
223− dependency to other functions. Typically this is called the
224− <emphasis>package attribute name</emphasis>. This is what Nix
225− expression authors see. It can also be used when installing using
226− <command>nix-env -iA</command>.</para></listitem>
227−
228− <listitem><para>The filename for (the directory containing) the Nix
229− expression.</para></listitem>
230−
231−</itemizedlist>
232−
233−Most of the time, these are the same. For instance, the package
234−<literal>e2fsprogs</literal> has a <varname>name</varname> attribute
235−<literal>"e2fsprogs-<replaceable>version</replaceable>"</literal>, is
236−bound to the variable name <varname>e2fsprogs</varname> in
237−<filename>all-packages.nix</filename>, and the Nix expression is in
238−<filename>pkgs/os-specific/linux/e2fsprogs/default.nix</filename>.
239−</para>
240−
241−<para>There are a few naming guidelines:
242−
243−<itemizedlist>
244−
245− <listitem><para>Generally, try to stick to the upstream package
246− name.</para></listitem>
247−
248− <listitem><para>Don’t use uppercase letters in the
249− <literal>name</literal> attribute — e.g.,
250− <literal>"mplayer-1.0rc2"</literal> instead of
251− <literal>"MPlayer-1.0rc2"</literal>.</para></listitem>
252−
253− <listitem><para>The version part of the <literal>name</literal>
254− attribute <emphasis>must</emphasis> start with a digit (following a
255− dash) — e.g., <literal>"hello-0.3.1rc2"</literal>.</para></listitem>
256−
257− <listitem><para>If a package is not a release but a commit from a repository, then
258− the version part of the name <emphasis>must</emphasis> be the date of that
259− (fetched) commit. The date must be in <literal>"YYYY-MM-DD"</literal> format.
260− Also append <literal>"unstable"</literal> to the name - e.g.,
261− <literal>"pkgname-unstable-2014-09-23"</literal>.</para></listitem>
262−
263− <listitem><para>Dashes in the package name should be preserved in
264− new variable names, rather than converted to underscores or camel
265− cased — e.g., <varname>http-parser</varname> instead of
266− <varname>http_parser</varname> or <varname>httpParser</varname>. The
267− hyphenated style is preferred in all three package
268− names.</para></listitem>
269−
270− <listitem><para>If there are multiple versions of a package, this
271− should be reflected in the variable names in
272− <filename>all-packages.nix</filename>,
273− e.g. <varname>json-c-0-9</varname> and <varname>json-c-0-11</varname>.
274− If there is an obvious “default” version, make an attribute like
275− <literal>json-c = json-c-0-9;</literal>.
276− See also <xref linkend="sec-versioning" /></para></listitem>
277−
278−</itemizedlist>
279−
280−</para>
281−
282−</section>
283−
284−
285−<section xml:id="sec-organisation"><title>File naming and organisation</title>
286−
287−<para>Names of files and directories should be in lowercase, with
288−dashes between words — not in camel case. For instance, it should be
289−<filename>all-packages.nix</filename>, not
290−<filename>allPackages.nix</filename> or
291−<filename>AllPackages.nix</filename>.</para>
292−
293−<section xml:id="sec-hierarchy"><title>Hierarchy</title>
294−
295−<para>Each package should be stored in its own directory somewhere in
296−the <filename>pkgs/</filename> tree, i.e. in
297−<filename>pkgs/<replaceable>category</replaceable>/<replaceable>subcategory</replaceable>/<replaceable>...</replaceable>/<replaceable>pkgname</replaceable></filename>.
298−Below are some rules for picking the right category for a package.
299−Many packages fall under several categories; what matters is the
300−<emphasis>primary</emphasis> purpose of a package. For example, the
301−<literal>libxml2</literal> package builds both a library and some
302−tools; but it’s a library foremost, so it goes under
303−<filename>pkgs/development/libraries</filename>.</para>
304−
305−<para>When in doubt, consider refactoring the
306−<filename>pkgs/</filename> tree, e.g. creating new categories or
307−splitting up an existing category.</para>
308−
309−<variablelist>
310− <varlistentry>
311− <term>If it’s used to support <emphasis>software development</emphasis>:</term>
194+ <para>
195+ In Nixpkgs, there are generally three different names associated with a
196+ package:
197+ <itemizedlist>
312198 <listitem>
313− <variablelist>
314− <varlistentry>
315− <term>If it’s a <emphasis>library</emphasis> used by other packages:</term>
316− <listitem>
317− <para><filename>development/libraries</filename> (e.g. <filename>libxml2</filename>)</para>
318− </listitem>
319− </varlistentry>
320− <varlistentry>
321− <term>If it’s a <emphasis>compiler</emphasis>:</term>
322− <listitem>
323− <para><filename>development/compilers</filename> (e.g. <filename>gcc</filename>)</para>
324− </listitem>
325− </varlistentry>
326− <varlistentry>
327− <term>If it’s an <emphasis>interpreter</emphasis>:</term>
328− <listitem>
329− <para><filename>development/interpreters</filename> (e.g. <filename>guile</filename>)</para>
330− </listitem>
331− </varlistentry>
332− <varlistentry>
333− <term>If it’s a (set of) development <emphasis>tool(s)</emphasis>:</term>
334− <listitem>
335− <variablelist>
336− <varlistentry>
337− <term>If it’s a <emphasis>parser generator</emphasis> (including lexers):</term>
338− <listitem>
339− <para><filename>development/tools/parsing</filename> (e.g. <filename>bison</filename>, <filename>flex</filename>)</para>
340− </listitem>
341− </varlistentry>
342− <varlistentry>
343− <term>If it’s a <emphasis>build manager</emphasis>:</term>
344− <listitem>
345− <para><filename>development/tools/build-managers</filename> (e.g. <filename>gnumake</filename>)</para>
346− </listitem>
347− </varlistentry>
348− <varlistentry>
349− <term>Else:</term>
350− <listitem>
351− <para><filename>development/tools/misc</filename> (e.g. <filename>binutils</filename>)</para>
352− </listitem>
353− </varlistentry>
354− </variablelist>
355− </listitem>
356− </varlistentry>
357− <varlistentry>
358− <term>Else:</term>
359− <listitem>
360− <para><filename>development/misc</filename></para>
361− </listitem>
362− </varlistentry>
363− </variablelist>
199+ <para>
200+ The <varname>name</varname> attribute of the derivation (excluding the
201+ version part). This is what most users see, in particular when using
202+ <command>nix-env</command>.
203+ </para>
364204 </listitem>
365− </varlistentry>
366− <varlistentry>
367− <term>If it’s a (set of) <emphasis>tool(s)</emphasis>:</term>
368205 <listitem>
369− <para>(A tool is a relatively small program, especially one intended
370− to be used non-interactively.)</para>
371− <variablelist>
372− <varlistentry>
373− <term>If it’s for <emphasis>networking</emphasis>:</term>
374− <listitem>
375− <para><filename>tools/networking</filename> (e.g. <filename>wget</filename>)</para>
376− </listitem>
377− </varlistentry>
378− <varlistentry>
379− <term>If it’s for <emphasis>text processing</emphasis>:</term>
380− <listitem>
381− <para><filename>tools/text</filename> (e.g. <filename>diffutils</filename>)</para>
382− </listitem>
383− </varlistentry>
384− <varlistentry>
385− <term>If it’s a <emphasis>system utility</emphasis>, i.e.,
386− something related or essential to the operation of a
387− system:</term>
388− <listitem>
389− <para><filename>tools/system</filename> (e.g. <filename>cron</filename>)</para>
390− </listitem>
391− </varlistentry>
392− <varlistentry>
393− <term>If it’s an <emphasis>archiver</emphasis> (which may
394− include a compression function):</term>
395− <listitem>
396− <para><filename>tools/archivers</filename> (e.g. <filename>zip</filename>, <filename>tar</filename>)</para>
397− </listitem>
398− </varlistentry>
399− <varlistentry>
400− <term>If it’s a <emphasis>compression</emphasis> program:</term>
401− <listitem>
402− <para><filename>tools/compression</filename> (e.g. <filename>gzip</filename>, <filename>bzip2</filename>)</para>
403− </listitem>
404− </varlistentry>
405− <varlistentry>
406− <term>If it’s a <emphasis>security</emphasis>-related program:</term>
407− <listitem>
408− <para><filename>tools/security</filename> (e.g. <filename>nmap</filename>, <filename>gnupg</filename>)</para>
409− </listitem>
410− </varlistentry>
411− <varlistentry>
412− <term>Else:</term>
413− <listitem>
414− <para><filename>tools/misc</filename></para>
415− </listitem>
416− </varlistentry>
417− </variablelist>
206+ <para>
207+ The variable name used for the instantiated package in
208+ <filename>all-packages.nix</filename>, and when passing it as a
209+ dependency to other functions. Typically this is called the
210+ <emphasis>package attribute name</emphasis>. This is what Nix expression
211+ authors see. It can also be used when installing using <command>nix-env
212+ -iA</command>.
213+ </para>
418214 </listitem>
419− </varlistentry>
420− <varlistentry>
421− <term>If it’s a <emphasis>shell</emphasis>:</term>
422215 <listitem>
423− <para><filename>shells</filename> (e.g. <filename>bash</filename>)</para>
216+ <para>
217+ The filename for (the directory containing) the Nix expression.
218+ </para>
424219 </listitem>
425− </varlistentry>
426− <varlistentry>
427− <term>If it’s a <emphasis>server</emphasis>:</term>
220+ </itemizedlist>
221+ Most of the time, these are the same. For instance, the package
222+ <literal>e2fsprogs</literal> has a <varname>name</varname> attribute
223+ <literal>"e2fsprogs-<replaceable>version</replaceable>"</literal>, is bound
224+ to the variable name <varname>e2fsprogs</varname> in
225+ <filename>all-packages.nix</filename>, and the Nix expression is in
226+ <filename>pkgs/os-specific/linux/e2fsprogs/default.nix</filename>.
227+ </para>
228+
229+ <para>
230+ There are a few naming guidelines:
231+ <itemizedlist>
428232 <listitem>
429− <variablelist>
430− <varlistentry>
431− <term>If it’s a web server:</term>
432− <listitem>
433− <para><filename>servers/http</filename> (e.g. <filename>apache-httpd</filename>)</para>
434− </listitem>
435− </varlistentry>
436− <varlistentry>
437− <term>If it’s an implementation of the X Windowing System:</term>
438− <listitem>
439− <para><filename>servers/x11</filename> (e.g. <filename>xorg</filename> — this includes the client libraries and programs)</para>
440− </listitem>
441− </varlistentry>
442− <varlistentry>
443− <term>Else:</term>
444− <listitem>
445− <para><filename>servers/misc</filename></para>
446− </listitem>
447− </varlistentry>
448− </variablelist>
233+ <para>
234+ Generally, try to stick to the upstream package name.
235+ </para>
449236 </listitem>
450− </varlistentry>
451− <varlistentry>
452− <term>If it’s a <emphasis>desktop environment</emphasis>:</term>
453237 <listitem>
454− <para><filename>desktops</filename> (e.g. <filename>kde</filename>, <filename>gnome</filename>, <filename>enlightenment</filename>)</para>
238+ <para>
239+ Don’t use uppercase letters in the <literal>name</literal> attribute
240+ — e.g., <literal>"mplayer-1.0rc2"</literal> instead of
241+ <literal>"MPlayer-1.0rc2"</literal>.
242+ </para>
455243 </listitem>
456− </varlistentry>
457− <varlistentry>
458− <term>If it’s a <emphasis>window manager</emphasis>:</term>
459244 <listitem>
460− <para><filename>applications/window-managers</filename> (e.g. <filename>awesome</filename>, <filename>stumpwm</filename>)</para>
245+ <para>
246+ The version part of the <literal>name</literal> attribute
247+ <emphasis>must</emphasis> start with a digit (following a dash) — e.g.,
248+ <literal>"hello-0.3.1rc2"</literal>.
249+ </para>
461250 </listitem>
462− </varlistentry>
463− <varlistentry>
464− <term>If it’s an <emphasis>application</emphasis>:</term>
465251 <listitem>
466− <para>A (typically large) program with a distinct user
467− interface, primarily used interactively.</para>
468− <variablelist>
469− <varlistentry>
470− <term>If it’s a <emphasis>version management system</emphasis>:</term>
471− <listitem>
472− <para><filename>applications/version-management</filename> (e.g. <filename>subversion</filename>)</para>
473− </listitem>
474− </varlistentry>
475− <varlistentry>
476− <term>If it’s for <emphasis>video playback / editing</emphasis>:</term>
477− <listitem>
478− <para><filename>applications/video</filename> (e.g. <filename>vlc</filename>)</para>
479− </listitem>
480− </varlistentry>
481− <varlistentry>
482− <term>If it’s for <emphasis>graphics viewing / editing</emphasis>:</term>
483− <listitem>
484− <para><filename>applications/graphics</filename> (e.g. <filename>gimp</filename>)</para>
485− </listitem>
486− </varlistentry>
487− <varlistentry>
488− <term>If it’s for <emphasis>networking</emphasis>:</term>
489− <listitem>
490− <variablelist>
491− <varlistentry>
492− <term>If it’s a <emphasis>mailreader</emphasis>:</term>
493− <listitem>
494− <para><filename>applications/networking/mailreaders</filename> (e.g. <filename>thunderbird</filename>)</para>
495− </listitem>
496− </varlistentry>
497− <varlistentry>
498− <term>If it’s a <emphasis>newsreader</emphasis>:</term>
499− <listitem>
500− <para><filename>applications/networking/newsreaders</filename> (e.g. <filename>pan</filename>)</para>
501− </listitem>
502− </varlistentry>
503− <varlistentry>
504− <term>If it’s a <emphasis>web browser</emphasis>:</term>
505− <listitem>
506− <para><filename>applications/networking/browsers</filename> (e.g. <filename>firefox</filename>)</para>
507− </listitem>
508− </varlistentry>
509− <varlistentry>
510− <term>Else:</term>
511− <listitem>
512− <para><filename>applications/networking/misc</filename></para>
513− </listitem>
514− </varlistentry>
515− </variablelist>
516− </listitem>
517− </varlistentry>
518− <varlistentry>
519− <term>Else:</term>
520− <listitem>
521− <para><filename>applications/misc</filename></para>
522− </listitem>
523− </varlistentry>
524− </variablelist>
252+ <para>
253+ If a package is not a release but a commit from a repository, then the
254+ version part of the name <emphasis>must</emphasis> be the date of that
255+ (fetched) commit. The date must be in <literal>"YYYY-MM-DD"</literal>
256+ format. Also append <literal>"unstable"</literal> to the name - e.g.,
257+ <literal>"pkgname-unstable-2014-09-23"</literal>.
258+ </para>
525259 </listitem>
526− </varlistentry>
527− <varlistentry>
528− <term>If it’s <emphasis>data</emphasis> (i.e., does not have a
529− straight-forward executable semantics):</term>
530260 <listitem>
531− <variablelist>
532− <varlistentry>
533− <term>If it’s a <emphasis>font</emphasis>:</term>
534− <listitem>
535− <para><filename>data/fonts</filename></para>
536− </listitem>
537− </varlistentry>
538− <varlistentry>
539− <term>If it’s related to <emphasis>SGML/XML processing</emphasis>:</term>
540− <listitem>
541− <variablelist>
542− <varlistentry>
543− <term>If it’s an <emphasis>XML DTD</emphasis>:</term>
544− <listitem>
545− <para><filename>data/sgml+xml/schemas/xml-dtd</filename> (e.g. <filename>docbook</filename>)</para>
546− </listitem>
547− </varlistentry>
548− <varlistentry>
549− <term>If it’s an <emphasis>XSLT stylesheet</emphasis>:</term>
550− <listitem>
551− <para>(Okay, these are executable...)</para>
552− <para><filename>data/sgml+xml/stylesheets/xslt</filename> (e.g. <filename>docbook-xsl</filename>)</para>
553− </listitem>
554− </varlistentry>
555− </variablelist>
556− </listitem>
557− </varlistentry>
558− </variablelist>
559− </listitem>
560− </varlistentry>
561− <varlistentry>
562− <term>If it’s a <emphasis>game</emphasis>:</term>
563− <listitem>
564− <para><filename>games</filename></para>
261+ <para>
262+ Dashes in the package name should be preserved in new variable names,
263+ rather than converted to underscores or camel cased — e.g.,
264+ <varname>http-parser</varname> instead of <varname>http_parser</varname>
265+ or <varname>httpParser</varname>. The hyphenated style is preferred in
266+ all three package names.
267+ </para>
565268 </listitem>
566− </varlistentry>
567− <varlistentry>
568− <term>Else:</term>
569269 <listitem>
570− <para><filename>misc</filename></para>
270+ <para>
271+ If there are multiple versions of a package, this should be reflected in
272+ the variable names in <filename>all-packages.nix</filename>, e.g.
273+ <varname>json-c-0-9</varname> and <varname>json-c-0-11</varname>. If
274+ there is an obvious “default” version, make an attribute like
275+ <literal>json-c = json-c-0-9;</literal>. See also
276+ <xref linkend="sec-versioning" />
277+ </para>
571278 </listitem>
572− </varlistentry>
573−</variablelist>
574−
575−</section>
576−
577−<section xml:id="sec-versioning"><title>Versioning</title>
578−
579−<para>Because every version of a package in Nixpkgs creates a
580−potential maintenance burden, old versions of a package should not be
581−kept unless there is a good reason to do so. For instance, Nixpkgs
582−contains several versions of GCC because other packages don’t build
583−with the latest version of GCC. Other examples are having both the
584−latest stable and latest pre-release version of a package, or to keep
585−several major releases of an application that differ significantly in
586−functionality.</para>
587−
588−<para>If there is only one version of a package, its Nix expression
589−should be named <filename>e2fsprogs/default.nix</filename>. If there
590−are multiple versions, this should be reflected in the filename,
591−e.g. <filename>e2fsprogs/1.41.8.nix</filename> and
592−<filename>e2fsprogs/1.41.9.nix</filename>. The version in the
593−filename should leave out unnecessary detail. For instance, if we
594−keep the latest Firefox 2.0.x and 3.5.x versions in Nixpkgs, they
595−should be named <filename>firefox/2.0.nix</filename> and
596−<filename>firefox/3.5.nix</filename>, respectively (which, at a given
597−point, might contain versions <literal>2.0.0.20</literal> and
598−<literal>3.5.4</literal>). If a version requires many auxiliary
599−files, you can use a subdirectory for each version,
600−e.g. <filename>firefox/2.0/default.nix</filename> and
601−<filename>firefox/3.5/default.nix</filename>.</para>
279+ </itemizedlist>
280+ </para>
281+ </section>
282+ <section xml:id="sec-organisation">
283+ <title>File naming and organisation</title>
602284
603−<para>All versions of a package <emphasis>must</emphasis> be included
604−in <filename>all-packages.nix</filename> to make sure that they
605−evaluate correctly.</para>
285+ <para>
286+ Names of files and directories should be in lowercase, with dashes between
287+ words — not in camel case. For instance, it should be
288+ <filename>all-packages.nix</filename>, not
289+ <filename>allPackages.nix</filename> or
290+ <filename>AllPackages.nix</filename>.
291+ </para>
606292
607−</section>
293+ <section xml:id="sec-hierarchy">
294+ <title>Hierarchy</title>
295+
296+ <para>
297+ Each package should be stored in its own directory somewhere in the
298+ <filename>pkgs/</filename> tree, i.e. in
299+ <filename>pkgs/<replaceable>category</replaceable>/<replaceable>subcategory</replaceable>/<replaceable>...</replaceable>/<replaceable>pkgname</replaceable></filename>.
300+ Below are some rules for picking the right category for a package. Many
301+ packages fall under several categories; what matters is the
302+ <emphasis>primary</emphasis> purpose of a package. For example, the
303+ <literal>libxml2</literal> package builds both a library and some tools;
304+ but it’s a library foremost, so it goes under
305+ <filename>pkgs/development/libraries</filename>.
306+ </para>
307+
308+ <para>
309+ When in doubt, consider refactoring the <filename>pkgs/</filename> tree,
310+ e.g. creating new categories or splitting up an existing category.
311+ </para>
312+
313+ <variablelist>
314+ <varlistentry>
315+ <term>
316+ If it’s used to support <emphasis>software development</emphasis>:
317+ </term>
318+ <listitem>
319+ <variablelist>
320+ <varlistentry>
321+ <term>
322+ If it’s a <emphasis>library</emphasis> used by other packages:
323+ </term>
324+ <listitem>
325+ <para>
326+ <filename>development/libraries</filename> (e.g.
327+ <filename>libxml2</filename>)
328+ </para>
329+ </listitem>
330+ </varlistentry>
331+ <varlistentry>
332+ <term>
333+ If it’s a <emphasis>compiler</emphasis>:
334+ </term>
335+ <listitem>
336+ <para>
337+ <filename>development/compilers</filename> (e.g.
338+ <filename>gcc</filename>)
339+ </para>
340+ </listitem>
341+ </varlistentry>
342+ <varlistentry>
343+ <term>
344+ If it’s an <emphasis>interpreter</emphasis>:
345+ </term>
346+ <listitem>
347+ <para>
348+ <filename>development/interpreters</filename> (e.g.
349+ <filename>guile</filename>)
350+ </para>
351+ </listitem>
352+ </varlistentry>
353+ <varlistentry>
354+ <term>
355+ If it’s a (set of) development <emphasis>tool(s)</emphasis>:
356+ </term>
357+ <listitem>
358+ <variablelist>
359+ <varlistentry>
360+ <term>
361+ If it’s a <emphasis>parser generator</emphasis> (including lexers):
362+ </term>
363+ <listitem>
364+ <para>
365+ <filename>development/tools/parsing</filename> (e.g.
366+ <filename>bison</filename>, <filename>flex</filename>)
367+ </para>
368+ </listitem>
369+ </varlistentry>
370+ <varlistentry>
371+ <term>
372+ If it’s a <emphasis>build manager</emphasis>:
373+ </term>
374+ <listitem>
375+ <para>
376+ <filename>development/tools/build-managers</filename> (e.g.
377+ <filename>gnumake</filename>)
378+ </para>
379+ </listitem>
380+ </varlistentry>
381+ <varlistentry>
382+ <term>
383+ Else:
384+ </term>
385+ <listitem>
386+ <para>
387+ <filename>development/tools/misc</filename> (e.g.
388+ <filename>binutils</filename>)
389+ </para>
390+ </listitem>
391+ </varlistentry>
392+ </variablelist>
393+ </listitem>
394+ </varlistentry>
395+ <varlistentry>
396+ <term>
397+ Else:
398+ </term>
399+ <listitem>
400+ <para>
401+ <filename>development/misc</filename>
402+ </para>
403+ </listitem>
404+ </varlistentry>
405+ </variablelist>
406+ </listitem>
407+ </varlistentry>
408+ <varlistentry>
409+ <term>
410+ If it’s a (set of) <emphasis>tool(s)</emphasis>:
411+ </term>
412+ <listitem>
413+ <para>
414+ (A tool is a relatively small program, especially one intended to be
415+ used non-interactively.)
416+ </para>
417+ <variablelist>
418+ <varlistentry>
419+ <term>
420+ If it’s for <emphasis>networking</emphasis>:
421+ </term>
422+ <listitem>
423+ <para>
424+ <filename>tools/networking</filename> (e.g.
425+ <filename>wget</filename>)
426+ </para>
427+ </listitem>
428+ </varlistentry>
429+ <varlistentry>
430+ <term>
431+ If it’s for <emphasis>text processing</emphasis>:
432+ </term>
433+ <listitem>
434+ <para>
435+ <filename>tools/text</filename> (e.g. <filename>diffutils</filename>)
436+ </para>
437+ </listitem>
438+ </varlistentry>
439+ <varlistentry>
440+ <term>
441+ If it’s a <emphasis>system utility</emphasis>, i.e., something related or essential to the operation of a system:
442+ </term>
443+ <listitem>
444+ <para>
445+ <filename>tools/system</filename> (e.g. <filename>cron</filename>)
446+ </para>
447+ </listitem>
448+ </varlistentry>
449+ <varlistentry>
450+ <term>
451+ If it’s an <emphasis>archiver</emphasis> (which may include a compression function):
452+ </term>
453+ <listitem>
454+ <para>
455+ <filename>tools/archivers</filename> (e.g. <filename>zip</filename>,
456+ <filename>tar</filename>)
457+ </para>
458+ </listitem>
459+ </varlistentry>
460+ <varlistentry>
461+ <term>
462+ If it’s a <emphasis>compression</emphasis> program:
463+ </term>
464+ <listitem>
465+ <para>
466+ <filename>tools/compression</filename> (e.g.
467+ <filename>gzip</filename>, <filename>bzip2</filename>)
468+ </para>
469+ </listitem>
470+ </varlistentry>
471+ <varlistentry>
472+ <term>
473+ If it’s a <emphasis>security</emphasis>-related program:
474+ </term>
475+ <listitem>
476+ <para>
477+ <filename>tools/security</filename> (e.g. <filename>nmap</filename>,
478+ <filename>gnupg</filename>)
479+ </para>
480+ </listitem>
481+ </varlistentry>
482+ <varlistentry>
483+ <term>
484+ Else:
485+ </term>
486+ <listitem>
487+ <para>
488+ <filename>tools/misc</filename>
489+ </para>
490+ </listitem>
491+ </varlistentry>
492+ </variablelist>
493+ </listitem>
494+ </varlistentry>
495+ <varlistentry>
496+ <term>
497+ If it’s a <emphasis>shell</emphasis>:
498+ </term>
499+ <listitem>
500+ <para>
501+ <filename>shells</filename> (e.g. <filename>bash</filename>)
502+ </para>
503+ </listitem>
504+ </varlistentry>
505+ <varlistentry>
506+ <term>
507+ If it’s a <emphasis>server</emphasis>:
508+ </term>
509+ <listitem>
510+ <variablelist>
511+ <varlistentry>
512+ <term>
513+ If it’s a web server:
514+ </term>
515+ <listitem>
516+ <para>
517+ <filename>servers/http</filename> (e.g.
518+ <filename>apache-httpd</filename>)
519+ </para>
520+ </listitem>
521+ </varlistentry>
522+ <varlistentry>
523+ <term>
524+ If it’s an implementation of the X Windowing System:
525+ </term>
526+ <listitem>
527+ <para>
528+ <filename>servers/x11</filename> (e.g. <filename>xorg</filename> —
529+ this includes the client libraries and programs)
530+ </para>
531+ </listitem>
532+ </varlistentry>
533+ <varlistentry>
534+ <term>
535+ Else:
536+ </term>
537+ <listitem>
538+ <para>
539+ <filename>servers/misc</filename>
540+ </para>
541+ </listitem>
542+ </varlistentry>
543+ </variablelist>
544+ </listitem>
545+ </varlistentry>
546+ <varlistentry>
547+ <term>
548+ If it’s a <emphasis>desktop environment</emphasis>:
549+ </term>
550+ <listitem>
551+ <para>
552+ <filename>desktops</filename> (e.g. <filename>kde</filename>,
553+ <filename>gnome</filename>, <filename>enlightenment</filename>)
554+ </para>
555+ </listitem>
556+ </varlistentry>
557+ <varlistentry>
558+ <term>
559+ If it’s a <emphasis>window manager</emphasis>:
560+ </term>
561+ <listitem>
562+ <para>
563+ <filename>applications/window-managers</filename> (e.g.
564+ <filename>awesome</filename>, <filename>stumpwm</filename>)
565+ </para>
566+ </listitem>
567+ </varlistentry>
568+ <varlistentry>
569+ <term>
570+ If it’s an <emphasis>application</emphasis>:
571+ </term>
572+ <listitem>
573+ <para>
574+ A (typically large) program with a distinct user interface, primarily
575+ used interactively.
576+ </para>
577+ <variablelist>
578+ <varlistentry>
579+ <term>
580+ If it’s a <emphasis>version management system</emphasis>:
581+ </term>
582+ <listitem>
583+ <para>
584+ <filename>applications/version-management</filename> (e.g.
585+ <filename>subversion</filename>)
586+ </para>
587+ </listitem>
588+ </varlistentry>
589+ <varlistentry>
590+ <term>
591+ If it’s for <emphasis>video playback / editing</emphasis>:
592+ </term>
593+ <listitem>
594+ <para>
595+ <filename>applications/video</filename> (e.g.
596+ <filename>vlc</filename>)
597+ </para>
598+ </listitem>
599+ </varlistentry>
600+ <varlistentry>
601+ <term>
602+ If it’s for <emphasis>graphics viewing / editing</emphasis>:
603+ </term>
604+ <listitem>
605+ <para>
606+ <filename>applications/graphics</filename> (e.g.
607+ <filename>gimp</filename>)
608+ </para>
609+ </listitem>
610+ </varlistentry>
611+ <varlistentry>
612+ <term>
613+ If it’s for <emphasis>networking</emphasis>:
614+ </term>
615+ <listitem>
616+ <variablelist>
617+ <varlistentry>
618+ <term>
619+ If it’s a <emphasis>mailreader</emphasis>:
620+ </term>
621+ <listitem>
622+ <para>
623+ <filename>applications/networking/mailreaders</filename> (e.g.
624+ <filename>thunderbird</filename>)
625+ </para>
626+ </listitem>
627+ </varlistentry>
628+ <varlistentry>
629+ <term>
630+ If it’s a <emphasis>newsreader</emphasis>:
631+ </term>
632+ <listitem>
633+ <para>
634+ <filename>applications/networking/newsreaders</filename> (e.g.
635+ <filename>pan</filename>)
636+ </para>
637+ </listitem>
638+ </varlistentry>
639+ <varlistentry>
640+ <term>
641+ If it’s a <emphasis>web browser</emphasis>:
642+ </term>
643+ <listitem>
644+ <para>
645+ <filename>applications/networking/browsers</filename> (e.g.
646+ <filename>firefox</filename>)
647+ </para>
648+ </listitem>
649+ </varlistentry>
650+ <varlistentry>
651+ <term>
652+ Else:
653+ </term>
654+ <listitem>
655+ <para>
656+ <filename>applications/networking/misc</filename>
657+ </para>
658+ </listitem>
659+ </varlistentry>
660+ </variablelist>
661+ </listitem>
662+ </varlistentry>
663+ <varlistentry>
664+ <term>
665+ Else:
666+ </term>
667+ <listitem>
668+ <para>
669+ <filename>applications/misc</filename>
670+ </para>
671+ </listitem>
672+ </varlistentry>
673+ </variablelist>
674+ </listitem>
675+ </varlistentry>
676+ <varlistentry>
677+ <term>
678+ If it’s <emphasis>data</emphasis> (i.e., does not have a straight-forward executable semantics):
679+ </term>
680+ <listitem>
681+ <variablelist>
682+ <varlistentry>
683+ <term>
684+ If it’s a <emphasis>font</emphasis>:
685+ </term>
686+ <listitem>
687+ <para>
688+ <filename>data/fonts</filename>
689+ </para>
690+ </listitem>
691+ </varlistentry>
692+ <varlistentry>
693+ <term>
694+ If it’s related to <emphasis>SGML/XML processing</emphasis>:
695+ </term>
696+ <listitem>
697+ <variablelist>
698+ <varlistentry>
699+ <term>
700+ If it’s an <emphasis>XML DTD</emphasis>:
701+ </term>
702+ <listitem>
703+ <para>
704+ <filename>data/sgml+xml/schemas/xml-dtd</filename> (e.g.
705+ <filename>docbook</filename>)
706+ </para>
707+ </listitem>
708+ </varlistentry>
709+ <varlistentry>
710+ <term>
711+ If it’s an <emphasis>XSLT stylesheet</emphasis>:
712+ </term>
713+ <listitem>
714+ <para>
715+ (Okay, these are executable...)
716+ </para>
717+ <para>
718+ <filename>data/sgml+xml/stylesheets/xslt</filename> (e.g.
719+ <filename>docbook-xsl</filename>)
720+ </para>
721+ </listitem>
722+ </varlistentry>
723+ </variablelist>
724+ </listitem>
725+ </varlistentry>
726+ </variablelist>
727+ </listitem>
728+ </varlistentry>
729+ <varlistentry>
730+ <term>
731+ If it’s a <emphasis>game</emphasis>:
732+ </term>
733+ <listitem>
734+ <para>
735+ <filename>games</filename>
736+ </para>
737+ </listitem>
738+ </varlistentry>
739+ <varlistentry>
740+ <term>
741+ Else:
742+ </term>
743+ <listitem>
744+ <para>
745+ <filename>misc</filename>
746+ </para>
747+ </listitem>
748+ </varlistentry>
749+ </variablelist>
750+ </section>
751+
752+ <section xml:id="sec-versioning">
753+ <title>Versioning</title>
754+
755+ <para>
756+ Because every version of a package in Nixpkgs creates a potential
757+ maintenance burden, old versions of a package should not be kept unless
758+ there is a good reason to do so. For instance, Nixpkgs contains several
759+ versions of GCC because other packages don’t build with the latest
760+ version of GCC. Other examples are having both the latest stable and latest
761+ pre-release version of a package, or to keep several major releases of an
762+ application that differ significantly in functionality.
763+ </para>
764+
765+ <para>
766+ If there is only one version of a package, its Nix expression should be
767+ named <filename>e2fsprogs/default.nix</filename>. If there are multiple
768+ versions, this should be reflected in the filename, e.g.
769+ <filename>e2fsprogs/1.41.8.nix</filename> and
770+ <filename>e2fsprogs/1.41.9.nix</filename>. The version in the filename
771+ should leave out unnecessary detail. For instance, if we keep the latest
772+ Firefox 2.0.x and 3.5.x versions in Nixpkgs, they should be named
773+ <filename>firefox/2.0.nix</filename> and
774+ <filename>firefox/3.5.nix</filename>, respectively (which, at a given
775+ point, might contain versions <literal>2.0.0.20</literal> and
776+ <literal>3.5.4</literal>). If a version requires many auxiliary files, you
777+ can use a subdirectory for each version, e.g.
778+ <filename>firefox/2.0/default.nix</filename> and
779+ <filename>firefox/3.5/default.nix</filename>.
780+ </para>
781+
782+ <para>
783+ All versions of a package <emphasis>must</emphasis> be included in
784+ <filename>all-packages.nix</filename> to make sure that they evaluate
785+ correctly.
786+ </para>
787+ </section>
788+ </section>
789+ <section xml:id="sec-sources">
790+ <title>Fetching Sources</title>
608791
609−</section>
610−<section xml:id="sec-sources"><title>Fetching Sources</title>
611− <para>There are multiple ways to fetch a package source in nixpkgs. The
612− general guideline is that you should package sources with a high degree of
613− availability. Right now there is only one fetcher which has mirroring
614− support and that is <literal>fetchurl</literal>. Note that you should also
615− prefer protocols which have a corresponding proxy environment variable.
792+ <para>
793+ There are multiple ways to fetch a package source in nixpkgs. The general
794+ guideline is that you should package sources with a high degree of
795+ availability. Right now there is only one fetcher which has mirroring
796+ support and that is <literal>fetchurl</literal>. Note that you should also
797+ prefer protocols which have a corresponding proxy environment variable.
616798 </para>
617− <para>You can find many source fetch helpers in <literal>pkgs/build-support/fetch*</literal>.
799+
800+ <para>
801+ You can find many source fetch helpers in
802+ <literal>pkgs/build-support/fetch*</literal>.
618803 </para>
619− <para>In the file <literal>pkgs/top-level/all-packages.nix</literal> you can
620− find fetch helpers, these have names on the form
621− <literal>fetchFrom*</literal>. The intention of these are to provide
622− snapshot fetches but using the same api as some of the version controlled
623− fetchers from <literal>pkgs/build-support/</literal>. As an example going
624− from bad to good:
625− <itemizedlist>
626− <listitem>
627− <para>Bad: Uses <literal>git://</literal> which won't be proxied.
804+
805+ <para>
806+ In the file <literal>pkgs/top-level/all-packages.nix</literal> you can find
807+ fetch helpers, these have names on the form <literal>fetchFrom*</literal>.
808+ The intention of these are to provide snapshot fetches but using the same
809+ api as some of the version controlled fetchers from
810+ <literal>pkgs/build-support/</literal>. As an example going from bad to
811+ good:
812+ <itemizedlist>
813+ <listitem>
814+ <para>
815+ Bad: Uses <literal>git://</literal> which won't be proxied.
628816<programlisting>
629817src = fetchgit {
630818 url = "git://github.com/NixOS/nix.git";
@@ -632,10 +820,11 @@ src = fetchgit {
632820 sha256 = "1cw5fszffl5pkpa6s6wjnkiv6lm5k618s32sp60kvmvpy7a2v9kg";
633821}
634822</programlisting>
635− </para>
636− </listitem>
637− <listitem>
638− <para>Better: This is ok, but an archive fetch will still be faster.
823+ </para>
824+ </listitem>
825+ <listitem>
826+ <para>
827+ Better: This is ok, but an archive fetch will still be faster.
639828<programlisting>
640829src = fetchgit {
641830 url = "https://github.com/NixOS/nix.git";
@@ -643,27 +832,35 @@ src = fetchgit {
643832 sha256 = "1cw5fszffl5pkpa6s6wjnkiv6lm5k618s32sp60kvmvpy7a2v9kg";
644833}
645834</programlisting>
646− </para>
647− </listitem>
648− <listitem>
649− <para>Best: Fetches a snapshot archive and you get the rev you want.
835+ </para>
836+ </listitem>
837+ <listitem>
838+ <para>
839+ Best: Fetches a snapshot archive and you get the rev you want.
650840<programlisting>
651841src = fetchFromGitHub {
652842 owner = "NixOS";
653843 repo = "nix";
654844 rev = "1f795f9f44607cc5bec70d1300150bfefcef2aae";
655− sha256 = "04yri911rj9j19qqqn6m82266fl05pz98inasni0vxr1cf1gdgv9";
845+ sha256 = "1i2yxndxb6yc9l6c99pypbd92lfq5aac4klq7y2v93c9qvx2cgpc";
656846}
657847</programlisting>
658− </para>
659− </listitem>
660− </itemizedlist>
848+ Find the value to put as <literal>sha256</literal> by running
849+ <literal>nix run -f '&lt;nixpkgs&gt;' nix-prefetch-github -c nix-prefetch-github --rev 1f795f9f44607cc5bec70d1300150bfefcef2aae NixOS nix</literal>
850+ or <literal>nix-prefetch-url --unpack https://github.com/NixOS/nix/archive/1f795f9f44607cc5bec70d1300150bfefcef2aae.tar.gz</literal>.
851+ </para>
852+ </listitem>
853+ </itemizedlist>
854+ </para>
855+ </section>
856+ <section xml:id="sec-patches">
857+ <title>Patches</title>
858+
859+ <para>
860+ Patches available online should be retrieved using
861+ <literal>fetchpatch</literal>.
661862 </para>
662−</section>
663863
664−<section xml:id="sec-patches"><title>Patches</title>
665− <para>Patches available online should be retrieved using
666− <literal>fetchpatch</literal>.</para>
667864 <para>
668865<programlisting>
669866patches = [
@@ -675,30 +872,54 @@ patches = [
675872];
676873</programlisting>
677874 </para>
678− <para>Otherwise, you can add a <literal>.patch</literal> file to the
679− <literal>nixpkgs</literal> repository. In the interest of keeping our
680− maintenance burden to a minimum, only patches that are unique
681− to <literal>nixpkgs</literal> should be added in this way.</para>
682−<para><programlisting>
875+
876+ <para>
877+ Otherwise, you can add a <literal>.patch</literal> file to the
878+ <literal>nixpkgs</literal> repository. In the interest of keeping our
879+ maintenance burden to a minimum, only patches that are unique to
880+ <literal>nixpkgs</literal> should be added in this way.
881+ </para>
882+
883+ <para>
884+<programlisting>
683885patches = [ ./0001-changes.patch ];
684−</programlisting></para>
685− <para>If you do need to do create this sort of patch file,
686− one way to do so is with git:
687− <orderedlist>
688− <listitem><para>Move to the root directory of the source code
689− you're patching.<screen>
690−$ cd the/program/source</screen></para></listitem>
691− <listitem><para>If a git repository is not already present,
692− create one and stage all of the source files.<screen>
886+</programlisting>
887+ </para>
888+
889+ <para>
890+ If you do need to do create this sort of patch file, one way to do so is
891+ with git:
892+ <orderedlist>
893+ <listitem>
894+ <para>
895+ Move to the root directory of the source code you're patching.
896+<screen>
897+$ cd the/program/source</screen>
898+ </para>
899+ </listitem>
900+ <listitem>
901+ <para>
902+ If a git repository is not already present, create one and stage all of
903+ the source files.
904+<screen>
693905$ git init
694−$ git add .</screen></para></listitem>
695− <listitem><para>Edit some files to make whatever changes need
696− to be included in the patch.</para></listitem>
697− <listitem><para>Use git to create a diff, and pipe the output
698− to a patch file:<screen>
906+$ git add .</screen>
907+ </para>
908+ </listitem>
909+ <listitem>
910+ <para>
911+ Edit some files to make whatever changes need to be included in the
912+ patch.
913+ </para>
914+ </listitem>
915+ <listitem>
916+ <para>
917+ Use git to create a diff, and pipe the output to a patch file:
918+<screen>
699919$ git diff > nixpkgs/pkgs/the/package/0001-changes.patch</screen>
700− </para></listitem>
701− </orderedlist></para>
702−</section>
703−
920+ </para>
921+ </listitem>
922+ </orderedlist>
923+ </para>
924+ </section>
704925</chapter>
doc/configuration.xml+329−284
@@ -1,40 +1,51 @@
11<chapter xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="chap-packageconfig">
4−
5−<title>Global configuration</title>
6−
7−<para>Nix comes with certain defaults about what packages can and
8−cannot be installed, based on a package's metadata. By default, Nix
9−will prevent installation if any of the following criteria are
10−true:</para>
11−
12−<itemizedlist>
13− <listitem><para>The package is thought to be broken, and has had
14− its <literal>meta.broken</literal> set to
15− <literal>true</literal>.</para></listitem>
16−
17− <listitem><para>The package's <literal>meta.license</literal> is set
18− to a license which is considered to be unfree.</para></listitem>
19−
20− <listitem><para>The package has known security vulnerabilities but
21− has not or can not be updated for some reason, and a list of issues
22− has been entered in to the package's
23− <literal>meta.knownVulnerabilities</literal>.</para></listitem>
24−</itemizedlist>
25−
26−<para>Note that all this is checked during evaluation already,
27−and the check includes any package that is evaluated.
28−In particular, all build-time dependencies are checked.
29−<literal>nix-env -qa</literal> will (attempt to) hide any packages
30−that would be refused.
31−</para>
32−
33−<para>Each of these criteria can be altered in the nixpkgs
34−configuration.</para>
35−
36−<para>The nixpkgs configuration for a NixOS system is set in the
37−<literal>configuration.nix</literal>, as in the following example:
4+ <title>Global configuration</title>
5+ <para>
6+ Nix comes with certain defaults about what packages can and cannot be
7+ installed, based on a package's metadata. By default, Nix will prevent
8+ installation if any of the following criteria are true:
9+ </para>
10+ <itemizedlist>
11+ <listitem>
12+ <para>
13+ The package is thought to be broken, and has had its
14+ <literal>meta.broken</literal> set to <literal>true</literal>.
15+ </para>
16+ </listitem>
17+ <listitem>
18+ <para>
19+ The package isn't intended to run on the given system, as none of its
20+ <literal>meta.platforms</literal> match the given system.
21+ </para>
22+ </listitem>
23+ <listitem>
24+ <para>
25+ The package's <literal>meta.license</literal> is set to a license which is
26+ considered to be unfree.
27+ </para>
28+ </listitem>
29+ <listitem>
30+ <para>
31+ The package has known security vulnerabilities but has not or can not be
32+ updated for some reason, and a list of issues has been entered in to the
33+ package's <literal>meta.knownVulnerabilities</literal>.
34+ </para>
35+ </listitem>
36+ </itemizedlist>
37+ <para>
38+ Note that all this is checked during evaluation already, and the check
39+ includes any package that is evaluated. In particular, all build-time
40+ dependencies are checked. <literal>nix-env -qa</literal> will (attempt to)
41+ hide any packages that would be refused.
42+ </para>
43+ <para>
44+ Each of these criteria can be altered in the nixpkgs configuration.
45+ </para>
46+ <para>
47+ The nixpkgs configuration for a NixOS system is set in the
48+ <literal>configuration.nix</literal>, as in the following example:
3849<programlisting>
3950{
4051 nixpkgs.config = {
@@ -42,151 +53,197 @@ configuration.</para>
4253 };
4354}
4455</programlisting>
45−However, this does not allow unfree software for individual users.
46−Their configurations are managed separately.</para>
47−
48−<para>A user's of nixpkgs configuration is stored in a user-specific
49−configuration file located at
50−<filename>~/.config/nixpkgs/config.nix</filename>. For example:
56+ However, this does not allow unfree software for individual users. Their
57+ configurations are managed separately.
58+ </para>
59+ <para>
60+ A user's of nixpkgs configuration is stored in a user-specific configuration
61+ file located at <filename>~/.config/nixpkgs/config.nix</filename>. For
62+ example:
5163<programlisting>
5264{
5365 allowUnfree = true;
5466}
5567</programlisting>
56−</para>
57−
58−<para>Note that we are not able to test or build unfree software on Hydra
59−due to policy. Most unfree licenses prohibit us from either executing or
60−distributing the software.</para>
61−
62−<section xml:id="sec-allow-broken">
68+ </para>
69+ <para>
70+ Note that we are not able to test or build unfree software on Hydra due to
71+ policy. Most unfree licenses prohibit us from either executing or
72+ distributing the software.
73+ </para>
74+ <section xml:id="sec-allow-broken">
6375 <title>Installing broken packages</title>
6476
65−
66− <para>There are two ways to try compiling a package which has been
67− marked as broken.</para>
77+ <para>
78+ There are two ways to try compiling a package which has been marked as
79+ broken.
80+ </para>
6881
6982 <itemizedlist>
70− <listitem><para>
71− For allowing the build of a broken package once, you can use an
72− environment variable for a single invocation of the nix tools:
73−
74− <programlisting>$ export NIXPKGS_ALLOW_BROKEN=1</programlisting>
75− </para></listitem>
76−
77− <listitem><para>
78− For permanently allowing broken packages to be built, you may
79− add <literal>allowBroken = true;</literal> to your user's
80− configuration file, like this:
81−
83+ <listitem>
84+ <para>
85+ For allowing the build of a broken package once, you can use an
86+ environment variable for a single invocation of the nix tools:
87+<programlisting>$ export NIXPKGS_ALLOW_BROKEN=1</programlisting>
88+ </para>
89+ </listitem>
90+ <listitem>
91+ <para>
92+ For permanently allowing broken packages to be built, you may add
93+ <literal>allowBroken = true;</literal> to your user's configuration file,
94+ like this:
8295<programlisting>
8396{
8497 allowBroken = true;
8598}
8699</programlisting>
87− </para></listitem>
100+ </para>
101+ </listitem>
88102 </itemizedlist>
89−</section>
103+ </section>
104+ <section xml:id="sec-allow-unsupported-system">
105+ <title>Installing packages on unsupported systems</title>
90106
91−<section xml:id="sec-allow-unfree">
92− <title>Installing unfree packages</title>
93−
94− <para>There are several ways to tweak how Nix handles a package
95− which has been marked as unfree.</para>
107+ <para>
108+ There are also two ways to try compiling a package which has been marked as
109+ unsuported for the given system.
110+ </para>
96111
97112 <itemizedlist>
98− <listitem><para>
99− To temporarily allow all unfree packages, you can use an
100− environment variable for a single invocation of the nix tools:
113+ <listitem>
114+ <para>
115+ For allowing the build of a broken package once, you can use an
116+ environment variable for a single invocation of the nix tools:
117+<programlisting>$ export NIXPKGS_ALLOW_UNSUPPORTED_SYSTEM=1</programlisting>
118+ </para>
119+ </listitem>
120+ <listitem>
121+ <para>
122+ For permanently allowing broken packages to be built, you may add
123+ <literal>allowUnsupportedSystem = true;</literal> to your user's
124+ configuration file, like this:
125+<programlisting>
126+{
127+ allowUnsupportedSystem = true;
128+}
129+</programlisting>
130+ </para>
131+ </listitem>
132+ </itemizedlist>
101133
102− <programlisting>$ export NIXPKGS_ALLOW_UNFREE=1</programlisting>
103− </para></listitem>
134+ <para>
135+ The difference between an a package being unsupported on some system and
136+ being broken is admittedly a bit fuzzy. If a program
137+ <emphasis>ought</emphasis> to work on a certain platform, but doesn't, the
138+ platform should be included in <literal>meta.platforms</literal>, but marked
139+ as broken with e.g. <literal>meta.broken =
140+ !hostPlatform.isWindows</literal>. Of course, this begs the question of what
141+ "ought" means exactly. That is left to the package maintainer.
142+ </para>
143+ </section>
144+ <section xml:id="sec-allow-unfree">
145+ <title>Installing unfree packages</title>
104146
105− <listitem><para>
106− It is possible to permanently allow individual unfree packages,
107− while still blocking unfree packages by default using the
108− <literal>allowUnfreePredicate</literal> configuration
109− option in the user configuration file.</para>
147+ <para>
148+ There are several ways to tweak how Nix handles a package which has been
149+ marked as unfree.
150+ </para>
110151
111− <para>This option is a function which accepts a package as a
112− parameter, and returns a boolean. The following example
113− configuration accepts a package and always returns false:
152+ <itemizedlist>
153+ <listitem>
154+ <para>
155+ To temporarily allow all unfree packages, you can use an environment
156+ variable for a single invocation of the nix tools:
157+<programlisting>$ export NIXPKGS_ALLOW_UNFREE=1</programlisting>
158+ </para>
159+ </listitem>
160+ <listitem>
161+ <para>
162+ It is possible to permanently allow individual unfree packages, while
163+ still blocking unfree packages by default using the
164+ <literal>allowUnfreePredicate</literal> configuration option in the user
165+ configuration file.
166+ </para>
167+ <para>
168+ This option is a function which accepts a package as a parameter, and
169+ returns a boolean. The following example configuration accepts a package
170+ and always returns false:
114171<programlisting>
115172{
116173 allowUnfreePredicate = (pkg: false);
117174}
118175</programlisting>
119− </para>
120−
121− <para>A more useful example, the following configuration allows
122− only allows flash player and visual studio code:
123−
176+ </para>
177+ <para>
178+ A more useful example, the following configuration allows only allows
179+ flash player and visual studio code:
124180<programlisting>
125181{
126182 allowUnfreePredicate = (pkg: elem (builtins.parseDrvName pkg.name).name [ "flashplayer" "vscode" ]);
127183}
128184</programlisting>
129− </para></listitem>
130−
131− <listitem>
132− <para>It is also possible to whitelist and blacklist licenses
133− that are specifically acceptable or not acceptable, using
134− <literal>whitelistedLicenses</literal> and
135− <literal>blacklistedLicenses</literal>, respectively.
136− </para>
137−
138− <para>The following example configuration whitelists the
139− licenses <literal>amd</literal> and <literal>wtfpl</literal>:
140−
185+ </para>
186+ </listitem>
187+ <listitem>
188+ <para>
189+ It is also possible to whitelist and blacklist licenses that are
190+ specifically acceptable or not acceptable, using
191+ <literal>whitelistedLicenses</literal> and
192+ <literal>blacklistedLicenses</literal>, respectively.
193+ </para>
194+ <para>
195+ The following example configuration whitelists the licenses
196+ <literal>amd</literal> and <literal>wtfpl</literal>:
141197<programlisting>
142198{
143199 whitelistedLicenses = with stdenv.lib.licenses; [ amd wtfpl ];
144200}
145201</programlisting>
146− </para>
147−
148− <para>The following example configuration blacklists the
149− <literal>gpl3</literal> and <literal>agpl3</literal> licenses:
150−
202+ </para>
203+ <para>
204+ The following example configuration blacklists the <literal>gpl3</literal>
205+ and <literal>agpl3</literal> licenses:
151206<programlisting>
152207{
153208 blacklistedLicenses = with stdenv.lib.licenses; [ agpl3 gpl3 ];
154209}
155210</programlisting>
156− </para>
157− </listitem>
211+ </para>
212+ </listitem>
158213 </itemizedlist>
159214
160− <para>A complete list of licenses can be found in the file
161− <filename>lib/licenses.nix</filename> of the nixpkgs tree.</para>
162−</section>
163−
164−
165−<section xml:id="sec-allow-insecure">
166− <title>
167− Installing insecure packages
168− </title>
215+ <para>
216+ A complete list of licenses can be found in the file
217+ <filename>lib/licenses.nix</filename> of the nixpkgs tree.
218+ </para>
219+ </section>
220+ <section xml:id="sec-allow-insecure">
221+ <title>Installing insecure packages</title>
169222
170− <para>There are several ways to tweak how Nix handles a package
171− which has been marked as insecure.</para>
223+ <para>
224+ There are several ways to tweak how Nix handles a package which has been
225+ marked as insecure.
226+ </para>
172227
173228 <itemizedlist>
174− <listitem><para>
175− To temporarily allow all insecure packages, you can use an
176− environment variable for a single invocation of the nix tools:
177−
178− <programlisting>$ export NIXPKGS_ALLOW_INSECURE=1</programlisting>
179− </para></listitem>
180−
181− <listitem><para>
182− It is possible to permanently allow individual insecure
183− packages, while still blocking other insecure packages by
184− default using the <literal>permittedInsecurePackages</literal>
185− configuration option in the user configuration file.</para>
186−
187− <para>The following example configuration permits the
188− installation of the hypothetically insecure package
189− <literal>hello</literal>, version <literal>1.2.3</literal>:
229+ <listitem>
230+ <para>
231+ To temporarily allow all insecure packages, you can use an environment
232+ variable for a single invocation of the nix tools:
233+<programlisting>$ export NIXPKGS_ALLOW_INSECURE=1</programlisting>
234+ </para>
235+ </listitem>
236+ <listitem>
237+ <para>
238+ It is possible to permanently allow individual insecure packages, while
239+ still blocking other insecure packages by default using the
240+ <literal>permittedInsecurePackages</literal> configuration option in the
241+ user configuration file.
242+ </para>
243+ <para>
244+ The following example configuration permits the installation of the
245+ hypothetically insecure package <literal>hello</literal>, version
246+ <literal>1.2.3</literal>:
190247<programlisting>
191248{
192249 permittedInsecurePackages = [
@@ -194,47 +251,44 @@ distributing the software.</para>
194251 ];
195252}
196253</programlisting>
197− </para>
198− </listitem>
199−
200− <listitem><para>
201− It is also possible to create a custom policy around which
202− insecure packages to allow and deny, by overriding the
203− <literal>allowInsecurePredicate</literal> configuration
204− option.</para>
205−
206− <para>The <literal>allowInsecurePredicate</literal> option is a
207− function which accepts a package and returns a boolean, much
208− like <literal>allowUnfreePredicate</literal>.</para>
209−
210− <para>The following configuration example only allows insecure
211− packages with very short names:
212−
254+ </para>
255+ </listitem>
256+ <listitem>
257+ <para>
258+ It is also possible to create a custom policy around which insecure
259+ packages to allow and deny, by overriding the
260+ <literal>allowInsecurePredicate</literal> configuration option.
261+ </para>
262+ <para>
263+ The <literal>allowInsecurePredicate</literal> option is a function which
264+ accepts a package and returns a boolean, much like
265+ <literal>allowUnfreePredicate</literal>.
266+ </para>
267+ <para>
268+ The following configuration example only allows insecure packages with
269+ very short names:
213270<programlisting>
214271{
215272 allowInsecurePredicate = (pkg: (builtins.stringLength (builtins.parseDrvName pkg.name).name) &lt;= 5);
216273}
217274</programlisting>
218− </para>
219−
220− <para>Note that <literal>permittedInsecurePackages</literal> is
221− only checked if <literal>allowInsecurePredicate</literal> is not
222− specified.
223− </para></listitem>
275+ </para>
276+ <para>
277+ Note that <literal>permittedInsecurePackages</literal> is only checked if
278+ <literal>allowInsecurePredicate</literal> is not specified.
279+ </para>
280+ </listitem>
224281 </itemizedlist>
225−</section>
226−
282+ </section>
227283<!--============================================================-->
228−
229−<section xml:id="sec-modify-via-packageOverrides"><title>Modify
230−packages via <literal>packageOverrides</literal></title>
231−
232−<para>You can define a function called
233−<varname>packageOverrides</varname> in your local
234−<filename>~/.config/nixpkgs/config.nix</filename> to override nix packages. It
235−must be a function that takes pkgs as an argument and return modified
236−set of packages.
237−
284+ <section xml:id="sec-modify-via-packageOverrides">
285+ <title>Modify packages via <literal>packageOverrides</literal></title>
286+
287+ <para>
288+ You can define a function called <varname>packageOverrides</varname> in your
289+ local <filename>~/.config/nixpkgs/config.nix</filename> to override nix
290+ packages. It must be a function that takes pkgs as an argument and return
291+ modified set of packages.
238292<programlisting>
239293{
240294 packageOverrides = pkgs: rec {
@@ -242,30 +296,27 @@ set of packages.
242296 };
243297}
244298</programlisting>
245−
246−</para>
247−
248−</section>
249−
250−<section xml:id="sec-declarative-package-management">
299+ </para>
300+ </section>
301+ <section xml:id="sec-declarative-package-management">
251302 <title>Declarative Package Management</title>
252303
253304 <section xml:id="sec-building-environment">
254− <title>Build an environment</title>
255−
256− <para>
257− Using <literal>packageOverrides</literal>, it is possible to manage
258− packages declaratively. This means that we can list all of our desired
259− packages within a declarative Nix expression. For example, to have
260− <literal>aspell</literal>, <literal>bc</literal>,
261− <literal>ffmpeg</literal>, <literal>coreutils</literal>,
262− <literal>gdb</literal>, <literal>nixUnstable</literal>,
263− <literal>emscripten</literal>, <literal>jq</literal>,
264− <literal>nox</literal>, and <literal>silver-searcher</literal>, we could
265− use the following in <filename>~/.config/nixpkgs/config.nix</filename>:
266− </para>
267−
268− <screen>
305+ <title>Build an environment</title>
306+
307+ <para>
308+ Using <literal>packageOverrides</literal>, it is possible to manage
309+ packages declaratively. This means that we can list all of our desired
310+ packages within a declarative Nix expression. For example, to have
311+ <literal>aspell</literal>, <literal>bc</literal>,
312+ <literal>ffmpeg</literal>, <literal>coreutils</literal>,
313+ <literal>gdb</literal>, <literal>nixUnstable</literal>,
314+ <literal>emscripten</literal>, <literal>jq</literal>,
315+ <literal>nox</literal>, and <literal>silver-searcher</literal>, we could
316+ use the following in <filename>~/.config/nixpkgs/config.nix</filename>:
317+ </para>
318+
319+<screen>
269320{
270321 packageOverrides = pkgs: with pkgs; {
271322 myPackages = pkgs.buildEnv {
@@ -274,19 +325,19 @@ set of packages.
274325 };
275326 };
276327}
277− </screen>
278−
279− <para>
280− To install it into our environment, you can just run <literal>nix-env -iA
281− nixpkgs.myPackages</literal>. If you want to load the packages to be built
282− from a working copy of <literal>nixpkgs</literal> you just run
283− <literal>nix-env -f. -iA myPackages</literal>. To explore what's been
284− installed, just look through <filename>~/.nix-profile/</filename>. You can
285− see that a lot of stuff has been installed. Some of this stuff is useful
286− some of it isn't. Let's tell Nixpkgs to only link the stuff that we want:
287− </para>
288−
289− <screen>
328+</screen>
329+
330+ <para>
331+ To install it into our environment, you can just run <literal>nix-env -iA
332+ nixpkgs.myPackages</literal>. If you want to load the packages to be built
333+ from a working copy of <literal>nixpkgs</literal> you just run
334+ <literal>nix-env -f. -iA myPackages</literal>. To explore what's been
335+ installed, just look through <filename>~/.nix-profile/</filename>. You can
336+ see that a lot of stuff has been installed. Some of this stuff is useful
337+ some of it isn't. Let's tell Nixpkgs to only link the stuff that we want:
338+ </para>
339+
340+<screen>
290341{
291342 packageOverrides = pkgs: with pkgs; {
292343 myPackages = pkgs.buildEnv {
@@ -296,65 +347,63 @@ set of packages.
296347 };
297348 };
298349}
299− </screen>
300−
301− <para>
302− <literal>pathsToLink</literal> tells Nixpkgs to only link the paths listed
303− which gets rid of the extra stuff in the profile.
304− <filename>/bin</filename> and <filename>/share</filename> are good
305− defaults for a user environment, getting rid of the clutter. If you are
306− running on Nix on MacOS, you may want to add another path as well,
307− <filename>/Applications</filename>, that makes GUI apps available.
308− </para>
309−
350+</screen>
351+
352+ <para>
353+ <literal>pathsToLink</literal> tells Nixpkgs to only link the paths listed
354+ which gets rid of the extra stuff in the profile. <filename>/bin</filename>
355+ and <filename>/share</filename> are good defaults for a user environment,
356+ getting rid of the clutter. If you are running on Nix on MacOS, you may
357+ want to add another path as well, <filename>/Applications</filename>, that
358+ makes GUI apps available.
359+ </para>
310360 </section>
311361
312362 <section xml:id="sec-getting-documentation">
313− <title>Getting documentation</title>
314−
315− <para>
316− After building that new environment, look through
317− <filename>~/.nix-profile</filename> to make sure everything is there that
318− we wanted. Discerning readers will note that some files are missing. Look
319− inside <filename>~/.nix-profile/share/man/man1/</filename> to verify this.
320− There are no man pages for any of the Nix tools! This is because some
321− packages like Nix have multiple outputs for things like documentation (see
322− section 4). Let's make Nix install those as well.
323− </para>
324−
325− <screen>
363+ <title>Getting documentation</title>
364+
365+ <para>
366+ After building that new environment, look through
367+ <filename>~/.nix-profile</filename> to make sure everything is there that
368+ we wanted. Discerning readers will note that some files are missing. Look
369+ inside <filename>~/.nix-profile/share/man/man1/</filename> to verify this.
370+ There are no man pages for any of the Nix tools! This is because some
371+ packages like Nix have multiple outputs for things like documentation (see
372+ section 4). Let's make Nix install those as well.
373+ </para>
374+
375+<screen>
326376{
327377 packageOverrides = pkgs: with pkgs; {
328378 myPackages = pkgs.buildEnv {
329379 name = "my-packages";
330380 paths = [ aspell bc coreutils ffmpeg nixUnstable emscripten jq nox silver-searcher ];
331− pathsToLink = [ "/share/man" "/share/doc" /bin" ];
381+ pathsToLink = [ "/share/man" "/share/doc" "/bin" ];
332382 extraOutputsToInstall = [ "man" "doc" ];
333383 };
334384 };
335385}
336− </screen>
386+</screen>
337387
338− <para>
339− This provides us with some useful documentation for using our packages.
340− However, if we actually want those manpages to be detected by man, we need
341− to set up our environment. This can also be managed within Nix
342− expressions.
343− </para>
388+ <para>
389+ This provides us with some useful documentation for using our packages.
390+ However, if we actually want those manpages to be detected by man, we need
391+ to set up our environment. This can also be managed within Nix expressions.
392+ </para>
344393
345− <screen>
394+<screen>
346395{
347396 packageOverrides = pkgs: with pkgs; rec {
348397 myProfile = writeText "my-profile" ''
349−export PATH=$HOME/.nix-profile/bin:/nix/var/nix/profiles/default/bin:/sbin:/bin:/usr/sbin:/usr/bin
350−export MANPATH=$HOME/.nix-profile/share/man:/nix/var/nix/profiles/default/share/man:/usr/share/man
398+ export PATH=$HOME/.nix-profile/bin:/nix/var/nix/profiles/default/bin:/sbin:/bin:/usr/sbin:/usr/bin
399+ export MANPATH=$HOME/.nix-profile/share/man:/nix/var/nix/profiles/default/share/man:/usr/share/man
351400 '';
352401 myPackages = pkgs.buildEnv {
353402 name = "my-packages";
354403 paths = [
355404 (runCommand "profile" {} ''
356−mkdir -p $out/etc/profile.d
357−cp ${myProfile} $out/etc/profile.d/my-profile.sh
405+ mkdir -p $out/etc/profile.d
406+ cp ${myProfile} $out/etc/profile.d/my-profile.sh
358407 '')
359408 aspell
360409 bc
@@ -367,20 +416,20 @@ cp ${myProfile} $out/etc/profile.d/my-profile.sh
367416 nox
368417 silver-searcher
369418 ];
370− pathsToLink = [ "/share/man" "/share/doc" /bin" "/etc" ];
419+ pathsToLink = [ "/share/man" "/share/doc" "/bin" "/etc" ];
371420 extraOutputsToInstall = [ "man" "doc" ];
372421 };
373422 };
374423}
375− </screen>
424+</screen>
376425
377− <para>
378− For this to work fully, you must also have this script sourced when you
379− are logged in. Try adding something like this to your
380− <filename>~/.profile</filename> file:
381− </para>
426+ <para>
427+ For this to work fully, you must also have this script sourced when you are
428+ logged in. Try adding something like this to your
429+ <filename>~/.profile</filename> file:
430+ </para>
382431
383− <screen>
432+<screen>
384433#!/bin/sh
385434if [ -d $HOME/.nix-profile/etc/profile.d ]; then
386435 for i in $HOME/.nix-profile/etc/profile.d/*.sh; do
@@ -389,38 +438,37 @@ if [ -d $HOME/.nix-profile/etc/profile.d ]; then
389438 fi
390439 done
391440fi
392− </screen>
393−
394− <para>
395− Now just run <literal>source $HOME/.profile</literal> and you can starting
396− loading man pages from your environent.
397− </para>
441+</screen>
398442
443+ <para>
444+ Now just run <literal>source $HOME/.profile</literal> and you can starting
445+ loading man pages from your environent.
446+ </para>
399447 </section>
400−
448+
401449 <section xml:id="sec-gnu-info-setup">
402− <title>GNU info setup</title>
450+ <title>GNU info setup</title>
403451
404− <para>
405− Configuring GNU info is a little bit trickier than man pages. To work
406− correctly, info needs a database to be generated. This can be done with
407− some small modifications to our environment scripts.
408− </para>
452+ <para>
453+ Configuring GNU info is a little bit trickier than man pages. To work
454+ correctly, info needs a database to be generated. This can be done with
455+ some small modifications to our environment scripts.
456+ </para>
409457
410− <screen>
458+<screen>
411459{
412460 packageOverrides = pkgs: with pkgs; rec {
413461 myProfile = writeText "my-profile" ''
414−export PATH=$HOME/.nix-profile/bin:/nix/var/nix/profiles/default/bin:/sbin:/bin:/usr/sbin:/usr/bin
415−export MANPATH=$HOME/.nix-profile/share/man:/nix/var/nix/profiles/default/share/man:/usr/share/man
416−export INFOPATH=$HOME/.nix-profile/share/info:/nix/var/nix/profiles/default/share/info:/usr/share/info
462+ export PATH=$HOME/.nix-profile/bin:/nix/var/nix/profiles/default/bin:/sbin:/bin:/usr/sbin:/usr/bin
463+ export MANPATH=$HOME/.nix-profile/share/man:/nix/var/nix/profiles/default/share/man:/usr/share/man
464+ export INFOPATH=$HOME/.nix-profile/share/info:/nix/var/nix/profiles/default/share/info:/usr/share/info
417465 '';
418466 myPackages = pkgs.buildEnv {
419467 name = "my-packages";
420468 paths = [
421469 (runCommand "profile" {} ''
422−mkdir -p $out/etc/profile.d
423−cp ${myProfile} $out/etc/profile.d/my-profile.sh
470+ mkdir -p $out/etc/profile.d
471+ cp ${myProfile} $out/etc/profile.d/my-profile.sh
424472 '')
425473 aspell
426474 bc
@@ -437,28 +485,25 @@ cp ${myProfile} $out/etc/profile.d/my-profile.sh
437485 pathsToLink = [ "/share/man" "/share/doc" "/share/info" "/bin" "/etc" ];
438486 extraOutputsToInstall = [ "man" "doc" "info" ];
439487 postBuild = ''
440− if [ -x $out/bin/install-info -a -w $out/share/info ]; then
441− shopt -s nullglob
442− for i in $out/share/info/*.info $out/share/info/*.info.gz; do
443− $out/bin/install-info $i $out/share/info/dir
444− done
445− fi
488+ if [ -x $out/bin/install-info -a -w $out/share/info ]; then
489+ shopt -s nullglob
490+ for i in $out/share/info/*.info $out/share/info/*.info.gz; do
491+ $out/bin/install-info $i $out/share/info/dir
492+ done
493+ fi
446494 '';
447495 };
448496 };
449497}
450− </screen>
451−
452− <para>
453− <literal>postBuild</literal> tells Nixpkgs to run a command after building
454− the environment. In this case, <literal>install-info</literal> adds the
455− installed info pages to <literal>dir</literal> which is GNU info's default
456− root node. Note that <literal>texinfoInteractive</literal> is added to the
457− environment to give the <literal>install-info</literal> command.
458− </para>
459−
498+</screen>
499+
500+ <para>
501+ <literal>postBuild</literal> tells Nixpkgs to run a command after building
502+ the environment. In this case, <literal>install-info</literal> adds the
503+ installed info pages to <literal>dir</literal> which is GNU info's default
504+ root node. Note that <literal>texinfoInteractive</literal> is added to the
505+ environment to give the <literal>install-info</literal> command.
506+ </para>
460507 </section>
461−
462−</section>
463−
508+ </section>
464509</chapter>
doc/contributing.xml+28−13
@@ -1,20 +1,35 @@
11<chapter xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="chap-contributing">
4−
5−<title>Contributing to this documentation</title>
6−
7−<para>The DocBook sources of the Nixpkgs manual are in the <filename
4+ <title>Contributing to this documentation</title>
5+ <para>
6+ The DocBook sources of the Nixpkgs manual are in the
7+ <filename
88xlink:href="https://github.com/NixOS/nixpkgs/tree/master/doc">doc</filename>
9−subdirectory of the Nixpkgs repository. If you make modifications to
10−the manual, it's important to build it before committing. You can do that as follows:
11−
9+ subdirectory of the Nixpkgs repository.
10+ </para>
11+ <para>
12+ You can quickly check your edits with <command>make</command>:
13+ </para>
1214<screen>
13−$ cd /path/to/nixpkgs
14−$ nix-build doc
15+ $ cd /path/to/nixpkgs/doc
16+ $ nix-shell
17+ [nix-shell]$ make
1518</screen>
16−
17−If the build succeeds, the manual will be in
18−<filename>./result/share/doc/nixpkgs/manual.html</filename>.</para>
19−
19+ <para>
20+ If you experience problems, run <command>make debug</command> to help
21+ understand the docbook errors.
22+ </para>
23+ <para>
24+ After making modifications to the manual, it's important to build it before
25+ committing. You can do that as follows:
26+<screen>
27+ $ cd /path/to/nixpkgs/doc
28+ $ nix-shell
29+ [nix-shell]$ make clean
30+ [nix-shell]$ nix-build .
31+</screen>
32+ If the build succeeds, the manual will be in
33+ <filename>./result/share/doc/nixpkgs/manual.html</filename>.
34+ </para>
2035</chapter>
doc/cross-compilation.xml+434−267
@@ -1,308 +1,475 @@
11<chapter xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="chap-cross">
4−
5−<title>Cross-compilation</title>
6−
7−<section xml:id="sec-cross-intro">
4+ <title>Cross-compilation</title>
5+ <section xml:id="sec-cross-intro">
86 <title>Introduction</title>
7+
98 <para>
10− "Cross-compilation" means compiling a program on one machine for another type of machine.
11− For example, a typical use of cross compilation is to compile programs for embedded devices.
12− These devices often don't have the computing power and memory to compile their own programs.
13− One might think that cross-compilation is a fairly niche concern, but there are advantages to being rigorous about distinguishing build-time vs run-time environments even when one is developing and deploying on the same machine.
14− Nixpkgs is increasingly adopting the opinion that packages should be written with cross-compilation in mind, and nixpkgs should evaluate in a similar way (by minimizing cross-compilation-specific special cases) whether or not one is cross-compiling.
9+ "Cross-compilation" means compiling a program on one machine for another
10+ type of machine. For example, a typical use of cross compilation is to
11+ compile programs for embedded devices. These devices often don't have the
12+ computing power and memory to compile their own programs. One might think
13+ that cross-compilation is a fairly niche concern, but there are advantages
14+ to being rigorous about distinguishing build-time vs run-time environments
15+ even when one is developing and deploying on the same machine. Nixpkgs is
16+ increasingly adopting the opinion that packages should be written with
17+ cross-compilation in mind, and nixpkgs should evaluate in a similar way (by
18+ minimizing cross-compilation-specific special cases) whether or not one is
19+ cross-compiling.
1520 </para>
1621
1722 <para>
18− This chapter will be organized in three parts.
19− First, it will describe the basics of how to package software in a way that supports cross-compilation.
20− Second, it will describe how to use Nixpkgs when cross-compiling.
21− Third, it will describe the internal infrastructure supporting cross-compilation.
23+ This chapter will be organized in three parts. First, it will describe the
24+ basics of how to package software in a way that supports cross-compilation.
25+ Second, it will describe how to use Nixpkgs when cross-compiling. Third, it
26+ will describe the internal infrastructure supporting cross-compilation.
2227 </para>
23−</section>
24−
28+ </section>
2529<!--============================================================-->
26−
27−<section xml:id="sec-cross-packaging">
30+ <section xml:id="sec-cross-packaging">
2831 <title>Packaging in a cross-friendly manner</title>
2932
30− <section>
31− <title>Platform parameters</title>
32− <para>
33− Nixpkgs follows the <link xlink:href="https://gcc.gnu.org/onlinedocs/gccint/Configure-Terms.html">common historical convention of GNU autoconf</link> of distinguishing between 3 types of platform: <wordasword>build</wordasword>, <wordasword>host</wordasword>, and <wordasword>target</wordasword>.
33+ <section xml:id="sec-cross-platform-parameters">
34+ <title>Platform parameters</title>
3435
35− In summary, <wordasword>build</wordasword> is the platform on which a package is being built, <wordasword>host</wordasword> is the platform on which it is to run. The third attribute, <wordasword>target</wordasword>, is relevant only for certain specific compilers and build tools.
36− </para>
36+ <para>
37+ Nixpkgs follows the
38+ <link xlink:href="https://gcc.gnu.org/onlinedocs/gccint/Configure-Terms.html">common
39+ historical convention of GNU autoconf</link> of distinguishing between 3
40+ types of platform: <wordasword>build</wordasword>,
41+ <wordasword>host</wordasword>, and <wordasword>target</wordasword>. In
42+ summary, <wordasword>build</wordasword> is the platform on which a package
43+ is being built, <wordasword>host</wordasword> is the platform on which it
44+ is to run. The third attribute, <wordasword>target</wordasword>, is
45+ relevant only for certain specific compilers and build tools.
46+ </para>
3747
38− <para>
39− In Nixpkgs, these three platforms are defined as attribute sets under the names <literal>buildPlatform</literal>, <literal>hostPlatform</literal>, and <literal>targetPlatform</literal>.
40− All three are always defined as attributes in the standard environment, and at the top level. That means one can get at them just like a dependency in a function that is imported with <literal>callPackage</literal>:
41− <programlisting>{ stdenv, buildPlatform, hostPlatform, fooDep, barDep, .. }: ...buildPlatform...</programlisting>, or just off <varname>stdenv</varname>:
42− <programlisting>{ stdenv, fooDep, barDep, .. }: ...stdenv.buildPlatform...</programlisting>.
43− </para>
44− <variablelist>
45− <varlistentry>
46− <term><varname>buildPlatform</varname></term>
47− <listitem><para>
48− The "build platform" is the platform on which a package is built.
49− Once someone has a built package, or pre-built binary package, the build platform should not matter and be safe to ignore.
50− </para></listitem>
51− </varlistentry>
52− <varlistentry>
53− <term><varname>hostPlatform</varname></term>
54− <listitem><para>
55− The "host platform" is the platform on which a package will be run.
56− This is the simplest platform to understand, but also the one with the worst name.
57− </para></listitem>
58− </varlistentry>
59− <varlistentry>
60− <term><varname>targetPlatform</varname></term>
61− <listitem>
62− <para>
63− The "target platform" attribute is, unlike the other two attributes, not actually fundamental to the process of building software.
64− Instead, it is only relevant for compatibility with building certain specific compilers and build tools.
65− It can be safely ignored for all other packages.
66− </para>
67− <para>
68− The build process of certain compilers is written in such a way that the compiler resulting from a single build can itself only produce binaries for a single platform.
69− The task specifying this single "target platform" is thus pushed to build time of the compiler.
70− The root cause of this mistake is often that the compiler (which will be run on the host) and the the standard library/runtime (which will be run on the target) are built by a single build process.
71− </para>
72− <para>
73− There is no fundamental need to think about a single target ahead of time like this.
74− If the tool supports modular or pluggable backends, both the need to specify the target at build time and the constraint of having only a single target disappear.
75− An example of such a tool is LLVM.
76− </para>
77− <para>
78− Although the existance of a "target platfom" is arguably a historical mistake, it is a common one: examples of tools that suffer from it are GCC, Binutils, GHC and Autoconf.
79− Nixpkgs tries to avoid sharing in the mistake where possible.
80− Still, because the concept of a target platform is so ingrained, it is best to support it as is.
81− </para>
82− </listitem>
83− </varlistentry>
84− </variablelist>
85− <para>
86− The exact schema these fields follow is a bit ill-defined due to a long and convoluted evolution, but this is slowly being cleaned up.
87− You can see examples of ones used in practice in <literal>lib.systems.examples</literal>; note how they are not all very consistent.
88− For now, here are few fields can count on them containing:
89− </para>
90− <variablelist>
91− <varlistentry>
92− <term><varname>system</varname></term>
93− <listitem>
94− <para>
95− This is a two-component shorthand for the platform.
96− Examples of this would be "x86_64-darwin" and "i686-linux"; see <literal>lib.systems.doubles</literal> for more.
97− This format isn't very standard, but has built-in support in Nix, such as the <varname>builtins.currentSystem</varname> impure string.
98− </para>
99− </listitem>
100− </varlistentry>
101− <varlistentry>
102− <term><varname>config</varname></term>
103− <listitem>
104− <para>
105− This is a 3- or 4- component shorthand for the platform.
106− Examples of this would be "x86_64-unknown-linux-gnu" and "aarch64-apple-darwin14".
107− This is a standard format called the "LLVM target triple", as they are pioneered by LLVM and traditionally just used for the <varname>targetPlatform</varname>.
108− This format is strictly more informative than the "Nix host double", as the previous format could analogously be termed.
109− This needs a better name than <varname>config</varname>!
110− </para>
111− </listitem>
112− </varlistentry>
113− <varlistentry>
114− <term><varname>parsed</varname></term>
115− <listitem>
116− <para>
117− This is a nix representation of a parsed LLVM target triple with white-listed components.
118− This can be specified directly, or actually parsed from the <varname>config</varname>.
119− [Technically, only one need be specified and the others can be inferred, though the precision of inference may not be very good.]
120− See <literal>lib.systems.parse</literal> for the exact representation.
121− </para>
122− </listitem>
123− </varlistentry>
124− <varlistentry>
125− <term><varname>libc</varname></term>
126− <listitem>
127− <para>
128− This is a string identifying the standard C library used.
129− Valid identifiers include "glibc" for GNU libc, "libSystem" for Darwin's Libsystem, and "uclibc" for µClibc.
130− It should probably be refactored to use the module system, like <varname>parse</varname>.
131− </para>
132− </listitem>
133− </varlistentry>
134− <varlistentry>
135− <term><varname>is*</varname></term>
136− <listitem>
137− <para>
138− These predicates are defined in <literal>lib.systems.inspect</literal>, and slapped on every platform.
139− They are superior to the ones in <varname>stdenv</varname> as they force the user to be explicit about which platform they are inspecting.
140− Please use these instead of those.
141− </para>
142− </listitem>
143− </varlistentry>
144− <varlistentry>
145− <term><varname>platform</varname></term>
146− <listitem>
147− <para>
148− This is, quite frankly, a dumping ground of ad-hoc settings (it's an attribute set).
149− See <literal>lib.systems.platforms</literal> for examples—there's hopefully one in there that will work verbatim for each platform that is working.
150− Please help us triage these flags and give them better homes!
151− </para>
152− </listitem>
153− </varlistentry>
154− </variablelist>
48+ <para>
49+ In Nixpkgs, these three platforms are defined as attribute sets under the
50+ names <literal>buildPlatform</literal>, <literal>hostPlatform</literal>,
51+ and <literal>targetPlatform</literal>. They are always defined as
52+ attributes in the standard environment. That means one can access them
53+ like:
54+<programlisting>{ stdenv, fooDep, barDep, .. }: ...stdenv.buildPlatform...</programlisting>
55+ .
56+ </para>
57+
58+ <variablelist>
59+ <varlistentry>
60+ <term>
61+ <varname>buildPlatform</varname>
62+ </term>
63+ <listitem>
64+ <para>
65+ The "build platform" is the platform on which a package is built. Once
66+ someone has a built package, or pre-built binary package, the build
67+ platform should not matter and be safe to ignore.
68+ </para>
69+ </listitem>
70+ </varlistentry>
71+ <varlistentry>
72+ <term>
73+ <varname>hostPlatform</varname>
74+ </term>
75+ <listitem>
76+ <para>
77+ The "host platform" is the platform on which a package will be run. This
78+ is the simplest platform to understand, but also the one with the worst
79+ name.
80+ </para>
81+ </listitem>
82+ </varlistentry>
83+ <varlistentry>
84+ <term>
85+ <varname>targetPlatform</varname>
86+ </term>
87+ <listitem>
88+ <para>
89+ The "target platform" attribute is, unlike the other two attributes, not
90+ actually fundamental to the process of building software. Instead, it is
91+ only relevant for compatibility with building certain specific compilers
92+ and build tools. It can be safely ignored for all other packages.
93+ </para>
94+ <para>
95+ The build process of certain compilers is written in such a way that the
96+ compiler resulting from a single build can itself only produce binaries
97+ for a single platform. The task specifying this single "target platform"
98+ is thus pushed to build time of the compiler. The root cause of this
99+ mistake is often that the compiler (which will be run on the host) and
100+ the the standard library/runtime (which will be run on the target) are
101+ built by a single build process.
102+ </para>
103+ <para>
104+ There is no fundamental need to think about a single target ahead of
105+ time like this. If the tool supports modular or pluggable backends, both
106+ the need to specify the target at build time and the constraint of
107+ having only a single target disappear. An example of such a tool is
108+ LLVM.
109+ </para>
110+ <para>
111+ Although the existence of a "target platfom" is arguably a historical
112+ mistake, it is a common one: examples of tools that suffer from it are
113+ GCC, Binutils, GHC and Autoconf. Nixpkgs tries to avoid sharing in the
114+ mistake where possible. Still, because the concept of a target platform
115+ is so ingrained, it is best to support it as is.
116+ </para>
117+ </listitem>
118+ </varlistentry>
119+ </variablelist>
120+
121+ <para>
122+ The exact schema these fields follow is a bit ill-defined due to a long and
123+ convoluted evolution, but this is slowly being cleaned up. You can see
124+ examples of ones used in practice in
125+ <literal>lib.systems.examples</literal>; note how they are not all very
126+ consistent. For now, here are few fields can count on them containing:
127+ </para>
128+
129+ <variablelist>
130+ <varlistentry>
131+ <term>
132+ <varname>system</varname>
133+ </term>
134+ <listitem>
135+ <para>
136+ This is a two-component shorthand for the platform. Examples of this
137+ would be "x86_64-darwin" and "i686-linux"; see
138+ <literal>lib.systems.doubles</literal> for more. This format isn't very
139+ standard, but has built-in support in Nix, such as the
140+ <varname>builtins.currentSystem</varname> impure string.
141+ </para>
142+ </listitem>
143+ </varlistentry>
144+ <varlistentry>
145+ <term>
146+ <varname>config</varname>
147+ </term>
148+ <listitem>
149+ <para>
150+ This is a 3- or 4- component shorthand for the platform. Examples of
151+ this would be "x86_64-unknown-linux-gnu" and "aarch64-apple-darwin14".
152+ This is a standard format called the "LLVM target triple", as they are
153+ pioneered by LLVM and traditionally just used for the
154+ <varname>targetPlatform</varname>. This format is strictly more
155+ informative than the "Nix host double", as the previous format could
156+ analogously be termed. This needs a better name than
157+ <varname>config</varname>!
158+ </para>
159+ </listitem>
160+ </varlistentry>
161+ <varlistentry>
162+ <term>
163+ <varname>parsed</varname>
164+ </term>
165+ <listitem>
166+ <para>
167+ This is a nix representation of a parsed LLVM target triple with
168+ white-listed components. This can be specified directly, or actually
169+ parsed from the <varname>config</varname>. [Technically, only one need
170+ be specified and the others can be inferred, though the precision of
171+ inference may not be very good.] See
172+ <literal>lib.systems.parse</literal> for the exact representation.
173+ </para>
174+ </listitem>
175+ </varlistentry>
176+ <varlistentry>
177+ <term>
178+ <varname>libc</varname>
179+ </term>
180+ <listitem>
181+ <para>
182+ This is a string identifying the standard C library used. Valid
183+ identifiers include "glibc" for GNU libc, "libSystem" for Darwin's
184+ Libsystem, and "uclibc" for µClibc. It should probably be refactored to
185+ use the module system, like <varname>parse</varname>.
186+ </para>
187+ </listitem>
188+ </varlistentry>
189+ <varlistentry>
190+ <term>
191+ <varname>is*</varname>
192+ </term>
193+ <listitem>
194+ <para>
195+ These predicates are defined in <literal>lib.systems.inspect</literal>,
196+ and slapped on every platform. They are superior to the ones in
197+ <varname>stdenv</varname> as they force the user to be explicit about
198+ which platform they are inspecting. Please use these instead of those.
199+ </para>
200+ </listitem>
201+ </varlistentry>
202+ <varlistentry>
203+ <term>
204+ <varname>platform</varname>
205+ </term>
206+ <listitem>
207+ <para>
208+ This is, quite frankly, a dumping ground of ad-hoc settings (it's an
209+ attribute set). See <literal>lib.systems.platforms</literal> for
210+ examples—there's hopefully one in there that will work verbatim for
211+ each platform that is working. Please help us triage these flags and
212+ give them better homes!
213+ </para>
214+ </listitem>
215+ </varlistentry>
216+ </variablelist>
155217 </section>
156218
157− <section>
158− <title>Specifying Dependencies</title>
159− <para>
160− In this section we explore the relationship between both runtime and buildtime dependencies and the 3 Autoconf platforms.
161− </para>
162− <para>
163− A runtime dependency between 2 packages implies that between them both the host and target platforms match.
164− This is directly implied by the meaning of "host platform" and "runtime dependency":
165− The package dependency exists while both packages are running on a single host platform.
166− </para>
167− <para>
168− A build time dependency, however, implies a shift in platforms between the depending package and the depended-on package.
169− The meaning of a build time dependency is that to build the depending package we need to be able to run the depended-on's package.
170− The depending package's build platform is therefore equal to the depended-on package's host platform.
171− Analogously, the depending package's host platform is equal to the depended-on package's target platform.
172− </para>
173− <para>
174− In this manner, given the 3 platforms for one package, we can determine the three platforms for all its transitive dependencies.
175− This is the most important guiding principle behind cross-compilation with Nixpkgs, and will be called the <wordasword>sliding window principle</wordasword>.
176− </para>
177− <para>
178− Some examples will probably make this clearer.
179− If a package is being built with a <literal>(build, host, target)</literal> platform triple of <literal>(foo, bar, bar)</literal>, then its build-time dependencies would have a triple of <literal>(foo, foo, bar)</literal>, and <emphasis>those packages'</emphasis> build-time dependencies would have triple of <literal>(foo, foo, foo)</literal>.
180− In other words, it should take two "rounds" of following build-time dependency edges before one reaches a fixed point where, by the sliding window principle, the platform triple no longer changes.
181− Indeed, this happens with cross compilation, where only rounds of native dependencies starting with the second necessarily coincide with native packages.
182− </para>
183− <note><para>
184− The depending package's target platform is unconstrained by the sliding window principle, which makes sense in that one can in principle build cross compilers targeting arbitrary platforms.
185− </para></note>
219+ <section xml:id="sec-cross-specifying-dependencies">
220+ <title>Specifying Dependencies</title>
221+
222+ <para>
223+ In this section we explore the relationship between both runtime and
224+ buildtime dependencies and the 3 Autoconf platforms.
225+ </para>
226+
227+ <para>
228+ A runtime dependency between 2 packages implies that between them both the
229+ host and target platforms match. This is directly implied by the meaning of
230+ "host platform" and "runtime dependency": The package dependency exists
231+ while both packages are running on a single host platform.
232+ </para>
233+
234+ <para>
235+ A build time dependency, however, implies a shift in platforms between the
236+ depending package and the depended-on package. The meaning of a build time
237+ dependency is that to build the depending package we need to be able to run
238+ the depended-on's package. The depending package's build platform is
239+ therefore equal to the depended-on package's host platform. Analogously,
240+ the depending package's host platform is equal to the depended-on package's
241+ target platform.
242+ </para>
243+
244+ <para>
245+ In this manner, given the 3 platforms for one package, we can determine the
246+ three platforms for all its transitive dependencies. This is the most
247+ important guiding principle behind cross-compilation with Nixpkgs, and will
248+ be called the <wordasword>sliding window principle</wordasword>.
249+ </para>
250+
251+ <para>
252+ Some examples will probably make this clearer. If a package is being built
253+ with a <literal>(build, host, target)</literal> platform triple of
254+ <literal>(foo, bar, bar)</literal>, then its build-time dependencies would
255+ have a triple of <literal>(foo, foo, bar)</literal>, and <emphasis>those
256+ packages'</emphasis> build-time dependencies would have triple of
257+ <literal>(foo, foo, foo)</literal>. In other words, it should take two
258+ "rounds" of following build-time dependency edges before one reaches a
259+ fixed point where, by the sliding window principle, the platform triple no
260+ longer changes. Indeed, this happens with cross compilation, where only
261+ rounds of native dependencies starting with the second necessarily coincide
262+ with native packages.
263+ </para>
264+
265+ <note>
186266 <para>
187− How does this work in practice? Nixpkgs is now structured so that build-time dependencies are taken from <varname>buildPackages</varname>, whereas run-time dependencies are taken from the top level attribute set.
188− For example, <varname>buildPackages.gcc</varname> should be used at build time, while <varname>gcc</varname> should be used at run time.
189− Now, for most of Nixpkgs's history, there was no <varname>buildPackages</varname>, and most packages have not been refactored to use it explicitly.
190− Instead, one can use the six (<emphasis>gasp</emphasis>) attributes used for specifying dependencies as documented in <xref linkend="ssec-stdenv-dependencies"/>.
191− We "splice" together the run-time and build-time package sets with <varname>callPackage</varname>, and then <varname>mkDerivation</varname> for each of four attributes pulls the right derivation out.
192− This splicing can be skipped when not cross compiling as the package sets are the same, but is a bit slow for cross compiling.
193− Because of this, a best-of-both-worlds solution is in the works with no splicing or explicit access of <varname>buildPackages</varname> needed.
194− For now, feel free to use either method.
267+ The depending package's target platform is unconstrained by the sliding
268+ window principle, which makes sense in that one can in principle build
269+ cross compilers targeting arbitrary platforms.
195270 </para>
196− <note><para>
197− There is also a "backlink" <varname>targetPackages</varname>, yielding a package set whose <varname>buildPackages</varname> is the current package set.
198− This is a hack, though, to accommodate compilers with lousy build systems.
199− Please do not use this unless you are absolutely sure you are packaging such a compiler and there is no other way.
200− </para></note>
201− </section>
271+ </note>
272+
273+ <para>
274+ How does this work in practice? Nixpkgs is now structured so that
275+ build-time dependencies are taken from <varname>buildPackages</varname>,
276+ whereas run-time dependencies are taken from the top level attribute set.
277+ For example, <varname>buildPackages.gcc</varname> should be used at build
278+ time, while <varname>gcc</varname> should be used at run time. Now, for
279+ most of Nixpkgs's history, there was no <varname>buildPackages</varname>,
280+ and most packages have not been refactored to use it explicitly. Instead,
281+ one can use the six (<emphasis>gasp</emphasis>) attributes used for
282+ specifying dependencies as documented in
283+ <xref linkend="ssec-stdenv-dependencies"/>. We "splice" together the
284+ run-time and build-time package sets with <varname>callPackage</varname>,
285+ and then <varname>mkDerivation</varname> for each of four attributes pulls
286+ the right derivation out. This splicing can be skipped when not cross
287+ compiling as the package sets are the same, but is a bit slow for cross
288+ compiling. Because of this, a best-of-both-worlds solution is in the works
289+ with no splicing or explicit access of <varname>buildPackages</varname>
290+ needed. For now, feel free to use either method.
291+ </para>
202292
203− <section>
204− <title>Cross packagaing cookbook</title>
293+ <note>
205294 <para>
206− Some frequently problems when packaging for cross compilation are good to just spell and answer.
207− Ideally the information above is exhaustive, so this section cannot provide any new information,
208− but its ludicrous and cruel to expect everyone to spend effort working through the interaction of many features just to figure out the same answer to the same common problem.
209− Feel free to add to this list!
295+ There is also a "backlink" <varname>targetPackages</varname>, yielding a
296+ package set whose <varname>buildPackages</varname> is the current package
297+ set. This is a hack, though, to accommodate compilers with lousy build
298+ systems. Please do not use this unless you are absolutely sure you are
299+ packaging such a compiler and there is no other way.
210300 </para>
211− <qandaset>
212− <qandaentry>
213− <question><para>
214− What if my package's build system needs to build a C program to be run under the build environment?
215− </para></question>
216− <answer><para>
217− <programlisting>depsBuildBuild = [ buildPackages.stdenv.cc ];</programlisting>
218− Add it to your <function>mkDerivation</function> invocation.
219− </para></answer>
220− </qandaentry>
221− <qandaentry>
222− <question><para>
223− My package fails to find <command>ar</command>.
224− </para></question>
225− <answer><para>
226− Many packages assume that an unprefixed <command>ar</command> is available, but Nix doesn't provide one.
227− It only provides a prefixed one, just as it only does for all the other binutils programs.
228− It may be necessary to patch the package to fix the build system to use a prefixed `ar`.
229− </para></answer>
230− </qandaentry>
231− <qandaentry>
232− <question><para>
233− My package's testsuite needs to run host platform code.
234− </para></question>
235− <answer><para>
236− <programlisting>doCheck = stdenv.hostPlatform != stdenv.buildPlatfrom;</programlisting>
237− Add it to your <function>mkDerivation</function> invocation.
238− </para></answer>
239− </qandaentry>
240− </qandaset>
301+ </note>
241302 </section>
242−</section>
243303
244−<!--============================================================-->
304+ <section xml:id="sec-cross-cookbook">
305+ <title>Cross packaging cookbook</title>
306+
307+ <para>
308+ Some frequently problems when packaging for cross compilation are good to
309+ just spell and answer. Ideally the information above is exhaustive, so this
310+ section cannot provide any new information, but its ludicrous and cruel to
311+ expect everyone to spend effort working through the interaction of many
312+ features just to figure out the same answer to the same common problem.
313+ Feel free to add to this list!
314+ </para>
245315
246−<section xml:id="sec-cross-usage">
316+ <qandaset>
317+ <qandaentry xml:id="cross-qa-build-c-program-in-build-environment">
318+ <question>
319+ <para>
320+ What if my package's build system needs to build a C program to be run
321+ under the build environment?
322+ </para>
323+ </question>
324+ <answer>
325+ <para>
326+<programlisting>depsBuildBuild = [ buildPackages.stdenv.cc ];</programlisting>
327+ Add it to your <function>mkDerivation</function> invocation.
328+ </para>
329+ </answer>
330+ </qandaentry>
331+ <qandaentry xml:id="cross-qa-fails-to-find-ar">
332+ <question>
333+ <para>
334+ My package fails to find <command>ar</command>.
335+ </para>
336+ </question>
337+ <answer>
338+ <para>
339+ Many packages assume that an unprefixed <command>ar</command> is
340+ available, but Nix doesn't provide one. It only provides a prefixed one,
341+ just as it only does for all the other binutils programs. It may be
342+ necessary to patch the package to fix the build system to use a prefixed
343+ `ar`.
344+ </para>
345+ </answer>
346+ </qandaentry>
347+ <qandaentry xml:id="cross-testsuite-runs-host-code">
348+ <question>
349+ <para>
350+ My package's testsuite needs to run host platform code.
351+ </para>
352+ </question>
353+ <answer>
354+ <para>
355+<programlisting>doCheck = stdenv.hostPlatform != stdenv.buildPlatfrom;</programlisting>
356+ Add it to your <function>mkDerivation</function> invocation.
357+ </para>
358+ </answer>
359+ </qandaentry>
360+ </qandaset>
361+ </section>
362+ </section>
363+<!--============================================================-->
364+ <section xml:id="sec-cross-usage">
247365 <title>Cross-building packages</title>
248− <note><para>
249− More information needs to moved from the old wiki, especially <link xlink:href="https://nixos.org/wiki/CrossCompiling" />, for this section.
250− </para></note>
366+
367+ <note>
368+ <para>
369+ More information needs to moved from the old wiki, especially
370+ <link xlink:href="https://nixos.org/wiki/CrossCompiling" />, for this
371+ section.
372+ </para>
373+ </note>
374+
251375 <para>
252− Nixpkgs can be instantiated with <varname>localSystem</varname> alone, in which case there is no cross compiling and everything is built by and for that system,
253− or also with <varname>crossSystem</varname>, in which case packages run on the latter, but all building happens on the former.
254− Both parameters take the same schema as the 3 (build, host, and target) platforms defined in the previous section.
255− As mentioned above, <literal>lib.systems.examples</literal> has some platforms which are used as arguments for these parameters in practice.
256− You can use them programmatically, or on the command line: <programlisting>
376+ Nixpkgs can be instantiated with <varname>localSystem</varname> alone, in
377+ which case there is no cross compiling and everything is built by and for
378+ that system, or also with <varname>crossSystem</varname>, in which case
379+ packages run on the latter, but all building happens on the former. Both
380+ parameters take the same schema as the 3 (build, host, and target) platforms
381+ defined in the previous section. As mentioned above,
382+ <literal>lib.systems.examples</literal> has some platforms which are used as
383+ arguments for these parameters in practice. You can use them
384+ programmatically, or on the command line:
385+<programlisting>
257386nix-build &lt;nixpkgs&gt; --arg crossSystem '(import &lt;nixpkgs/lib&gt;).systems.examples.fooBarBaz' -A whatever</programlisting>
258387 </para>
388+
259389 <note>
260− <para>
261− Eventually we would like to make these platform examples an unnecessary convenience so that <programlisting>
390+ <para>
391+ Eventually we would like to make these platform examples an unnecessary
392+ convenience so that
393+<programlisting>
262394nix-build &lt;nixpkgs&gt; --arg crossSystem.config '&lt;arch&gt;-&lt;os&gt;-&lt;vendor&gt;-&lt;abi&gt;' -A whatever</programlisting>
263− works in the vast majority of cases.
264− The problem today is dependencies on other sorts of configuration which aren't given proper defaults.
265− We rely on the examples to crudely to set those configuration parameters in some vaguely sane manner on the users behalf.
266− Issue <link xlink:href="https://github.com/NixOS/nixpkgs/issues/34274">#34274</link> tracks this inconvenience along with its root cause in crufty configuration options.
267− </para>
395+ works in the vast majority of cases. The problem today is dependencies on
396+ other sorts of configuration which aren't given proper defaults. We rely on
397+ the examples to crudely to set those configuration parameters in some
398+ vaguely sane manner on the users behalf. Issue
399+ <link xlink:href="https://github.com/NixOS/nixpkgs/issues/34274">#34274</link>
400+ tracks this inconvenience along with its root cause in crufty configuration
401+ options.
402+ </para>
268403 </note>
404+
269405 <para>
270− While one is free to pass both parameters in full, there's a lot of logic to fill in missing fields.
271− As discussed in the previous section, only one of <varname>system</varname>, <varname>config</varname>, and <varname>parsed</varname> is needed to infer the other two.
272− Additionally, <varname>libc</varname> will be inferred from <varname>parse</varname>.
273− Finally, <literal>localSystem.system</literal> is also <emphasis>impurely</emphasis> inferred based on the platform evaluation occurs.
274− This means it is often not necessary to pass <varname>localSystem</varname> at all, as in the command-line example in the previous paragraph.
406+ While one is free to pass both parameters in full, there's a lot of logic to
407+ fill in missing fields. As discussed in the previous section, only one of
408+ <varname>system</varname>, <varname>config</varname>, and
409+ <varname>parsed</varname> is needed to infer the other two. Additionally,
410+ <varname>libc</varname> will be inferred from <varname>parse</varname>.
411+ Finally, <literal>localSystem.system</literal> is also
412+ <emphasis>impurely</emphasis> inferred based on the platform evaluation
413+ occurs. This means it is often not necessary to pass
414+ <varname>localSystem</varname> at all, as in the command-line example in the
415+ previous paragraph.
275416 </para>
417+
276418 <note>
277− <para>
278− Many sources (manual, wiki, etc) probably mention passing <varname>system</varname>, <varname>platform</varname>, along with the optional <varname>crossSystem</varname> to nixpkgs:
279− <literal>import &lt;nixpkgs&gt; { system = ..; platform = ..; crossSystem = ..; }</literal>.
280− Passing those two instead of <varname>localSystem</varname> is still supported for compatibility, but is discouraged.
281− Indeed, much of the inference we do for these parameters is motivated by compatibility as much as convenience.
282− </para>
419+ <para>
420+ Many sources (manual, wiki, etc) probably mention passing
421+ <varname>system</varname>, <varname>platform</varname>, along with the
422+ optional <varname>crossSystem</varname> to nixpkgs: <literal>import
423+ &lt;nixpkgs&gt; { system = ..; platform = ..; crossSystem = ..;
424+ }</literal>. Passing those two instead of <varname>localSystem</varname> is
425+ still supported for compatibility, but is discouraged. Indeed, much of the
426+ inference we do for these parameters is motivated by compatibility as much
427+ as convenience.
428+ </para>
283429 </note>
430+
284431 <para>
285− One would think that <varname>localSystem</varname> and <varname>crossSystem</varname> overlap horribly with the three <varname>*Platforms</varname> (<varname>buildPlatform</varname>, <varname>hostPlatform,</varname> and <varname>targetPlatform</varname>; see <varname>stage.nix</varname> or the manual).
286− Actually, those identifiers are purposefully not used here to draw a subtle but important distinction:
287− While the granularity of having 3 platforms is necessary to properly *build* packages, it is overkill for specifying the user's *intent* when making a build plan or package set.
288− A simple "build vs deploy" dichotomy is adequate: the sliding window principle described in the previous section shows how to interpolate between the these two "end points" to get the 3 platform triple for each bootstrapping stage.
289− That means for any package a given package set, even those not bound on the top level but only reachable via dependencies or <varname>buildPackages</varname>, the three platforms will be defined as one of <varname>localSystem</varname> or <varname>crossSystem</varname>, with the former replacing the latter as one traverses build-time dependencies.
290− A last simple difference then is <varname>crossSystem</varname> should be null when one doesn't want to cross-compile, while the <varname>*Platform</varname>s are always non-null.
291− <varname>localSystem</varname> is always non-null.
432+ One would think that <varname>localSystem</varname> and
433+ <varname>crossSystem</varname> overlap horribly with the three
434+ <varname>*Platforms</varname> (<varname>buildPlatform</varname>,
435+ <varname>hostPlatform,</varname> and <varname>targetPlatform</varname>; see
436+ <varname>stage.nix</varname> or the manual). Actually, those identifiers are
437+ purposefully not used here to draw a subtle but important distinction: While
438+ the granularity of having 3 platforms is necessary to properly *build*
439+ packages, it is overkill for specifying the user's *intent* when making a
440+ build plan or package set. A simple "build vs deploy" dichotomy is adequate:
441+ the sliding window principle described in the previous section shows how to
442+ interpolate between the these two "end points" to get the 3 platform triple
443+ for each bootstrapping stage. That means for any package a given package
444+ set, even those not bound on the top level but only reachable via
445+ dependencies or <varname>buildPackages</varname>, the three platforms will
446+ be defined as one of <varname>localSystem</varname> or
447+ <varname>crossSystem</varname>, with the former replacing the latter as one
448+ traverses build-time dependencies. A last simple difference then is
449+ <varname>crossSystem</varname> should be null when one doesn't want to
450+ cross-compile, while the <varname>*Platform</varname>s are always non-null.
451+ <varname>localSystem</varname> is always non-null.
292452 </para>
293−</section>
294−
453+ </section>
295454<!--============================================================-->
296−
297−<section xml:id="sec-cross-infra">
455+ <section xml:id="sec-cross-infra">
298456 <title>Cross-compilation infrastructure</title>
299− <para>To be written.</para>
300− <note><para>
301− If one explores nixpkgs, they will see derivations with names like <literal>gccCross</literal>.
302− Such <literal>*Cross</literal> derivations is a holdover from before we properly distinguished between the host and target platforms
303− —the derivation with "Cross" in the name covered the <literal>build = host != target</literal> case, while the other covered the <literal>host = target</literal>, with build platform the same or not based on whether one was using its <literal>.nativeDrv</literal> or <literal>.crossDrv</literal>.
304− This ugliness will disappear soon.
305− </para></note>
306−</section>
307457
458+ <para>
459+ To be written.
460+ </para>
461+
462+ <note>
463+ <para>
464+ If one explores nixpkgs, they will see derivations with names like
465+ <literal>gccCross</literal>. Such <literal>*Cross</literal> derivations is
466+ a holdover from before we properly distinguished between the host and
467+ target platforms —the derivation with "Cross" in the name covered the
468+ <literal>build = host != target</literal> case, while the other covered the
469+ <literal>host = target</literal>, with build platform the same or not based
470+ on whether one was using its <literal>.nativeDrv</literal> or
471+ <literal>.crossDrv</literal>. This ugliness will disappear soon.
472+ </para>
473+ </note>
474+ </section>
308475</chapter>
doc/default.nix+38−106
@@ -1,118 +1,50 @@
1+{ pkgs ? (import ./.. { }), nixpkgs ? { }}:
12let
2− pkgs = import ./.. { };
33 lib = pkgs.lib;
4− sources = lib.sourceFilesBySuffices ./. [".xml"];
5− sources-langs = ./languages-frameworks;
4+ locationsXml = import ./lib-function-locations.nix { inherit pkgs nixpkgs; };
65in
76pkgs.stdenv.mkDerivation {
87 name = "nixpkgs-manual";
98
10−
11− buildInputs = with pkgs; [ pandoc libxml2 libxslt zip ];
12−
13− xsltFlags = ''
14− --param section.autolabel 1
15− --param section.label.includes.component.label 1
16− --param html.stylesheet 'style.css'
17− --param xref.with.number.and.title 1
18− --param toc.section.depth 3
19− --param admon.style '''
20− --param callout.graphics.extension '.gif'
9+ buildInputs = with pkgs; [ pandoc libxml2 libxslt zip jing xmlformat ];
10+
11+ src = ./.;
12+
13+ # Hacking on these variables? Make sure to close and open
14+ # nix-shell between each test, maybe even:
15+ # $ nix-shell --run "make clean all"
16+ # otherwise they won't reapply :)
17+ HIGHLIGHTJS = pkgs.documentation-highlighter;
18+ XSL = "${pkgs.docbook_xsl_ns}/xml/xsl";
19+ RNG = "${pkgs.docbook5}/xml/rng/docbook/docbook.rng";
20+ XMLFORMAT_CONFIG = ../nixos/doc/xmlformat.conf;
21+ xsltFlags = lib.concatStringsSep " " [
22+ "--param section.autolabel 1"
23+ "--param section.label.includes.component.label 1"
24+ "--stringparam html.stylesheet 'style.css overrides.css highlightjs/mono-blue.css'"
25+ "--stringparam html.script './highlightjs/highlight.pack.js ./highlightjs/loader.js'"
26+ "--param xref.with.number.and.title 1"
27+ "--param toc.section.depth 3"
28+ "--stringparam admon.style ''"
29+ "--stringparam callout.graphics.extension .svg"
30+ ];
31+
32+ postPatch = ''
33+ rm -rf ./functions/library/locations.xml
34+ ln -s ${locationsXml} ./functions/library/locations.xml
35+ echo ${lib.version} > .version
2136 '';
2237
38+ installPhase = ''
39+ dest="$out/share/doc/nixpkgs"
40+ mkdir -p "$(dirname "$dest")"
41+ mv out/html "$dest"
42+ mv "$dest/index.html" "$dest/manual.html"
2343
24− buildCommand = let toDocbook = { useChapters ? false, inputFile, outputFile }:
25− let
26− extraHeader = lib.optionalString (!useChapters)
27− ''xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" '';
28− in ''
29− {
30− pandoc '${inputFile}' -w docbook+smart ${lib.optionalString useChapters "--top-level-division=chapter"} \
31− -f markdown+smart \
32− | sed -e 's|<ulink url=|<link xlink:href=|' \
33− -e 's|</ulink>|</link>|' \
34− -e 's|<sect. id=|<section xml:id=|' \
35− -e 's|</sect[0-9]>|</section>|' \
36− -e '1s| id=| xml:id=|' \
37− -e '1s|\(<[^ ]* \)|\1${extraHeader}|'
38− } > '${outputFile}'
39− '';
40− in
41−
42− ''
43− ln -s '${sources}/'*.xml .
44− mkdir ./languages-frameworks
45− cp -s '${sources-langs}'/* ./languages-frameworks
46− ''
47− + toDocbook {
48− inputFile = ./introduction.md;
49− outputFile = "introduction.xml";
50− useChapters = true;
51− }
52− + toDocbook {
53− inputFile = ./shell.md;
54− outputFile = "shell.xml";
55− }
56− + toDocbook {
57− inputFile = ./languages-frameworks/python.md;
58− outputFile = "./languages-frameworks/python.xml";
59− }
60− + toDocbook {
61− inputFile = ./languages-frameworks/haskell.md;
62− outputFile = "./languages-frameworks/haskell.xml";
63− }
64− + toDocbook {
65− inputFile = ../pkgs/development/idris-modules/README.md;
66− outputFile = "languages-frameworks/idris.xml";
67− }
68− + toDocbook {
69− inputFile = ../pkgs/development/node-packages/README.md;
70− outputFile = "languages-frameworks/node.xml";
71− }
72− + toDocbook {
73− inputFile = ../pkgs/development/r-modules/README.md;
74− outputFile = "languages-frameworks/r.xml";
75− }
76− + toDocbook {
77− inputFile = ./languages-frameworks/rust.md;
78− outputFile = "./languages-frameworks/rust.xml";
79− }
80− + toDocbook {
81− inputFile = ./languages-frameworks/vim.md;
82− outputFile = "./languages-frameworks/vim.xml";
83− }
84− + ''
85− echo ${lib.nixpkgsVersion} > .version
86−
87− # validate against relaxng schema
88− xmllint --nonet --xinclude --noxincludenode manual.xml --output manual-full.xml
89− ${pkgs.jing}/bin/jing ${pkgs.docbook5}/xml/rng/docbook/docbook.rng manual-full.xml
90−
91− dst=$out/share/doc/nixpkgs
92− mkdir -p $dst
93− xsltproc $xsltFlags --nonet --xinclude \
94− --output $dst/manual.html \
95− ${pkgs.docbook5_xsl}/xml/xsl/docbook/xhtml/docbook.xsl \
96− ./manual.xml
97−
98− cp ${./style.css} $dst/style.css
99−
100− mkdir -p $dst/images/callouts
101− cp "${pkgs.docbook5_xsl}/xml/xsl/docbook/images/callouts/"*.gif $dst/images/callouts/
102−
103− mkdir -p $out/nix-support
104− echo "doc manual $dst manual.html" >> $out/nix-support/hydra-build-products
105−
106− xsltproc $xsltFlags --nonet --xinclude \
107− --output $dst/epub/ \
108− ${pkgs.docbook5_xsl}/xml/xsl/docbook/epub/docbook.xsl \
109− ./manual.xml
44+ mv out/epub/manual.epub "$dest/nixpkgs-manual.epub"
11045
111− cp -r $dst/images $dst/epub/OEBPS
112− echo "application/epub+zip" > mimetype
113− manual="$dst/nixpkgs-manual.epub"
114− zip -0Xq "$manual" mimetype
115− cd $dst/epub && zip -Xr9D "$manual" *
116− rm -rf $dst/epub
46+ mkdir -p $out/nix-support/
47+ echo "doc manual $dest manual.html" >> $out/nix-support/hydra-build-products
48+ echo "doc manual $dest nixpkgs-manual.epub" >> $out/nix-support/hydra-build-products
11749 '';
11850}
doc/functions.xml+15−704
@@ -1,706 +1,17 @@
11<chapter xmlns="http://docbook.org/ns/docbook"
2− xmlns:xlink="http://www.w3.org/1999/xlink"
3− xml:id="chap-functions">
4−
5−<title>Functions reference</title>
6−
7−<para>
8− The nixpkgs repository has several utility functions to manipulate Nix expressions.
9−</para>
10−
11−<section xml:id="sec-overrides">
12− <title>Overriding</title>
13−
14− <para>
15− Sometimes one wants to override parts of
16− <literal>nixpkgs</literal>, e.g. derivation attributes, the results of
17− derivations or even the whole package set.
18− </para>
19−
20− <section xml:id="sec-pkg-override">
21− <title>&lt;pkg&gt;.override</title>
22−
23− <para>
24− The function <varname>override</varname> is usually available for all the
25− derivations in the nixpkgs expression (<varname>pkgs</varname>).
26− </para>
27− <para>
28− It is used to override the arguments passed to a function.
29− </para>
30− <para>
31− Example usages:
32−
33− <programlisting>pkgs.foo.override { arg1 = val1; arg2 = val2; ... }</programlisting>
34− <programlisting>import pkgs.path { overlays = [ (self: super: {
35− foo = super.foo.override { barSupport = true ; };
36− })]};</programlisting>
37− <programlisting>mypkg = pkgs.callPackage ./mypkg.nix {
38− mydep = pkgs.mydep.override { ... };
39− }</programlisting>
40− </para>
41−
42− <para>
43− In the first example, <varname>pkgs.foo</varname> is the result of a function call
44− with some default arguments, usually a derivation.
45− Using <varname>pkgs.foo.override</varname> will call the same function with
46− the given new arguments.
47− </para>
48−
49− </section>
50−
51− <section xml:id="sec-pkg-overrideAttrs">
52− <title>&lt;pkg&gt;.overrideAttrs</title>
53−
54− <para>
55− The function <varname>overrideAttrs</varname> allows overriding the
56− attribute set passed to a <varname>stdenv.mkDerivation</varname> call,
57− producing a new derivation based on the original one.
58− This function is available on all derivations produced by the
59− <varname>stdenv.mkDerivation</varname> function, which is most packages
60− in the nixpkgs expression <varname>pkgs</varname>.
61− </para>
62−
63− <para>
64− Example usage:
65−
66− <programlisting>helloWithDebug = pkgs.hello.overrideAttrs (oldAttrs: rec {
67− separateDebugInfo = true;
68− });</programlisting>
69− </para>
70−
71− <para>
72− In the above example, the <varname>separateDebugInfo</varname> attribute is
73− overridden to be true, thus building debug info for
74− <varname>helloWithDebug</varname>, while all other attributes will be
75− retained from the original <varname>hello</varname> package.
76− </para>
77−
78− <para>
79− The argument <varname>oldAttrs</varname> is conventionally used to refer to
80− the attr set originally passed to <varname>stdenv.mkDerivation</varname>.
81− </para>
82−
83− <note>
84− <para>
85− Note that <varname>separateDebugInfo</varname> is processed only by the
86− <varname>stdenv.mkDerivation</varname> function, not the generated, raw
87− Nix derivation. Thus, using <varname>overrideDerivation</varname> will
88− not work in this case, as it overrides only the attributes of the final
89− derivation. It is for this reason that <varname>overrideAttrs</varname>
90− should be preferred in (almost) all cases to
91− <varname>overrideDerivation</varname>, i.e. to allow using
92− <varname>sdenv.mkDerivation</varname> to process input arguments, as well
93− as the fact that it is easier to use (you can use the same attribute
94− names you see in your Nix code, instead of the ones generated (e.g.
95− <varname>buildInputs</varname> vs <varname>nativeBuildInputs</varname>,
96− and involves less typing.
97− </para>
98− </note>
99−
100− </section>
101−
102−
103− <section xml:id="sec-pkg-overrideDerivation">
104− <title>&lt;pkg&gt;.overrideDerivation</title>
105−
106− <warning>
107− <para>You should prefer <varname>overrideAttrs</varname> in almost all
108− cases, see its documentation for the reasons why.
109− <varname>overrideDerivation</varname> is not deprecated and will continue
110− to work, but is less nice to use and does not have as many abilities as
111− <varname>overrideAttrs</varname>.
112− </para>
113− </warning>
114−
115− <warning>
116− <para>Do not use this function in Nixpkgs as it evaluates a Derivation
117− before modifying it, which breaks package abstraction and removes
118− error-checking of function arguments. In addition, this
119− evaluation-per-function application incurs a performance penalty,
120− which can become a problem if many overrides are used.
121− It is only intended for ad-hoc customisation, such as in
122− <filename>~/.config/nixpkgs/config.nix</filename>.
123− </para>
124− </warning>
125−
126− <para>
127− The function <varname>overrideDerivation</varname> creates a new derivation
128− based on an existing one by overriding the original's attributes with
129− the attribute set produced by the specified function.
130− This function is available on all
131− derivations defined using the <varname>makeOverridable</varname> function.
132− Most standard derivation-producing functions, such as
133− <varname>stdenv.mkDerivation</varname>, are defined using this
134− function, which means most packages in the nixpkgs expression,
135− <varname>pkgs</varname>, have this function.
136− </para>
137−
138− <para>
139− Example usage:
140−
141− <programlisting>mySed = pkgs.gnused.overrideDerivation (oldAttrs: {
142− name = "sed-4.2.2-pre";
143− src = fetchurl {
144− url = ftp://alpha.gnu.org/gnu/sed/sed-4.2.2-pre.tar.bz2;
145− sha256 = "11nq06d131y4wmf3drm0yk502d2xc6n5qy82cg88rb9nqd2lj41k";
146− };
147− patches = [];
148− });</programlisting>
149− </para>
150−
151− <para>
152− In the above example, the <varname>name</varname>, <varname>src</varname>,
153− and <varname>patches</varname> of the derivation will be overridden, while
154− all other attributes will be retained from the original derivation.
155− </para>
156−
157− <para>
158− The argument <varname>oldAttrs</varname> is used to refer to the attribute set of
159− the original derivation.
160− </para>
161−
162− <note>
163− <para>
164− A package's attributes are evaluated *before* being modified by
165− the <varname>overrideDerivation</varname> function.
166− For example, the <varname>name</varname> attribute reference
167− in <varname>url = "mirror://gnu/hello/${name}.tar.gz";</varname>
168− is filled-in *before* the <varname>overrideDerivation</varname> function
169− modifies the attribute set. This means that overriding the
170− <varname>name</varname> attribute, in this example, *will not* change the
171− value of the <varname>url</varname> attribute. Instead, we need to override
172− both the <varname>name</varname> *and* <varname>url</varname> attributes.
173− </para>
174− </note>
175−
176− </section>
177−
178− <section xml:id="sec-lib-makeOverridable">
179− <title>lib.makeOverridable</title>
180−
181− <para>
182− The function <varname>lib.makeOverridable</varname> is used to make the result
183− of a function easily customizable. This utility only makes sense for functions
184− that accept an argument set and return an attribute set.
185− </para>
186−
187− <para>
188− Example usage:
189−
190− <programlisting>f = { a, b }: { result = a+b; }
191− c = lib.makeOverridable f { a = 1; b = 2; }</programlisting>
192−
193− </para>
194−
195− <para>
196− The variable <varname>c</varname> is the value of the <varname>f</varname> function
197− applied with some default arguments. Hence the value of <varname>c.result</varname>
198− is <literal>3</literal>, in this example.
199− </para>
200−
201− <para>
202− The variable <varname>c</varname> however also has some additional functions, like
203− <link linkend="sec-pkg-override">c.override</link> which can be used to
204− override the default arguments. In this example the value of
205− <varname>(c.override { a = 4; }).result</varname> is 6.
206− </para>
207−
208− </section>
209−
210−</section>
211−
212−<section xml:id="sec-generators">
213− <title>Generators</title>
214−
215− <para>
216− Generators are functions that create file formats from nix
217− data structures, e. g. for configuration files.
218− There are generators available for: <literal>INI</literal>,
219− <literal>JSON</literal> and <literal>YAML</literal>
220− </para>
221−
222− <para>
223− All generators follow a similar call interface: <code>generatorName
224− configFunctions data</code>, where <literal>configFunctions</literal> is a
225− set of user-defined functions that format variable parts of the content.
226− They each have common defaults, so often they do not need to be set
227− manually. An example is <code>mkSectionName ? (name: libStr.escape [ "[" "]"
228− ] name)</code> from the <literal>INI</literal> generator. It gets the name
229− of a section and returns a sanitized name. The default
230− <literal>mkSectionName</literal> escapes <literal>[</literal> and
231− <literal>]</literal> with a backslash.
232− </para>
233−
234− <note><para>Nix store paths can be converted to strings by enclosing a
235− derivation attribute like so: <code>"${drv}"</code>.</para></note>
236−
237− <para>
238− Detailed documentation for each generator can be found in
239− <literal>lib/generators.nix</literal>.
240− </para>
241−
242−</section>
243−
244−
245−<section xml:id="sec-fhs-environments">
246− <title>buildFHSUserEnv</title>
247−
248− <para>
249− <function>buildFHSUserEnv</function> provides a way to build and run
250− FHS-compatible lightweight sandboxes. It creates an isolated root with
251− bound <filename>/nix/store</filename>, so its footprint in terms of disk
252− space needed is quite small. This allows one to run software which is hard or
253− unfeasible to patch for NixOS -- 3rd-party source trees with FHS assumptions,
254− games distributed as tarballs, software with integrity checking and/or external
255− self-updated binaries. It uses Linux namespaces feature to create
256− temporary lightweight environments which are destroyed after all child
257− processes exit, without root user rights requirement. Accepted arguments are:
258− </para>
259−
260− <variablelist>
261− <varlistentry>
262− <term><literal>name</literal></term>
263−
264− <listitem><para>Environment name.</para></listitem>
265− </varlistentry>
266−
267− <varlistentry>
268− <term><literal>targetPkgs</literal></term>
269−
270− <listitem><para>Packages to be installed for the main host's architecture
271− (i.e. x86_64 on x86_64 installations). Along with libraries binaries are also
272− installed.</para></listitem>
273− </varlistentry>
274−
275− <varlistentry>
276− <term><literal>multiPkgs</literal></term>
277−
278− <listitem><para>Packages to be installed for all architectures supported by
279− a host (i.e. i686 and x86_64 on x86_64 installations). Only libraries are
280− installed by default.</para></listitem>
281− </varlistentry>
282−
283− <varlistentry>
284− <term><literal>extraBuildCommands</literal></term>
285−
286− <listitem><para>Additional commands to be executed for finalizing the
287− directory structure.</para></listitem>
288− </varlistentry>
289−
290− <varlistentry>
291− <term><literal>extraBuildCommandsMulti</literal></term>
292−
293− <listitem><para>Like <literal>extraBuildCommands</literal>, but
294− executed only on multilib architectures.</para></listitem>
295− </varlistentry>
296−
297− <varlistentry>
298− <term><literal>extraOutputsToInstall</literal></term>
299−
300− <listitem><para>Additional derivation outputs to be linked for both
301− target and multi-architecture packages.</para></listitem>
302− </varlistentry>
303−
304− <varlistentry>
305− <term><literal>extraInstallCommands</literal></term>
306−
307− <listitem><para>Additional commands to be executed for finalizing the
308− derivation with runner script.</para></listitem>
309− </varlistentry>
310−
311− <varlistentry>
312− <term><literal>runScript</literal></term>
313−
314− <listitem><para>A command that would be executed inside the sandbox and
315− passed all the command line arguments. It defaults to
316− <literal>bash</literal>.</para></listitem>
317− </varlistentry>
318− </variablelist>
319−
320− <para>
321− One can create a simple environment using a <literal>shell.nix</literal>
322− like that:
323− </para>
324−
325−<programlisting><![CDATA[
326−{ pkgs ? import <nixpkgs> {} }:
327−
328−(pkgs.buildFHSUserEnv {
329− name = "simple-x11-env";
330− targetPkgs = pkgs: (with pkgs;
331− [ udev
332− alsaLib
333− ]) ++ (with pkgs.xorg;
334− [ libX11
335− libXcursor
336− libXrandr
337− ]);
338− multiPkgs = pkgs: (with pkgs;
339− [ udev
340− alsaLib
341− ]);
342− runScript = "bash";
343−}).env
344−]]></programlisting>
345−
346− <para>
347− Running <literal>nix-shell</literal> would then drop you into a shell with
348− these libraries and binaries available. You can use this to run
349− closed-source applications which expect FHS structure without hassles:
350− simply change <literal>runScript</literal> to the application path,
351− e.g. <filename>./bin/start.sh</filename> -- relative paths are supported.
352− </para>
353−</section>
354−
355−<section xml:id="sec-pkgs-dockerTools">
356−<title>pkgs.dockerTools</title>
357−
358−<para>
359− <varname>pkgs.dockerTools</varname> is a set of functions for creating and
360− manipulating Docker images according to the
361− <link xlink:href="https://github.com/moby/moby/blob/master/image/spec/v1.2.md#docker-image-specification-v120">
362− Docker Image Specification v1.2.0
363− </link>. Docker itself is not used to perform any of the operations done by these
364− functions.
365−</para>
366−
367−<warning>
368− <para>
369− The <varname>dockerTools</varname> API is unstable and may be subject to
370− backwards-incompatible changes in the future.
371− </para>
372−</warning>
373−
374−<section xml:id="ssec-pkgs-dockerTools-buildImage">
375− <title>buildImage</title>
376−
377− <para>
378− This function is analogous to the <command>docker build</command> command,
379− in that can used to build a Docker-compatible repository tarball containing
380− a single image with one or multiple layers. As such, the result
381− is suitable for being loaded in Docker with <command>docker load</command>.
382− </para>
383−
384− <para>
385− The parameters of <varname>buildImage</varname> with relative example values are
386− described below:
387− </para>
388−
389− <example xml:id='ex-dockerTools-buildImage'><title>Docker build</title>
390− <programlisting>
391− buildImage {
392− name = "redis"; <co xml:id='ex-dockerTools-buildImage-1' />
393− tag = "latest"; <co xml:id='ex-dockerTools-buildImage-2' />
394−
395− fromImage = someBaseImage; <co xml:id='ex-dockerTools-buildImage-3' />
396− fromImageName = null; <co xml:id='ex-dockerTools-buildImage-4' />
397− fromImageTag = "latest"; <co xml:id='ex-dockerTools-buildImage-5' />
398−
399− contents = pkgs.redis; <co xml:id='ex-dockerTools-buildImage-6' />
400− runAsRoot = '' <co xml:id='ex-dockerTools-buildImage-runAsRoot' />
401− #!${stdenv.shell}
402− mkdir -p /data
403− '';
404−
405− config = { <co xml:id='ex-dockerTools-buildImage-8' />
406− Cmd = [ "/bin/redis-server" ];
407− WorkingDir = "/data";
408− Volumes = {
409− "/data" = {};
410− };
411− };
412− }
413− </programlisting>
414− </example>
415−
416− <para>The above example will build a Docker image <literal>redis/latest</literal>
417− from the given base image. Loading and running this image in Docker results in
418− <literal>redis-server</literal> being started automatically.
419− </para>
420−
421− <calloutlist>
422− <callout arearefs='ex-dockerTools-buildImage-1'>
423− <para>
424− <varname>name</varname> specifies the name of the resulting image.
425− This is the only required argument for <varname>buildImage</varname>.
426− </para>
427− </callout>
428−
429− <callout arearefs='ex-dockerTools-buildImage-2'>
430− <para>
431− <varname>tag</varname> specifies the tag of the resulting image.
432− By default it's <literal>latest</literal>.
433− </para>
434− </callout>
435−
436− <callout arearefs='ex-dockerTools-buildImage-3'>
437− <para>
438− <varname>fromImage</varname> is the repository tarball containing the base image.
439− It must be a valid Docker image, such as exported by <command>docker save</command>.
440− By default it's <literal>null</literal>, which can be seen as equivalent
441− to <literal>FROM scratch</literal> of a <filename>Dockerfile</filename>.
442− </para>
443− </callout>
444−
445− <callout arearefs='ex-dockerTools-buildImage-4'>
446− <para>
447− <varname>fromImageName</varname> can be used to further specify
448− the base image within the repository, in case it contains multiple images.
449− By default it's <literal>null</literal>, in which case
450− <varname>buildImage</varname> will peek the first image available
451− in the repository.
452− </para>
453− </callout>
454−
455− <callout arearefs='ex-dockerTools-buildImage-5'>
456− <para>
457− <varname>fromImageTag</varname> can be used to further specify the tag
458− of the base image within the repository, in case an image contains multiple tags.
459− By default it's <literal>null</literal>, in which case
460− <varname>buildImage</varname> will peek the first tag available for the base image.
461− </para>
462− </callout>
463−
464− <callout arearefs='ex-dockerTools-buildImage-6'>
465− <para>
466− <varname>contents</varname> is a derivation that will be copied in the new
467− layer of the resulting image. This can be similarly seen as
468− <command>ADD contents/ /</command> in a <filename>Dockerfile</filename>.
469− By default it's <literal>null</literal>.
470− </para>
471− </callout>
472−
473− <callout arearefs='ex-dockerTools-buildImage-runAsRoot'>
474− <para>
475− <varname>runAsRoot</varname> is a bash script that will run as root
476− in an environment that overlays the existing layers of the base image with
477− the new resulting layer, including the previously copied
478− <varname>contents</varname> derivation.
479− This can be similarly seen as
480− <command>RUN ...</command> in a <filename>Dockerfile</filename>.
481−
482− <note>
483− <para>
484− Using this parameter requires the <literal>kvm</literal>
485− device to be available.
486− </para>
487− </note>
488− </para>
489− </callout>
490−
491− <callout arearefs='ex-dockerTools-buildImage-8'>
492− <para>
493− <varname>config</varname> is used to specify the configuration of the
494− containers that will be started off the built image in Docker.
495− The available options are listed in the
496− <link xlink:href="https://github.com/moby/moby/blob/master/image/spec/v1.2.md#image-json-field-descriptions">
497− Docker Image Specification v1.2.0
498− </link>.
499− </para>
500− </callout>
501−
502− </calloutlist>
503−
504− <para>
505− After the new layer has been created, its closure
506− (to which <varname>contents</varname>, <varname>config</varname> and
507− <varname>runAsRoot</varname> contribute) will be copied in the layer itself.
508− Only new dependencies that are not already in the existing layers will be copied.
509− </para>
510−
511− <para>
512− At the end of the process, only one new single layer will be produced and
513− added to the resulting image.
514− </para>
515−
516− <para>
517− The resulting repository will only list the single image
518− <varname>image/tag</varname>. In the case of <xref linkend='ex-dockerTools-buildImage'/>
519− it would be <varname>redis/latest</varname>.
520− </para>
521−
522− <para>
523− It is possible to inspect the arguments with which an image was built
524− using its <varname>buildArgs</varname> attribute.
525− </para>
526−
527−
528−
529− <note>
530− <para>
531− If you see errors similar to <literal>getProtocolByName: does not exist (no such protocol name: tcp)</literal>
532− you may need to add <literal>pkgs.iana-etc</literal> to <varname>contents</varname>.
533− </para>
534− </note>
535−
536− <note>
537− <para>
538− If you see errors similar to <literal>Error_Protocol ("certificate has unknown CA",True,UnknownCa)</literal>
539− you may need to add <literal>pkgs.cacert</literal> to <varname>contents</varname>.
540− </para>
541− </note>
542−
543−</section>
544−
545−<section xml:id="ssec-pkgs-dockerTools-fetchFromRegistry">
546− <title>pullImage</title>
547−
548− <para>
549− This function is analogous to the <command>docker pull</command> command,
550− in that can be used to fetch a Docker image from a Docker registry.
551− Currently only registry <literal>v1</literal> is supported.
552− By default <link xlink:href="https://hub.docker.com/">Docker Hub</link>
553− is used to pull images.
554− </para>
555−
556− <para>
557− Its parameters are described in the example below:
558− </para>
559−
560− <example xml:id='ex-dockerTools-pullImage'><title>Docker pull</title>
561− <programlisting>
562− pullImage {
563− imageName = "debian"; <co xml:id='ex-dockerTools-pullImage-1' />
564− imageTag = "jessie"; <co xml:id='ex-dockerTools-pullImage-2' />
565− imageId = null; <co xml:id='ex-dockerTools-pullImage-3' />
566− sha256 = "1bhw5hkz6chrnrih0ymjbmn69hyfriza2lr550xyvpdrnbzr4gk2"; <co xml:id='ex-dockerTools-pullImage-4' />
567−
568− indexUrl = "https://index.docker.io"; <co xml:id='ex-dockerTools-pullImage-5' />
569− registryVersion = "v1";
570− }
571− </programlisting>
572− </example>
573−
574− <calloutlist>
575− <callout arearefs='ex-dockerTools-pullImage-1'>
576− <para>
577− <varname>imageName</varname> specifies the name of the image to be downloaded,
578− which can also include the registry namespace (e.g. <literal>library/debian</literal>).
579− This argument is required.
580− </para>
581− </callout>
582−
583− <callout arearefs='ex-dockerTools-pullImage-2'>
584− <para>
585− <varname>imageTag</varname> specifies the tag of the image to be downloaded.
586− By default it's <literal>latest</literal>.
587− </para>
588− </callout>
589−
590− <callout arearefs='ex-dockerTools-pullImage-3'>
591− <para>
592− <varname>imageId</varname>, if specified this exact image will be fetched, instead
593− of <varname>imageName/imageTag</varname>. However, the resulting repository
594− will still be named <varname>imageName/imageTag</varname>.
595− By default it's <literal>null</literal>.
596− </para>
597− </callout>
598−
599− <callout arearefs='ex-dockerTools-pullImage-4'>
600− <para>
601− <varname>sha256</varname> is the checksum of the whole fetched image.
602− This argument is required.
603− </para>
604−
605− <note>
606− <para>The checksum is computed on the unpacked directory, not on the final tarball.</para>
607− </note>
608−
609− </callout>
610−
611− <callout arearefs='ex-dockerTools-pullImage-5'>
612− <para>
613− In the above example the default values are shown for the variables
614− <varname>indexUrl</varname> and <varname>registryVersion</varname>.
615− Hence by default the Docker.io registry is used to pull the images.
616− </para>
617− </callout>
618− </calloutlist>
619−
620−</section>
621−
622−<section xml:id="ssec-pkgs-dockerTools-exportImage">
623− <title>exportImage</title>
624−
625− <para>
626− This function is analogous to the <command>docker export</command> command,
627− in that can used to flatten a Docker image that contains multiple layers.
628− It is in fact the result of the merge of all the layers of the image.
629− As such, the result is suitable for being imported in Docker
630− with <command>docker import</command>.
631− </para>
632−
633− <note>
634− <para>
635− Using this function requires the <literal>kvm</literal>
636− device to be available.
637− </para>
638− </note>
639−
640− <para>
641− The parameters of <varname>exportImage</varname> are the following:
642− </para>
643−
644− <example xml:id='ex-dockerTools-exportImage'><title>Docker export</title>
645− <programlisting>
646− exportImage {
647− fromImage = someLayeredImage;
648− fromImageName = null;
649− fromImageTag = null;
650−
651− name = someLayeredImage.name;
652− }
653− </programlisting>
654− </example>
655−
656− <para>
657− The parameters relative to the base image have the same synopsis as
658− described in <xref linkend='ssec-pkgs-dockerTools-buildImage'/>, except that
659− <varname>fromImage</varname> is the only required argument in this case.
660− </para>
661−
662− <para>
663− The <varname>name</varname> argument is the name of the derivation output,
664− which defaults to <varname>fromImage.name</varname>.
665− </para>
666−</section>
667−
668−<section xml:id="ssec-pkgs-dockerTools-shadowSetup">
669− <title>shadowSetup</title>
670−
671− <para>
672− This constant string is a helper for setting up the base files for managing
673− users and groups, only if such files don't exist already.
674− It is suitable for being used in a
675− <varname>runAsRoot</varname> <xref linkend='ex-dockerTools-buildImage-runAsRoot'/> script for cases like
676− in the example below:
677− </para>
678−
679− <example xml:id='ex-dockerTools-shadowSetup'><title>Shadow base files</title>
680− <programlisting>
681− buildImage {
682− name = "shadow-basic";
683−
684− runAsRoot = ''
685− #!${stdenv.shell}
686− ${shadowSetup}
687− groupadd -r redis
688− useradd -r -g redis redis
689− mkdir /data
690− chown redis:redis /data
691− '';
692− }
693− </programlisting>
694− </example>
695−
696− <para>
697− Creating base files like <literal>/etc/passwd</literal> or
698− <literal>/etc/login.defs</literal> are necessary for shadow-utils to
699− manipulate users and groups.
700− </para>
701−
702−</section>
703−
704−</section>
705−
2+ xmlns:xlink="http://www.w3.org/1999/xlink"
3+ xmlns:xi="http://www.w3.org/2001/XInclude"
4+ xml:id="chap-functions">
5+ <title>Functions reference</title>
6+ <para>
7+ The nixpkgs repository has several utility functions to manipulate Nix
8+ expressions.
9+ </para>
10+ <xi:include href="functions/library.xml" />
11+ <xi:include href="functions/overrides.xml" />
12+ <xi:include href="functions/generators.xml" />
13+ <xi:include href="functions/debug.xml" />
14+ <xi:include href="functions/fhs-environments.xml" />
15+ <xi:include href="functions/shell.xml" />
16+ <xi:include href="functions/dockertools.xml" />
70617</chapter>
doc/functions/debug.xmlnew file+21
@@ -0,0 +1,21 @@
1+<section xmlns="http://docbook.org/ns/docbook"
2+ xmlns:xlink="http://www.w3.org/1999/xlink"
3+ xmlns:xi="http://www.w3.org/2001/XInclude"
4+ xml:id="sec-debug">
5+ <title>Debugging Nix Expressions</title>
6+
7+ <para>
8+ Nix is a unityped, dynamic language, this means every value can potentially
9+ appear anywhere. Since it is also non-strict, evaluation order and what
10+ ultimately is evaluated might surprise you. Therefore it is important to be
11+ able to debug nix expressions.
12+ </para>
13+
14+ <para>
15+ In the <literal>lib/debug.nix</literal> file you will find a number of
16+ functions that help (pretty-)printing values while evaluation is runnnig. You
17+ can even specify how deep these values should be printed recursively, and
18+ transform them on the fly. Please consult the docstrings in
19+ <literal>lib/debug.nix</literal> for usage information.
20+ </para>
21+</section>
doc/functions/dockertools.xmlnew file+564
@@ -0,0 +1,564 @@
1+<section xmlns="http://docbook.org/ns/docbook"
2+ xmlns:xlink="http://www.w3.org/1999/xlink"
3+ xmlns:xi="http://www.w3.org/2001/XInclude"
4+ xml:id="sec-pkgs-dockerTools">
5+ <title>pkgs.dockerTools</title>
6+
7+ <para>
8+ <varname>pkgs.dockerTools</varname> is a set of functions for creating and
9+ manipulating Docker images according to the
10+ <link xlink:href="https://github.com/moby/moby/blob/master/image/spec/v1.2.md#docker-image-specification-v120">
11+ Docker Image Specification v1.2.0 </link>. Docker itself is not used to
12+ perform any of the operations done by these functions.
13+ </para>
14+
15+ <warning>
16+ <para>
17+ The <varname>dockerTools</varname> API is unstable and may be subject to
18+ backwards-incompatible changes in the future.
19+ </para>
20+ </warning>
21+
22+ <section xml:id="ssec-pkgs-dockerTools-buildImage">
23+ <title>buildImage</title>
24+
25+ <para>
26+ This function is analogous to the <command>docker build</command> command,
27+ in that can used to build a Docker-compatible repository tarball containing
28+ a single image with one or multiple layers. As such, the result is suitable
29+ for being loaded in Docker with <command>docker load</command>.
30+ </para>
31+
32+ <para>
33+ The parameters of <varname>buildImage</varname> with relative example values
34+ are described below:
35+ </para>
36+
37+ <example xml:id='ex-dockerTools-buildImage'>
38+ <title>Docker build</title>
39+<programlisting>
40+buildImage {
41+ name = "redis"; <co xml:id='ex-dockerTools-buildImage-1' />
42+ tag = "latest"; <co xml:id='ex-dockerTools-buildImage-2' />
43+
44+ fromImage = someBaseImage; <co xml:id='ex-dockerTools-buildImage-3' />
45+ fromImageName = null; <co xml:id='ex-dockerTools-buildImage-4' />
46+ fromImageTag = "latest"; <co xml:id='ex-dockerTools-buildImage-5' />
47+
48+ contents = pkgs.redis; <co xml:id='ex-dockerTools-buildImage-6' />
49+ runAsRoot = '' <co xml:id='ex-dockerTools-buildImage-runAsRoot' />
50+ #!${stdenv.shell}
51+ mkdir -p /data
52+ '';
53+
54+ config = { <co xml:id='ex-dockerTools-buildImage-8' />
55+ Cmd = [ "/bin/redis-server" ];
56+ WorkingDir = "/data";
57+ Volumes = {
58+ "/data" = {};
59+ };
60+ };
61+}
62+</programlisting>
63+ </example>
64+
65+ <para>
66+ The above example will build a Docker image <literal>redis/latest</literal>
67+ from the given base image. Loading and running this image in Docker results
68+ in <literal>redis-server</literal> being started automatically.
69+ </para>
70+
71+ <calloutlist>
72+ <callout arearefs='ex-dockerTools-buildImage-1'>
73+ <para>
74+ <varname>name</varname> specifies the name of the resulting image. This is
75+ the only required argument for <varname>buildImage</varname>.
76+ </para>
77+ </callout>
78+ <callout arearefs='ex-dockerTools-buildImage-2'>
79+ <para>
80+ <varname>tag</varname> specifies the tag of the resulting image. By
81+ default it's <literal>null</literal>, which indicates that the nix output
82+ hash will be used as tag.
83+ </para>
84+ </callout>
85+ <callout arearefs='ex-dockerTools-buildImage-3'>
86+ <para>
87+ <varname>fromImage</varname> is the repository tarball containing the base
88+ image. It must be a valid Docker image, such as exported by
89+ <command>docker save</command>. By default it's <literal>null</literal>,
90+ which can be seen as equivalent to <literal>FROM scratch</literal> of a
91+ <filename>Dockerfile</filename>.
92+ </para>
93+ </callout>
94+ <callout arearefs='ex-dockerTools-buildImage-4'>
95+ <para>
96+ <varname>fromImageName</varname> can be used to further specify the base
97+ image within the repository, in case it contains multiple images. By
98+ default it's <literal>null</literal>, in which case
99+ <varname>buildImage</varname> will peek the first image available in the
100+ repository.
101+ </para>
102+ </callout>
103+ <callout arearefs='ex-dockerTools-buildImage-5'>
104+ <para>
105+ <varname>fromImageTag</varname> can be used to further specify the tag of
106+ the base image within the repository, in case an image contains multiple
107+ tags. By default it's <literal>null</literal>, in which case
108+ <varname>buildImage</varname> will peek the first tag available for the
109+ base image.
110+ </para>
111+ </callout>
112+ <callout arearefs='ex-dockerTools-buildImage-6'>
113+ <para>
114+ <varname>contents</varname> is a derivation that will be copied in the new
115+ layer of the resulting image. This can be similarly seen as <command>ADD
116+ contents/ /</command> in a <filename>Dockerfile</filename>. By default
117+ it's <literal>null</literal>.
118+ </para>
119+ </callout>
120+ <callout arearefs='ex-dockerTools-buildImage-runAsRoot'>
121+ <para>
122+ <varname>runAsRoot</varname> is a bash script that will run as root in an
123+ environment that overlays the existing layers of the base image with the
124+ new resulting layer, including the previously copied
125+ <varname>contents</varname> derivation. This can be similarly seen as
126+ <command>RUN ...</command> in a <filename>Dockerfile</filename>.
127+ <note>
128+ <para>
129+ Using this parameter requires the <literal>kvm</literal> device to be
130+ available.
131+ </para>
132+ </note>
133+ </para>
134+ </callout>
135+ <callout arearefs='ex-dockerTools-buildImage-8'>
136+ <para>
137+ <varname>config</varname> is used to specify the configuration of the
138+ containers that will be started off the built image in Docker. The
139+ available options are listed in the
140+ <link xlink:href="https://github.com/moby/moby/blob/master/image/spec/v1.2.md#image-json-field-descriptions">
141+ Docker Image Specification v1.2.0 </link>.
142+ </para>
143+ </callout>
144+ </calloutlist>
145+
146+ <para>
147+ After the new layer has been created, its closure (to which
148+ <varname>contents</varname>, <varname>config</varname> and
149+ <varname>runAsRoot</varname> contribute) will be copied in the layer itself.
150+ Only new dependencies that are not already in the existing layers will be
151+ copied.
152+ </para>
153+
154+ <para>
155+ At the end of the process, only one new single layer will be produced and
156+ added to the resulting image.
157+ </para>
158+
159+ <para>
160+ The resulting repository will only list the single image
161+ <varname>image/tag</varname>. In the case of
162+ <xref linkend='ex-dockerTools-buildImage'/> it would be
163+ <varname>redis/latest</varname>.
164+ </para>
165+
166+ <para>
167+ It is possible to inspect the arguments with which an image was built using
168+ its <varname>buildArgs</varname> attribute.
169+ </para>
170+
171+ <note>
172+ <para>
173+ If you see errors similar to <literal>getProtocolByName: does not exist (no
174+ such protocol name: tcp)</literal> you may need to add
175+ <literal>pkgs.iana-etc</literal> to <varname>contents</varname>.
176+ </para>
177+ </note>
178+
179+ <note>
180+ <para>
181+ If you see errors similar to <literal>Error_Protocol ("certificate has
182+ unknown CA",True,UnknownCa)</literal> you may need to add
183+ <literal>pkgs.cacert</literal> to <varname>contents</varname>.
184+ </para>
185+ </note>
186+
187+ <example xml:id="example-pkgs-dockerTools-buildImage-creation-date">
188+ <title>Impurely Defining a Docker Layer's Creation Date</title>
189+ <para>
190+ By default <function>buildImage</function> will use a static date of one
191+ second past the UNIX Epoch. This allows <function>buildImage</function> to
192+ produce binary reproducible images. When listing images with
193+ <command>docker list images</command>, the newly created images will be
194+ listed like this:
195+ </para>
196+<screen><![CDATA[
197+$ docker image list
198+REPOSITORY TAG IMAGE ID CREATED SIZE
199+hello latest 08c791c7846e 48 years ago 25.2MB
200+]]></screen>
201+ <para>
202+ You can break binary reproducibility but have a sorted, meaningful
203+ <literal>CREATED</literal> column by setting <literal>created</literal> to
204+ <literal>now</literal>.
205+ </para>
206+<programlisting><![CDATA[
207+pkgs.dockerTools.buildImage {
208+ name = "hello";
209+ tag = "latest";
210+ created = "now";
211+ contents = pkgs.hello;
212+
213+ config.Cmd = [ "/bin/hello" ];
214+}
215+]]></programlisting>
216+ <para>
217+ and now the Docker CLI will display a reasonable date and sort the images
218+ as expected:
219+<screen><![CDATA[
220+$ docker image list
221+REPOSITORY TAG IMAGE ID CREATED SIZE
222+hello latest de2bf4786de6 About a minute ago 25.2MB
223+]]></screen>
224+ however, the produced images will not be binary reproducible.
225+ </para>
226+ </example>
227+ </section>
228+
229+ <section xml:id="ssec-pkgs-dockerTools-buildLayeredImage">
230+ <title>buildLayeredImage</title>
231+
232+ <para>
233+ Create a Docker image with many of the store paths being on their own layer
234+ to improve sharing between images.
235+ </para>
236+
237+ <variablelist>
238+ <varlistentry>
239+ <term>
240+ <varname>name</varname>
241+ </term>
242+ <listitem>
243+ <para>
244+ The name of the resulting image.
245+ </para>
246+ </listitem>
247+ </varlistentry>
248+ <varlistentry>
249+ <term>
250+ <varname>tag</varname> <emphasis>optional</emphasis>
251+ </term>
252+ <listitem>
253+ <para>
254+ Tag of the generated image.
255+ </para>
256+ <para>
257+ <emphasis>Default:</emphasis> the output path's hash
258+ </para>
259+ </listitem>
260+ </varlistentry>
261+ <varlistentry>
262+ <term>
263+ <varname>contents</varname> <emphasis>optional</emphasis>
264+ </term>
265+ <listitem>
266+ <para>
267+ Top level paths in the container. Either a single derivation, or a list
268+ of derivations.
269+ </para>
270+ <para>
271+ <emphasis>Default:</emphasis> <literal>[]</literal>
272+ </para>
273+ </listitem>
274+ </varlistentry>
275+ <varlistentry>
276+ <term>
277+ <varname>config</varname> <emphasis>optional</emphasis>
278+ </term>
279+ <listitem>
280+ <para>
281+ Run-time configuration of the container. A full list of the options are
282+ available at in the
283+ <link xlink:href="https://github.com/moby/moby/blob/master/image/spec/v1.2.md#image-json-field-descriptions">
284+ Docker Image Specification v1.2.0 </link>.
285+ </para>
286+ <para>
287+ <emphasis>Default:</emphasis> <literal>{}</literal>
288+ </para>
289+ </listitem>
290+ </varlistentry>
291+ <varlistentry>
292+ <term>
293+ <varname>created</varname> <emphasis>optional</emphasis>
294+ </term>
295+ <listitem>
296+ <para>
297+ Date and time the layers were created. Follows the same
298+ <literal>now</literal> exception supported by
299+ <literal>buildImage</literal>.
300+ </para>
301+ <para>
302+ <emphasis>Default:</emphasis> <literal>1970-01-01T00:00:01Z</literal>
303+ </para>
304+ </listitem>
305+ </varlistentry>
306+ <varlistentry>
307+ <term>
308+ <varname>maxLayers</varname> <emphasis>optional</emphasis>
309+ </term>
310+ <listitem>
311+ <para>
312+ Maximum number of layers to create.
313+ </para>
314+ <para>
315+ <emphasis>Default:</emphasis> <literal>24</literal>
316+ </para>
317+ </listitem>
318+ </varlistentry>
319+ </variablelist>
320+
321+ <section xml:id="dockerTools-buildLayeredImage-arg-contents">
322+ <title>Behavior of <varname>contents</varname> in the final image</title>
323+
324+ <para>
325+ Each path directly listed in <varname>contents</varname> will have a
326+ symlink in the root of the image.
327+ </para>
328+
329+ <para>
330+ For example:
331+<programlisting><![CDATA[
332+pkgs.dockerTools.buildLayeredImage {
333+ name = "hello";
334+ contents = [ pkgs.hello ];
335+}
336+]]></programlisting>
337+ will create symlinks for all the paths in the <literal>hello</literal>
338+ package:
339+<screen><![CDATA[
340+/bin/hello -> /nix/store/h1zb1padqbbb7jicsvkmrym3r6snphxg-hello-2.10/bin/hello
341+/share/info/hello.info -> /nix/store/h1zb1padqbbb7jicsvkmrym3r6snphxg-hello-2.10/share/info/hello.info
342+/share/locale/bg/LC_MESSAGES/hello.mo -> /nix/store/h1zb1padqbbb7jicsvkmrym3r6snphxg-hello-2.10/share/locale/bg/LC_MESSAGES/hello.mo
343+]]></screen>
344+ </para>
345+ </section>
346+
347+ <section xml:id="dockerTools-buildLayeredImage-arg-config">
348+ <title>Automatic inclusion of <varname>config</varname> references</title>
349+
350+ <para>
351+ The closure of <varname>config</varname> is automatically included in the
352+ closure of the final image.
353+ </para>
354+
355+ <para>
356+ This allows you to make very simple Docker images with very little code.
357+ This container will start up and run <command>hello</command>:
358+<programlisting><![CDATA[
359+pkgs.dockerTools.buildLayeredImage {
360+ name = "hello";
361+ config.Cmd = [ "${pkgs.hello}/bin/hello" ];
362+}
363+]]></programlisting>
364+ </para>
365+ </section>
366+
367+ <section xml:id="dockerTools-buildLayeredImage-arg-maxLayers">
368+ <title>Adjusting <varname>maxLayers</varname></title>
369+
370+ <para>
371+ Increasing the <varname>maxLayers</varname> increases the number of layers
372+ which have a chance to be shared between different images.
373+ </para>
374+
375+ <para>
376+ Modern Docker installations support up to 128 layers, however older
377+ versions support as few as 42.
378+ </para>
379+
380+ <para>
381+ If the produced image will not be extended by other Docker builds, it is
382+ safe to set <varname>maxLayers</varname> to <literal>128</literal>. However
383+ it will be impossible to extend the image further.
384+ </para>
385+
386+ <para>
387+ The first (<literal>maxLayers-2</literal>) most "popular" paths will have
388+ their own individual layers, then layer #<literal>maxLayers-1</literal>
389+ will contain all the remaining "unpopular" paths, and finally layer
390+ #<literal>maxLayers</literal> will contain the Image configuration.
391+ </para>
392+
393+ <para>
394+ Docker's Layers are not inherently ordered, they are content-addressable
395+ and are not explicitly layered until they are composed in to an Image.
396+ </para>
397+ </section>
398+ </section>
399+
400+ <section xml:id="ssec-pkgs-dockerTools-fetchFromRegistry">
401+ <title>pullImage</title>
402+
403+ <para>
404+ This function is analogous to the <command>docker pull</command> command, in
405+ that can be used to pull a Docker image from a Docker registry. By default
406+ <link xlink:href="https://hub.docker.com/">Docker Hub</link> is used to pull
407+ images.
408+ </para>
409+
410+ <para>
411+ Its parameters are described in the example below:
412+ </para>
413+
414+ <example xml:id='ex-dockerTools-pullImage'>
415+ <title>Docker pull</title>
416+<programlisting>
417+pullImage {
418+ imageName = "nixos/nix"; <co xml:id='ex-dockerTools-pullImage-1' />
419+ imageDigest = "sha256:20d9485b25ecfd89204e843a962c1bd70e9cc6858d65d7f5fadc340246e2116b"; <co xml:id='ex-dockerTools-pullImage-2' />
420+ finalImageTag = "1.11"; <co xml:id='ex-dockerTools-pullImage-3' />
421+ sha256 = "0mqjy3zq2v6rrhizgb9nvhczl87lcfphq9601wcprdika2jz7qh8"; <co xml:id='ex-dockerTools-pullImage-4' />
422+ os = "linux"; <co xml:id='ex-dockerTools-pullImage-5' />
423+ arch = "x86_64"; <co xml:id='ex-dockerTools-pullImage-6' />
424+}
425+</programlisting>
426+ </example>
427+
428+ <calloutlist>
429+ <callout arearefs='ex-dockerTools-pullImage-1'>
430+ <para>
431+ <varname>imageName</varname> specifies the name of the image to be
432+ downloaded, which can also include the registry namespace (e.g.
433+ <literal>nixos</literal>). This argument is required.
434+ </para>
435+ </callout>
436+ <callout arearefs='ex-dockerTools-pullImage-2'>
437+ <para>
438+ <varname>imageDigest</varname> specifies the digest of the image to be
439+ downloaded. Skopeo can be used to get the digest of an image, with its
440+ <varname>inspect</varname> subcommand. Since a given
441+ <varname>imageName</varname> may transparently refer to a manifest list of
442+ images which support multiple architectures and/or operating systems,
443+ supply the `--override-os` and `--override-arch` arguments to specify
444+ exactly which image you want. By default it will match the OS and
445+ architecture of the host the command is run on.
446+<programlisting>
447+$ nix-shell --packages skopeo jq --command "skopeo --override-os linux --override-arch x86_64 inspect docker://docker.io/nixos/nix:1.11 | jq -r '.Digest'"
448+sha256:20d9485b25ecfd89204e843a962c1bd70e9cc6858d65d7f5fadc340246e2116b
449+</programlisting>
450+ This argument is required.
451+ </para>
452+ </callout>
453+ <callout arearefs='ex-dockerTools-pullImage-3'>
454+ <para>
455+ <varname>finalImageTag</varname>, if specified, this is the tag of the
456+ image to be created. Note it is never used to fetch the image since we
457+ prefer to rely on the immutable digest ID. By default it's
458+ <literal>latest</literal>.
459+ </para>
460+ </callout>
461+ <callout arearefs='ex-dockerTools-pullImage-4'>
462+ <para>
463+ <varname>sha256</varname> is the checksum of the whole fetched image. This
464+ argument is required.
465+ </para>
466+ </callout>
467+ <callout arearefs='ex-dockerTools-pullImage-5'>
468+ <para>
469+ <varname>os</varname>, if specified, is the operating system of the
470+ fetched image. By default it's <literal>linux</literal>.
471+ </para>
472+ </callout>
473+ <callout arearefs='ex-dockerTools-pullImage-6'>
474+ <para>
475+ <varname>arch</varname>, if specified, is the cpu architecture of the
476+ fetched image. By default it's <literal>x86_64</literal>.
477+ </para>
478+ </callout>
479+ </calloutlist>
480+ </section>
481+
482+ <section xml:id="ssec-pkgs-dockerTools-exportImage">
483+ <title>exportImage</title>
484+
485+ <para>
486+ This function is analogous to the <command>docker export</command> command,
487+ in that can used to flatten a Docker image that contains multiple layers. It
488+ is in fact the result of the merge of all the layers of the image. As such,
489+ the result is suitable for being imported in Docker with <command>docker
490+ import</command>.
491+ </para>
492+
493+ <note>
494+ <para>
495+ Using this function requires the <literal>kvm</literal> device to be
496+ available.
497+ </para>
498+ </note>
499+
500+ <para>
501+ The parameters of <varname>exportImage</varname> are the following:
502+ </para>
503+
504+ <example xml:id='ex-dockerTools-exportImage'>
505+ <title>Docker export</title>
506+<programlisting>
507+exportImage {
508+ fromImage = someLayeredImage;
509+ fromImageName = null;
510+ fromImageTag = null;
511+
512+ name = someLayeredImage.name;
513+}
514+ </programlisting>
515+ </example>
516+
517+ <para>
518+ The parameters relative to the base image have the same synopsis as
519+ described in <xref linkend='ssec-pkgs-dockerTools-buildImage'/>, except that
520+ <varname>fromImage</varname> is the only required argument in this case.
521+ </para>
522+
523+ <para>
524+ The <varname>name</varname> argument is the name of the derivation output,
525+ which defaults to <varname>fromImage.name</varname>.
526+ </para>
527+ </section>
528+
529+ <section xml:id="ssec-pkgs-dockerTools-shadowSetup">
530+ <title>shadowSetup</title>
531+
532+ <para>
533+ This constant string is a helper for setting up the base files for managing
534+ users and groups, only if such files don't exist already. It is suitable for
535+ being used in a <varname>runAsRoot</varname>
536+ <xref linkend='ex-dockerTools-buildImage-runAsRoot'/> script for cases like
537+ in the example below:
538+ </para>
539+
540+ <example xml:id='ex-dockerTools-shadowSetup'>
541+ <title>Shadow base files</title>
542+<programlisting>
543+buildImage {
544+ name = "shadow-basic";
545+
546+ runAsRoot = ''
547+ #!${stdenv.shell}
548+ ${shadowSetup}
549+ groupadd -r redis
550+ useradd -r -g redis redis
551+ mkdir /data
552+ chown redis:redis /data
553+ '';
554+}
555+</programlisting>
556+ </example>
557+
558+ <para>
559+ Creating base files like <literal>/etc/passwd</literal> or
560+ <literal>/etc/login.defs</literal> are necessary for shadow-utils to
561+ manipulate users and groups.
562+ </para>
563+ </section>
564+</section>
doc/functions/fhs-environments.xmlnew file+142
@@ -0,0 +1,142 @@
1+<section xmlns="http://docbook.org/ns/docbook"
2+ xmlns:xlink="http://www.w3.org/1999/xlink"
3+ xmlns:xi="http://www.w3.org/2001/XInclude"
4+ xml:id="sec-fhs-environments">
5+ <title>buildFHSUserEnv</title>
6+
7+ <para>
8+ <function>buildFHSUserEnv</function> provides a way to build and run
9+ FHS-compatible lightweight sandboxes. It creates an isolated root with bound
10+ <filename>/nix/store</filename>, so its footprint in terms of disk space
11+ needed is quite small. This allows one to run software which is hard or
12+ unfeasible to patch for NixOS -- 3rd-party source trees with FHS assumptions,
13+ games distributed as tarballs, software with integrity checking and/or
14+ external self-updated binaries. It uses Linux namespaces feature to create
15+ temporary lightweight environments which are destroyed after all child
16+ processes exit, without root user rights requirement. Accepted arguments are:
17+ </para>
18+
19+ <variablelist>
20+ <varlistentry>
21+ <term>
22+ <literal>name</literal>
23+ </term>
24+ <listitem>
25+ <para>
26+ Environment name.
27+ </para>
28+ </listitem>
29+ </varlistentry>
30+ <varlistentry>
31+ <term>
32+ <literal>targetPkgs</literal>
33+ </term>
34+ <listitem>
35+ <para>
36+ Packages to be installed for the main host's architecture (i.e. x86_64 on
37+ x86_64 installations). Along with libraries binaries are also installed.
38+ </para>
39+ </listitem>
40+ </varlistentry>
41+ <varlistentry>
42+ <term>
43+ <literal>multiPkgs</literal>
44+ </term>
45+ <listitem>
46+ <para>
47+ Packages to be installed for all architectures supported by a host (i.e.
48+ i686 and x86_64 on x86_64 installations). Only libraries are installed by
49+ default.
50+ </para>
51+ </listitem>
52+ </varlistentry>
53+ <varlistentry>
54+ <term>
55+ <literal>extraBuildCommands</literal>
56+ </term>
57+ <listitem>
58+ <para>
59+ Additional commands to be executed for finalizing the directory structure.
60+ </para>
61+ </listitem>
62+ </varlistentry>
63+ <varlistentry>
64+ <term>
65+ <literal>extraBuildCommandsMulti</literal>
66+ </term>
67+ <listitem>
68+ <para>
69+ Like <literal>extraBuildCommands</literal>, but executed only on multilib
70+ architectures.
71+ </para>
72+ </listitem>
73+ </varlistentry>
74+ <varlistentry>
75+ <term>
76+ <literal>extraOutputsToInstall</literal>
77+ </term>
78+ <listitem>
79+ <para>
80+ Additional derivation outputs to be linked for both target and
81+ multi-architecture packages.
82+ </para>
83+ </listitem>
84+ </varlistentry>
85+ <varlistentry>
86+ <term>
87+ <literal>extraInstallCommands</literal>
88+ </term>
89+ <listitem>
90+ <para>
91+ Additional commands to be executed for finalizing the derivation with
92+ runner script.
93+ </para>
94+ </listitem>
95+ </varlistentry>
96+ <varlistentry>
97+ <term>
98+ <literal>runScript</literal>
99+ </term>
100+ <listitem>
101+ <para>
102+ A command that would be executed inside the sandbox and passed all the
103+ command line arguments. It defaults to <literal>bash</literal>.
104+ </para>
105+ </listitem>
106+ </varlistentry>
107+ </variablelist>
108+
109+ <para>
110+ One can create a simple environment using a <literal>shell.nix</literal> like
111+ that:
112+ </para>
113+
114+<programlisting><![CDATA[
115+{ pkgs ? import <nixpkgs> {} }:
116+
117+(pkgs.buildFHSUserEnv {
118+ name = "simple-x11-env";
119+ targetPkgs = pkgs: (with pkgs;
120+ [ udev
121+ alsaLib
122+ ]) ++ (with pkgs.xorg;
123+ [ libX11
124+ libXcursor
125+ libXrandr
126+ ]);
127+ multiPkgs = pkgs: (with pkgs;
128+ [ udev
129+ alsaLib
130+ ]);
131+ runScript = "bash";
132+}).env
133+]]></programlisting>
134+
135+ <para>
136+ Running <literal>nix-shell</literal> would then drop you into a shell with
137+ these libraries and binaries available. You can use this to run closed-source
138+ applications which expect FHS structure without hassles: simply change
139+ <literal>runScript</literal> to the application path, e.g.
140+ <filename>./bin/start.sh</filename> -- relative paths are supported.
141+ </para>
142+</section>
doc/functions/generators.xmlnew file+89
@@ -0,0 +1,89 @@
1+<section xmlns="http://docbook.org/ns/docbook"
2+ xmlns:xlink="http://www.w3.org/1999/xlink"
3+ xmlns:xi="http://www.w3.org/2001/XInclude"
4+ xml:id="sec-generators">
5+ <title>Generators</title>
6+
7+ <para>
8+ Generators are functions that create file formats from nix data structures,
9+ e. g. for configuration files. There are generators available for:
10+ <literal>INI</literal>, <literal>JSON</literal> and <literal>YAML</literal>
11+ </para>
12+
13+ <para>
14+ All generators follow a similar call interface: <code>generatorName
15+ configFunctions data</code>, where <literal>configFunctions</literal> is an
16+ attrset of user-defined functions that format nested parts of the content.
17+ They each have common defaults, so often they do not need to be set manually.
18+ An example is <code>mkSectionName ? (name: libStr.escape [ "[" "]" ]
19+ name)</code> from the <literal>INI</literal> generator. It receives the name
20+ of a section and sanitizes it. The default <literal>mkSectionName</literal>
21+ escapes <literal>[</literal> and <literal>]</literal> with a backslash.
22+ </para>
23+
24+ <para>
25+ Generators can be fine-tuned to produce exactly the file format required by
26+ your application/service. One example is an INI-file format which uses
27+ <literal>: </literal> as separator, the strings
28+ <literal>"yes"</literal>/<literal>"no"</literal> as boolean values and
29+ requires all string values to be quoted:
30+ </para>
31+
32+<programlisting>
33+with lib;
34+let
35+ customToINI = generators.toINI {
36+ # specifies how to format a key/value pair
37+ mkKeyValue = generators.mkKeyValueDefault {
38+ # specifies the generated string for a subset of nix values
39+ mkValueString = v:
40+ if v == true then ''"yes"''
41+ else if v == false then ''"no"''
42+ else if isString v then ''"${v}"''
43+ # and delegats all other values to the default generator
44+ else generators.mkValueStringDefault {} v;
45+ } ":";
46+ };
47+
48+# the INI file can now be given as plain old nix values
49+in customToINI {
50+ main = {
51+ pushinfo = true;
52+ autopush = false;
53+ host = "localhost";
54+ port = 42;
55+ };
56+ mergetool = {
57+ merge = "diff3";
58+ };
59+}
60+</programlisting>
61+
62+ <para>
63+ This will produce the following INI file as nix string:
64+ </para>
65+
66+<programlisting>
67+[main]
68+autopush:"no"
69+host:"localhost"
70+port:42
71+pushinfo:"yes"
72+str\:ange:"very::strange"
73+
74+[mergetool]
75+merge:"diff3"
76+</programlisting>
77+
78+ <note>
79+ <para>
80+ Nix store paths can be converted to strings by enclosing a derivation
81+ attribute like so: <code>"${drv}"</code>.
82+ </para>
83+ </note>
84+
85+ <para>
86+ Detailed documentation for each generator can be found in
87+ <literal>lib/generators.nix</literal>.
88+ </para>
89+</section>
doc/functions/library.xmlnew file+15
@@ -0,0 +1,15 @@
1+<section xmlns="http://docbook.org/ns/docbook"
2+ xmlns:xlink="http://www.w3.org/1999/xlink"
3+ xmlns:xi="http://www.w3.org/2001/XInclude"
4+ xml:id="sec-functions-library">
5+ <title>Nixpkgs Library Functions</title>
6+
7+ <para>
8+ Nixpkgs provides a standard library at <varname>pkgs.lib</varname>, or
9+ through <code>import &lt;nixpkgs/lib&gt;</code>.
10+ </para>
11+
12+ <xi:include href="./library/asserts.xml" />
13+
14+ <xi:include href="./library/attrsets.xml" />
15+</section>
doc/functions/library/asserts.xmlnew file+117
@@ -0,0 +1,117 @@
1+<section xmlns="http://docbook.org/ns/docbook"
2+ xmlns:xlink="http://www.w3.org/1999/xlink"
3+ xmlns:xi="http://www.w3.org/2001/XInclude"
4+ xml:id="sec-functions-library-asserts">
5+ <title>Assert functions</title>
6+
7+ <section xml:id="function-library-lib.asserts.assertMsg">
8+ <title><function>lib.asserts.assertMsg</function></title>
9+
10+ <subtitle><literal>assertMsg :: Bool -> String -> Bool</literal>
11+ </subtitle>
12+
13+ <xi:include href="./locations.xml" xpointer="lib.asserts.assertMsg" />
14+
15+ <para>
16+ Print a trace message if <literal>pred</literal> is false.
17+ </para>
18+
19+ <para>
20+ Intended to be used to augment asserts with helpful error messages.
21+ </para>
22+
23+ <variablelist>
24+ <varlistentry>
25+ <term>
26+ <varname>pred</varname>
27+ </term>
28+ <listitem>
29+ <para>
30+ Condition under which the <varname>msg</varname> should
31+ <emphasis>not</emphasis> be printed.
32+ </para>
33+ </listitem>
34+ </varlistentry>
35+ <varlistentry>
36+ <term>
37+ <varname>msg</varname>
38+ </term>
39+ <listitem>
40+ <para>
41+ Message to print.
42+ </para>
43+ </listitem>
44+ </varlistentry>
45+ </variablelist>
46+
47+ <example xml:id="function-library-lib.asserts.assertMsg-example-false">
48+ <title>Printing when the predicate is false</title>
49+<programlisting><![CDATA[
50+assert lib.asserts.assertMsg ("foo" == "bar") "foo is not bar, silly"
51+stderr> trace: foo is not bar, silly
52+stderr> assert failed
53+]]></programlisting>
54+ </example>
55+ </section>
56+
57+ <section xml:id="function-library-lib.asserts.assertOneOf">
58+ <title><function>lib.asserts.assertOneOf</function></title>
59+
60+ <subtitle><literal>assertOneOf :: String -> String ->
61+ StringList -> Bool</literal>
62+ </subtitle>
63+
64+ <xi:include href="./locations.xml" xpointer="lib.asserts.assertOneOf" />
65+
66+ <para>
67+ Specialized <function>asserts.assertMsg</function> for checking if
68+ <varname>val</varname> is one of the elements of <varname>xs</varname>.
69+ Useful for checking enums.
70+ </para>
71+
72+ <variablelist>
73+ <varlistentry>
74+ <term>
75+ <varname>name</varname>
76+ </term>
77+ <listitem>
78+ <para>
79+ The name of the variable the user entered <varname>val</varname> into,
80+ for inclusion in the error message.
81+ </para>
82+ </listitem>
83+ </varlistentry>
84+ <varlistentry>
85+ <term>
86+ <varname>val</varname>
87+ </term>
88+ <listitem>
89+ <para>
90+ The value of what the user provided, to be compared against the values in
91+ <varname>xs</varname>.
92+ </para>
93+ </listitem>
94+ </varlistentry>
95+ <varlistentry>
96+ <term>
97+ <varname>xs</varname>
98+ </term>
99+ <listitem>
100+ <para>
101+ The list of valid values.
102+ </para>
103+ </listitem>
104+ </varlistentry>
105+ </variablelist>
106+
107+ <example xml:id="function-library-lib.asserts.assertOneOf-example">
108+ <title>Ensuring a user provided a possible value</title>
109+<programlisting><![CDATA[
110+let sslLibrary = "bearssl";
111+in lib.asserts.assertOneOf "sslLibrary" sslLibrary [ "openssl" "bearssl" ];
112+=> false
113+stderr> trace: sslLibrary must be one of "openssl", "libressl", but is: "bearssl"
114+ ]]></programlisting>
115+ </example>
116+ </section>
117+</section>
doc/functions/library/attrsets.xmlnew file+1731
@@ -0,0 +1,1731 @@
1+<section xmlns="http://docbook.org/ns/docbook"
2+ xmlns:xlink="http://www.w3.org/1999/xlink"
3+ xmlns:xi="http://www.w3.org/2001/XInclude"
4+ xml:id="sec-functions-library-attrset">
5+ <title>Attribute-Set Functions</title>
6+
7+ <section xml:id="function-library-lib.attrsets.attrByPath">
8+ <title><function>lib.attrset.attrByPath</function></title>
9+
10+ <subtitle><literal>attrByPath :: [String] -> Any -> AttrSet</literal>
11+ </subtitle>
12+
13+ <xi:include href="./locations.xml" xpointer="lib.attrsets.attrByPath" />
14+
15+ <para>
16+ Return an attribute from within nested attribute sets.
17+ </para>
18+
19+ <variablelist>
20+ <varlistentry>
21+ <term>
22+ <varname>attrPath</varname>
23+ </term>
24+ <listitem>
25+ <para>
26+ A list of strings representing the path through the nested attribute set
27+ <varname>set</varname>.
28+ </para>
29+ </listitem>
30+ </varlistentry>
31+ <varlistentry>
32+ <term>
33+ <varname>default</varname>
34+ </term>
35+ <listitem>
36+ <para>
37+ Default value if <varname>attrPath</varname> does not resolve to an
38+ existing value.
39+ </para>
40+ </listitem>
41+ </varlistentry>
42+ <varlistentry>
43+ <term>
44+ <varname>set</varname>
45+ </term>
46+ <listitem>
47+ <para>
48+ The nested attributeset to select values from.
49+ </para>
50+ </listitem>
51+ </varlistentry>
52+ </variablelist>
53+
54+ <example xml:id="function-library-lib.attrset.attrByPath-example-value-exists">
55+ <title>Extracting a value from a nested attribute set</title>
56+<programlisting><![CDATA[
57+let set = { a = { b = 3; }; };
58+in lib.attrsets.attrByPath [ "a" "b" ] 0 set
59+=> 3
60+]]></programlisting>
61+ </example>
62+
63+ <example xml:id="function-library-lib.attrset.attrByPath-example-default-value">
64+ <title>No value at the path, instead using the default</title>
65+<programlisting><![CDATA[
66+lib.attrsets.attrByPath [ "a" "b" ] 0 {}
67+=> 0
68+]]></programlisting>
69+ </example>
70+ </section>
71+
72+ <section xml:id="function-library-lib.attrsets.hasAttrByPath">
73+ <title><function>lib.attrsets.hasAttrByPath</function></title>
74+
75+ <subtitle><literal>hasAttrByPath :: [String] -> AttrSet -> Bool</literal>
76+ </subtitle>
77+
78+ <xi:include href="./locations.xml" xpointer="lib.attrsets.hasAttrByPath" />
79+
80+ <para>
81+ Determine if an attribute exists within a nested attribute set.
82+ </para>
83+
84+ <variablelist>
85+ <varlistentry>
86+ <term>
87+ <varname>attrPath</varname>
88+ </term>
89+ <listitem>
90+ <para>
91+ A list of strings representing the path through the nested attribute set
92+ <varname>set</varname>.
93+ </para>
94+ </listitem>
95+ </varlistentry>
96+ <varlistentry>
97+ <term>
98+ <varname>set</varname>
99+ </term>
100+ <listitem>
101+ <para>
102+ The nested attributeset to check.
103+ </para>
104+ </listitem>
105+ </varlistentry>
106+ </variablelist>
107+
108+ <example xml:id="function-library-lib.attrsets.hasAttrByPath-example">
109+ <title>A nested value does exist inside a set</title>
110+<programlisting><![CDATA[
111+lib.attrsets.hasAttrByPath
112+ [ "a" "b" "c" "d" ]
113+ { a = { b = { c = { d = 123; }; }; }; }
114+=> true
115+]]></programlisting>
116+ </example>
117+ </section>
118+
119+ <section xml:id="function-library-lib.attrsets.setAttrByPath">
120+ <title><function>lib.attrsets.setAttrByPath</function></title>
121+
122+ <subtitle><literal>setAttrByPath :: [String] -> Any -> AttrSet</literal>
123+ </subtitle>
124+
125+ <xi:include href="./locations.xml" xpointer="lib.attrsets.setAttrByPath" />
126+
127+ <para>
128+ Create a new attribute set with <varname>value</varname> set at the nested
129+ attribute location specified in <varname>attrPath</varname>.
130+ </para>
131+
132+ <variablelist>
133+ <varlistentry>
134+ <term>
135+ <varname>attrPath</varname>
136+ </term>
137+ <listitem>
138+ <para>
139+ A list of strings representing the path through the nested attribute set.
140+ </para>
141+ </listitem>
142+ </varlistentry>
143+ <varlistentry>
144+ <term>
145+ <varname>value</varname>
146+ </term>
147+ <listitem>
148+ <para>
149+ The value to set at the location described by
150+ <varname>attrPath</varname>.
151+ </para>
152+ </listitem>
153+ </varlistentry>
154+ </variablelist>
155+
156+ <example xml:id="function-library-lib.attrsets.setAttrByPath-example">
157+ <title>Creating a new nested attribute set</title>
158+<programlisting><![CDATA[
159+lib.attrsets.setAttrByPath [ "a" "b" ] 3
160+=> { a = { b = 3; }; }
161+]]></programlisting>
162+ </example>
163+ </section>
164+
165+ <section xml:id="function-library-lib.attrsets.getAttrFromPath">
166+ <title><function>lib.attrsets.getAttrFromPath</function></title>
167+
168+ <subtitle><literal>getAttrFromPath :: [String] -> AttrSet -> Value</literal>
169+ </subtitle>
170+
171+ <xi:include href="./locations.xml" xpointer="lib.attrsets.getAttrFromPath" />
172+
173+ <para>
174+ Like <xref linkend="function-library-lib.attrsets.attrByPath" /> except
175+ without a default, and it will throw if the value doesn't exist.
176+ </para>
177+
178+ <variablelist>
179+ <varlistentry>
180+ <term>
181+ <varname>attrPath</varname>
182+ </term>
183+ <listitem>
184+ <para>
185+ A list of strings representing the path through the nested attribute set
186+ <varname>set</varname>.
187+ </para>
188+ </listitem>
189+ </varlistentry>
190+ <varlistentry>
191+ <term>
192+ <varname>set</varname>
193+ </term>
194+ <listitem>
195+ <para>
196+ The nested attribute set to find the value in.
197+ </para>
198+ </listitem>
199+ </varlistentry>
200+ </variablelist>
201+
202+ <example xml:id="function-library-lib.attrsets.getAttrPath-example-success">
203+ <title>Succesfully getting a value from an attribute set</title>
204+<programlisting><![CDATA[
205+lib.attrsets.getAttrFromPath [ "a" "b" ] { a = { b = 3; }; }
206+=> 3
207+]]></programlisting>
208+ </example>
209+
210+ <example xml:id="function-library-lib.attrsets.getAttrPath-example-throw">
211+ <title>Throwing after failing to get a value from an attribute set</title>
212+<programlisting><![CDATA[
213+lib.attrsets.getAttrFromPath [ "x" "y" ] { }
214+=> error: cannot find attribute `x.y'
215+]]></programlisting>
216+ </example>
217+ </section>
218+
219+ <section xml:id="function-library-lib.attrsets.attrVals">
220+ <title><function>lib.attrsets.attrVals</function></title>
221+
222+ <subtitle><literal>attrVals :: [String] -> AttrSet -> [Any]</literal>
223+ </subtitle>
224+
225+ <xi:include href="./locations.xml" xpointer="lib.attrsets.attrVals" />
226+
227+ <para>
228+ Return the specified attributes from a set. All values must exist.
229+ </para>
230+
231+ <variablelist>
232+ <varlistentry>
233+ <term>
234+ <varname>nameList</varname>
235+ </term>
236+ <listitem>
237+ <para>
238+ The list of attributes to fetch from <varname>set</varname>. Each
239+ attribute name must exist on the attrbitue set.
240+ </para>
241+ </listitem>
242+ </varlistentry>
243+ <varlistentry>
244+ <term>
245+ <varname>set</varname>
246+ </term>
247+ <listitem>
248+ <para>
249+ The set to get attribute values from.
250+ </para>
251+ </listitem>
252+ </varlistentry>
253+ </variablelist>
254+
255+ <example xml:id="function-library-lib.attrsets.attrVals-example-success">
256+ <title>Getting several values from an attribute set</title>
257+<programlisting><![CDATA[
258+lib.attrsets.attrVals [ "a" "b" "c" ] { a = 1; b = 2; c = 3; }
259+=> [ 1 2 3 ]
260+]]></programlisting>
261+ </example>
262+
263+ <example xml:id="function-library-lib.attrsets.attrVals-failure">
264+ <title>Getting missing values from an attribute set</title>
265+<programlisting><![CDATA[
266+lib.attrsets.attrVals [ "d" ] { }
267+error: attribute 'd' missing
268+]]></programlisting>
269+ </example>
270+ </section>
271+
272+ <section xml:id="function-library-lib.attrsets.attrValues">
273+ <title><function>lib.attrsets.attrValues</function></title>
274+
275+ <subtitle><literal>attrValues :: AttrSet -> [Any]</literal>
276+ </subtitle>
277+
278+ <xi:include href="./locations.xml" xpointer="lib.attrsets.attrValues" />
279+
280+ <para>
281+ Get all the attribute values from an attribute set.
282+ </para>
283+
284+ <para>
285+ Provides a backwards-compatible interface of
286+ <function>builtins.attrValues</function> for Nix version older than 1.8.
287+ </para>
288+
289+ <variablelist>
290+ <varlistentry>
291+ <term>
292+ <varname>attrs</varname>
293+ </term>
294+ <listitem>
295+ <para>
296+ The attribute set.
297+ </para>
298+ </listitem>
299+ </varlistentry>
300+ </variablelist>
301+
302+ <example xml:id="function-library-lib.attrsets.attrValues-example">
303+ <title></title>
304+<programlisting><![CDATA[
305+lib.attrsets.attrValues { a = 1; b = 2; c = 3; }
306+=> [ 1 2 3 ]
307+]]></programlisting>
308+ </example>
309+ </section>
310+
311+ <section xml:id="function-library-lib.attrsets.catAttrs">
312+ <title><function>lib.attrsets.catAttrs</function></title>
313+
314+ <subtitle><literal>catAttrs :: String -> AttrSet -> [Any]</literal>
315+ </subtitle>
316+
317+ <xi:include href="./locations.xml" xpointer="lib.attrsets.catAttrs" />
318+
319+ <para>
320+ Collect each attribute named `attr' from the list of attribute sets,
321+ <varname>sets</varname>. Sets that don't contain the named attribute are
322+ ignored.
323+ </para>
324+
325+ <para>
326+ Provides a backwards-compatible interface of
327+ <function>builtins.catAttrs</function> for Nix version older than 1.9.
328+ </para>
329+
330+ <variablelist>
331+ <varlistentry>
332+ <term>
333+ <varname>attr</varname>
334+ </term>
335+ <listitem>
336+ <para>
337+ Attribute name to select from each attribute set in
338+ <varname>sets</varname>.
339+ </para>
340+ </listitem>
341+ </varlistentry>
342+ <varlistentry>
343+ <term>
344+ <varname>sets</varname>
345+ </term>
346+ <listitem>
347+ <para>
348+ The list of attribute sets to select <varname>attr</varname> from.
349+ </para>
350+ </listitem>
351+ </varlistentry>
352+ </variablelist>
353+
354+ <example xml:id="function-library-lib.attrsets.catAttrs-example">
355+ <title>Collect an attribute from a list of attribute sets.</title>
356+ <para>
357+ Attribute sets which don't have the attribute are ignored.
358+ </para>
359+<programlisting><![CDATA[
360+catAttrs "a" [{a = 1;} {b = 0;} {a = 2;}]
361+=> [ 1 2 ]
362+ ]]></programlisting>
363+ </example>
364+ </section>
365+
366+ <section xml:id="function-library-lib.attrsets.filterAttrs">
367+ <title><function>lib.attrsets.filterAttrs</function></title>
368+
369+ <subtitle><literal>filterAttrs :: (String -> Any -> Bool) -> AttrSet -> AttrSet</literal>
370+ </subtitle>
371+
372+ <xi:include href="./locations.xml" xpointer="lib.attrsets.filterAttrs" />
373+
374+ <para>
375+ Filter an attribute set by removing all attributes for which the given
376+ predicate return false.
377+ </para>
378+
379+ <variablelist>
380+ <varlistentry>
381+ <term>
382+ <varname>pred</varname>
383+ </term>
384+ <listitem>
385+ <para>
386+ <literal>String -> Any -> Bool</literal>
387+ </para>
388+ <para>
389+ Predicate which returns true to include an attribute, or returns false to
390+ exclude it.
391+ </para>
392+ <variablelist>
393+ <varlistentry>
394+ <term>
395+ <varname>name</varname>
396+ </term>
397+ <listitem>
398+ <para>
399+ The attribute's name
400+ </para>
401+ </listitem>
402+ </varlistentry>
403+ <varlistentry>
404+ <term>
405+ <varname>value</varname>
406+ </term>
407+ <listitem>
408+ <para>
409+ The attribute's value
410+ </para>
411+ </listitem>
412+ </varlistentry>
413+ </variablelist>
414+ <para>
415+ Returns <literal>true</literal> to include the attribute,
416+ <literal>false</literal> to exclude the attribute.
417+ </para>
418+ </listitem>
419+ </varlistentry>
420+ <varlistentry>
421+ <term>
422+ <varname>set</varname>
423+ </term>
424+ <listitem>
425+ <para>
426+ The attribute set to filter
427+ </para>
428+ </listitem>
429+ </varlistentry>
430+ </variablelist>
431+
432+ <example xml:id="function-library-lib.attrsets.filterAttrs-example">
433+ <title>Filtering an attributeset</title>
434+<programlisting><![CDATA[
435+filterAttrs (n: v: n == "foo") { foo = 1; bar = 2; }
436+=> { foo = 1; }
437+]]></programlisting>
438+ </example>
439+ </section>
440+
441+ <section xml:id="function-library-lib.attrsets.filterAttrsRecursive">
442+ <title><function>lib.attrsets.filterAttrsRecursive</function></title>
443+
444+ <subtitle><literal>filterAttrsRecursive :: (String -> Any -> Bool) -> AttrSet -> AttrSet</literal>
445+ </subtitle>
446+
447+ <xi:include href="./locations.xml" xpointer="lib.attrsets.filterAttrsRecursive" />
448+
449+ <para>
450+ Filter an attribute set recursively by removing all attributes for which the
451+ given predicate return false.
452+ </para>
453+
454+ <variablelist>
455+ <varlistentry>
456+ <term>
457+ <varname>pred</varname>
458+ </term>
459+ <listitem>
460+ <para>
461+ <literal>String -> Any -> Bool</literal>
462+ </para>
463+ <para>
464+ Predicate which returns true to include an attribute, or returns false to
465+ exclude it.
466+ </para>
467+ <variablelist>
468+ <varlistentry>
469+ <term>
470+ <varname>name</varname>
471+ </term>
472+ <listitem>
473+ <para>
474+ The attribute's name
475+ </para>
476+ </listitem>
477+ </varlistentry>
478+ <varlistentry>
479+ <term>
480+ <varname>value</varname>
481+ </term>
482+ <listitem>
483+ <para>
484+ The attribute's value
485+ </para>
486+ </listitem>
487+ </varlistentry>
488+ </variablelist>
489+ <para>
490+ Returns <literal>true</literal> to include the attribute,
491+ <literal>false</literal> to exclude the attribute.
492+ </para>
493+ </listitem>
494+ </varlistentry>
495+ <varlistentry>
496+ <term>
497+ <varname>set</varname>
498+ </term>
499+ <listitem>
500+ <para>
501+ The attribute set to filter
502+ </para>
503+ </listitem>
504+ </varlistentry>
505+ </variablelist>
506+
507+ <example xml:id="function-library-lib.attrsets.filterAttrsRecursive-example">
508+ <title>Recursively filtering an attribute set</title>
509+<programlisting><![CDATA[
510+lib.attrsets.filterAttrsRecursive
511+ (n: v: v != null)
512+ {
513+ levelA = {
514+ example = "hi";
515+ levelB = {
516+ hello = "there";
517+ this-one-is-present = {
518+ this-is-excluded = null;
519+ };
520+ };
521+ this-one-is-also-excluded = null;
522+ };
523+ also-excluded = null;
524+ }
525+=> {
526+ levelA = {
527+ example = "hi";
528+ levelB = {
529+ hello = "there";
530+ this-one-is-present = { };
531+ };
532+ };
533+ }
534+ ]]></programlisting>
535+ </example>
536+ </section>
537+
538+ <section xml:id="function-library-lib.attrsets.foldAttrs">
539+ <title><function>lib.attrsets.foldAttrs</function></title>
540+
541+ <subtitle><literal>foldAttrs :: (Any -> Any -> Any) -> Any -> [AttrSets] -> Any</literal>
542+ </subtitle>
543+
544+ <xi:include href="./locations.xml" xpointer="lib.attrsets.foldAttrs" />
545+
546+ <para>
547+ Apply fold function to values grouped by key.
548+ </para>
549+
550+ <variablelist>
551+ <varlistentry>
552+ <term>
553+ <varname>op</varname>
554+ </term>
555+ <listitem>
556+ <para>
557+ <literal>Any -> Any -> Any</literal>
558+ </para>
559+ <para>
560+ Given a value <varname>val</varname> and a collector
561+ <varname>col</varname>, combine the two.
562+ </para>
563+ <variablelist>
564+ <varlistentry>
565+ <term>
566+ <varname>val</varname>
567+ </term>
568+ <listitem>
569+ <para>
570+ An attribute's value
571+ </para>
572+ </listitem>
573+ </varlistentry>
574+ <varlistentry>
575+ <term>
576+ <varname>col</varname>
577+ </term>
578+ <listitem>
579+<!-- TODO: make this not bad, use more fold-ey terms -->
580+ <para>
581+ The result of previous <function>op</function> calls with other values
582+ and <function>nul</function>.
583+ </para>
584+ </listitem>
585+ </varlistentry>
586+ </variablelist>
587+ </listitem>
588+ </varlistentry>
589+ <varlistentry>
590+ <term>
591+ <varname>nul</varname>
592+ </term>
593+ <listitem>
594+ <para>
595+ The null-value, the starting value.
596+ </para>
597+ </listitem>
598+ </varlistentry>
599+ <varlistentry>
600+ <term>
601+ <varname>list_of_attrs</varname>
602+ </term>
603+ <listitem>
604+ <para>
605+ A list of attribute sets to fold together by key.
606+ </para>
607+ </listitem>
608+ </varlistentry>
609+ </variablelist>
610+
611+ <example xml:id="function-library-lib.attrsets.foldAttrs-example">
612+ <title>Combining an attribute of lists in to one attribute set</title>
613+<programlisting><![CDATA[
614+lib.attrsets.foldAttrs
615+ (n: a: [n] ++ a) []
616+ [
617+ { a = 2; b = 7; }
618+ { a = 3; }
619+ { b = 6; }
620+ ]
621+=> { a = [ 2 3 ]; b = [ 7 6 ]; }
622+]]></programlisting>
623+ </example>
624+ </section>
625+
626+ <section xml:id="function-library-lib.attrsets.collect">
627+ <title><function>lib.attrsets.collect</function></title>
628+
629+ <subtitle><literal>collect :: (Any -> Bool) -> AttrSet -> [Any]</literal>
630+ </subtitle>
631+
632+ <xi:include href="./locations.xml" xpointer="lib.attrsets.collect" />
633+
634+ <para>
635+ Recursively collect sets that verify a given predicate named
636+ <varname>pred</varname> from the set <varname>attrs</varname>. The recursion
637+ stops when <varname>pred</varname> returns <literal>true</literal>.
638+ </para>
639+
640+ <variablelist>
641+ <varlistentry>
642+ <term>
643+ <varname>pred</varname>
644+ </term>
645+ <listitem>
646+ <para>
647+ <literal>Any -> Bool</literal>
648+ </para>
649+ <para>
650+ Given an attribute's value, determine if recursion should stop.
651+ </para>
652+ <variablelist>
653+ <varlistentry>
654+ <term>
655+ <varname>value</varname>
656+ </term>
657+ <listitem>
658+ <para>
659+ The attribute set value.
660+ </para>
661+ </listitem>
662+ </varlistentry>
663+ </variablelist>
664+ </listitem>
665+ </varlistentry>
666+ <varlistentry>
667+ <term>
668+ <varname>attrs</varname>
669+ </term>
670+ <listitem>
671+ <para>
672+ The attribute set to recursively collect.
673+ </para>
674+ </listitem>
675+ </varlistentry>
676+ </variablelist>
677+
678+ <example xml:id="function-library-lib.attrsets.collect-example-lists">
679+ <title>Collecting all lists from an attribute set</title>
680+<programlisting><![CDATA[
681+lib.attrsets.collect isList { a = { b = ["b"]; }; c = [1]; }
682+=> [["b"] [1]]
683+]]></programlisting>
684+ </example>
685+
686+ <example xml:id="function-library-lib.attrsets.collect-example-outpath">
687+ <title>Collecting all attribute-sets which contain the <literal>outPath</literal> attribute name.</title>
688+<programlisting><![CDATA[
689+collect (x: x ? outPath)
690+ { a = { outPath = "a/"; }; b = { outPath = "b/"; }; }
691+=> [{ outPath = "a/"; } { outPath = "b/"; }]
692+]]></programlisting>
693+ </example>
694+ </section>
695+
696+ <section xml:id="function-library-lib.attrsets.nameValuePair">
697+ <title><function>lib.attrsets.nameValuePair</function></title>
698+
699+ <subtitle><literal>nameValuePair :: String -> Any -> AttrSet</literal>
700+ </subtitle>
701+
702+ <xi:include href="./locations.xml" xpointer="lib.attrsets.nameValuePair" />
703+
704+ <para>
705+ Utility function that creates a <literal>{name, value}</literal> pair as
706+ expected by <function>builtins.listToAttrs</function>.
707+ </para>
708+
709+ <variablelist>
710+ <varlistentry>
711+ <term>
712+ <varname>name</varname>
713+ </term>
714+ <listitem>
715+ <para>
716+ The attribute name.
717+ </para>
718+ </listitem>
719+ </varlistentry>
720+ <varlistentry>
721+ <term>
722+ <varname>value</varname>
723+ </term>
724+ <listitem>
725+ <para>
726+ The attribute value.
727+ </para>
728+ </listitem>
729+ </varlistentry>
730+ </variablelist>
731+
732+ <example xml:id="function-library-lib.attrsets.nameValuePair-example">
733+ <title>Creating a name value pair</title>
734+<programlisting><![CDATA[
735+nameValuePair "some" 6
736+=> { name = "some"; value = 6; }
737+]]></programlisting>
738+ </example>
739+ </section>
740+
741+ <section xml:id="function-library-lib.attrsets.mapAttrs">
742+ <title><function>lib.attrsets.mapAttrs</function></title>
743+
744+ <subtitle><literal></literal>
745+ </subtitle>
746+
747+ <xi:include href="./locations.xml" xpointer="lib.attrsets.mapAttrs" />
748+
749+ <para>
750+ Apply a function to each element in an attribute set, creating a new
751+ attribute set.
752+ </para>
753+
754+ <para>
755+ Provides a backwards-compatible interface of
756+ <function>builtins.mapAttrs</function> for Nix version older than 2.1.
757+ </para>
758+
759+ <variablelist>
760+ <varlistentry>
761+ <term>
762+ <varname>fn</varname>
763+ </term>
764+ <listitem>
765+ <para>
766+ <literal>String -> Any -> Any</literal>
767+ </para>
768+ <para>
769+ Given an attribute's name and value, return a new value.
770+ </para>
771+ <variablelist>
772+ <varlistentry>
773+ <term>
774+ <varname>name</varname>
775+ </term>
776+ <listitem>
777+ <para>
778+ The name of the attribute.
779+ </para>
780+ </listitem>
781+ </varlistentry>
782+ <varlistentry>
783+ <term>
784+ <varname>value</varname>
785+ </term>
786+ <listitem>
787+ <para>
788+ The attribute's value.
789+ </para>
790+ </listitem>
791+ </varlistentry>
792+ </variablelist>
793+ </listitem>
794+ </varlistentry>
795+ </variablelist>
796+
797+ <example xml:id="function-library-lib.attrsets.mapAttrs-example">
798+ <title>Modifying each value of an attribute set</title>
799+<programlisting><![CDATA[
800+lib.attrsets.mapAttrs
801+ (name: value: name + "-" value)
802+ { x = "foo"; y = "bar"; }
803+=> { x = "x-foo"; y = "y-bar"; }
804+]]></programlisting>
805+ </example>
806+ </section>
807+
808+ <section xml:id="function-library-lib.attrsets.mapAttrs-prime">
809+ <title><function>lib.attrsets.mapAttrs&apos;</function></title>
810+
811+ <subtitle><literal>mapAttrs' :: (String -> Any -> { name = String; value = Any }) -> AttrSet -> AttrSet</literal>
812+ </subtitle>
813+
814+ <xi:include href="./locations.xml" xpointer="lib.attrsets.mapAttrs-prime" />
815+
816+ <para>
817+ Like <function>mapAttrs</function>, but allows the name of each attribute to
818+ be changed in addition to the value. The applied function should return both
819+ the new name and value as a <function>nameValuePair</function>.
820+ </para>
821+
822+ <variablelist>
823+ <varlistentry>
824+ <term>
825+ <varname>fn</varname>
826+ </term>
827+ <listitem>
828+ <para>
829+ <literal>String -> Any -> { name = String; value = Any }</literal>
830+ </para>
831+ <para>
832+ Given an attribute's name and value, return a new
833+ <link
834+ linkend="function-library-lib.attrsets.nameValuePair">name
835+ value pair</link>.
836+ </para>
837+ <variablelist>
838+ <varlistentry>
839+ <term>
840+ <varname>name</varname>
841+ </term>
842+ <listitem>
843+ <para>
844+ The name of the attribute.
845+ </para>
846+ </listitem>
847+ </varlistentry>
848+ <varlistentry>
849+ <term>
850+ <varname>value</varname>
851+ </term>
852+ <listitem>
853+ <para>
854+ The attribute's value.
855+ </para>
856+ </listitem>
857+ </varlistentry>
858+ </variablelist>
859+ </listitem>
860+ </varlistentry>
861+ <varlistentry>
862+ <term>
863+ <varname>set</varname>
864+ </term>
865+ <listitem>
866+ <para>
867+ The attribute set to map over.
868+ </para>
869+ </listitem>
870+ </varlistentry>
871+ </variablelist>
872+
873+ <example xml:id="function-library-lib.attrsets.mapAttrs-prime-example">
874+ <title>Change the name and value of each attribute of an attribute set</title>
875+<programlisting><![CDATA[
876+lib.attrsets.mapAttrs' (name: value: lib.attrsets.nameValuePair ("foo_" + name) ("bar-" + value))
877+ { x = "a"; y = "b"; }
878+=> { foo_x = "bar-a"; foo_y = "bar-b"; }
879+
880+ ]]></programlisting>
881+ </example>
882+ </section>
883+
884+ <section xml:id="function-library-lib.attrsets.mapAttrsToList">
885+ <title><function>lib.attrsets.mapAttrsToList</function></title>
886+
887+ <subtitle><literal>mapAttrsToList :: (String -> Any -> Any) ->
888+ AttrSet -> Any</literal>
889+ </subtitle>
890+
891+ <xi:include href="./locations.xml" xpointer="lib.attrsets.mapAttrsToList" />
892+
893+ <para>
894+ Call <varname>fn</varname> for each attribute in the given
895+ <varname>set</varname> and return the result in a list.
896+ </para>
897+
898+ <variablelist>
899+ <varlistentry>
900+ <term>
901+ <varname>fn</varname>
902+ </term>
903+ <listitem>
904+ <para>
905+ <literal>String -> Any -> Any</literal>
906+ </para>
907+ <para>
908+ Given an attribute's name and value, return a new value.
909+ </para>
910+ <variablelist>
911+ <varlistentry>
912+ <term>
913+ <varname>name</varname>
914+ </term>
915+ <listitem>
916+ <para>
917+ The name of the attribute.
918+ </para>
919+ </listitem>
920+ </varlistentry>
921+ <varlistentry>
922+ <term>
923+ <varname>value</varname>
924+ </term>
925+ <listitem>
926+ <para>
927+ The attribute's value.
928+ </para>
929+ </listitem>
930+ </varlistentry>
931+ </variablelist>
932+ </listitem>
933+ </varlistentry>
934+ <varlistentry>
935+ <term>
936+ <varname>set</varname>
937+ </term>
938+ <listitem>
939+ <para>
940+ The attribute set to map over.
941+ </para>
942+ </listitem>
943+ </varlistentry>
944+ </variablelist>
945+
946+ <example xml:id="function-library-lib.attrsets.mapAttrsToList-example">
947+ <title>Combine attribute values and names in to a list</title>
948+<programlisting><![CDATA[
949+lib.attrsets.mapAttrsToList (name: value: "${name}=${value}")
950+ { x = "a"; y = "b"; }
951+=> [ "x=a" "y=b" ]
952+]]></programlisting>
953+ </example>
954+ </section>
955+
956+ <section xml:id="function-library-lib.attrsets.mapAttrsRecursive">
957+ <title><function>lib.attrsets.mapAttrsRecursive</function></title>
958+
959+ <subtitle><literal>mapAttrsRecursive :: ([String] > Any -> Any) -> AttrSet -> AttrSet</literal>
960+ </subtitle>
961+
962+ <xi:include href="./locations.xml" xpointer="lib.attrsets.mapAttrsRecursive" />
963+
964+ <para>
965+ Like <function>mapAttrs</function>, except that it recursively applies
966+ itself to attribute sets. Also, the first argument of the argument function
967+ is a <emphasis>list</emphasis> of the names of the containing attributes.
968+ </para>
969+
970+ <variablelist>
971+ <varlistentry>
972+ <term>
973+ <varname>f</varname>
974+ </term>
975+ <listitem>
976+ <para>
977+ <literal>[ String ] -> Any -> Any</literal>
978+ </para>
979+ <para>
980+ Given a list of attribute names and value, return a new value.
981+ </para>
982+ <variablelist>
983+ <varlistentry>
984+ <term>
985+ <varname>name_path</varname>
986+ </term>
987+ <listitem>
988+ <para>
989+ The list of attribute names to this value.
990+ </para>
991+ <para>
992+ For example, the <varname>name_path</varname> for the
993+ <literal>example</literal> string in the attribute set <literal>{ foo
994+ = { bar = "example"; }; }</literal> is <literal>[ "foo" "bar"
995+ ]</literal>.
996+ </para>
997+ </listitem>
998+ </varlistentry>
999+ <varlistentry>
1000+ <term>
1001+ <varname>value</varname>
1002+ </term>
1003+ <listitem>
1004+ <para>
1005+ The attribute's value.
1006+ </para>
1007+ </listitem>
1008+ </varlistentry>
1009+ </variablelist>
1010+ </listitem>
1011+ </varlistentry>
1012+ <varlistentry>
1013+ <term>
1014+ <varname>set</varname>
1015+ </term>
1016+ <listitem>
1017+ <para>
1018+ The attribute set to recursively map over.
1019+ </para>
1020+ </listitem>
1021+ </varlistentry>
1022+ </variablelist>
1023+
1024+ <example xml:id="function-library-lib.attrsets.mapAttrsRecursive-example">
1025+ <title>A contrived example of using <function>lib.attrsets.mapAttrsRecursive</function></title>
1026+<programlisting><![CDATA[
1027+mapAttrsRecursive
1028+ (path: value: concatStringsSep "-" (path ++ [value]))
1029+ {
1030+ n = {
1031+ a = "A";
1032+ m = {
1033+ b = "B";
1034+ c = "C";
1035+ };
1036+ };
1037+ d = "D";
1038+ }
1039+=> {
1040+ n = {
1041+ a = "n-a-A";
1042+ m = {
1043+ b = "n-m-b-B";
1044+ c = "n-m-c-C";
1045+ };
1046+ };
1047+ d = "d-D";
1048+ }
1049+ ]]></programlisting>
1050+ </example>
1051+ </section>
1052+
1053+ <section xml:id="function-library-lib.attrsets.mapAttrsRecursiveCond">
1054+ <title><function>lib.attrsets.mapAttrsRecursiveCond</function></title>
1055+
1056+ <subtitle><literal>mapAttrsRecursiveCond :: (AttrSet -> Bool) -> ([ String ] -> Any -> Any) -> AttrSet -> AttrSet</literal>
1057+ </subtitle>
1058+
1059+ <xi:include href="./locations.xml" xpointer="lib.attrsets.mapAttrsRecursiveCond" />
1060+
1061+ <para>
1062+ Like <function>mapAttrsRecursive</function>, but it takes an additional
1063+ predicate function that tells it whether to recursive into an attribute set.
1064+ If it returns false, <function>mapAttrsRecursiveCond</function> does not
1065+ recurse, but does apply the map function. It is returns true, it does
1066+ recurse, and does not apply the map function.
1067+ </para>
1068+
1069+ <variablelist>
1070+ <varlistentry>
1071+ <term>
1072+ <varname>cond</varname>
1073+ </term>
1074+ <listitem>
1075+ <para>
1076+ <literal>(AttrSet -> Bool)</literal>
1077+ </para>
1078+ <para>
1079+ Determine if <function>mapAttrsRecursive</function> should recurse deeper
1080+ in to the attribute set.
1081+ </para>
1082+ <variablelist>
1083+ <varlistentry>
1084+ <term>
1085+ <varname>attributeset</varname>
1086+ </term>
1087+ <listitem>
1088+ <para>
1089+ An attribute set.
1090+ </para>
1091+ </listitem>
1092+ </varlistentry>
1093+ </variablelist>
1094+ </listitem>
1095+ </varlistentry>
1096+ <varlistentry>
1097+ <term>
1098+ <varname>f</varname>
1099+ </term>
1100+ <listitem>
1101+ <para>
1102+ <literal>[ String ] -> Any -> Any</literal>
1103+ </para>
1104+ <para>
1105+ Given a list of attribute names and value, return a new value.
1106+ </para>
1107+ <variablelist>
1108+ <varlistentry>
1109+ <term>
1110+ <varname>name_path</varname>
1111+ </term>
1112+ <listitem>
1113+ <para>
1114+ The list of attribute names to this value.
1115+ </para>
1116+ <para>
1117+ For example, the <varname>name_path</varname> for the
1118+ <literal>example</literal> string in the attribute set <literal>{ foo
1119+ = { bar = "example"; }; }</literal> is <literal>[ "foo" "bar"
1120+ ]</literal>.
1121+ </para>
1122+ </listitem>
1123+ </varlistentry>
1124+ <varlistentry>
1125+ <term>
1126+ <varname>value</varname>
1127+ </term>
1128+ <listitem>
1129+ <para>
1130+ The attribute's value.
1131+ </para>
1132+ </listitem>
1133+ </varlistentry>
1134+ </variablelist>
1135+ </listitem>
1136+ </varlistentry>
1137+ <varlistentry>
1138+ <term>
1139+ <varname>set</varname>
1140+ </term>
1141+ <listitem>
1142+ <para>
1143+ The attribute set to recursively map over.
1144+ </para>
1145+ </listitem>
1146+ </varlistentry>
1147+ </variablelist>
1148+
1149+ <example xml:id="function-library-lib.attrsets.mapAttrsRecursiveCond-example">
1150+ <title>Only convert attribute values to JSON if the containing attribute set is marked for recursion</title>
1151+<programlisting><![CDATA[
1152+lib.attrsets.mapAttrsRecursiveCond
1153+ ({ recurse ? false, ... }: recurse)
1154+ (name: value: builtins.toJSON value)
1155+ {
1156+ dorecur = {
1157+ recurse = true;
1158+ hello = "there";
1159+ };
1160+ dontrecur = {
1161+ converted-to- = "json";
1162+ };
1163+ }
1164+=> {
1165+ dorecur = {
1166+ hello = "\"there\"";
1167+ recurse = "true";
1168+ };
1169+ dontrecur = "{\"converted-to\":\"json\"}";
1170+ }
1171+ ]]></programlisting>
1172+ </example>
1173+ </section>
1174+
1175+ <section xml:id="function-library-lib.attrsets.genAttrs">
1176+ <title><function>lib.attrsets.genAttrs</function></title>
1177+
1178+ <subtitle><literal>genAttrs :: [ String ] -> (String -> Any) -> AttrSet</literal>
1179+ </subtitle>
1180+
1181+ <xi:include href="./locations.xml" xpointer="lib.attrsets.genAttrs" />
1182+
1183+ <para>
1184+ Generate an attribute set by mapping a function over a list of attribute
1185+ names.
1186+ </para>
1187+
1188+ <variablelist>
1189+ <varlistentry>
1190+ <term>
1191+ <varname>names</varname>
1192+ </term>
1193+ <listitem>
1194+ <para>
1195+ Names of values in the resulting attribute set.
1196+ </para>
1197+ </listitem>
1198+ </varlistentry>
1199+ <varlistentry>
1200+ <term>
1201+ <varname>f</varname>
1202+ </term>
1203+ <listitem>
1204+ <para>
1205+ <literal>String -> Any</literal>
1206+ </para>
1207+ <para>
1208+ Takes the name of the attribute and return the attribute's value.
1209+ </para>
1210+ <variablelist>
1211+ <varlistentry>
1212+ <term>
1213+ <varname>name</varname>
1214+ </term>
1215+ <listitem>
1216+ <para>
1217+ The name of the attribute to generate a value for.
1218+ </para>
1219+ </listitem>
1220+ </varlistentry>
1221+ </variablelist>
1222+ </listitem>
1223+ </varlistentry>
1224+ </variablelist>
1225+
1226+ <example xml:id="function-library-lib.attrsets.genAttrs-example">
1227+ <title>Generate an attrset based on names only</title>
1228+<programlisting><![CDATA[
1229+lib.attrsets.genAttrs [ "foo" "bar" ] (name: "x_${name}")
1230+=> { foo = "x_foo"; bar = "x_bar"; }
1231+ ]]></programlisting>
1232+ </example>
1233+ </section>
1234+
1235+ <section xml:id="function-library-lib.attrsets.isDerivation">
1236+ <title><function>lib.attrsets.isDerivation</function></title>
1237+
1238+ <subtitle><literal>isDerivation :: Any -> Bool</literal>
1239+ </subtitle>
1240+
1241+ <xi:include href="./locations.xml" xpointer="lib.attrsets.isDerivation" />
1242+
1243+ <para>
1244+ Check whether the argument is a derivation. Any set with <code>{ type =
1245+ "derivation"; }</code> counts as a derivation.
1246+ </para>
1247+
1248+ <variablelist>
1249+ <varlistentry>
1250+ <term>
1251+ <varname>value</varname>
1252+ </term>
1253+ <listitem>
1254+ <para>
1255+ The value which is possibly a derivation.
1256+ </para>
1257+ </listitem>
1258+ </varlistentry>
1259+ </variablelist>
1260+
1261+ <example xml:id="function-library-lib.attrsets.isDerivation-example-true">
1262+ <title>A package is a derivation</title>
1263+<programlisting><![CDATA[
1264+lib.attrsets.isDerivation (import <nixpkgs> {}).ruby
1265+=> true
1266+ ]]></programlisting>
1267+ </example>
1268+
1269+ <example xml:id="function-library-lib.attrsets.isDerivation-example-false">
1270+ <title>Anything else is not a derivation</title>
1271+<programlisting><![CDATA[
1272+lib.attrsets.isDerivation "foobar"
1273+=> false
1274+ ]]></programlisting>
1275+ </example>
1276+ </section>
1277+
1278+ <section xml:id="function-library-lib.attrsets.toDerivation">
1279+ <title><function>lib.attrsets.toDerivation</function></title>
1280+
1281+ <subtitle><literal>toDerivation :: Path -> Derivation</literal>
1282+ </subtitle>
1283+
1284+ <xi:include href="./locations.xml" xpointer="lib.attrsets.toDerivation" />
1285+
1286+ <para>
1287+ Converts a store path to a fake derivation.
1288+ </para>
1289+
1290+ <variablelist>
1291+ <varlistentry>
1292+ <term>
1293+ <varname>path</varname>
1294+ </term>
1295+ <listitem>
1296+ <para>
1297+ A store path to convert to a derivation.
1298+ </para>
1299+ </listitem>
1300+ </varlistentry>
1301+ </variablelist>
1302+ </section>
1303+
1304+ <section xml:id="function-library-lib.attrsets.optionalAttrs">
1305+ <title><function>lib.attrsets.optionalAttrs</function></title>
1306+
1307+ <subtitle><literal>optionalAttrs :: Bool -> AttrSet</literal>
1308+ </subtitle>
1309+
1310+ <xi:include href="./locations.xml" xpointer="lib.attrsets.optionalAttrs" />
1311+
1312+ <para>
1313+ Conditionally return an attribute set or an empty attribute set.
1314+ </para>
1315+
1316+ <variablelist>
1317+ <varlistentry>
1318+ <term>
1319+ <varname>cond</varname>
1320+ </term>
1321+ <listitem>
1322+ <para>
1323+ Condition under which the <varname>as</varname> attribute set is
1324+ returned.
1325+ </para>
1326+ </listitem>
1327+ </varlistentry>
1328+ <varlistentry>
1329+ <term>
1330+ <varname>as</varname>
1331+ </term>
1332+ <listitem>
1333+ <para>
1334+ The attribute set to return if <varname>cond</varname> is true.
1335+ </para>
1336+ </listitem>
1337+ </varlistentry>
1338+ </variablelist>
1339+
1340+ <example xml:id="function-library-lib.attrsets.optionalAttrs-example-true">
1341+ <title>Return the provided attribute set when <varname>cond</varname> is true</title>
1342+<programlisting><![CDATA[
1343+lib.attrsets.optionalAttrs true { my = "set"; }
1344+=> { my = "set"; }
1345+ ]]></programlisting>
1346+ </example>
1347+
1348+ <example xml:id="function-library-lib.attrsets.optionalAttrs-example-false">
1349+ <title>Return an empty attribute set when <varname>cond</varname> is false</title>
1350+<programlisting><![CDATA[
1351+lib.attrsets.optionalAttrs false { my = "set"; }
1352+=> { }
1353+ ]]></programlisting>
1354+ </example>
1355+ </section>
1356+
1357+ <section xml:id="function-library-lib.attrsets.zipAttrsWithNames">
1358+ <title><function>lib.attrsets.zipAttrsWithNames</function></title>
1359+
1360+ <subtitle><literal>zipAttrsWithNames :: [ String ] -> (String -> [ Any ] -> Any) -> [ AttrSet ] -> AttrSet</literal>
1361+ </subtitle>
1362+
1363+ <xi:include href="./locations.xml" xpointer="lib.attrsets.zipAttrsWithNames" />
1364+
1365+ <para>
1366+ Merge sets of attributes and use the function <varname>f</varname> to merge
1367+ attribute values where the attribute name is in <varname>names</varname>.
1368+ </para>
1369+
1370+ <variablelist>
1371+ <varlistentry>
1372+ <term>
1373+ <varname>names</varname>
1374+ </term>
1375+ <listitem>
1376+ <para>
1377+ A list of attribute names to zip.
1378+ </para>
1379+ </listitem>
1380+ </varlistentry>
1381+ <varlistentry>
1382+ <term>
1383+ <varname>f</varname>
1384+ </term>
1385+ <listitem>
1386+ <para>
1387+ <literal>(String -> [ Any ] -> Any</literal>
1388+ </para>
1389+ <para>
1390+ Accepts an attribute name, all the values, and returns a combined value.
1391+ </para>
1392+ <variablelist>
1393+ <varlistentry>
1394+ <term>
1395+ <varname>name</varname>
1396+ </term>
1397+ <listitem>
1398+ <para>
1399+ The name of the attribute each value came from.
1400+ </para>
1401+ </listitem>
1402+ </varlistentry>
1403+ <varlistentry>
1404+ <term>
1405+ <varname>vs</varname>
1406+ </term>
1407+ <listitem>
1408+ <para>
1409+ A list of values collected from the list of attribute sets.
1410+ </para>
1411+ </listitem>
1412+ </varlistentry>
1413+ </variablelist>
1414+ </listitem>
1415+ </varlistentry>
1416+ <varlistentry>
1417+ <term>
1418+ <varname>sets</varname>
1419+ </term>
1420+ <listitem>
1421+ <para>
1422+ A list of attribute sets to zip together.
1423+ </para>
1424+ </listitem>
1425+ </varlistentry>
1426+ </variablelist>
1427+
1428+ <example xml:id="function-library-lib.attrsets.zipAttrsWithNames-example">
1429+ <title>Summing a list of attribute sets of numbers</title>
1430+<programlisting><![CDATA[
1431+lib.attrsets.zipAttrsWithNames
1432+ [ "a" "b" ]
1433+ (name: vals: "${name} ${toString (builtins.foldl' (a: b: a + b) 0 vals)}")
1434+ [
1435+ { a = 1; b = 1; c = 1; }
1436+ { a = 10; }
1437+ { b = 100; }
1438+ { c = 1000; }
1439+ ]
1440+=> { a = "a 11"; b = "b 101"; }
1441+ ]]></programlisting>
1442+ </example>
1443+ </section>
1444+
1445+ <section xml:id="function-library-lib.attrsets.zipAttrsWith">
1446+ <title><function>lib.attrsets.zipAttrsWith</function></title>
1447+
1448+ <subtitle><literal>zipAttrsWith :: (String -> [ Any ] -> Any) -> [ AttrSet ] -> AttrSet</literal>
1449+ </subtitle>
1450+
1451+ <xi:include href="./locations.xml" xpointer="lib.attrsets.zipAttrsWith" />
1452+
1453+ <para>
1454+ Merge sets of attributes and use the function <varname>f</varname> to merge
1455+ attribute values. Similar to
1456+ <xref
1457+ linkend="function-library-lib.attrsets.zipAttrsWithNames" /> where
1458+ all key names are passed for <varname>names</varname>.
1459+ </para>
1460+
1461+ <variablelist>
1462+ <varlistentry>
1463+ <term>
1464+ <varname>f</varname>
1465+ </term>
1466+ <listitem>
1467+ <para>
1468+ <literal>(String -> [ Any ] -> Any</literal>
1469+ </para>
1470+ <para>
1471+ Accepts an attribute name, all the values, and returns a combined value.
1472+ </para>
1473+ <variablelist>
1474+ <varlistentry>
1475+ <term>
1476+ <varname>name</varname>
1477+ </term>
1478+ <listitem>
1479+ <para>
1480+ The name of the attribute each value came from.
1481+ </para>
1482+ </listitem>
1483+ </varlistentry>
1484+ <varlistentry>
1485+ <term>
1486+ <varname>vs</varname>
1487+ </term>
1488+ <listitem>
1489+ <para>
1490+ A list of values collected from the list of attribute sets.
1491+ </para>
1492+ </listitem>
1493+ </varlistentry>
1494+ </variablelist>
1495+ </listitem>
1496+ </varlistentry>
1497+ <varlistentry>
1498+ <term>
1499+ <varname>sets</varname>
1500+ </term>
1501+ <listitem>
1502+ <para>
1503+ A list of attribute sets to zip together.
1504+ </para>
1505+ </listitem>
1506+ </varlistentry>
1507+ </variablelist>
1508+
1509+ <example xml:id="function-library-lib.attrsets.zipAttrsWith-example">
1510+ <title>Summing a list of attribute sets of numbers</title>
1511+<programlisting><![CDATA[
1512+lib.attrsets.zipAttrsWith
1513+ (name: vals: "${name} ${toString (builtins.foldl' (a: b: a + b) 0 vals)}")
1514+ [
1515+ { a = 1; b = 1; c = 1; }
1516+ { a = 10; }
1517+ { b = 100; }
1518+ { c = 1000; }
1519+ ]
1520+=> { a = "a 11"; b = "b 101"; c = "c 1001"; }
1521+ ]]></programlisting>
1522+ </example>
1523+ </section>
1524+
1525+ <section xml:id="function-library-lib.attrsets.zipAttrs">
1526+ <title><function>lib.attrsets.zipAttrs</function></title>
1527+
1528+ <subtitle><literal>zipAttrsWith :: [ AttrSet ] -> AttrSet</literal>
1529+ </subtitle>
1530+
1531+ <xi:include href="./locations.xml" xpointer="lib.attrsets.zipAttrs" />
1532+
1533+ <para>
1534+ Merge sets of attributes and combine each attribute value in to a list.
1535+ Similar to <xref linkend="function-library-lib.attrsets.zipAttrsWith" />
1536+ where the merge function returns a list of all values.
1537+ </para>
1538+
1539+ <variablelist>
1540+ <varlistentry>
1541+ <term>
1542+ <varname>sets</varname>
1543+ </term>
1544+ <listitem>
1545+ <para>
1546+ A list of attribute sets to zip together.
1547+ </para>
1548+ </listitem>
1549+ </varlistentry>
1550+ </variablelist>
1551+
1552+ <example xml:id="function-library-lib.attrsets.zipAttrs-example">
1553+ <title>Combining a list of attribute sets</title>
1554+<programlisting><![CDATA[
1555+lib.attrsets.zipAttrs
1556+ [
1557+ { a = 1; b = 1; c = 1; }
1558+ { a = 10; }
1559+ { b = 100; }
1560+ { c = 1000; }
1561+ ]
1562+=> { a = [ 1 10 ]; b = [ 1 100 ]; c = [ 1 1000 ]; }
1563+ ]]></programlisting>
1564+ </example>
1565+ </section>
1566+
1567+ <section xml:id="function-library-lib.attrsets.recursiveUpdateUntil">
1568+ <title><function>lib.attrsets.recursiveUpdateUntil</function></title>
1569+
1570+ <subtitle><literal>recursiveUpdateUntil :: ( [ String ] -> AttrSet -> AttrSet -> Bool ) -> AttrSet -> AttrSet -> AttrSet</literal>
1571+ </subtitle>
1572+
1573+ <xi:include href="./locations.xml" xpointer="lib.attrsets.recursiveUpdateUntil" />
1574+
1575+ <para>
1576+ Does the same as the update operator <literal>//</literal> except that
1577+ attributes are merged until the given predicate is verified. The predicate
1578+ should accept 3 arguments which are the path to reach the attribute, a part
1579+ of the first attribute set and a part of the second attribute set. When the
1580+ predicate is verified, the value of the first attribute set is replaced by
1581+ the value of the second attribute set.
1582+ </para>
1583+
1584+ <variablelist>
1585+ <varlistentry>
1586+ <term>
1587+ <varname>pred</varname>
1588+ </term>
1589+ <listitem>
1590+ <para>
1591+ <literal>[ String ] -> AttrSet -> AttrSet -> Bool</literal>
1592+ </para>
1593+ <variablelist>
1594+ <varlistentry>
1595+ <term>
1596+ <varname>path</varname>
1597+ </term>
1598+ <listitem>
1599+ <para>
1600+ The path to the values in the left and right hand sides.
1601+ </para>
1602+ </listitem>
1603+ </varlistentry>
1604+ <varlistentry>
1605+ <term>
1606+ <varname>l</varname>
1607+ </term>
1608+ <listitem>
1609+ <para>
1610+ The left hand side value.
1611+ </para>
1612+ </listitem>
1613+ </varlistentry>
1614+ <varlistentry>
1615+ <term>
1616+ <varname>r</varname>
1617+ </term>
1618+ <listitem>
1619+ <para>
1620+ The right hand side value.
1621+ </para>
1622+ </listitem>
1623+ </varlistentry>
1624+ </variablelist>
1625+ </listitem>
1626+ </varlistentry>
1627+ <varlistentry>
1628+ <term>
1629+ <varname>lhs</varname>
1630+ </term>
1631+ <listitem>
1632+ <para>
1633+ The left hand attribute set of the merge.
1634+ </para>
1635+ </listitem>
1636+ </varlistentry>
1637+ <varlistentry>
1638+ <term>
1639+ <varname>rhs</varname>
1640+ </term>
1641+ <listitem>
1642+ <para>
1643+ The right hand attribute set of the merge.
1644+ </para>
1645+ </listitem>
1646+ </varlistentry>
1647+ </variablelist>
1648+
1649+ <example xml:id="function-library-lib.attrsets.recursiveUpdateUntil-example">
1650+ <title>Recursively merging two attribute sets</title>
1651+<programlisting><![CDATA[
1652+lib.attrsets.recursiveUpdateUntil (path: l: r: path == ["foo"])
1653+ {
1654+ # first attribute set
1655+ foo.bar = 1;
1656+ foo.baz = 2;
1657+ bar = 3;
1658+ }
1659+ {
1660+ #second attribute set
1661+ foo.bar = 1;
1662+ foo.quz = 2;
1663+ baz = 4;
1664+ }
1665+=> {
1666+ foo.bar = 1; # 'foo.*' from the second set
1667+ foo.quz = 2; #
1668+ bar = 3; # 'bar' from the first set
1669+ baz = 4; # 'baz' from the second set
1670+}
1671+ ]]></programlisting>
1672+ </example>
1673+ </section>
1674+
1675+ <section xml:id="function-library-lib.attrsets.recursiveUpdate">
1676+ <title><function>lib.attrsets.recursiveUpdate</function></title>
1677+
1678+ <subtitle><literal>recursiveUpdate :: AttrSet -> AttrSet -> AttrSet</literal>
1679+ </subtitle>
1680+
1681+ <xi:include href="./locations.xml" xpointer="lib.attrsets.recursiveUpdate" />
1682+
1683+ <para>
1684+ A recursive variant of the update operator <literal>//</literal>. The
1685+ recursion stops when one of the attribute values is not an attribute set, in
1686+ which case the right hand side value takes precedence over the left hand
1687+ side value.
1688+ </para>
1689+
1690+ <variablelist>
1691+ <varlistentry>
1692+ <term>
1693+ <varname>lhs</varname>
1694+ </term>
1695+ <listitem>
1696+ <para>
1697+ The left hand attribute set of the merge.
1698+ </para>
1699+ </listitem>
1700+ </varlistentry>
1701+ <varlistentry>
1702+ <term>
1703+ <varname>rhs</varname>
1704+ </term>
1705+ <listitem>
1706+ <para>
1707+ The right hand attribute set of the merge.
1708+ </para>
1709+ </listitem>
1710+ </varlistentry>
1711+ </variablelist>
1712+
1713+ <example xml:id="function-library-lib.attrsets.recursiveUpdate-example">
1714+ <title>Recursively merging two attribute sets</title>
1715+<programlisting><![CDATA[
1716+recursiveUpdate
1717+ {
1718+ boot.loader.grub.enable = true;
1719+ boot.loader.grub.device = "/dev/hda";
1720+ }
1721+ {
1722+ boot.loader.grub.device = "";
1723+ }
1724+=> {
1725+ boot.loader.grub.enable = true;
1726+ boot.loader.grub.device = "";
1727+}
1728+]]></programlisting>
1729+ </example>
1730+ </section>
1731+</section>
doc/functions/overrides.xmlnew file+212
@@ -0,0 +1,212 @@
1+<section xmlns="http://docbook.org/ns/docbook"
2+ xmlns:xlink="http://www.w3.org/1999/xlink"
3+ xmlns:xi="http://www.w3.org/2001/XInclude"
4+ xml:id="sec-overrides">
5+ <title>Overriding</title>
6+
7+ <para>
8+ Sometimes one wants to override parts of <literal>nixpkgs</literal>, e.g.
9+ derivation attributes, the results of derivations.
10+ </para>
11+
12+ <para>
13+ These functions are used to make changes to packages, returning only single
14+ packages. <link xlink:href="#chap-overlays">Overlays</link>, on the other
15+ hand, can be used to combine the overridden packages across the entire
16+ package set of Nixpkgs.
17+ </para>
18+
19+ <section xml:id="sec-pkg-override">
20+ <title>&lt;pkg&gt;.override</title>
21+
22+ <para>
23+ The function <varname>override</varname> is usually available for all the
24+ derivations in the nixpkgs expression (<varname>pkgs</varname>).
25+ </para>
26+
27+ <para>
28+ It is used to override the arguments passed to a function.
29+ </para>
30+
31+ <para>
32+ Example usages:
33+<programlisting>pkgs.foo.override { arg1 = val1; arg2 = val2; ... }</programlisting>
34+<!-- TODO: move below programlisting to a new section about extending and overlays
35+ and reference it
36+ -->
37+<programlisting>
38+import pkgs.path { overlays = [ (self: super: {
39+ foo = super.foo.override { barSupport = true ; };
40+ })]};
41+</programlisting>
42+<programlisting>
43+mypkg = pkgs.callPackage ./mypkg.nix {
44+ mydep = pkgs.mydep.override { ... };
45+ }
46+</programlisting>
47+ </para>
48+
49+ <para>
50+ In the first example, <varname>pkgs.foo</varname> is the result of a
51+ function call with some default arguments, usually a derivation. Using
52+ <varname>pkgs.foo.override</varname> will call the same function with the
53+ given new arguments.
54+ </para>
55+ </section>
56+
57+ <section xml:id="sec-pkg-overrideAttrs">
58+ <title>&lt;pkg&gt;.overrideAttrs</title>
59+
60+ <para>
61+ The function <varname>overrideAttrs</varname> allows overriding the
62+ attribute set passed to a <varname>stdenv.mkDerivation</varname> call,
63+ producing a new derivation based on the original one. This function is
64+ available on all derivations produced by the
65+ <varname>stdenv.mkDerivation</varname> function, which is most packages in
66+ the nixpkgs expression <varname>pkgs</varname>.
67+ </para>
68+
69+ <para>
70+ Example usage:
71+<programlisting>
72+helloWithDebug = pkgs.hello.overrideAttrs (oldAttrs: rec {
73+ separateDebugInfo = true;
74+});
75+</programlisting>
76+ </para>
77+
78+ <para>
79+ In the above example, the <varname>separateDebugInfo</varname> attribute is
80+ overridden to be true, thus building debug info for
81+ <varname>helloWithDebug</varname>, while all other attributes will be
82+ retained from the original <varname>hello</varname> package.
83+ </para>
84+
85+ <para>
86+ The argument <varname>oldAttrs</varname> is conventionally used to refer to
87+ the attr set originally passed to <varname>stdenv.mkDerivation</varname>.
88+ </para>
89+
90+ <note>
91+ <para>
92+ Note that <varname>separateDebugInfo</varname> is processed only by the
93+ <varname>stdenv.mkDerivation</varname> function, not the generated, raw Nix
94+ derivation. Thus, using <varname>overrideDerivation</varname> will not work
95+ in this case, as it overrides only the attributes of the final derivation.
96+ It is for this reason that <varname>overrideAttrs</varname> should be
97+ preferred in (almost) all cases to <varname>overrideDerivation</varname>,
98+ i.e. to allow using <varname>stdenv.mkDerivation</varname> to process input
99+ arguments, as well as the fact that it is easier to use (you can use the
100+ same attribute names you see in your Nix code, instead of the ones
101+ generated (e.g. <varname>buildInputs</varname> vs
102+ <varname>nativeBuildInputs</varname>), and it involves less typing).
103+ </para>
104+ </note>
105+ </section>
106+
107+ <section xml:id="sec-pkg-overrideDerivation">
108+ <title>&lt;pkg&gt;.overrideDerivation</title>
109+
110+ <warning>
111+ <para>
112+ You should prefer <varname>overrideAttrs</varname> in almost all cases, see
113+ its documentation for the reasons why.
114+ <varname>overrideDerivation</varname> is not deprecated and will continue
115+ to work, but is less nice to use and does not have as many abilities as
116+ <varname>overrideAttrs</varname>.
117+ </para>
118+ </warning>
119+
120+ <warning>
121+ <para>
122+ Do not use this function in Nixpkgs as it evaluates a Derivation before
123+ modifying it, which breaks package abstraction and removes error-checking
124+ of function arguments. In addition, this evaluation-per-function
125+ application incurs a performance penalty, which can become a problem if
126+ many overrides are used. It is only intended for ad-hoc customisation, such
127+ as in <filename>~/.config/nixpkgs/config.nix</filename>.
128+ </para>
129+ </warning>
130+
131+ <para>
132+ The function <varname>overrideDerivation</varname> creates a new derivation
133+ based on an existing one by overriding the original's attributes with the
134+ attribute set produced by the specified function. This function is available
135+ on all derivations defined using the <varname>makeOverridable</varname>
136+ function. Most standard derivation-producing functions, such as
137+ <varname>stdenv.mkDerivation</varname>, are defined using this function,
138+ which means most packages in the nixpkgs expression,
139+ <varname>pkgs</varname>, have this function.
140+ </para>
141+
142+ <para>
143+ Example usage:
144+<programlisting>
145+mySed = pkgs.gnused.overrideDerivation (oldAttrs: {
146+ name = "sed-4.2.2-pre";
147+ src = fetchurl {
148+ url = ftp://alpha.gnu.org/gnu/sed/sed-4.2.2-pre.tar.bz2;
149+ sha256 = "11nq06d131y4wmf3drm0yk502d2xc6n5qy82cg88rb9nqd2lj41k";
150+ };
151+ patches = [];
152+});
153+</programlisting>
154+ </para>
155+
156+ <para>
157+ In the above example, the <varname>name</varname>, <varname>src</varname>,
158+ and <varname>patches</varname> of the derivation will be overridden, while
159+ all other attributes will be retained from the original derivation.
160+ </para>
161+
162+ <para>
163+ The argument <varname>oldAttrs</varname> is used to refer to the attribute
164+ set of the original derivation.
165+ </para>
166+
167+ <note>
168+ <para>
169+ A package's attributes are evaluated *before* being modified by the
170+ <varname>overrideDerivation</varname> function. For example, the
171+ <varname>name</varname> attribute reference in <varname>url =
172+ "mirror://gnu/hello/${name}.tar.gz";</varname> is filled-in *before* the
173+ <varname>overrideDerivation</varname> function modifies the attribute set.
174+ This means that overriding the <varname>name</varname> attribute, in this
175+ example, *will not* change the value of the <varname>url</varname>
176+ attribute. Instead, we need to override both the <varname>name</varname>
177+ *and* <varname>url</varname> attributes.
178+ </para>
179+ </note>
180+ </section>
181+
182+ <section xml:id="sec-lib-makeOverridable">
183+ <title>lib.makeOverridable</title>
184+
185+ <para>
186+ The function <varname>lib.makeOverridable</varname> is used to make the
187+ result of a function easily customizable. This utility only makes sense for
188+ functions that accept an argument set and return an attribute set.
189+ </para>
190+
191+ <para>
192+ Example usage:
193+<programlisting>
194+f = { a, b }: { result = a+b; };
195+c = lib.makeOverridable f { a = 1; b = 2; };
196+</programlisting>
197+ </para>
198+
199+ <para>
200+ The variable <varname>c</varname> is the value of the <varname>f</varname>
201+ function applied with some default arguments. Hence the value of
202+ <varname>c.result</varname> is <literal>3</literal>, in this example.
203+ </para>
204+
205+ <para>
206+ The variable <varname>c</varname> however also has some additional
207+ functions, like <link linkend="sec-pkg-override">c.override</link> which can
208+ be used to override the default arguments. In this example the value of
209+ <varname>(c.override { a = 4; }).result</varname> is 6.
210+ </para>
211+ </section>
212+</section>
doc/functions/shell.xmlnew file+26
@@ -0,0 +1,26 @@
1+<section xmlns="http://docbook.org/ns/docbook"
2+ xmlns:xlink="http://www.w3.org/1999/xlink"
3+ xmlns:xi="http://www.w3.org/2001/XInclude"
4+ xml:id="sec-pkgs-mkShell">
5+ <title>pkgs.mkShell</title>
6+
7+ <para>
8+ <function>pkgs.mkShell</function> is a special kind of derivation that is
9+ only useful when using it combined with <command>nix-shell</command>. It will
10+ in fact fail to instantiate when invoked with <command>nix-build</command>.
11+ </para>
12+
13+ <section xml:id="sec-pkgs-mkShell-usage">
14+ <title>Usage</title>
15+
16+<programlisting><![CDATA[
17+{ pkgs ? import <nixpkgs> {} }:
18+pkgs.mkShell {
19+ # this will make all the build inputs from hello and gnutar
20+ # available to the shell environment
21+ inputsFrom = with pkgs; [ hello gnutar ];
22+ buildInputs = [ pkgs.gnumake ];
23+}
24+]]></programlisting>
25+ </section>
26+</section>
doc/introduction.chapter.mdnew file+51
@@ -0,0 +1,51 @@
1+---
2+title: Introduction
3+author: Frederik Rietdijk
4+date: 2015-11-25
5+---
6+
7+# Introduction
8+
9+The Nix Packages collection (Nixpkgs) is a set of thousands of packages for the
10+[Nix package manager](http://nixos.org/nix/), released under a
11+[permissive MIT/X11 license](https://github.com/NixOS/nixpkgs/blob/master/COPYING).
12+Packages are available for several platforms, and can be used with the Nix
13+package manager on most GNU/Linux distributions as well as NixOS.
14+
15+This manual primarily describes how to write packages for the Nix Packages collection
16+(Nixpkgs). Thus it’s mainly for packagers and developers who want to add packages to
17+Nixpkgs. If you like to learn more about the Nix package manager and the Nix
18+expression language, then you are kindly referred to the [Nix manual](http://nixos.org/nix/manual/).
19+
20+## Overview of Nixpkgs
21+
22+Nix expressions describe how to build packages from source and are collected in
23+the [nixpkgs repository](https://github.com/NixOS/nixpkgs). Also included in the
24+collection are Nix expressions for
25+[NixOS modules](http://nixos.org/nixos/manual/index.html#sec-writing-modules).
26+With these expressions the Nix package manager can build binary packages.
27+
28+Packages, including the Nix packages collection, are distributed through
29+[channels](http://nixos.org/nix/manual/#sec-channels). The collection is
30+distributed for users of Nix on non-NixOS distributions through the channel
31+`nixpkgs`. Users of NixOS generally use one of the `nixos-*` channels, e.g.
32+`nixos-16.03`, which includes all packages and modules for the stable NixOS
33+16.03. Stable NixOS releases are generally only given
34+security updates. More up to date packages and modules are available via the
35+`nixos-unstable` channel.
36+
37+Both `nixos-unstable` and `nixpkgs` follow the `master` branch of the Nixpkgs
38+repository, although both do lag the `master` branch by generally
39+[a couple of days](http://howoldis.herokuapp.com/). Updates to a channel are
40+distributed as soon as all tests for that channel pass, e.g.
41+[this table](http://hydra.nixos.org/job/nixpkgs/trunk/unstable#tabs-constituents)
42+shows the status of tests for the `nixpkgs` channel.
43+
44+The tests are conducted by a cluster called [Hydra](http://nixos.org/hydra/),
45+which also builds binary packages from the Nix expressions in Nixpkgs for
46+`x86_64-linux`, `i686-linux` and `x86_64-darwin`.
47+The binaries are made available via a [binary cache](https://cache.nixos.org).
48+
49+The current Nix expressions of the channels are available in the
50+[`nixpkgs-channels`](https://github.com/NixOS/nixpkgs-channels) repository,
51+which has branches corresponding to the available channels.
doc/introduction.mddeleted−51
@@ -1,51 +0,0 @@
1−---
2−title: Introduction
3−author: Frederik Rietdijk
4−date: 2015-11-25
5−---
6−
7−# Introduction
8−
9−The Nix Packages collection (Nixpkgs) is a set of thousands of packages for the
10−[Nix package manager](http://nixos.org/nix/), released under a
11−[permissive MIT/X11 license](https://github.com/NixOS/nixpkgs/blob/master/COPYING).
12−Packages are available for several platforms, and can be used with the Nix
13−package manager on most GNU/Linux distributions as well as NixOS.
14−
15−This manual primarily describes how to write packages for the Nix Packages collection
16−(Nixpkgs). Thus it’s mainly for packagers and developers who want to add packages to
17−Nixpkgs. If you like to learn more about the Nix package manager and the Nix
18−expression language, then you are kindly referred to the [Nix manual](http://nixos.org/nix/manual/).
19−
20−## Overview of Nixpkgs
21−
22−Nix expressions describe how to build packages from source and are collected in
23−the [nixpkgs repository](https://github.com/NixOS/nixpkgs). Also included in the
24−collection are Nix expressions for
25−[NixOS modules](http://nixos.org/nixos/manual/index.html#sec-writing-modules).
26−With these expressions the Nix package manager can build binary packages.
27−
28−Packages, including the Nix packages collection, are distributed through
29−[channels](http://nixos.org/nix/manual/#sec-channels). The collection is
30−distributed for users of Nix on non-NixOS distributions through the channel
31−`nixpkgs`. Users of NixOS generally use one of the `nixos-*` channels, e.g.
32−`nixos-16.03`, which includes all packages and modules for the stable NixOS
33−16.03. The purpose of stable NixOS releases are generally only given
34−security updates. More up to date packages and modules are available via the
35−`nixos-unstable` channel.
36−
37−Both `nixos-unstable` and `nixpkgs` follow the `master` branch of the Nixpkgs
38−repository, although both do lag the `master` branch by generally
39−[a couple of days](http://howoldis.herokuapp.com/). Updates to a channel are
40−distributed as soon as all tests for that channel pass, e.g.
41−[this table](http://hydra.nixos.org/job/nixpkgs/trunk/unstable#tabs-constituents)
42−shows the status of tests for the `nixpkgs` channel.
43−
44−The tests are conducted by a cluster called [Hydra](http://nixos.org/hydra/),
45−which also builds binary packages from the Nix expressions in Nixpkgs for
46−`x86_64-linux`, `i686-linux` and `x86_64-darwin`.
47−The binaries are made available via a [binary cache](https://cache.nixos.org).
48−
49−The current Nix expressions of the channels are available in the
50−[`nixpkgs-channels`](https://github.com/NixOS/nixpkgs-channels) repository,
51−which has branches corresponding to the available channels.
doc/languages-frameworks/beam.xml+277−223
@@ -1,124 +1,137 @@
11<section xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="sec-beam">
4+ <title>BEAM Languages (Erlang, Elixir &amp; LFE)</title>
45
5− <title>BEAM Languages (Erlang, Elixir &amp; LFE)</title>
6− <section xml:id="beam-introduction">
7− <title>Introduction</title>
8− <para>
9− In this document and related Nix expressions, we use the term,
10− <emphasis>BEAM</emphasis>, to describe the environment. BEAM is the name
11− of the Erlang Virtual Machine and, as far as we're concerned, from a
12− packaging perspective, all languages that run on the BEAM are
13− interchangeable. That which varies, like the build system, is transparent
14− to users of any given BEAM package, so we make no distinction.
15− </para>
16− </section>
17− <section xml:id="beam-structure">
18− <title>Structure</title>
19− <para>
20− All BEAM-related expressions are available via the top-level
21− <literal>beam</literal> attribute, which includes:
22− </para>
23− <itemizedlist>
24− <listitem>
25− <para>
26− <literal>interpreters</literal>: a set of compilers running on the
27− BEAM, including multiple Erlang/OTP versions
28− (<literal>beam.interpreters.erlangR19</literal>, etc), Elixir
29− (<literal>beam.interpreters.elixir</literal>) and LFE
30− (<literal>beam.interpreters.lfe</literal>).
31− </para>
32− </listitem>
33− <listitem>
34− <para>
35− <literal>packages</literal>: a set of package sets, each compiled with
36− a specific Erlang/OTP version, e.g.
37− <literal>beam.packages.erlangR19</literal>.
38− </para>
39− </listitem>
40− </itemizedlist>
41− <para>
42− The default Erlang compiler, defined by
43− <literal>beam.interpreters.erlang</literal>, is aliased as
44− <literal>erlang</literal>. The default BEAM package set is defined by
45− <literal>beam.packages.erlang</literal> and aliased at the top level as
46− <literal>beamPackages</literal>.
47− </para>
6+ <section xml:id="beam-introduction">
7+ <title>Introduction</title>
8+
9+ <para>
10+ In this document and related Nix expressions, we use the term,
11+ <emphasis>BEAM</emphasis>, to describe the environment. BEAM is the name of
12+ the Erlang Virtual Machine and, as far as we're concerned, from a packaging
13+ perspective, all languages that run on the BEAM are interchangeable. That
14+ which varies, like the build system, is transparent to users of any given
15+ BEAM package, so we make no distinction.
16+ </para>
17+ </section>
18+
19+ <section xml:id="beam-structure">
20+ <title>Structure</title>
21+
22+ <para>
23+ All BEAM-related expressions are available via the top-level
24+ <literal>beam</literal> attribute, which includes:
25+ </para>
26+
27+ <itemizedlist>
28+ <listitem>
4829 <para>
49− To create a package set built with a custom Erlang version, use the
50− lambda, <literal>beam.packagesWith</literal>, which accepts an Erlang/OTP
51− derivation and produces a package set similar to
52− <literal>beam.packages.erlang</literal>.
30+ <literal>interpreters</literal>: a set of compilers running on the BEAM,
31+ including multiple Erlang/OTP versions
32+ (<literal>beam.interpreters.erlangR19</literal>, etc), Elixir
33+ (<literal>beam.interpreters.elixir</literal>) and LFE
34+ (<literal>beam.interpreters.lfe</literal>).
5335 </para>
36+ </listitem>
37+ <listitem>
5438 <para>
55− Many Erlang/OTP distributions available in
56− <literal>beam.interpreters</literal> have versions with ODBC and/or Java
57− enabled. For example, there's
58− <literal>beam.interpreters.erlangR19_odbc_javac</literal>, which
59− corresponds to <literal>beam.interpreters.erlangR19</literal>.
39+ <literal>packages</literal>: a set of package sets, each compiled with a
40+ specific Erlang/OTP version, e.g.
41+ <literal>beam.packages.erlangR19</literal>.
6042 </para>
61− <para xml:id="erlang-call-package">
62− We also provide the lambda,
63− <literal>beam.packages.erlang.callPackage</literal>, which simplifies
64− writing BEAM package definitions by injecting all packages from
65− <literal>beam.packages.erlang</literal> into the top-level context.
66− </para>
67− </section>
68− <section xml:id="build-tools">
43+ </listitem>
44+ </itemizedlist>
45+
46+ <para>
47+ The default Erlang compiler, defined by
48+ <literal>beam.interpreters.erlang</literal>, is aliased as
49+ <literal>erlang</literal>. The default BEAM package set is defined by
50+ <literal>beam.packages.erlang</literal> and aliased at the top level as
51+ <literal>beamPackages</literal>.
52+ </para>
53+
54+ <para>
55+ To create a package set built with a custom Erlang version, use the lambda,
56+ <literal>beam.packagesWith</literal>, which accepts an Erlang/OTP derivation
57+ and produces a package set similar to
58+ <literal>beam.packages.erlang</literal>.
59+ </para>
60+
61+ <para>
62+ Many Erlang/OTP distributions available in
63+ <literal>beam.interpreters</literal> have versions with ODBC and/or Java
64+ enabled. For example, there's
65+ <literal>beam.interpreters.erlangR19_odbc_javac</literal>, which corresponds
66+ to <literal>beam.interpreters.erlangR19</literal>.
67+ </para>
68+
69+ <para xml:id="erlang-call-package">
70+ We also provide the lambda,
71+ <literal>beam.packages.erlang.callPackage</literal>, which simplifies
72+ writing BEAM package definitions by injecting all packages from
73+ <literal>beam.packages.erlang</literal> into the top-level context.
74+ </para>
75+ </section>
76+
77+ <section xml:id="build-tools">
6978 <title>Build Tools</title>
79+
7080 <section xml:id="build-tools-rebar3">
71− <title>Rebar3</title>
72− <para>
73− By default, Rebar3 wants to manage its own dependencies. This is perfectly
74− acceptable in the normal, non-Nix setup, but in the Nix world, it is not.
75− To rectify this, we provide two versions of Rebar3:
76− <itemizedlist>
77− <listitem>
78− <para>
79− <literal>rebar3</literal>: patched to remove the ability to download
80− anything. When not running it via <literal>nix-shell</literal> or
81− <literal>nix-build</literal>, it's probably not going to work as
82− desired.
83− </para>
84− </listitem>
85− <listitem>
86− <para>
87− <literal>rebar3-open</literal>: the normal, unmodified Rebar3. It
88− should work exactly as would any other version of Rebar3. Any Erlang
89− package should rely on <literal>rebar3</literal> instead. See <xref
81+ <title>Rebar3</title>
82+
83+ <para>
84+ By default, Rebar3 wants to manage its own dependencies. This is perfectly
85+ acceptable in the normal, non-Nix setup, but in the Nix world, it is not.
86+ To rectify this, we provide two versions of Rebar3:
87+ <itemizedlist>
88+ <listitem>
89+ <para>
90+ <literal>rebar3</literal>: patched to remove the ability to download
91+ anything. When not running it via <literal>nix-shell</literal> or
92+ <literal>nix-build</literal>, it's probably not going to work as
93+ desired.
94+ </para>
95+ </listitem>
96+ <listitem>
97+ <para>
98+ <literal>rebar3-open</literal>: the normal, unmodified Rebar3. It should
99+ work exactly as would any other version of Rebar3. Any Erlang package
100+ should rely on <literal>rebar3</literal> instead. See
101+ <xref
90102 linkend="rebar3-packages"/>.
91− </para>
92− </listitem>
93− </itemizedlist>
94− </para>
103+ </para>
104+ </listitem>
105+ </itemizedlist>
106+ </para>
95107 </section>
108+
96109 <section xml:id="build-tools-other">
97− <title>Mix &amp; Erlang.mk</title>
98− <para>
99− Both Mix and Erlang.mk work exactly as expected. There is a bootstrap
100− process that needs to be run for both, however, which is supported by the
101− <literal>buildMix</literal> and <literal>buildErlangMk</literal>
102− derivations, respectively.
103− </para>
110+ <title>Mix &amp; Erlang.mk</title>
111+
112+ <para>
113+ Both Mix and Erlang.mk work exactly as expected. There is a bootstrap
114+ process that needs to be run for both, however, which is supported by the
115+ <literal>buildMix</literal> and <literal>buildErlangMk</literal>
116+ derivations, respectively.
117+ </para>
104118 </section>
105−</section>
119+ </section>
106120
107−<section xml:id="how-to-install-beam-packages">
121+ <section xml:id="how-to-install-beam-packages">
108122 <title>How to Install BEAM Packages</title>
123+
109124 <para>
110− BEAM packages are not registered at the top level, simply because they are
111− not relevant to the vast majority of Nix users. They are installable using
112− the <literal>beam.packages.erlang</literal> attribute set (aliased as
113− <literal>beamPackages</literal>), which points to packages built by the
114− default Erlang/OTP version in Nixpkgs, as defined by
115− <literal>beam.interpreters.erlang</literal>.
116−
117− To list the available packages in
118− <literal>beamPackages</literal>, use the following command:
125+ BEAM packages are not registered at the top level, simply because they are
126+ not relevant to the vast majority of Nix users. They are installable using
127+ the <literal>beam.packages.erlang</literal> attribute set (aliased as
128+ <literal>beamPackages</literal>), which points to packages built by the
129+ default Erlang/OTP version in Nixpkgs, as defined by
130+ <literal>beam.interpreters.erlang</literal>. To list the available packages
131+ in <literal>beamPackages</literal>, use the following command:
119132 </para>
120133
121− <programlisting>
134+<programlisting>
122135$ nix-env -f &quot;&lt;nixpkgs&gt;&quot; -qaP -A beamPackages
123136beamPackages.esqlite esqlite-0.2.1
124137beamPackages.goldrush goldrush-0.1.7
@@ -128,34 +141,43 @@ beamPackages.lager lager-3.0.2
128141beamPackages.meck meck-0.8.3
129142beamPackages.rebar3-pc pc-1.1.0
130143 </programlisting>
144+
131145 <para>
132− To install any of those packages into your profile, refer to them by their
133− attribute path (first column):
146+ To install any of those packages into your profile, refer to them by their
147+ attribute path (first column):
134148 </para>
135− <programlisting>
149+
150+<programlisting>
136151$ nix-env -f &quot;&lt;nixpkgs&gt;&quot; -iA beamPackages.ibrowse
137152 </programlisting>
153+
138154 <para>
139− The attribute path of any BEAM package corresponds to the name of that
140− particular package in <link xlink:href="https://hex.pm">Hex</link> or its
141− OTP Application/Release name.
155+ The attribute path of any BEAM package corresponds to the name of that
156+ particular package in <link xlink:href="https://hex.pm">Hex</link> or its
157+ OTP Application/Release name.
142158 </para>
143−</section>
144−<section xml:id="packaging-beam-applications">
159+ </section>
160+
161+ <section xml:id="packaging-beam-applications">
145162 <title>Packaging BEAM Applications</title>
163+
146164 <section xml:id="packaging-erlang-applications">
147− <title>Erlang Applications</title>
148− <section xml:id="rebar3-packages">
149− <title>Rebar3 Packages</title>
150− <para>
151− The Nix function, <literal>buildRebar3</literal>, defined in
152− <literal>beam.packages.erlang.buildRebar3</literal> and aliased at the
153− top level, can be used to build a derivation that understands how to
154− build a Rebar3 project. For example, we can build <link
155− xlink:href="https://github.com/erlang-nix/hex2nix">hex2nix</link> as
156− follows:
157− </para>
158− <programlisting>
165+ <title>Erlang Applications</title>
166+
167+ <section xml:id="rebar3-packages">
168+ <title>Rebar3 Packages</title>
169+
170+ <para>
171+ The Nix function, <literal>buildRebar3</literal>, defined in
172+ <literal>beam.packages.erlang.buildRebar3</literal> and aliased at the top
173+ level, can be used to build a derivation that understands how to build a
174+ Rebar3 project. For example, we can build
175+ <link
176+ xlink:href="https://github.com/erlang-nix/hex2nix">hex2nix</link>
177+ as follows:
178+ </para>
179+
180+<programlisting>
159181 { stdenv, fetchFromGitHub, buildRebar3, ibrowse, jsx, erlware_commons }:
160182
161183 buildRebar3 rec {
@@ -172,33 +194,40 @@ $ nix-env -f &quot;&lt;nixpkgs&gt;&quot; -iA beamPackages.ibrowse
172194 beamDeps = [ ibrowse jsx erlware_commons ];
173195 }
174196 </programlisting>
175− <para>
176− Such derivations are callable with
177− <literal>beam.packages.erlang.callPackage</literal> (see <xref
178− linkend="erlang-call-package"/>). To call this package using the normal
179− <literal>callPackage</literal>, refer to dependency packages via
180− <literal>beamPackages</literal>, e.g.
181− <literal>beamPackages.ibrowse</literal>.
182− </para>
183− <para>
184− Notably, <literal>buildRebar3</literal> includes
185− <literal>beamDeps</literal>, while
186− <literal>stdenv.mkDerivation</literal> does not. BEAM dependencies added
187− there will be correctly handled by the system.
188− </para>
189− <para>
190− If a package needs to compile native code via Rebar3's port compilation
191− mechanism, add <literal>compilePort = true;</literal> to the derivation.
192− </para>
193− </section>
194− <section xml:id="erlang-mk-packages">
195− <title>Erlang.mk Packages</title>
196− <para>
197− Erlang.mk functions similarly to Rebar3, except we use
198− <literal>buildErlangMk</literal> instead of
199− <literal>buildRebar3</literal>.
200− </para>
201− <programlisting>
197+
198+ <para>
199+ Such derivations are callable with
200+ <literal>beam.packages.erlang.callPackage</literal> (see
201+ <xref
202+ linkend="erlang-call-package"/>). To call this package using
203+ the normal <literal>callPackage</literal>, refer to dependency packages
204+ via <literal>beamPackages</literal>, e.g.
205+ <literal>beamPackages.ibrowse</literal>.
206+ </para>
207+
208+ <para>
209+ Notably, <literal>buildRebar3</literal> includes
210+ <literal>beamDeps</literal>, while <literal>stdenv.mkDerivation</literal>
211+ does not. BEAM dependencies added there will be correctly handled by the
212+ system.
213+ </para>
214+
215+ <para>
216+ If a package needs to compile native code via Rebar3's port compilation
217+ mechanism, add <literal>compilePort = true;</literal> to the derivation.
218+ </para>
219+ </section>
220+
221+ <section xml:id="erlang-mk-packages">
222+ <title>Erlang.mk Packages</title>
223+
224+ <para>
225+ Erlang.mk functions similarly to Rebar3, except we use
226+ <literal>buildErlangMk</literal> instead of
227+ <literal>buildRebar3</literal>.
228+ </para>
229+
230+<programlisting>
202231 { buildErlangMk, fetchHex, cowlib, ranch }:
203232
204233 buildErlangMk {
@@ -222,14 +251,17 @@ $ nix-env -f &quot;&lt;nixpkgs&gt;&quot; -iA beamPackages.ibrowse
222251 };
223252 }
224253 </programlisting>
225− </section>
226− <section xml:id="mix-packages">
227− <title>Mix Packages</title>
228− <para>
229− Mix functions similarly to Rebar3, except we use
230− <literal>buildMix</literal> instead of <literal>buildRebar3</literal>.
231− </para>
232− <programlisting>
254+ </section>
255+
256+ <section xml:id="mix-packages">
257+ <title>Mix Packages</title>
258+
259+ <para>
260+ Mix functions similarly to Rebar3, except we use
261+ <literal>buildMix</literal> instead of <literal>buildRebar3</literal>.
262+ </para>
263+
264+<programlisting>
233265 { buildMix, fetchHex, plug, absinthe }:
234266
235267 buildMix {
@@ -253,10 +285,12 @@ $ nix-env -f &quot;&lt;nixpkgs&gt;&quot; -iA beamPackages.ibrowse
253285 };
254286 }
255287 </programlisting>
256− <para>
257− Alternatively, we can use <literal>buildHex</literal> as a shortcut:
258− </para>
259− <programlisting>
288+
289+ <para>
290+ Alternatively, we can use <literal>buildHex</literal> as a shortcut:
291+ </para>
292+
293+<programlisting>
260294 { buildHex, buildMix, plug, absinthe }:
261295
262296 buildHex {
@@ -278,21 +312,25 @@ $ nix-env -f &quot;&lt;nixpkgs&gt;&quot; -iA beamPackages.ibrowse
278312 };
279313 }
280314 </programlisting>
281− </section>
315+ </section>
282316 </section>
283−</section>
284−<section xml:id="how-to-develop">
317+ </section>
318+
319+ <section xml:id="how-to-develop">
285320 <title>How to Develop</title>
321+
286322 <section xml:id="accessing-an-environment">
287− <title>Accessing an Environment</title>
288− <para>
289− Often, we simply want to access a valid environment that contains a
290− specific package and its dependencies. We can accomplish that with the
291− <literal>env</literal> attribute of a derivation. For example, let's say
292− we want to access an Erlang REPL with <literal>ibrowse</literal> loaded
293− up. We could do the following:
294− </para>
295− <programlisting>
323+ <title>Accessing an Environment</title>
324+
325+ <para>
326+ Often, we simply want to access a valid environment that contains a
327+ specific package and its dependencies. We can accomplish that with the
328+ <literal>env</literal> attribute of a derivation. For example, let's say we
329+ want to access an Erlang REPL with <literal>ibrowse</literal> loaded up. We
330+ could do the following:
331+ </para>
332+
333+<programlisting>
296334 $ nix-shell -A beamPackages.ibrowse.env --run "erl"
297335 Erlang/OTP 18 [erts-7.0] [source] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:false]
298336
@@ -333,22 +371,25 @@ $ nix-env -f &quot;&lt;nixpkgs&gt;&quot; -iA beamPackages.ibrowse
333371 ok
334372 2>
335373 </programlisting>
336− <para>
337− Notice the <literal>-A beamPackages.ibrowse.env</literal>. That is the key
338− to this functionality.
339− </para>
374+
375+ <para>
376+ Notice the <literal>-A beamPackages.ibrowse.env</literal>. That is the key
377+ to this functionality.
378+ </para>
340379 </section>
380+
341381 <section xml:id="creating-a-shell">
342− <title>Creating a Shell</title>
343− <para>
344− Getting access to an environment often isn't enough to do real
345− development. Usually, we need to create a <literal>shell.nix</literal>
346− file and do our development inside of the environment specified therein.
347− This file looks a lot like the packaging described above, except that
348− <literal>src</literal> points to the project root and we call the package
349− directly.
350− </para>
351− <programlisting>
382+ <title>Creating a Shell</title>
383+
384+ <para>
385+ Getting access to an environment often isn't enough to do real development.
386+ Usually, we need to create a <literal>shell.nix</literal> file and do our
387+ development inside of the environment specified therein. This file looks a
388+ lot like the packaging described above, except that <literal>src</literal>
389+ points to the project root and we call the package directly.
390+ </para>
391+
392+<programlisting>
352393{ pkgs ? import &quot;&lt;nixpkgs&quot;&gt; {} }:
353394
354395with pkgs;
@@ -368,13 +409,16 @@ in
368409
369410 drv
370411 </programlisting>
371− <section xml:id="building-in-a-shell">
412+
413+ <section xml:id="building-in-a-shell">
372414 <title>Building in a Shell (for Mix Projects)</title>
415+
373416 <para>
374− We can leverage the support of the derivation, irrespective of the build
375− derivation, by calling the commands themselves.
417+ We can leverage the support of the derivation, irrespective of the build
418+ derivation, by calling the commands themselves.
376419 </para>
377− <programlisting>
420+
421+<programlisting>
378422# =============================================================================
379423# Variables
380424# =============================================================================
@@ -431,44 +475,54 @@ analyze: build plt
431475 $(NIX_SHELL) --run "mix dialyzer --no-compile"
432476
433477 </programlisting>
478+
434479 <para>
435− Using a <literal>shell.nix</literal> as described (see <xref
480+ Using a <literal>shell.nix</literal> as described (see
481+ <xref
436482 linkend="creating-a-shell"/>) should just work. Aside from
437− <literal>test</literal>, <literal>plt</literal>, and
438− <literal>analyze</literal>, the Make targets work just fine for all of the
439− build derivations.
483+ <literal>test</literal>, <literal>plt</literal>, and
484+ <literal>analyze</literal>, the Make targets work just fine for all of the
485+ build derivations.
440486 </para>
487+ </section>
441488 </section>
442−</section>
443−</section>
444−<section xml:id="generating-packages-from-hex-with-hex2nix">
489+ </section>
490+
491+ <section xml:id="generating-packages-from-hex-with-hex2nix">
445492 <title>Generating Packages from Hex with <literal>hex2nix</literal></title>
493+
446494 <para>
447− Updating the <link xlink:href="https://hex.pm">Hex</link> package set
448− requires <link
449− xlink:href="https://github.com/erlang-nix/hex2nix">hex2nix</link>. Given the
450− path to the Erlang modules (usually
451− <literal>pkgs/development/erlang-modules</literal>), it will dump a file
452− called <literal>hex-packages.nix</literal>, containing all the packages that
453− use a recognized build system in <link
454− xlink:href="https://hex.pm">Hex</link>. It can't be determined, however,
455− whether every package is buildable.
456− </para>
457− <para>
458− To make life easier for our users, try to build every <link
459− xlink:href="https://hex.pm">Hex</link> package and remove those that fail.
460− To do that, simply run the following command in the root of your
461− <literal>nixpkgs</literal> repository:
462− </para>
463− <programlisting>
495+ Updating the <link xlink:href="https://hex.pm">Hex</link> package set
496+ requires
497+ <link
498+ xlink:href="https://github.com/erlang-nix/hex2nix">hex2nix</link>.
499+ Given the path to the Erlang modules (usually
500+ <literal>pkgs/development/erlang-modules</literal>), it will dump a file
501+ called <literal>hex-packages.nix</literal>, containing all the packages that
502+ use a recognized build system in
503+ <link
504+ xlink:href="https://hex.pm">Hex</link>. It can't be determined,
505+ however, whether every package is buildable.
506+ </para>
507+
508+ <para>
509+ To make life easier for our users, try to build every
510+ <link
511+ xlink:href="https://hex.pm">Hex</link> package and remove those
512+ that fail. To do that, simply run the following command in the root of your
513+ <literal>nixpkgs</literal> repository:
514+ </para>
515+
516+<programlisting>
464517$ nix-build -A beamPackages
465518 </programlisting>
466− <para>
467− That will attempt to build every package in
468− <literal>beamPackages</literal>. Then manually remove those that fail.
469− Hopefully, someone will improve <link
470− xlink:href="https://github.com/erlang-nix/hex2nix">hex2nix</link> in the
471− future to automate the process.
472− </para>
473−</section>
519+
520+ <para>
521+ That will attempt to build every package in <literal>beamPackages</literal>.
522+ Then manually remove those that fail. Hopefully, someone will improve
523+ <link
524+ xlink:href="https://github.com/erlang-nix/hex2nix">hex2nix</link>
525+ in the future to automate the process.
526+ </para>
527+ </section>
474528</section>
doc/languages-frameworks/bower.xml+137−152
@@ -1,40 +1,37 @@
11<section xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="sec-bower">
4−
5−<title>Bower</title>
6−
7−<para>
8− <link xlink:href="http://bower.io">Bower</link> is a package manager
9− for web site front-end components. Bower packages (comprising of
10− build artefacts and sometimes sources) are stored in
11− <command>git</command> repositories, typically on Github. The
12− package registry is run by the Bower team with package metadata
13− coming from the <filename>bower.json</filename> file within each
14− package.
15−</para>
16−
17−<para>
18− The end result of running Bower is a
19− <filename>bower_components</filename> directory which can be included
20− in the web app's build process.
21−</para>
22−
23−<para>
4+ <title>Bower</title>
5+
6+ <para>
7+ <link xlink:href="http://bower.io">Bower</link> is a package manager for web
8+ site front-end components. Bower packages (comprising of build artefacts and
9+ sometimes sources) are stored in <command>git</command> repositories,
10+ typically on Github. The package registry is run by the Bower team with
11+ package metadata coming from the <filename>bower.json</filename> file within
12+ each package.
13+ </para>
14+
15+ <para>
16+ The end result of running Bower is a <filename>bower_components</filename>
17+ directory which can be included in the web app's build process.
18+ </para>
19+
20+ <para>
2421 Bower can be run interactively, by installing
2522 <varname>nodePackages.bower</varname>. More interestingly, the Bower
2623 components can be declared in a Nix derivation, with the help of
2724 <varname>nodePackages.bower2nix</varname>.
28−</para>
25+ </para>
2926
30−<section xml:id="ssec-bower2nix-usage">
27+ <section xml:id="ssec-bower2nix-usage">
3128 <title><command>bower2nix</command> usage</title>
3229
33−<para>
34− Suppose you have a <filename>bower.json</filename> with the following contents:
35−
36−
37−<example xml:id="ex-bowerJson"><title><filename>bower.json</filename></title>
30+ <para>
31+ Suppose you have a <filename>bower.json</filename> with the following
32+ contents:
33+ <example xml:id="ex-bowerJson">
34+ <title><filename>bower.json</filename></title>
3835<programlisting language="json">
3936<![CDATA[{
4037 "name": "my-web-app",
@@ -44,14 +41,12 @@
4441 }
4542}]]>
4643</programlisting>
47−</example>
48−</para>
49−
50−
51−<para>
52− Running <command>bower2nix</command> will produce something like the
53− following output:
44+ </example>
45+ </para>
5446
47+ <para>
48+ Running <command>bower2nix</command> will produce something like the
49+ following output:
5550<programlisting language="nix">
5651<![CDATA[{ fetchbower, buildEnv }:
5752buildEnv { name = "bower-env"; ignoreCollisions = true; paths = [
@@ -60,31 +55,31 @@ buildEnv { name = "bower-env"; ignoreCollisions = true; paths = [
6055 (fetchbower "jquery" "2.2.2" "1.9.1 - 2" "10sp5h98sqwk90y4k6hbdviwqzvzwqf47r3r51pakch5ii2y7js1")
6156]; }]]>
6257</programlisting>
63−</para>
64−
58+ </para>
6559
66−<para>
67− Using the <command>bower2nix</command> command line arguments, the
68− output can be redirected to a file. A name like
69− <filename>bower-packages.nix</filename> would be fine.
70−</para>
60+ <para>
61+ Using the <command>bower2nix</command> command line arguments, the output
62+ can be redirected to a file. A name like
63+ <filename>bower-packages.nix</filename> would be fine.
64+ </para>
7165
72−<para>
73− The resulting derivation is a union of all the downloaded Bower
74− packages (and their dependencies). To use it, they still need to be
75− linked together by Bower, which is where
76− <varname>buildBowerComponents</varname> is useful.
77−</para>
78−</section>
66+ <para>
67+ The resulting derivation is a union of all the downloaded Bower packages
68+ (and their dependencies). To use it, they still need to be linked together
69+ by Bower, which is where <varname>buildBowerComponents</varname> is useful.
70+ </para>
71+ </section>
7972
80−<section xml:id="ssec-build-bower-components"><title><varname>buildBowerComponents</varname> function</title>
73+ <section xml:id="ssec-build-bower-components">
74+ <title><varname>buildBowerComponents</varname> function</title>
8175
8276 <para>
83− The function is implemented in <link xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/bower-modules/generic/default.nix">
84− <filename>pkgs/development/bower-modules/generic/default.nix</filename></link>.
85− Example usage:
86−
87−<example xml:id="ex-buildBowerComponents"><title>buildBowerComponents</title>
77+ The function is implemented in
78+ <link xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/bower-modules/generic/default.nix">
79+ <filename>pkgs/development/bower-modules/generic/default.nix</filename></link>.
80+ Example usage:
81+ <example xml:id="ex-buildBowerComponents">
82+ <title>buildBowerComponents</title>
8883<programlisting language="nix">
8984bowerComponents = buildBowerComponents {
9085 name = "my-web-app";
@@ -92,42 +87,42 @@ bowerComponents = buildBowerComponents {
9287 src = myWebApp; <co xml:id="ex-buildBowerComponents-2" />
9388};
9489</programlisting>
95−</example>
90+ </example>
9691 </para>
9792
98−<para>
99−In <xref linkend="ex-buildBowerComponents" />, the following arguments
100−are of special significance to the function:
101−
102−<calloutlist>
103− <callout arearefs="ex-buildBowerComponents-1">
104− <para>
105− <varname>generated</varname> specifies the file which was created by <command>bower2nix</command>.
106− </para>
107− </callout>
108−
109− <callout arearefs="ex-buildBowerComponents-2">
110− <para>
111− <varname>src</varname> is your project's sources. It needs to
112− contain a <filename>bower.json</filename> file.
113− </para>
114− </callout>
115−</calloutlist>
116−</para>
117−
118−<para>
119− <varname>buildBowerComponents</varname> will run Bower to link
120− together the output of <command>bower2nix</command>, resulting in a
121− <filename>bower_components</filename> directory which can be used.
122−</para>
123−
124−<para>
125− Here is an example of a web frontend build process using
126− <command>gulp</command>. You might use <command>grunt</command>, or
127− anything else.
128−</para>
129−
130−<example xml:id="ex-bowerGulpFile"><title>Example build script (<filename>gulpfile.js</filename>)</title>
93+ <para>
94+ In <xref linkend="ex-buildBowerComponents" />, the following arguments are
95+ of special significance to the function:
96+ <calloutlist>
97+ <callout arearefs="ex-buildBowerComponents-1">
98+ <para>
99+ <varname>generated</varname> specifies the file which was created by
100+ <command>bower2nix</command>.
101+ </para>
102+ </callout>
103+ <callout arearefs="ex-buildBowerComponents-2">
104+ <para>
105+ <varname>src</varname> is your project's sources. It needs to contain a
106+ <filename>bower.json</filename> file.
107+ </para>
108+ </callout>
109+ </calloutlist>
110+ </para>
111+
112+ <para>
113+ <varname>buildBowerComponents</varname> will run Bower to link together the
114+ output of <command>bower2nix</command>, resulting in a
115+ <filename>bower_components</filename> directory which can be used.
116+ </para>
117+
118+ <para>
119+ Here is an example of a web frontend build process using
120+ <command>gulp</command>. You might use <command>grunt</command>, or anything
121+ else.
122+ </para>
123+
124+ <example xml:id="ex-bowerGulpFile">
125+ <title>Example build script (<filename>gulpfile.js</filename>)</title>
131126<programlisting language="javascript">
132127<![CDATA[var gulp = require('gulp');
133128
@@ -142,10 +137,10 @@ gulp.task('build', [], function () {
142137 .pipe(gulp.dest("./gulpdist/"));
143138});]]>
144139</programlisting>
145−</example>
140+ </example>
146141
147−<example xml:id="ex-buildBowerComponentsDefaultNix">
148− <title>Full example — <filename>default.nix</filename></title>
142+ <example xml:id="ex-buildBowerComponentsDefaultNix">
143+ <title>Full example — <filename>default.nix</filename></title>
149144<programlisting language="nix">
150145{ myWebApp ? { outPath = ./.; name = "myWebApp"; }
151146, pkgs ? import &lt;nixpkgs&gt; {}
@@ -172,73 +167,63 @@ pkgs.stdenv.mkDerivation {
172167 installPhase = "mv gulpdist $out";
173168}
174169</programlisting>
175−</example>
176−
177−<para>
178−A few notes about <xref linkend="ex-buildBowerComponentsDefaultNix" />:
179−
180−<calloutlist>
181− <callout arearefs="ex-buildBowerComponentsDefault-1">
182− <para>
183− The result of <varname>buildBowerComponents</varname> is an
184− input to the frontend build.
185− </para>
186− </callout>
187−
188− <callout arearefs="ex-buildBowerComponentsDefault-2">
189− <para>
190− Whether to symlink or copy the
191− <filename>bower_components</filename> directory depends on the
192− build tool in use. In this case a copy is used to avoid
193− <command>gulp</command> silliness with permissions.
194− </para>
195− </callout>
196−
197− <callout arearefs="ex-buildBowerComponentsDefault-3">
198− <para>
199− <command>gulp</command> requires <varname>HOME</varname> to
200− refer to a writeable directory.
201− </para>
202− </callout>
203−
204− <callout arearefs="ex-buildBowerComponentsDefault-4">
205− <para>
170+ </example>
171+
172+ <para>
173+ A few notes about <xref linkend="ex-buildBowerComponentsDefaultNix" />:
174+ <calloutlist>
175+ <callout arearefs="ex-buildBowerComponentsDefault-1">
176+ <para>
177+ The result of <varname>buildBowerComponents</varname> is an input to the
178+ frontend build.
179+ </para>
180+ </callout>
181+ <callout arearefs="ex-buildBowerComponentsDefault-2">
182+ <para>
183+ Whether to symlink or copy the <filename>bower_components</filename>
184+ directory depends on the build tool in use. In this case a copy is used
185+ to avoid <command>gulp</command> silliness with permissions.
186+ </para>
187+ </callout>
188+ <callout arearefs="ex-buildBowerComponentsDefault-3">
189+ <para>
190+ <command>gulp</command> requires <varname>HOME</varname> to refer to a
191+ writeable directory.
192+ </para>
193+ </callout>
194+ <callout arearefs="ex-buildBowerComponentsDefault-4">
195+ <para>
206196 The actual build command. Other tools could be used.
207− </para>
208− </callout>
209−</calloutlist>
210−</para>
211−</section>
197+ </para>
198+ </callout>
199+ </calloutlist>
200+ </para>
201+ </section>
212202
213−<section xml:id="ssec-bower2nix-troubleshooting">
203+ <section xml:id="ssec-bower2nix-troubleshooting">
214204 <title>Troubleshooting</title>
215205
216−<variablelist>
217−
218− <varlistentry>
206+ <variablelist>
207+ <varlistentry>
219208 <term>
220− <literal>ENOCACHE</literal> errors from
221− <varname>buildBowerComponents</varname>
209+ <literal>ENOCACHE</literal> errors from <varname>buildBowerComponents</varname>
222210 </term>
223211 <listitem>
224− <para>
225− This means that Bower was looking for a package version which
226− doesn't exist in the generated
227− <filename>bower-packages.nix</filename>.
228− </para>
229− <para>
230− If <filename>bower.json</filename> has been updated, then run
231− <command>bower2nix</command> again.
232− </para>
233− <para>
234− It could also be a bug in <command>bower2nix</command> or
235− <command>fetchbower</command>. If possible, try reformulating
236− the version specification in <filename>bower.json</filename>.
237− </para>
212+ <para>
213+ This means that Bower was looking for a package version which doesn't
214+ exist in the generated <filename>bower-packages.nix</filename>.
215+ </para>
216+ <para>
217+ If <filename>bower.json</filename> has been updated, then run
218+ <command>bower2nix</command> again.
219+ </para>
220+ <para>
221+ It could also be a bug in <command>bower2nix</command> or
222+ <command>fetchbower</command>. If possible, try reformulating the version
223+ specification in <filename>bower.json</filename>.
224+ </para>
238225 </listitem>
239− </varlistentry>
240−</variablelist>
241−
242−</section>
243−
226+ </varlistentry>
227+ </variablelist>
228+ </section>
244229</section>
doc/languages-frameworks/coq.xml+30−29
@@ -1,36 +1,37 @@
11<section xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="sec-language-coq">
4+ <title>Coq</title>
45
5−<title>Coq</title>
6− <para>
7− Coq libraries should be installed in
8− <literal>$(out)/lib/coq/${coq.coq-version}/user-contrib/</literal>.
9− Such directories are automatically added to the
10− <literal>$COQPATH</literal> environment variable by the hook defined
11− in the Coq derivation.
12− </para>
13− <para>
14− Some libraries require OCaml and sometimes also Camlp5 or findlib.
15− The exact versions that were used to build Coq are saved in the
16− <literal>coq.ocaml</literal> and <literal>coq.camlp5</literal>
17− and <literal>coq.findlib</literal> attributes.
18− </para>
19− <para>
20− Coq libraries may be compatible with some specific versions of Coq only.
21− The <literal>compatibleCoqVersions</literal> attribute is used to
22− precisely select those versions of Coq that are compatible with this
23− derivation.
24− </para>
25− <para>
26− Here is a simple package example. It is a pure Coq library, thus it
27− depends on Coq. It builds on the Mathematical Components library, thus it
28− also takes <literal>mathcomp</literal> as <literal>buildInputs</literal>.
29− Its <literal>Makefile</literal> has been generated using
30− <literal>coq_makefile</literal> so we only have to
31− set the <literal>$COQLIB</literal> variable at install time.
32− </para>
33− <programlisting>
6+ <para>
7+ Coq libraries should be installed in
8+ <literal>$(out)/lib/coq/${coq.coq-version}/user-contrib/</literal>. Such
9+ directories are automatically added to the <literal>$COQPATH</literal>
10+ environment variable by the hook defined in the Coq derivation.
11+ </para>
12+
13+ <para>
14+ Some extensions (plugins) might require OCaml and sometimes other OCaml
15+ packages. The <literal>coq.ocamlPackages</literal> attribute can be used to
16+ depend on the same package set Coq was built against.
17+ </para>
18+
19+ <para>
20+ Coq libraries may be compatible with some specific versions of Coq only. The
21+ <literal>compatibleCoqVersions</literal> attribute is used to precisely
22+ select those versions of Coq that are compatible with this derivation.
23+ </para>
24+
25+ <para>
26+ Here is a simple package example. It is a pure Coq library, thus it depends
27+ on Coq. It builds on the Mathematical Components library, thus it also takes
28+ <literal>mathcomp</literal> as <literal>buildInputs</literal>. Its
29+ <literal>Makefile</literal> has been generated using
30+ <literal>coq_makefile</literal> so we only have to set the
31+ <literal>$COQLIB</literal> variable at install time.
32+ </para>
33+
34+<programlisting>
3435{ stdenv, fetchFromGitHub, coq, mathcomp }:
3536
3637stdenv.mkDerivation rec {
doc/languages-frameworks/emscripten.section.mdnew file+185
@@ -0,0 +1,185 @@
1+# User's Guide to Emscripten in Nixpkgs
2+
3+[Emscripten](https://github.com/kripken/emscripten): An LLVM-to-JavaScript Compiler
4+
5+This section of the manual covers how to use `emscripten` in nixpkgs.
6+
7+Minimal requirements:
8+
9+* nix
10+* nixpkgs
11+
12+Modes of use of `emscripten`:
13+
14+* **Imperative usage** (on the command line):
15+
16+ If you want to work with `emcc`, `emconfigure` and `emmake` as you are used to from Ubuntu and similar distributions you can use these commands:
17+
18+ * `nix-env -i emscripten`
19+ * `nix-shell -p emscripten`
20+
21+* **Declarative usage**:
22+
23+ This mode is far more power full since this makes use of `nix` for dependency management of emscripten libraries and targets by using the `mkDerivation` which is implemented by `pkgs.emscriptenStdenv` and `pkgs.buildEmscriptenPackage`. The source for the packages is in `pkgs/top-level/emscripten-packages.nix` and the abstraction behind it in `pkgs/development/em-modules/generic/default.nix`.
24+ * build and install all packages:
25+ * `nix-env -iA emscriptenPackages`
26+
27+ * dev-shell for zlib implementation hacking:
28+ * `nix-shell -A emscriptenPackages.zlib`
29+
30+
31+## Imperative usage
32+
33+A few things to note:
34+
35+* `export EMCC_DEBUG=2` is nice for debugging
36+* `~/.emscripten`, the build artifact cache sometimes creates issues and needs to be removed from time to time
37+
38+
39+## Declarative usage
40+
41+Let's see two different examples from `pkgs/top-level/emscripten-packages.nix`:
42+
43+* `pkgs.zlib.override`
44+* `pkgs.buildEmscriptenPackage`
45+
46+Both are interesting concepts.
47+
48+A special requirement of the `pkgs.buildEmscriptenPackage` is the `doCheck = true` is a default meaning that each emscriptenPackage requires a `checkPhase` implemented.
49+
50+* Use `export EMCC_DEBUG=2` from within a emscriptenPackage's `phase` to get more detailed debug output what is going wrong.
51+* ~/.emscripten cache is requiring us to set `HOME=$TMPDIR` in individual phases. This makes compilation slower but also makes it more deterministic.
52+
53+### Usage 1: pkgs.zlib.override
54+
55+This example uses `zlib` from nixpkgs but instead of compiling **C** to **ELF** it compiles **C** to **JS** since we were using `pkgs.zlib.override` and changed stdenv to `pkgs.emscriptenStdenv`. A few adaptions and hacks were set in place to make it working. One advantage is that when `pkgs.zlib` is updated, it will automatically update this package as well. However, this can also be the downside...
56+
57+See the `zlib` example:
58+
59+ zlib = (pkgs.zlib.override {
60+ stdenv = pkgs.emscriptenStdenv;
61+ }).overrideDerivation
62+ (old: rec {
63+ buildInputs = old.buildInputs ++ [ pkgconfig ];
64+ # we need to reset this setting!
65+ NIX_CFLAGS_COMPILE="";
66+ configurePhase = ''
67+ # FIXME: Some tests require writing at $HOME
68+ HOME=$TMPDIR
69+ runHook preConfigure
70+
71+ #export EMCC_DEBUG=2
72+ emconfigure ./configure --prefix=$out --shared
73+
74+ runHook postConfigure
75+ '';
76+ dontStrip = true;
77+ outputs = [ "out" ];
78+ buildPhase = ''
79+ emmake make
80+ '';
81+ installPhase = ''
82+ emmake make install
83+ '';
84+ checkPhase = ''
85+ echo "================= testing zlib using node ================="
86+
87+ echo "Compiling a custom test"
88+ set -x
89+ emcc -O2 -s EMULATE_FUNCTION_POINTER_CASTS=1 test/example.c -DZ_SOLO \
90+ libz.so.${old.version} -I . -o example.js
91+
92+ echo "Using node to execute the test"
93+ ${pkgs.nodejs}/bin/node ./example.js
94+
95+ set +x
96+ if [ $? -ne 0 ]; then
97+ echo "test failed for some reason"
98+ exit 1;
99+ else
100+ echo "it seems to work! very good."
101+ fi
102+ echo "================= /testing zlib using node ================="
103+ '';
104+
105+ postPatch = pkgs.stdenv.lib.optionalString pkgs.stdenv.isDarwin ''
106+ substituteInPlace configure \
107+ --replace '/usr/bin/libtool' 'ar' \
108+ --replace 'AR="libtool"' 'AR="ar"' \
109+ --replace 'ARFLAGS="-o"' 'ARFLAGS="-r"'
110+ '';
111+ });
112+
113+### Usage 2: pkgs.buildEmscriptenPackage
114+
115+This `xmlmirror` example features a emscriptenPackage which is defined completely from this context and no `pkgs.zlib.override` is used.
116+
117+ xmlmirror = pkgs.buildEmscriptenPackage rec {
118+ name = "xmlmirror";
119+
120+ buildInputs = [ pkgconfig autoconf automake libtool gnumake libxml2 nodejs openjdk json_c ];
121+ nativeBuildInputs = [ pkgconfig zlib ];
122+
123+ src = pkgs.fetchgit {
124+ url = "https://gitlab.com/odfplugfest/xmlmirror.git";
125+ rev = "4fd7e86f7c9526b8f4c1733e5c8b45175860a8fd";
126+ sha256 = "1jasdqnbdnb83wbcnyrp32f36w3xwhwp0wq8lwwmhqagxrij1r4b";
127+ };
128+
129+ configurePhase = ''
130+ rm -f fastXmlLint.js*
131+ # a fix for ERROR:root:For asm.js, TOTAL_MEMORY must be a multiple of 16MB, was 234217728
132+ # https://gitlab.com/odfplugfest/xmlmirror/issues/8
133+ sed -e "s/TOTAL_MEMORY=234217728/TOTAL_MEMORY=268435456/g" -i Makefile.emEnv
134+ # https://github.com/kripken/emscripten/issues/6344
135+ # https://gitlab.com/odfplugfest/xmlmirror/issues/9
136+ sed -e "s/\$(JSONC_LDFLAGS) \$(ZLIB_LDFLAGS) \$(LIBXML20_LDFLAGS)/\$(JSONC_LDFLAGS) \$(LIBXML20_LDFLAGS) \$(ZLIB_LDFLAGS) /g" -i Makefile.emEnv
137+ # https://gitlab.com/odfplugfest/xmlmirror/issues/11
138+ sed -e "s/-o fastXmlLint.js/-s EXTRA_EXPORTED_RUNTIME_METHODS='[\"ccall\", \"cwrap\"]' -o fastXmlLint.js/g" -i Makefile.emEnv
139+ '';
140+
141+ buildPhase = ''
142+ HOME=$TMPDIR
143+ make -f Makefile.emEnv
144+ '';
145+
146+ outputs = [ "out" "doc" ];
147+
148+ installPhase = ''
149+ mkdir -p $out/share
150+ mkdir -p $doc/share/${name}
151+
152+ cp Demo* $out/share
153+ cp -R codemirror-5.12 $out/share
154+ cp fastXmlLint.js* $out/share
155+ cp *.xsd $out/share
156+ cp *.js $out/share
157+ cp *.xhtml $out/share
158+ cp *.html $out/share
159+ cp *.json $out/share
160+ cp *.rng $out/share
161+ cp README.md $doc/share/${name}
162+ '';
163+ checkPhase = ''
164+
165+ '';
166+ };
167+
168+### Declarative debugging
169+
170+Use `nix-shell -I nixpkgs=/some/dir/nixpkgs -A emscriptenPackages.libz` and from there you can go trough the individual steps. This makes it easy to build a good `unit test` or list the files of the project.
171+
172+1. `nix-shell -I nixpkgs=/some/dir/nixpkgs -A emscriptenPackages.libz`
173+2. `cd /tmp/`
174+3. `unpackPhase`
175+4. cd libz-1.2.3
176+5. `configurePhase`
177+6. `buildPhase`
178+7. ... happy hacking...
179+
180+## Summary
181+
182+Using this toolchain makes it easy to leverage `nix` from NixOS, MacOSX or even Windows (WSL+ubuntu+nix). This toolchain is reproducible, behaves like the rest of the packages from nixpkgs and contains a set of well working examples to learn and adapt from.
183+
184+If in trouble, ask the maintainers.
185+
doc/languages-frameworks/go.xml+84−90
@@ -1,14 +1,14 @@
11<section xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="sec-language-go">
4+ <title>Go</title>
45
5−<title>Go</title>
6+ <para>
7+ The function <varname>buildGoPackage</varname> builds standard Go programs.
8+ </para>
69
7−<para>The function <varname>buildGoPackage</varname> builds
8−standard Go programs.
9−</para>
10−
11−<example xml:id='ex-buildGoPackage'><title>buildGoPackage</title>
10+ <example xml:id='ex-buildGoPackage'>
11+ <title>buildGoPackage</title>
1212<programlisting>
1313deis = buildGoPackage rec {
1414 name = "deis-${version}";
@@ -29,55 +29,56 @@ deis = buildGoPackage rec {
2929 buildFlags = "--tags release"; <co xml:id='ex-buildGoPackage-4' />
3030}
3131</programlisting>
32−</example>
33−
34−<para><xref linkend='ex-buildGoPackage'/> is an example expression using buildGoPackage,
35−the following arguments are of special significance to the function:
36−
37−<calloutlist>
38−
39− <callout arearefs='ex-buildGoPackage-1'>
32+ </example>
33+
34+ <para>
35+ <xref linkend='ex-buildGoPackage'/> is an example expression using
36+ buildGoPackage, the following arguments are of special significance to the
37+ function:
38+ <calloutlist>
39+ <callout arearefs='ex-buildGoPackage-1'>
4040 <para>
41− <varname>goPackagePath</varname> specifies the package's canonical Go import path.
41+ <varname>goPackagePath</varname> specifies the package's canonical Go
42+ import path.
4243 </para>
43− </callout>
44−
45− <callout arearefs='ex-buildGoPackage-2'>
44+ </callout>
45+ <callout arearefs='ex-buildGoPackage-2'>
4646 <para>
47− <varname>subPackages</varname> limits the builder from building child packages that
48− have not been listed. If <varname>subPackages</varname> is not specified, all child
49− packages will be built.
47+ <varname>subPackages</varname> limits the builder from building child
48+ packages that have not been listed. If <varname>subPackages</varname> is
49+ not specified, all child packages will be built.
5050 </para>
5151 <para>
52− In this example only <literal>github.com/deis/deis/client</literal> will be built.
52+ In this example only <literal>github.com/deis/deis/client</literal> will
53+ be built.
5354 </para>
54− </callout>
55−
56− <callout arearefs='ex-buildGoPackage-3'>
55+ </callout>
56+ <callout arearefs='ex-buildGoPackage-3'>
5757 <para>
58− <varname>goDeps</varname> is where the Go dependencies of a Go program are listed
59− as a list of package source identified by Go import path.
60− It could be imported as a separate <varname>deps.nix</varname> file for
61− readability. The dependency data structure is described below.
58+ <varname>goDeps</varname> is where the Go dependencies of a Go program are
59+ listed as a list of package source identified by Go import path. It could
60+ be imported as a separate <varname>deps.nix</varname> file for
61+ readability. The dependency data structure is described below.
6262 </para>
63− </callout>
64−
65− <callout arearefs='ex-buildGoPackage-4'>
63+ </callout>
64+ <callout arearefs='ex-buildGoPackage-4'>
6665 <para>
67− <varname>buildFlags</varname> is a list of flags passed to the go build command.
66+ <varname>buildFlags</varname> is a list of flags passed to the go build
67+ command.
6868 </para>
69− </callout>
70−
71−</calloutlist>
72−
73−</para>
74−
75−<para>The <varname>goDeps</varname> attribute can be imported from a separate
76− <varname>nix</varname> file that defines which Go libraries are needed and should
77− be included in <varname>GOPATH</varname> for <varname>buildPhase</varname>.
78−</para>
79−
80−<example xml:id='ex-goDeps'><title>deps.nix</title>
69+ </callout>
70+ </calloutlist>
71+ </para>
72+
73+ <para>
74+ The <varname>goDeps</varname> attribute can be imported from a separate
75+ <varname>nix</varname> file that defines which Go libraries are needed and
76+ should be included in <varname>GOPATH</varname> for
77+ <varname>buildPhase</varname>.
78+ </para>
79+
80+ <example xml:id='ex-goDeps'>
81+ <title>deps.nix</title>
8182<programlisting>
8283[ <co xml:id='ex-goDeps-1' />
8384 {
@@ -100,67 +101,60 @@ the following arguments are of special significance to the function:
100101 }
101102]
102103</programlisting>
103−</example>
104+ </example>
104105
105−<para>
106−
107−<calloutlist>
108−
109− <callout arearefs='ex-goDeps-1'>
106+ <para>
107+ <calloutlist>
108+ <callout arearefs='ex-goDeps-1'>
110109 <para>
111− <varname>goDeps</varname> is a list of Go dependencies.
110+ <varname>goDeps</varname> is a list of Go dependencies.
112111 </para>
113− </callout>
114−
115− <callout arearefs='ex-goDeps-2'>
112+ </callout>
113+ <callout arearefs='ex-goDeps-2'>
116114 <para>
117− <varname>goPackagePath</varname> specifies Go package import path.
115+ <varname>goPackagePath</varname> specifies Go package import path.
118116 </para>
119− </callout>
120−
121− <callout arearefs='ex-goDeps-3'>
117+ </callout>
118+ <callout arearefs='ex-goDeps-3'>
122119 <para>
123− <varname>fetch type</varname> that needs to be used to get package source. If <varname>git</varname>
124− is used there should be <varname>url</varname>, <varname>rev</varname> and <varname>sha256</varname>
125− defined next to it.
120+ <varname>fetch type</varname> that needs to be used to get package source.
121+ If <varname>git</varname> is used there should be <varname>url</varname>,
122+ <varname>rev</varname> and <varname>sha256</varname> defined next to it.
126123 </para>
127− </callout>
128−
129−</calloutlist>
130−
131−</para>
132−
133−<para>To extract dependency information from a Go package in automated way use <link xlink:href="https://github.com/kamilchm/go2nix">go2nix</link>.
134− It can produce complete derivation and <varname>goDeps</varname> file for Go programs.</para>
135−
136−<para>
137− <varname>buildGoPackage</varname> produces <xref linkend='chap-multiple-output' xrefstyle="select: title" />
138− where <varname>bin</varname> includes program binaries. You can test build a Go binary as follows:
139−
140− <screen>
124+ </callout>
125+ </calloutlist>
126+ </para>
127+
128+ <para>
129+ To extract dependency information from a Go package in automated way use
130+ <link xlink:href="https://github.com/kamilchm/go2nix">go2nix</link>. It can
131+ produce complete derivation and <varname>goDeps</varname> file for Go
132+ programs.
133+ </para>
134+
135+ <para>
136+ <varname>buildGoPackage</varname> produces
137+ <xref linkend='chap-multiple-output' xrefstyle="select: title" /> where
138+ <varname>bin</varname> includes program binaries. You can test build a Go
139+ binary as follows:
140+<screen>
141141 $ nix-build -A deis.bin
142142 </screen>
143−
144143 or build all outputs with:
145−
146− <screen>
144+<screen>
147145 $ nix-build -A deis.all
148146 </screen>
147+ <varname>bin</varname> output will be installed by default with
148+ <varname>nix-env -i</varname> or <varname>systemPackages</varname>.
149+ </para>
149150
150− <varname>bin</varname> output will be installed by default with <varname>nix-env -i</varname>
151− or <varname>systemPackages</varname>.
152−
153−</para>
154−
155−<para>
156−You may use Go packages installed into the active Nix profiles by adding
157−the following to your ~/.bashrc:
158−
151+ <para>
152+ You may use Go packages installed into the active Nix profiles by adding the
153+ following to your ~/.bashrc:
159154<screen>
160155for p in $NIX_PROFILES; do
161156 GOPATH="$p/share/go:$GOPATH"
162157done
163158</screen>
164−</para>
165−
159+ </para>
166160</section>
doc/languages-frameworks/haskell.mddeleted−955
@@ -1,955 +0,0 @@
1−---
2−title: User's Guide for Haskell in Nixpkgs
3−author: Peter Simons
4−date: 2015-06-01
5−---
6−# User's Guide to the Haskell Infrastructure
7−
8−
9−## How to install Haskell packages
10−
11−Nixpkgs distributes build instructions for all Haskell packages registered on
12−[Hackage](http://hackage.haskell.org/), but strangely enough normal Nix package
13−lookups don't seem to discover any of them, except for the default version of ghc, cabal-install, and stack:
14−```
15−$ nix-env -i alex
16−error: selector ‘alex’ matches no derivations
17−$ nix-env -qa ghc
18−ghc-7.10.2
19−```
20−
21−The Haskell package set is not registered in the top-level namespace because it
22−is *huge*. If all Haskell packages were visible to these commands, then
23−name-based search/install operations would be much slower than they are now. We
24−avoided that by keeping all Haskell-related packages in a separate attribute
25−set called `haskellPackages`, which the following command will list:
26−```
27−$ nix-env -f "<nixpkgs>" -qaP -A haskellPackages
28−haskellPackages.a50 a50-0.5
29−haskellPackages.abacate haskell-abacate-0.0.0.0
30−haskellPackages.abcBridge haskell-abcBridge-0.12
31−haskellPackages.afv afv-0.1.1
32−haskellPackages.alex alex-3.1.4
33−haskellPackages.Allure Allure-0.4.101.1
34−haskellPackages.alms alms-0.6.7
35−[... some 8000 entries omitted ...]
36−```
37−
38−To install any of those packages into your profile, refer to them by their
39−attribute path (first column):
40−```shell
41−nix-env -f "<nixpkgs>" -iA haskellPackages.Allure ...
42−```
43−
44−The attribute path of any Haskell packages corresponds to the name of that
45−particular package on Hackage: the package `cabal-install` has the attribute
46−`haskellPackages.cabal-install`, and so on. (Actually, this convention causes
47−trouble with packages like `3dmodels` and `4Blocks`, because these names are
48−invalid identifiers in the Nix language. The issue of how to deal with these
49−rare corner cases is currently unresolved.)
50−
51−Haskell packages whose Nix name (second column) begins with a `haskell-` prefix
52−are packages that provide a library whereas packages without that prefix
53−provide just executables. Libraries may provide executables too, though: the
54−package `haskell-pandoc`, for example, installs both a library and an
55−application. You can install and use Haskell executables just like any other
56−program in Nixpkgs, but using Haskell libraries for development is a bit
57−trickier and we'll address that subject in great detail in section [How to
58−create a development environment].
59−
60−Attribute paths are deterministic inside of Nixpkgs, but the path necessary to
61−reach Nixpkgs varies from system to system. We dodged that problem by giving
62−`nix-env` an explicit `-f "<nixpkgs>"` parameter, but if you call `nix-env`
63−without that flag, then chances are the invocation fails:
64−```
65−$ nix-env -iA haskellPackages.cabal-install
66−error: attribute ‘haskellPackages’ in selection path
67− ‘haskellPackages.cabal-install’ not found
68−```
69−
70−On NixOS, for example, Nixpkgs does *not* exist in the top-level namespace by
71−default. To figure out the proper attribute path, it's easiest to query for the
72−path of a well-known Nixpkgs package, i.e.:
73−```
74−$ nix-env -qaP coreutils
75−nixos.coreutils coreutils-8.23
76−```
77−
78−If your system responds like that (most NixOS installations will), then the
79−attribute path to `haskellPackages` is `nixos.haskellPackages`. Thus, if you
80−want to use `nix-env` without giving an explicit `-f` flag, then that's the way
81−to do it:
82−```shell
83−nix-env -qaP -A nixos.haskellPackages
84−nix-env -iA nixos.haskellPackages.cabal-install
85−```
86−
87−Our current default compiler is GHC 7.10.x and the `haskellPackages` set
88−contains packages built with that particular version. Nixpkgs contains the
89−latest major release of every GHC since 6.10.4, however, and there is a whole
90−family of package sets available that defines Hackage packages built with each
91−of those compilers, too:
92−```shell
93−nix-env -f "<nixpkgs>" -qaP -A haskell.packages.ghc6123
94−nix-env -f "<nixpkgs>" -qaP -A haskell.packages.ghc763
95−```
96−
97−The name `haskellPackages` is really just a synonym for
98−`haskell.packages.ghc7102`, because we prefer that package set internally and
99−recommend it to our users as their default choice, but ultimately you are free
100−to compile your Haskell packages with any GHC version you please. The following
101−command displays the complete list of available compilers:
102−```
103−$ nix-env -f "<nixpkgs>" -qaP -A haskell.compiler
104−haskell.compiler.ghc6104 ghc-6.10.4
105−haskell.compiler.ghc6123 ghc-6.12.3
106−haskell.compiler.ghc704 ghc-7.0.4
107−haskell.compiler.ghc722 ghc-7.2.2
108−haskell.compiler.ghc742 ghc-7.4.2
109−haskell.compiler.ghc763 ghc-7.6.3
110−haskell.compiler.ghc784 ghc-7.8.4
111−haskell.compiler.ghc7102 ghc-7.10.2
112−haskell.compiler.ghcHEAD ghc-7.11.20150402
113−haskell.compiler.ghcNokinds ghc-nokinds-7.11.20150704
114−haskell.compiler.ghcjs ghcjs-0.1.0
115−haskell.compiler.jhc jhc-0.8.2
116−haskell.compiler.uhc uhc-1.1.9.0
117−```
118−
119−We have no package sets for `jhc` or `uhc` yet, unfortunately, but for every
120−version of GHC listed above, there exists a package set based on that compiler.
121−Also, the attributes `haskell.compiler.ghcXYC` and
122−`haskell.packages.ghcXYC.ghc` are synonymous for the sake of convenience.
123−
124−## How to create a development environment
125−
126−### How to install a compiler
127−
128−A simple development environment consists of a Haskell compiler and one or both
129−of the tools `cabal-install` and `stack`. We saw in section
130−[How to install Haskell packages] how you can install those programs into your
131−user profile:
132−```shell
133−nix-env -f "<nixpkgs>" -iA haskellPackages.ghc haskellPackages.cabal-install
134−```
135−
136−Instead of the default package set `haskellPackages`, you can also use the more
137−precise name `haskell.compiler.ghc7102`, which has the advantage that it refers
138−to the same GHC version regardless of what Nixpkgs considers "default" at any
139−given time.
140−
141−Once you've made those tools available in `$PATH`, it's possible to build
142−Hackage packages the same way people without access to Nix do it all the time:
143−```shell
144−cabal get lens-4.11 && cd lens-4.11
145−cabal install -j --dependencies-only
146−cabal configure
147−cabal build
148−```
149−
150−If you enjoy working with Cabal sandboxes, then that's entirely possible too:
151−just execute the command
152−```shell
153−cabal sandbox init
154−```
155−before installing the required dependencies.
156−
157−The `nix-shell` utility makes it easy to switch to a different compiler
158−version; just enter the Nix shell environment with the command
159−```shell
160−nix-shell -p haskell.compiler.ghc784
161−```
162−to bring GHC 7.8.4 into `$PATH`. Alternatively, you can use Stack instead of
163−`nix-shell` directly to select compiler versions and other build tools
164−per-project. It uses `nix-shell` under the hood when Nix support is turned on.
165−See [How to build a Haskell project using Stack].
166−
167−If you're using `cabal-install`, re-running `cabal configure` inside the spawned
168−shell switches your build to use that compiler instead. If you're working on
169−a project that doesn't depend on any additional system libraries outside of GHC,
170−then it's even sufficient to just run the `cabal configure` command inside of
171−the shell:
172−```shell
173−nix-shell -p haskell.compiler.ghc784 --command "cabal configure"
174−```
175−
176−Afterwards, all other commands like `cabal build` work just fine in any shell
177−environment, because the configure phase recorded the absolute paths to all
178−required tools like GHC in its build configuration inside of the `dist/`
179−directory. Please note, however, that `nix-collect-garbage` can break such an
180−environment because the Nix store paths created by `nix-shell` aren't "alive"
181−anymore once `nix-shell` has terminated. If you find that your Haskell builds
182−no longer work after garbage collection, then you'll have to re-run `cabal
183−configure` inside of a new `nix-shell` environment.
184−
185−### How to install a compiler with libraries
186−
187−GHC expects to find all installed libraries inside of its own `lib` directory.
188−This approach works fine on traditional Unix systems, but it doesn't work for
189−Nix, because GHC's store path is immutable once it's built. We cannot install
190−additional libraries into that location. As a consequence, our copies of GHC
191−don't know any packages except their own core libraries, like `base`,
192−`containers`, `Cabal`, etc.
193−
194−We can register additional libraries to GHC, however, using a special build
195−function called `ghcWithPackages`. That function expects one argument: a
196−function that maps from an attribute set of Haskell packages to a list of
197−packages, which determines the libraries known to that particular version of
198−GHC. For example, the Nix expression `ghcWithPackages (pkgs: [pkgs.mtl])`
199−generates a copy of GHC that has the `mtl` library registered in addition to
200−its normal core packages:
201−```
202−$ nix-shell -p "haskellPackages.ghcWithPackages (pkgs: [pkgs.mtl])"
203−
204−[nix-shell:~]$ ghc-pkg list mtl
205−/nix/store/zy79...-ghc-7.10.2/lib/ghc-7.10.2/package.conf.d:
206− mtl-2.2.1
207−```
208−
209−This function allows users to define their own development environment by means
210−of an override. After adding the following snippet to `~/.config/nixpkgs/config.nix`,
211−```nix
212−{
213− packageOverrides = super: let self = super.pkgs; in
214− {
215− myHaskellEnv = self.haskell.packages.ghc7102.ghcWithPackages
216− (haskellPackages: with haskellPackages; [
217− # libraries
218− arrows async cgi criterion
219− # tools
220− cabal-install haskintex
221− ]);
222− };
223−}
224−```
225−it's possible to install that compiler with `nix-env -f "<nixpkgs>" -iA
226−myHaskellEnv`. If you'd like to switch that development environment to a
227−different version of GHC, just replace the `ghc7102` bit in the previous
228−definition with the appropriate name. Of course, it's also possible to define
229−any number of these development environments! (You can't install two of them
230−into the same profile at the same time, though, because that would result in
231−file conflicts.)
232−
233−The generated `ghc` program is a wrapper script that re-directs the real
234−GHC executable to use a new `lib` directory --- one that we specifically
235−constructed to contain all those packages the user requested:
236−```
237−$ cat $(type -p ghc)
238−#! /nix/store/xlxj...-bash-4.3-p33/bin/bash -e
239−export NIX_GHC=/nix/store/19sm...-ghc-7.10.2/bin/ghc
240−export NIX_GHCPKG=/nix/store/19sm...-ghc-7.10.2/bin/ghc-pkg
241−export NIX_GHC_DOCDIR=/nix/store/19sm...-ghc-7.10.2/share/doc/ghc/html
242−export NIX_GHC_LIBDIR=/nix/store/19sm...-ghc-7.10.2/lib/ghc-7.10.2
243−exec /nix/store/j50p...-ghc-7.10.2/bin/ghc "-B$NIX_GHC_LIBDIR" "$@"
244−```
245−
246−The variables `$NIX_GHC`, `$NIX_GHCPKG`, etc. point to the *new* store path
247−`ghcWithPackages` constructed specifically for this environment. The last line
248−of the wrapper script then executes the real `ghc`, but passes the path to the
249−new `lib` directory using GHC's `-B` flag.
250−
251−The purpose of those environment variables is to work around an impurity in the
252−popular [ghc-paths](http://hackage.haskell.org/package/ghc-paths) library. That
253−library promises to give its users access to GHC's installation paths. Only,
254−the library can't possible know that path when it's compiled, because the path
255−GHC considers its own is determined only much later, when the user configures
256−it through `ghcWithPackages`. So we [patched
257−ghc-paths](https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/haskell-modules/patches/ghc-paths-nix.patch)
258−to return the paths found in those environment variables at run-time rather
259−than trying to guess them at compile-time.
260−
261−To make sure that mechanism works properly all the time, we recommend that you
262−set those variables to meaningful values in your shell environment, too, i.e.
263−by adding the following code to your `~/.bashrc`:
264−```bash
265−if type >/dev/null 2>&1 -p ghc; then
266− eval "$(egrep ^export "$(type -p ghc)")"
267−fi
268−```
269−
270−If you are certain that you'll use only one GHC environment which is located in
271−your user profile, then you can use the following code, too, which has the
272−advantage that it doesn't contain any paths from the Nix store, i.e. those
273−settings always remain valid even if a `nix-env -u` operation updates the GHC
274−environment in your profile:
275−```bash
276−if [ -e ~/.nix-profile/bin/ghc ]; then
277− export NIX_GHC="$HOME/.nix-profile/bin/ghc"
278− export NIX_GHCPKG="$HOME/.nix-profile/bin/ghc-pkg"
279− export NIX_GHC_DOCDIR="$HOME/.nix-profile/share/doc/ghc/html"
280− export NIX_GHC_LIBDIR="$HOME/.nix-profile/lib/ghc-$($NIX_GHC --numeric-version)"
281−fi
282−```
283−
284−### How to install a compiler with libraries, hoogle and documentation indexes
285−
286−If you plan to use your environment for interactive programming, not just
287−compiling random Haskell code, you might want to replace `ghcWithPackages` in
288−all the listings above with `ghcWithHoogle`.
289−
290−This environment generator not only produces an environment with GHC and all
291−the specified libraries, but also generates a `hoogle` and `haddock` indexes
292−for all the packages, and provides a wrapper script around `hoogle` binary that
293−uses all those things. A precise name for this thing would be
294−"`ghcWithPackagesAndHoogleAndDocumentationIndexes`", which is, regrettably, too
295−long and scary.
296−
297−For example, installing the following environment
298−```nix
299−{
300− packageOverrides = super: let self = super.pkgs; in
301− {
302− myHaskellEnv = self.haskellPackages.ghcWithHoogle
303− (haskellPackages: with haskellPackages; [
304− # libraries
305− arrows async cgi criterion
306− # tools
307− cabal-install haskintex
308− ]);
309− };
310−}
311−```
312−allows one to browse module documentation index [not too dissimilar to
313−this](https://downloads.haskell.org/~ghc/latest/docs/html/libraries/index.html)
314−for all the specified packages and their dependencies by directing a browser of
315−choice to `~/.nix-profiles/share/doc/hoogle/index.html` (or
316−`/run/current-system/sw/share/doc/hoogle/index.html` in case you put it in
317−`environment.systemPackages` in NixOS).
318−
319−After you've marveled enough at that try adding the following to your
320−`~/.ghc/ghci.conf`
321−```
322−:def hoogle \s -> return $ ":! hoogle search -cl --count=15 \"" ++ s ++ "\""
323−:def doc \s -> return $ ":! hoogle search -cl --info \"" ++ s ++ "\""
324−```
325−and test it by typing into `ghci`:
326−```
327−:hoogle a -> a
328−:doc a -> a
329−```
330−
331−Be sure to note the links to `haddock` files in the output. With any modern and
332−properly configured terminal emulator you can just click those links to
333−navigate there.
334−
335−Finally, you can run
336−```shell
337−hoogle server -p 8080 --local
338−```
339−and navigate to http://localhost:8080/ for your own local
340−[Hoogle](https://www.haskell.org/hoogle/).
341−
342−### How to build a Haskell project using Stack
343−
344−[Stack](http://haskellstack.org) is a popular build tool for Haskell projects.
345−It has first-class support for Nix. Stack can optionally use Nix to
346−automatically select the right version of GHC and other build tools to build,
347−test and execute apps in an existing project downloaded from somewhere on the
348−Internet. Pass the `--nix` flag to any `stack` command to do so, e.g.
349−```shell
350−git clone --recursive http://github.com/yesodweb/wai
351−cd wai
352−stack --nix build
353−```
354−
355−If you want `stack` to use Nix by default, you can add a `nix` section to the
356−`stack.yaml` file, as explained in the [Stack documentation][stack-nix-doc]. For
357−example:
358−```yaml
359−nix:
360− enable: true
361− packages: [pkgconfig zeromq zlib]
362−```
363−
364−The example configuration snippet above tells Stack to create an ad hoc
365−environment for `nix-shell` as in the below section, in which the `pkgconfig`,
366−`zeromq` and `zlib` packages from Nixpkgs are available. All `stack` commands
367−will implicitly be executed inside this ad hoc environment.
368−
369−Some projects have more sophisticated needs. For examples, some ad hoc
370−environments might need to expose Nixpkgs packages compiled in a certain way, or
371−with extra environment variables. In these cases, you'll need a `shell` field
372−instead of `packages`:
373−```yaml
374−nix:
375− enable: true
376− shell-file: shell.nix
377−```
378−
379−For more on how to write a `shell.nix` file see the below section. You'll need
380−to express a derivation. Note that Nixpkgs ships with a convenience wrapper
381−function around `mkDerivation` called `haskell.lib.buildStackProject` to help you
382−create this derivation in exactly the way Stack expects. All of the same inputs
383−as `mkDerivation` can be provided. For example, to build a Stack project that
384−including packages that link against a version of the R library compiled with
385−special options turned on:
386−```nix
387−with (import <nixpkgs> { });
388−
389−let R = pkgs.R.override { enableStrictBarrier = true; };
390−in
391−haskell.lib.buildStackProject {
392− name = "HaskellR";
393− buildInputs = [ R zeromq zlib ];
394−}
395−```
396−
397−You can select a particular GHC version to compile with by setting the
398−`ghc` attribute as an argument to `buildStackProject`. Better yet, let
399−Stack choose what GHC version it wants based on the snapshot specified
400−in `stack.yaml` (only works with Stack >= 1.1.3):
401−```nix
402−{nixpkgs ? import <nixpkgs> { }, ghc ? nixpkgs.ghc}:
403−
404−with nixpkgs;
405−
406−let R = pkgs.R.override { enableStrictBarrier = true; };
407−in
408−haskell.lib.buildStackProject {
409− name = "HaskellR";
410− buildInputs = [ R zeromq zlib ];
411− inherit ghc;
412−}
413−```
414−
415−[stack-nix-doc]: http://docs.haskellstack.org/en/stable/nix_integration.html
416−
417−### How to create ad hoc environments for `nix-shell`
418−
419−The easiest way to create an ad hoc development environment is to run
420−`nix-shell` with the appropriate GHC environment given on the command-line:
421−```shell
422−nix-shell -p "haskellPackages.ghcWithPackages (pkgs: with pkgs; [mtl pandoc])"
423−```
424−
425−For more sophisticated use-cases, however, it's more convenient to save the
426−desired configuration in a file called `shell.nix` that looks like this:
427−```nix
428−{ nixpkgs ? import <nixpkgs> {}, compiler ? "ghc7102" }:
429−let
430− inherit (nixpkgs) pkgs;
431− ghc = pkgs.haskell.packages.${compiler}.ghcWithPackages (ps: with ps; [
432− monad-par mtl
433− ]);
434−in
435−pkgs.stdenv.mkDerivation {
436− name = "my-haskell-env-0";
437− buildInputs = [ ghc ];
438− shellHook = "eval $(egrep ^export ${ghc}/bin/ghc)";
439−}
440−```
441−
442−Now run `nix-shell` --- or even `nix-shell --pure` --- to enter a shell
443−environment that has the appropriate compiler in `$PATH`. If you use `--pure`,
444−then add all other packages that your development environment needs into the
445−`buildInputs` attribute. If you'd like to switch to a different compiler
446−version, then pass an appropriate `compiler` argument to the expression, i.e.
447−`nix-shell --argstr compiler ghc784`.
448−
449−If you need such an environment because you'd like to compile a Hackage package
450−outside of Nix --- i.e. because you're hacking on the latest version from Git
451−---, then the package set provides suitable nix-shell environments for you
452−already! Every Haskell package has an `env` attribute that provides a shell
453−environment suitable for compiling that particular package. If you'd like to
454−hack the `lens` library, for example, then you just have to check out the
455−source code and enter the appropriate environment:
456−```
457−$ cabal get lens-4.11 && cd lens-4.11
458−Downloading lens-4.11...
459−Unpacking to lens-4.11/
460−
461−$ nix-shell "<nixpkgs>" -A haskellPackages.lens.env
462−[nix-shell:/tmp/lens-4.11]$
463−```
464−
465−At point, you can run `cabal configure`, `cabal build`, and all the other
466−development commands. Note that you need `cabal-install` installed in your
467−`$PATH` already to use it here --- the `nix-shell` environment does not provide
468−it.
469−
470−## How to create Nix builds for your own private Haskell packages
471−
472−If your own Haskell packages have build instructions for Cabal, then you can
473−convert those automatically into build instructions for Nix using the
474−`cabal2nix` utility, which you can install into your profile by running
475−`nix-env -i cabal2nix`.
476−
477−### How to build a stand-alone project
478−
479−For example, let's assume that you're working on a private project called
480−`foo`. To generate a Nix build expression for it, change into the project's
481−top-level directory and run the command:
482−```shell
483−cabal2nix . > foo.nix
484−```
485−Then write the following snippet into a file called `default.nix`:
486−```nix
487−{ nixpkgs ? import <nixpkgs> {}, compiler ? "ghc7102" }:
488−nixpkgs.pkgs.haskell.packages.${compiler}.callPackage ./foo.nix { }
489−```
490−
491−Finally, store the following code in a file called `shell.nix`:
492−```nix
493−{ nixpkgs ? import <nixpkgs> {}, compiler ? "ghc7102" }:
494−(import ./default.nix { inherit nixpkgs compiler; }).env
495−```
496−
497−At this point, you can run `nix-build` to have Nix compile your project and
498−install it into a Nix store path. The local directory will contain a symlink
499−called `result` after `nix-build` returns that points into that location. Of
500−course, passing the flag `--argstr compiler ghc763` allows switching the build
501−to any version of GHC currently supported.
502−
503−Furthermore, you can call `nix-shell` to enter an interactive development
504−environment in which you can use `cabal configure` and `cabal build` to develop
505−your code. That environment will automatically contain a proper GHC derivation
506−with all the required libraries registered as well as all the system-level
507−libraries your package might need.
508−
509−If your package does not depend on any system-level libraries, then it's
510−sufficient to run
511−```shell
512−nix-shell --command "cabal configure"
513−```
514−once to set up your build. `cabal-install` determines the absolute paths to all
515−resources required for the build and writes them into a config file in the
516−`dist/` directory. Once that's done, you can run `cabal build` and any other
517−command for that project even outside of the `nix-shell` environment. This
518−feature is particularly nice for those of us who like to edit their code with
519−an IDE, like Emacs' `haskell-mode`, because it's not necessary to start Emacs
520−inside of nix-shell just to make it find out the necessary settings for
521−building the project; `cabal-install` has already done that for us.
522−
523−If you want to do some quick-and-dirty hacking and don't want to bother setting
524−up a `default.nix` and `shell.nix` file manually, then you can use the
525−`--shell` flag offered by `cabal2nix` to have it generate a stand-alone
526−`nix-shell` environment for you. With that feature, running
527−```shell
528−cabal2nix --shell . > shell.nix
529−nix-shell --command "cabal configure"
530−```
531−is usually enough to set up a build environment for any given Haskell package.
532−You can even use that generated file to run `nix-build`, too:
533−```shell
534−nix-build shell.nix
535−```
536−
537−### How to build projects that depend on each other
538−
539−If you have multiple private Haskell packages that depend on each other, then
540−you'll have to register those packages in the Nixpkgs set to make them visible
541−for the dependency resolution performed by `callPackage`. First of all, change
542−into each of your projects top-level directories and generate a `default.nix`
543−file with `cabal2nix`:
544−```shell
545−cd ~/src/foo && cabal2nix . > default.nix
546−cd ~/src/bar && cabal2nix . > default.nix
547−```
548−Then edit your `~/.config/nixpkgs/config.nix` file to register those builds in the
549−default Haskell package set:
550−```nix
551−{
552− packageOverrides = super: let self = super.pkgs; in
553− {
554− haskellPackages = super.haskellPackages.override {
555− overrides = self: super: {
556− foo = self.callPackage ../src/foo {};
557− bar = self.callPackage ../src/bar {};
558− };
559− };
560− };
561−}
562−```
563−Once that's accomplished, `nix-env -f "<nixpkgs>" -qA haskellPackages` will
564−show your packages like any other package from Hackage, and you can build them
565−```shell
566−nix-build "<nixpkgs>" -A haskellPackages.foo
567−```
568−or enter an interactive shell environment suitable for building them:
569−```shell
570−nix-shell "<nixpkgs>" -A haskellPackages.bar.env
571−```
572−
573−## Miscellaneous Topics
574−
575−### How to build with profiling enabled
576−
577−Every Haskell package set takes a function called `overrides` that you can use
578−to manipulate the package as much as you please. One useful application of this
579−feature is to replace the default `mkDerivation` function with one that enables
580−library profiling for all packages. To accomplish that add the following
581−snippet to your `~/.config/nixpkgs/config.nix` file:
582−```nix
583−{
584− packageOverrides = super: let self = super.pkgs; in
585− {
586− profiledHaskellPackages = self.haskellPackages.override {
587− overrides = self: super: {
588− mkDerivation = args: super.mkDerivation (args // {
589− enableLibraryProfiling = true;
590− });
591− };
592− };
593− };
594−}
595−```
596−Then, replace instances of `haskellPackages` in the `cabal2nix`-generated
597−`default.nix` or `shell.nix` files with `profiledHaskellPackages`.
598−
599−### How to override package versions in a compiler-specific package set
600−
601−Nixpkgs provides the latest version of
602−[`ghc-events`](http://hackage.haskell.org/package/ghc-events), which is 0.4.4.0
603−at the time of this writing. This is fine for users of GHC 7.10.x, but GHC
604−7.8.4 cannot compile that binary. Now, one way to solve that problem is to
605−register an older version of `ghc-events` in the 7.8.x-specific package set.
606−The first step is to generate Nix build instructions with `cabal2nix`:
607−```shell
608−cabal2nix cabal://ghc-events-0.4.3.0 > ~/.nixpkgs/ghc-events-0.4.3.0.nix
609−```
610−Then add the override in `~/.config/nixpkgs/config.nix`:
611−```nix
612−{
613− packageOverrides = super: let self = super.pkgs; in
614− {
615− haskell = super.haskell // {
616− packages = super.haskell.packages // {
617− ghc784 = super.haskell.packages.ghc784.override {
618− overrides = self: super: {
619− ghc-events = self.callPackage ./ghc-events-0.4.3.0.nix {};
620− };
621− };
622− };
623− };
624− };
625−}
626−```
627−
628−This code is a little crazy, no doubt, but it's necessary because the intuitive
629−version
630−```nix
631−{ # ...
632−
633− haskell.packages.ghc784 = super.haskell.packages.ghc784.override {
634− overrides = self: super: {
635− ghc-events = self.callPackage ./ghc-events-0.4.3.0.nix {};
636− };
637− };
638−}
639−```
640−doesn't do what we want it to: that code replaces the `haskell` package set in
641−Nixpkgs with one that contains only one entry,`packages`, which contains only
642−one entry `ghc784`. This override loses the `haskell.compiler` set, and it
643−loses the `haskell.packages.ghcXYZ` sets for all compilers but GHC 7.8.4. To
644−avoid that problem, we have to perform the convoluted little dance from above,
645−iterating over each step in hierarchy.
646−
647−Once it's accomplished, however, we can install a variant of `ghc-events`
648−that's compiled with GHC 7.8.4:
649−```shell
650−nix-env -f "<nixpkgs>" -iA haskell.packages.ghc784.ghc-events
651−```
652−Unfortunately, it turns out that this build fails again while executing the
653−test suite! Apparently, the release archive on Hackage is missing some data
654−files that the test suite requires, so we cannot run it. We accomplish that by
655−re-generating the Nix expression with the `--no-check` flag:
656−```shell
657−cabal2nix --no-check cabal://ghc-events-0.4.3.0 > ~/.nixpkgs/ghc-events-0.4.3.0.nix
658−```
659−Now the builds succeeds.
660−
661−Of course, in the concrete example of `ghc-events` this whole exercise is not
662−an ideal solution, because `ghc-events` can analyze the output emitted by any
663−version of GHC later than 6.12 regardless of the compiler version that was used
664−to build the `ghc-events` executable, so strictly speaking there's no reason to
665−prefer one built with GHC 7.8.x in the first place. However, for users who
666−cannot use GHC 7.10.x at all for some reason, the approach of downgrading to an
667−older version might be useful.
668−
669−### How to recover from GHC's infamous non-deterministic library ID bug
670−
671−GHC and distributed build farms don't get along well:
672−
673− - https://ghc.haskell.org/trac/ghc/ticket/4012
674−
675−When you see an error like this one
676−```
677−package foo-0.7.1.0 is broken due to missing package
678−text-1.2.0.4-98506efb1b9ada233bb5c2b2db516d91
679−```
680−then you have to download and re-install `foo` and all its dependents from
681−scratch:
682−```shell
683−nix-store -q --referrers /nix/store/*-haskell-text-1.2.0.4 \
684− | xargs -L 1 nix-store --repair-path
685−```
686−
687−If you're using additional Hydra servers other than `hydra.nixos.org`, then it
688−might be necessary to purge the local caches that store data from those
689−machines to disable these binary channels for the duration of the previous
690−command, i.e. by running:
691−```shell
692−rm /nix/var/nix/binary-cache-v3.sqlite
693−rm /nix/var/nix/manifests/*
694−rm /nix/var/nix/channel-cache/*
695−```
696−
697−### Builds on Darwin fail with `math.h` not found
698−
699−Users of GHC on Darwin have occasionally reported that builds fail, because the
700−compiler complains about a missing include file:
701−```
702−fatal error: 'math.h' file not found
703−```
704−The issue has been discussed at length in [ticket
705−6390](https://github.com/NixOS/nixpkgs/issues/6390), and so far no good
706−solution has been proposed. As a work-around, users who run into this problem
707−can configure the environment variables
708−```shell
709−export NIX_CFLAGS_COMPILE="-idirafter /usr/include"
710−export NIX_CFLAGS_LINK="-L/usr/lib"
711−```
712−in their `~/.bashrc` file to avoid the compiler error.
713−
714−### Builds using Stack complain about missing system libraries
715−
716−```
717−-- While building package zlib-0.5.4.2 using:
718− runhaskell -package=Cabal-1.22.4.0 -clear-package-db [... lots of flags ...]
719−Process exited with code: ExitFailure 1
720−Logs have been written to: /home/foo/src/stack-ide/.stack-work/logs/zlib-0.5.4.2.log
721−
722−Configuring zlib-0.5.4.2...
723−Setup.hs: Missing dependency on a foreign library:
724−* Missing (or bad) header file: zlib.h
725−This problem can usually be solved by installing the system package that
726−provides this library (you may need the "-dev" version). If the library is
727−already installed but in a non-standard location then you can use the flags
728−--extra-include-dirs= and --extra-lib-dirs= to specify where it is.
729−If the header file does exist, it may contain errors that are caught by the C
730−compiler at the preprocessing stage. In this case you can re-run configure
731−with the verbosity flag -v3 to see the error messages.
732−```
733−
734−When you run the build inside of the nix-shell environment, the system
735−is configured to find `libz.so` without any special flags -- the compiler
736−and linker "just know" how to find it. Consequently, Cabal won't record
737−any search paths for `libz.so` in the package description, which means
738−that the package works fine inside of nix-shell, but once you leave the
739−shell the shared object can no longer be found. That issue is by no
740−means specific to Stack: you'll have that problem with any other
741−Haskell package that's built inside of nix-shell but run outside of that
742−environment.
743−
744−You can remedy this issue in several ways. The easiest is to add a `nix` section
745−to the `stack.yaml` like the following:
746−```yaml
747−nix:
748− enable: true
749− packages: [ zlib ]
750−```
751−
752−Stack's Nix support knows to add `${zlib.out}/lib` and `${zlib.dev}/include`
753−as an `--extra-lib-dirs` and `extra-include-dirs`, respectively.
754−Alternatively, you can achieve the same effect by hand. First of all, run
755−```
756−$ nix-build --no-out-link "<nixpkgs>" -A zlib
757−/nix/store/alsvwzkiw4b7ip38l4nlfjijdvg3fvzn-zlib-1.2.8
758−```
759−to find out the store path of the system's zlib library. Now, you can
760−
761− 1. add that path (plus a "/lib" suffix) to your `$LD_LIBRARY_PATH`
762− environment variable to make sure your system linker finds `libz.so`
763− automatically. It's no pretty solution, but it will work.
764−
765− 2. As a variant of (1), you can also install any number of system
766− libraries into your user's profile (or some other profile) and point
767− `$LD_LIBRARY_PATH` to that profile instead, so that you don't have to
768− list dozens of those store paths all over the place.
769−
770− 3. The solution I prefer is to call stack with an appropriate
771− --extra-lib-dirs flag like so:
772− ```shell
773− stack --extra-lib-dirs=/nix/store/alsvwzkiw4b7ip38l4nlfjijdvg3fvzn-zlib-1.2.8/lib build
774− ```
775−
776−Typically, you'll need `--extra-include-dirs` as well. It's possible
777−to add those flag to the project's `stack.yaml` or your user's
778−global `~/.stack/global/stack.yaml` file so that you don't have to
779−specify them manually every time. But again, you're likely better off
780−using Stack's Nix support instead.
781−
782−The same thing applies to `cabal configure`, of course, if you're
783−building with `cabal-install` instead of Stack.
784−
785−### Creating statically linked binaries
786−
787−There are two levels of static linking. The first option is to configure the
788−build with the Cabal flag `--disable-executable-dynamic`. In Nix expressions,
789−this can be achieved by setting the attribute:
790−```
791−enableSharedExecutables = false;
792−```
793−That gives you a binary with statically linked Haskell libraries and
794−dynamically linked system libraries.
795−
796−To link both Haskell libraries and system libraries statically, the additional
797−flags `--ghc-option=-optl=-static --ghc-option=-optl=-pthread` need to be used.
798−In Nix, this is accomplished with:
799−```
800−configureFlags = [ "--ghc-option=-optl=-static" "--ghc-option=-optl=-pthread" ];
801−```
802−
803−It's important to realize, however, that most system libraries in Nix are
804−built as shared libraries only, i.e. there is just no static library
805−available that Cabal could link!
806−
807−### Building GHC with integer-simple
808−
809−By default GHC implements the Integer type using the
810−[GNU Multiple Precision Arithmetic (GMP) library](https://gmplib.org/).
811−The implementation can be found in the
812−[integer-gmp](http://hackage.haskell.org/package/integer-gmp) package.
813−
814−A potential problem with this is that GMP is licensed under the
815−[GNU Lesser General Public License (LGPL)](http://www.gnu.org/copyleft/lesser.html),
816−a kind of "copyleft" license. According to the terms of the LGPL, paragraph 5,
817−you may distribute a program that is designed to be compiled and dynamically
818−linked with the library under the terms of your choice (i.e., commercially) but
819−if your program incorporates portions of the library, if it is linked
820−statically, then your program is a "derivative"--a "work based on the
821−library"--and according to paragraph 2, section c, you "must cause the whole of
822−the work to be licensed" under the terms of the LGPL (including for free).
823−
824−The LGPL licensing for GMP is a problem for the overall licensing of binary
825−programs compiled with GHC because most distributions (and builds) of GHC use
826−static libraries. (Dynamic libraries are currently distributed only for macOS.)
827−The LGPL licensing situation may be worse: even though
828−[The Glasgow Haskell Compiler License](https://www.haskell.org/ghc/license)
829−is essentially a "free software" license (BSD3), according to
830−paragraph 2 of the LGPL, GHC must be distributed under the terms of the LGPL!
831−
832−To work around these problems GHC can be build with a slower but LGPL-free
833−alternative implemention for Integer called
834−[integer-simple](http://hackage.haskell.org/package/integer-simple).
835−
836−To get a GHC compiler build with `integer-simple` instead of `integer-gmp` use
837−the attribute: `haskell.compiler.integer-simple."${ghcVersion}"`.
838−For example:
839−```
840−$ nix-build -E '(import <nixpkgs> {}).haskell.compiler.integer-simple.ghc802'
841−...
842−$ result/bin/ghc-pkg list | grep integer
843− integer-simple-0.1.1.1
844−```
845−The following command displays the complete list of GHC compilers build with `integer-simple`:
846−```
847−$ nix-env -f "<nixpkgs>" -qaP -A haskell.compiler.integer-simple
848−haskell.compiler.integer-simple.ghc7102 ghc-7.10.2
849−haskell.compiler.integer-simple.ghc7103 ghc-7.10.3
850−haskell.compiler.integer-simple.ghc722 ghc-7.2.2
851−haskell.compiler.integer-simple.ghc742 ghc-7.4.2
852−haskell.compiler.integer-simple.ghc783 ghc-7.8.3
853−haskell.compiler.integer-simple.ghc784 ghc-7.8.4
854−haskell.compiler.integer-simple.ghc801 ghc-8.0.1
855−haskell.compiler.integer-simple.ghc802 ghc-8.0.2
856−haskell.compiler.integer-simple.ghcHEAD ghc-8.1.20170106
857−```
858−
859−To get a package set supporting `integer-simple` use the attribute:
860−`haskell.packages.integer-simple."${ghcVersion}"`. For example
861−use the following to get the `scientific` package build with `integer-simple`:
862−```shell
863−nix-build -A haskell.packages.integer-simple.ghc802.scientific
864−```
865−
866−### Quality assurance
867−
868−The `haskell.lib` library includes a number of functions for checking for
869−various imperfections in Haskell packages. It's useful to apply these functions
870−to your own Haskell packages and integrate that in a Continuous Integration
871−server like [hydra](https://nixos.org/hydra/) to assure your packages maintain a
872−minimum level of quality. This section discusses some of these functions.
873−
874−#### failOnAllWarnings
875−
876−Applying `haskell.lib.failOnAllWarnings` to a Haskell package enables the
877−`-Wall` and `-Werror` GHC options to turn all warnings into build failures.
878−
879−#### buildStrictly
880−
881−Applying `haskell.lib.buildStrictly` to a Haskell package calls
882−`failOnAllWarnings` on the given package to turn all warnings into build
883−failures. Additionally the source of your package is gotten from first invoking
884−`cabal sdist` to ensure all needed files are listed in the Cabal file.
885−
886−#### checkUnusedPackages
887−
888−Applying `haskell.lib.checkUnusedPackages` to a Haskell package invokes
889−the [packunused](http://hackage.haskell.org/package/packunused) tool on the
890−package. `packunused` complains when it finds packages listed as build-depends
891−in the Cabal file which are redundant. For example:
892−
893−```
894−$ nix-build -E 'let pkgs = import <nixpkgs> {}; in pkgs.haskell.lib.checkUnusedPackages {} pkgs.haskellPackages.scientific'
895−these derivations will be built:
896− /nix/store/3lc51cxj2j57y3zfpq5i69qbzjpvyci1-scientific-0.3.5.1.drv
897−...
898−detected package components
899−~~~~~~~~~~~~~~~~~~~~~~~~~~~
900−
901− - library
902− - testsuite(s): test-scientific
903− - benchmark(s): bench-scientific*
904−
905−(component names suffixed with '*' are not configured to be built)
906−
907−library
908−~~~~~~~
909−
910−The following package dependencies seem redundant:
911−
912− - ghc-prim-0.5.0.0
913−
914−testsuite(test-scientific)
915−~~~~~~~~~~~~~~~~~~~~~~~~~~
916−
917−no redundant packages dependencies found
918−
919−builder for ‘/nix/store/3lc51cxj2j57y3zfpq5i69qbzjpvyci1-scientific-0.3.5.1.drv’ failed with exit code 1
920−error: build of ‘/nix/store/3lc51cxj2j57y3zfpq5i69qbzjpvyci1-scientific-0.3.5.1.drv’ failed
921−```
922−
923−As you can see, `packunused` finds out that although the testsuite component has
924−no redundant dependencies the library component of `scientific-0.3.5.1` depends
925−on `ghc-prim` which is unused in the library.
926−
927−## Other resources
928−
929− - The Youtube video [Nix Loves Haskell](https://www.youtube.com/watch?v=BsBhi_r-OeE)
930− provides an introduction into Haskell NG aimed at beginners. The slides are
931− available at http://cryp.to/nixos-meetup-3-slides.pdf and also -- in a form
932− ready for cut & paste -- at
933− https://github.com/NixOS/cabal2nix/blob/master/doc/nixos-meetup-3-slides.md.
934−
935− - Another Youtube video is [Escaping Cabal Hell with Nix](https://www.youtube.com/watch?v=mQd3s57n_2Y),
936− which discusses the subject of Haskell development with Nix but also provides
937− a basic introduction to Nix as well, i.e. it's suitable for viewers with
938− almost no prior Nix experience.
939−
940− - Oliver Charles wrote a very nice [Tutorial how to develop Haskell packages with Nix](http://wiki.ocharles.org.uk/Nix).
941−
942− - The *Journey into the Haskell NG infrastructure* series of postings
943− describe the new Haskell infrastructure in great detail:
944−
945− - [Part 1](https://nixos.org/nix-dev/2015-January/015591.html)
946− explains the differences between the old and the new code and gives
947− instructions how to migrate to the new setup.
948−
949− - [Part 2](https://nixos.org/nix-dev/2015-January/015608.html)
950− looks in-depth at how to tweak and configure your setup by means of
951− overrides.
952−
953− - [Part 3](https://nixos.org/nix-dev/2015-April/016912.html)
954− describes the infrastructure that keeps the Haskell package set in Nixpkgs
955− up-to-date.
doc/languages-frameworks/haskell.section.mdnew file+1091
@@ -0,0 +1,1091 @@
1+---
2+title: User's Guide for Haskell in Nixpkgs
3+author: Peter Simons
4+date: 2015-06-01
5+---
6+# User's Guide to the Haskell Infrastructure
7+
8+
9+## How to install Haskell packages
10+
11+Nixpkgs distributes build instructions for all Haskell packages registered on
12+[Hackage](http://hackage.haskell.org/), but strangely enough normal Nix package
13+lookups don't seem to discover any of them, except for the default version of ghc, cabal-install, and stack:
14+```
15+$ nix-env -i alex
16+error: selector ‘alex’ matches no derivations
17+$ nix-env -qa ghc
18+ghc-7.10.2
19+```
20+
21+The Haskell package set is not registered in the top-level namespace because it
22+is *huge*. If all Haskell packages were visible to these commands, then
23+name-based search/install operations would be much slower than they are now. We
24+avoided that by keeping all Haskell-related packages in a separate attribute
25+set called `haskellPackages`, which the following command will list:
26+```
27+$ nix-env -f "<nixpkgs>" -qaP -A haskellPackages
28+haskellPackages.a50 a50-0.5
29+haskellPackages.abacate haskell-abacate-0.0.0.0
30+haskellPackages.abcBridge haskell-abcBridge-0.12
31+haskellPackages.afv afv-0.1.1
32+haskellPackages.alex alex-3.1.4
33+haskellPackages.Allure Allure-0.4.101.1
34+haskellPackages.alms alms-0.6.7
35+[... some 8000 entries omitted ...]
36+```
37+
38+To install any of those packages into your profile, refer to them by their
39+attribute path (first column):
40+```shell
41+nix-env -f "<nixpkgs>" -iA haskellPackages.Allure ...
42+```
43+
44+The attribute path of any Haskell packages corresponds to the name of that
45+particular package on Hackage: the package `cabal-install` has the attribute
46+`haskellPackages.cabal-install`, and so on. (Actually, this convention causes
47+trouble with packages like `3dmodels` and `4Blocks`, because these names are
48+invalid identifiers in the Nix language. The issue of how to deal with these
49+rare corner cases is currently unresolved.)
50+
51+Haskell packages whose Nix name (second column) begins with a `haskell-` prefix
52+are packages that provide a library whereas packages without that prefix
53+provide just executables. Libraries may provide executables too, though: the
54+package `haskell-pandoc`, for example, installs both a library and an
55+application. You can install and use Haskell executables just like any other
56+program in Nixpkgs, but using Haskell libraries for development is a bit
57+trickier and we'll address that subject in great detail in section [How to
58+create a development environment].
59+
60+Attribute paths are deterministic inside of Nixpkgs, but the path necessary to
61+reach Nixpkgs varies from system to system. We dodged that problem by giving
62+`nix-env` an explicit `-f "<nixpkgs>"` parameter, but if you call `nix-env`
63+without that flag, then chances are the invocation fails:
64+```
65+$ nix-env -iA haskellPackages.cabal-install
66+error: attribute ‘haskellPackages’ in selection path
67+ ‘haskellPackages.cabal-install’ not found
68+```
69+
70+On NixOS, for example, Nixpkgs does *not* exist in the top-level namespace by
71+default. To figure out the proper attribute path, it's easiest to query for the
72+path of a well-known Nixpkgs package, i.e.:
73+```
74+$ nix-env -qaP coreutils
75+nixos.coreutils coreutils-8.23
76+```
77+
78+If your system responds like that (most NixOS installations will), then the
79+attribute path to `haskellPackages` is `nixos.haskellPackages`. Thus, if you
80+want to use `nix-env` without giving an explicit `-f` flag, then that's the way
81+to do it:
82+```shell
83+nix-env -qaP -A nixos.haskellPackages
84+nix-env -iA nixos.haskellPackages.cabal-install
85+```
86+
87+Our current default compiler is GHC 7.10.x and the `haskellPackages` set
88+contains packages built with that particular version. Nixpkgs contains the
89+latest major release of every GHC since 6.10.4, however, and there is a whole
90+family of package sets available that defines Hackage packages built with each
91+of those compilers, too:
92+```shell
93+nix-env -f "<nixpkgs>" -qaP -A haskell.packages.ghc6123
94+nix-env -f "<nixpkgs>" -qaP -A haskell.packages.ghc763
95+```
96+
97+The name `haskellPackages` is really just a synonym for
98+`haskell.packages.ghc7102`, because we prefer that package set internally and
99+recommend it to our users as their default choice, but ultimately you are free
100+to compile your Haskell packages with any GHC version you please. The following
101+command displays the complete list of available compilers:
102+```
103+$ nix-env -f "<nixpkgs>" -qaP -A haskell.compiler
104+haskell.compiler.ghc6104 ghc-6.10.4
105+haskell.compiler.ghc6123 ghc-6.12.3
106+haskell.compiler.ghc704 ghc-7.0.4
107+haskell.compiler.ghc722 ghc-7.2.2
108+haskell.compiler.ghc742 ghc-7.4.2
109+haskell.compiler.ghc763 ghc-7.6.3
110+haskell.compiler.ghc784 ghc-7.8.4
111+haskell.compiler.ghc7102 ghc-7.10.2
112+haskell.compiler.ghcHEAD ghc-7.11.20150402
113+haskell.compiler.ghcNokinds ghc-nokinds-7.11.20150704
114+haskell.compiler.ghcjs ghcjs-0.1.0
115+haskell.compiler.jhc jhc-0.8.2
116+haskell.compiler.uhc uhc-1.1.9.0
117+```
118+
119+We have no package sets for `jhc` or `uhc` yet, unfortunately, but for every
120+version of GHC listed above, there exists a package set based on that compiler.
121+Also, the attributes `haskell.compiler.ghcXYC` and
122+`haskell.packages.ghcXYC.ghc` are synonymous for the sake of convenience.
123+
124+## How to create a development environment
125+
126+### How to install a compiler
127+
128+A simple development environment consists of a Haskell compiler and one or both
129+of the tools `cabal-install` and `stack`. We saw in section
130+[How to install Haskell packages] how you can install those programs into your
131+user profile:
132+```shell
133+nix-env -f "<nixpkgs>" -iA haskellPackages.ghc haskellPackages.cabal-install
134+```
135+
136+Instead of the default package set `haskellPackages`, you can also use the more
137+precise name `haskell.compiler.ghc7102`, which has the advantage that it refers
138+to the same GHC version regardless of what Nixpkgs considers "default" at any
139+given time.
140+
141+Once you've made those tools available in `$PATH`, it's possible to build
142+Hackage packages the same way people without access to Nix do it all the time:
143+```shell
144+cabal get lens-4.11 && cd lens-4.11
145+cabal install -j --dependencies-only
146+cabal configure
147+cabal build
148+```
149+
150+If you enjoy working with Cabal sandboxes, then that's entirely possible too:
151+just execute the command
152+```shell
153+cabal sandbox init
154+```
155+before installing the required dependencies.
156+
157+The `nix-shell` utility makes it easy to switch to a different compiler
158+version; just enter the Nix shell environment with the command
159+```shell
160+nix-shell -p haskell.compiler.ghc784
161+```
162+to bring GHC 7.8.4 into `$PATH`. Alternatively, you can use Stack instead of
163+`nix-shell` directly to select compiler versions and other build tools
164+per-project. It uses `nix-shell` under the hood when Nix support is turned on.
165+See [How to build a Haskell project using Stack].
166+
167+If you're using `cabal-install`, re-running `cabal configure` inside the spawned
168+shell switches your build to use that compiler instead. If you're working on
169+a project that doesn't depend on any additional system libraries outside of GHC,
170+then it's even sufficient to just run the `cabal configure` command inside of
171+the shell:
172+```shell
173+nix-shell -p haskell.compiler.ghc784 --command "cabal configure"
174+```
175+
176+Afterwards, all other commands like `cabal build` work just fine in any shell
177+environment, because the configure phase recorded the absolute paths to all
178+required tools like GHC in its build configuration inside of the `dist/`
179+directory. Please note, however, that `nix-collect-garbage` can break such an
180+environment because the Nix store paths created by `nix-shell` aren't "alive"
181+anymore once `nix-shell` has terminated. If you find that your Haskell builds
182+no longer work after garbage collection, then you'll have to re-run `cabal
183+configure` inside of a new `nix-shell` environment.
184+
185+### How to install a compiler with libraries
186+
187+GHC expects to find all installed libraries inside of its own `lib` directory.
188+This approach works fine on traditional Unix systems, but it doesn't work for
189+Nix, because GHC's store path is immutable once it's built. We cannot install
190+additional libraries into that location. As a consequence, our copies of GHC
191+don't know any packages except their own core libraries, like `base`,
192+`containers`, `Cabal`, etc.
193+
194+We can register additional libraries to GHC, however, using a special build
195+function called `ghcWithPackages`. That function expects one argument: a
196+function that maps from an attribute set of Haskell packages to a list of
197+packages, which determines the libraries known to that particular version of
198+GHC. For example, the Nix expression `ghcWithPackages (pkgs: [pkgs.mtl])`
199+generates a copy of GHC that has the `mtl` library registered in addition to
200+its normal core packages:
201+```
202+$ nix-shell -p "haskellPackages.ghcWithPackages (pkgs: [pkgs.mtl])"
203+
204+[nix-shell:~]$ ghc-pkg list mtl
205+/nix/store/zy79...-ghc-7.10.2/lib/ghc-7.10.2/package.conf.d:
206+ mtl-2.2.1
207+```
208+
209+This function allows users to define their own development environment by means
210+of an override. After adding the following snippet to `~/.config/nixpkgs/config.nix`,
211+```nix
212+{
213+ packageOverrides = super: let self = super.pkgs; in
214+ {
215+ myHaskellEnv = self.haskell.packages.ghc7102.ghcWithPackages
216+ (haskellPackages: with haskellPackages; [
217+ # libraries
218+ arrows async cgi criterion
219+ # tools
220+ cabal-install haskintex
221+ ]);
222+ };
223+}
224+```
225+it's possible to install that compiler with `nix-env -f "<nixpkgs>" -iA
226+myHaskellEnv`. If you'd like to switch that development environment to a
227+different version of GHC, just replace the `ghc7102` bit in the previous
228+definition with the appropriate name. Of course, it's also possible to define
229+any number of these development environments! (You can't install two of them
230+into the same profile at the same time, though, because that would result in
231+file conflicts.)
232+
233+The generated `ghc` program is a wrapper script that re-directs the real
234+GHC executable to use a new `lib` directory --- one that we specifically
235+constructed to contain all those packages the user requested:
236+```
237+$ cat $(type -p ghc)
238+#! /nix/store/xlxj...-bash-4.3-p33/bin/bash -e
239+export NIX_GHC=/nix/store/19sm...-ghc-7.10.2/bin/ghc
240+export NIX_GHCPKG=/nix/store/19sm...-ghc-7.10.2/bin/ghc-pkg
241+export NIX_GHC_DOCDIR=/nix/store/19sm...-ghc-7.10.2/share/doc/ghc/html
242+export NIX_GHC_LIBDIR=/nix/store/19sm...-ghc-7.10.2/lib/ghc-7.10.2
243+exec /nix/store/j50p...-ghc-7.10.2/bin/ghc "-B$NIX_GHC_LIBDIR" "$@"
244+```
245+
246+The variables `$NIX_GHC`, `$NIX_GHCPKG`, etc. point to the *new* store path
247+`ghcWithPackages` constructed specifically for this environment. The last line
248+of the wrapper script then executes the real `ghc`, but passes the path to the
249+new `lib` directory using GHC's `-B` flag.
250+
251+The purpose of those environment variables is to work around an impurity in the
252+popular [ghc-paths](http://hackage.haskell.org/package/ghc-paths) library. That
253+library promises to give its users access to GHC's installation paths. Only,
254+the library can't possible know that path when it's compiled, because the path
255+GHC considers its own is determined only much later, when the user configures
256+it through `ghcWithPackages`. So we [patched
257+ghc-paths](https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/haskell-modules/patches/ghc-paths-nix.patch)
258+to return the paths found in those environment variables at run-time rather
259+than trying to guess them at compile-time.
260+
261+To make sure that mechanism works properly all the time, we recommend that you
262+set those variables to meaningful values in your shell environment, too, i.e.
263+by adding the following code to your `~/.bashrc`:
264+```bash
265+if type >/dev/null 2>&1 -p ghc; then
266+ eval "$(egrep ^export "$(type -p ghc)")"
267+fi
268+```
269+
270+If you are certain that you'll use only one GHC environment which is located in
271+your user profile, then you can use the following code, too, which has the
272+advantage that it doesn't contain any paths from the Nix store, i.e. those
273+settings always remain valid even if a `nix-env -u` operation updates the GHC
274+environment in your profile:
275+```bash
276+if [ -e ~/.nix-profile/bin/ghc ]; then
277+ export NIX_GHC="$HOME/.nix-profile/bin/ghc"
278+ export NIX_GHCPKG="$HOME/.nix-profile/bin/ghc-pkg"
279+ export NIX_GHC_DOCDIR="$HOME/.nix-profile/share/doc/ghc/html"
280+ export NIX_GHC_LIBDIR="$HOME/.nix-profile/lib/ghc-$($NIX_GHC --numeric-version)"
281+fi
282+```
283+
284+### How to install a compiler with libraries, hoogle and documentation indexes
285+
286+If you plan to use your environment for interactive programming, not just
287+compiling random Haskell code, you might want to replace `ghcWithPackages` in
288+all the listings above with `ghcWithHoogle`.
289+
290+This environment generator not only produces an environment with GHC and all
291+the specified libraries, but also generates a `hoogle` and `haddock` indexes
292+for all the packages, and provides a wrapper script around `hoogle` binary that
293+uses all those things. A precise name for this thing would be
294+"`ghcWithPackagesAndHoogleAndDocumentationIndexes`", which is, regrettably, too
295+long and scary.
296+
297+For example, installing the following environment
298+```nix
299+{
300+ packageOverrides = super: let self = super.pkgs; in
301+ {
302+ myHaskellEnv = self.haskellPackages.ghcWithHoogle
303+ (haskellPackages: with haskellPackages; [
304+ # libraries
305+ arrows async cgi criterion
306+ # tools
307+ cabal-install haskintex
308+ ]);
309+ };
310+}
311+```
312+allows one to browse module documentation index [not too dissimilar to
313+this](https://downloads.haskell.org/~ghc/latest/docs/html/libraries/index.html)
314+for all the specified packages and their dependencies by directing a browser of
315+choice to `~/.nix-profile/share/doc/hoogle/index.html` (or
316+`/run/current-system/sw/share/doc/hoogle/index.html` in case you put it in
317+`environment.systemPackages` in NixOS).
318+
319+After you've marveled enough at that try adding the following to your
320+`~/.ghc/ghci.conf`
321+```
322+:def hoogle \s -> return $ ":! hoogle search -cl --count=15 \"" ++ s ++ "\""
323+:def doc \s -> return $ ":! hoogle search -cl --info \"" ++ s ++ "\""
324+```
325+and test it by typing into `ghci`:
326+```
327+:hoogle a -> a
328+:doc a -> a
329+```
330+
331+Be sure to note the links to `haddock` files in the output. With any modern and
332+properly configured terminal emulator you can just click those links to
333+navigate there.
334+
335+Finally, you can run
336+```shell
337+hoogle server --local -p 8080
338+```
339+and navigate to http://localhost:8080/ for your own local
340+[Hoogle](https://www.haskell.org/hoogle/). The `--local` flag makes the hoogle
341+server serve files from your nix store over http, without the flag it will use
342+`file://` URIs. Note, however, that Firefox and possibly other browsers
343+disallow navigation from `http://` to `file://` URIs for security reasons,
344+which might be quite an inconvenience. Versions before v5 did not have this
345+flag. See
346+[this page](http://kb.mozillazine.org/Links_to_local_pages_do_not_work) for
347+workarounds.
348+
349+For NixOS users there's a service which runs this exact command for you.
350+Specify the `packages` you want documentation for and the `haskellPackages` set
351+you want them to come from. Add the following to `configuration.nix`.
352+
353+```nix
354+services.hoogle = {
355+enable = true;
356+packages = (hpkgs: with hpkgs; [text cryptonite]);
357+haskellPackages = pkgs.haskellPackages;
358+};
359+```
360+
361+### How to build a Haskell project using Stack
362+
363+[Stack](http://haskellstack.org) is a popular build tool for Haskell projects.
364+It has first-class support for Nix. Stack can optionally use Nix to
365+automatically select the right version of GHC and other build tools to build,
366+test and execute apps in an existing project downloaded from somewhere on the
367+Internet. Pass the `--nix` flag to any `stack` command to do so, e.g.
368+```shell
369+git clone --recursive http://github.com/yesodweb/wai
370+cd wai
371+stack --nix build
372+```
373+
374+If you want `stack` to use Nix by default, you can add a `nix` section to the
375+`stack.yaml` file, as explained in the [Stack documentation][stack-nix-doc]. For
376+example:
377+```yaml
378+nix:
379+ enable: true
380+ packages: [pkgconfig zeromq zlib]
381+```
382+
383+The example configuration snippet above tells Stack to create an ad hoc
384+environment for `nix-shell` as in the below section, in which the `pkgconfig`,
385+`zeromq` and `zlib` packages from Nixpkgs are available. All `stack` commands
386+will implicitly be executed inside this ad hoc environment.
387+
388+Some projects have more sophisticated needs. For examples, some ad hoc
389+environments might need to expose Nixpkgs packages compiled in a certain way, or
390+with extra environment variables. In these cases, you'll need a `shell` field
391+instead of `packages`:
392+```yaml
393+nix:
394+ enable: true
395+ shell-file: shell.nix
396+```
397+
398+For more on how to write a `shell.nix` file see the below section. You'll need
399+to express a derivation. Note that Nixpkgs ships with a convenience wrapper
400+function around `mkDerivation` called `haskell.lib.buildStackProject` to help you
401+create this derivation in exactly the way Stack expects. All of the same inputs
402+as `mkDerivation` can be provided. For example, to build a Stack project that
403+including packages that link against a version of the R library compiled with
404+special options turned on:
405+```nix
406+with (import <nixpkgs> { });
407+
408+let R = pkgs.R.override { enableStrictBarrier = true; };
409+in
410+haskell.lib.buildStackProject {
411+ name = "HaskellR";
412+ buildInputs = [ R zeromq zlib ];
413+}
414+```
415+
416+You can select a particular GHC version to compile with by setting the
417+`ghc` attribute as an argument to `buildStackProject`. Better yet, let
418+Stack choose what GHC version it wants based on the snapshot specified
419+in `stack.yaml` (only works with Stack >= 1.1.3):
420+```nix
421+{nixpkgs ? import <nixpkgs> { }, ghc ? nixpkgs.ghc}:
422+
423+with nixpkgs;
424+
425+let R = pkgs.R.override { enableStrictBarrier = true; };
426+in
427+haskell.lib.buildStackProject {
428+ name = "HaskellR";
429+ buildInputs = [ R zeromq zlib ];
430+ inherit ghc;
431+}
432+```
433+
434+[stack-nix-doc]: http://docs.haskellstack.org/en/stable/nix_integration.html
435+
436+### How to create ad hoc environments for `nix-shell`
437+
438+The easiest way to create an ad hoc development environment is to run
439+`nix-shell` with the appropriate GHC environment given on the command-line:
440+```shell
441+nix-shell -p "haskellPackages.ghcWithPackages (pkgs: with pkgs; [mtl pandoc])"
442+```
443+
444+For more sophisticated use-cases, however, it's more convenient to save the
445+desired configuration in a file called `shell.nix` that looks like this:
446+```nix
447+{ nixpkgs ? import <nixpkgs> {}, compiler ? "ghc7102" }:
448+let
449+ inherit (nixpkgs) pkgs;
450+ ghc = pkgs.haskell.packages.${compiler}.ghcWithPackages (ps: with ps; [
451+ monad-par mtl
452+ ]);
453+in
454+pkgs.stdenv.mkDerivation {
455+ name = "my-haskell-env-0";
456+ buildInputs = [ ghc ];
457+ shellHook = "eval $(egrep ^export ${ghc}/bin/ghc)";
458+}
459+```
460+
461+Now run `nix-shell` --- or even `nix-shell --pure` --- to enter a shell
462+environment that has the appropriate compiler in `$PATH`. If you use `--pure`,
463+then add all other packages that your development environment needs into the
464+`buildInputs` attribute. If you'd like to switch to a different compiler
465+version, then pass an appropriate `compiler` argument to the expression, i.e.
466+`nix-shell --argstr compiler ghc784`.
467+
468+If you need such an environment because you'd like to compile a Hackage package
469+outside of Nix --- i.e. because you're hacking on the latest version from Git
470+---, then the package set provides suitable nix-shell environments for you
471+already! Every Haskell package has an `env` attribute that provides a shell
472+environment suitable for compiling that particular package. If you'd like to
473+hack the `lens` library, for example, then you just have to check out the
474+source code and enter the appropriate environment:
475+```
476+$ cabal get lens-4.11 && cd lens-4.11
477+Downloading lens-4.11...
478+Unpacking to lens-4.11/
479+
480+$ nix-shell "<nixpkgs>" -A haskellPackages.lens.env
481+[nix-shell:/tmp/lens-4.11]$
482+```
483+
484+At point, you can run `cabal configure`, `cabal build`, and all the other
485+development commands. Note that you need `cabal-install` installed in your
486+`$PATH` already to use it here --- the `nix-shell` environment does not provide
487+it.
488+
489+## How to create Nix builds for your own private Haskell packages
490+
491+If your own Haskell packages have build instructions for Cabal, then you can
492+convert those automatically into build instructions for Nix using the
493+`cabal2nix` utility, which you can install into your profile by running
494+`nix-env -i cabal2nix`.
495+
496+### How to build a stand-alone project
497+
498+For example, let's assume that you're working on a private project called
499+`foo`. To generate a Nix build expression for it, change into the project's
500+top-level directory and run the command:
501+```shell
502+cabal2nix . > foo.nix
503+```
504+Then write the following snippet into a file called `default.nix`:
505+```nix
506+{ nixpkgs ? import <nixpkgs> {}, compiler ? "ghc7102" }:
507+nixpkgs.pkgs.haskell.packages.${compiler}.callPackage ./foo.nix { }
508+```
509+
510+Finally, store the following code in a file called `shell.nix`:
511+```nix
512+{ nixpkgs ? import <nixpkgs> {}, compiler ? "ghc7102" }:
513+(import ./default.nix { inherit nixpkgs compiler; }).env
514+```
515+
516+At this point, you can run `nix-build` to have Nix compile your project and
517+install it into a Nix store path. The local directory will contain a symlink
518+called `result` after `nix-build` returns that points into that location. Of
519+course, passing the flag `--argstr compiler ghc763` allows switching the build
520+to any version of GHC currently supported.
521+
522+Furthermore, you can call `nix-shell` to enter an interactive development
523+environment in which you can use `cabal configure` and `cabal build` to develop
524+your code. That environment will automatically contain a proper GHC derivation
525+with all the required libraries registered as well as all the system-level
526+libraries your package might need.
527+
528+If your package does not depend on any system-level libraries, then it's
529+sufficient to run
530+```shell
531+nix-shell --command "cabal configure"
532+```
533+once to set up your build. `cabal-install` determines the absolute paths to all
534+resources required for the build and writes them into a config file in the
535+`dist/` directory. Once that's done, you can run `cabal build` and any other
536+command for that project even outside of the `nix-shell` environment. This
537+feature is particularly nice for those of us who like to edit their code with
538+an IDE, like Emacs' `haskell-mode`, because it's not necessary to start Emacs
539+inside of nix-shell just to make it find out the necessary settings for
540+building the project; `cabal-install` has already done that for us.
541+
542+If you want to do some quick-and-dirty hacking and don't want to bother setting
543+up a `default.nix` and `shell.nix` file manually, then you can use the
544+`--shell` flag offered by `cabal2nix` to have it generate a stand-alone
545+`nix-shell` environment for you. With that feature, running
546+```shell
547+cabal2nix --shell . > shell.nix
548+nix-shell --command "cabal configure"
549+```
550+is usually enough to set up a build environment for any given Haskell package.
551+You can even use that generated file to run `nix-build`, too:
552+```shell
553+nix-build shell.nix
554+```
555+
556+### How to build projects that depend on each other
557+
558+If you have multiple private Haskell packages that depend on each other, then
559+you'll have to register those packages in the Nixpkgs set to make them visible
560+for the dependency resolution performed by `callPackage`. First of all, change
561+into each of your projects top-level directories and generate a `default.nix`
562+file with `cabal2nix`:
563+```shell
564+cd ~/src/foo && cabal2nix . > default.nix
565+cd ~/src/bar && cabal2nix . > default.nix
566+```
567+Then edit your `~/.config/nixpkgs/config.nix` file to register those builds in the
568+default Haskell package set:
569+```nix
570+{
571+ packageOverrides = super: let self = super.pkgs; in
572+ {
573+ haskellPackages = super.haskellPackages.override {
574+ overrides = self: super: {
575+ foo = self.callPackage ../src/foo {};
576+ bar = self.callPackage ../src/bar {};
577+ };
578+ };
579+ };
580+}
581+```
582+Once that's accomplished, `nix-env -f "<nixpkgs>" -qA haskellPackages` will
583+show your packages like any other package from Hackage, and you can build them
584+```shell
585+nix-build "<nixpkgs>" -A haskellPackages.foo
586+```
587+or enter an interactive shell environment suitable for building them:
588+```shell
589+nix-shell "<nixpkgs>" -A haskellPackages.bar.env
590+```
591+
592+## Miscellaneous Topics
593+
594+### How to build with profiling enabled
595+
596+Every Haskell package set takes a function called `overrides` that you can use
597+to manipulate the package as much as you please. One useful application of this
598+feature is to replace the default `mkDerivation` function with one that enables
599+library profiling for all packages. To accomplish that add the following
600+snippet to your `~/.config/nixpkgs/config.nix` file:
601+```nix
602+{
603+ packageOverrides = super: let self = super.pkgs; in
604+ {
605+ profiledHaskellPackages = self.haskellPackages.override {
606+ overrides = self: super: {
607+ mkDerivation = args: super.mkDerivation (args // {
608+ enableLibraryProfiling = true;
609+ });
610+ };
611+ };
612+ };
613+}
614+```
615+Then, replace instances of `haskellPackages` in the `cabal2nix`-generated
616+`default.nix` or `shell.nix` files with `profiledHaskellPackages`.
617+
618+### How to override package versions in a compiler-specific package set
619+
620+Nixpkgs provides the latest version of
621+[`ghc-events`](http://hackage.haskell.org/package/ghc-events), which is 0.4.4.0
622+at the time of this writing. This is fine for users of GHC 7.10.x, but GHC
623+7.8.4 cannot compile that binary. Now, one way to solve that problem is to
624+register an older version of `ghc-events` in the 7.8.x-specific package set.
625+The first step is to generate Nix build instructions with `cabal2nix`:
626+```shell
627+cabal2nix cabal://ghc-events-0.4.3.0 > ~/.nixpkgs/ghc-events-0.4.3.0.nix
628+```
629+Then add the override in `~/.config/nixpkgs/config.nix`:
630+```nix
631+{
632+ packageOverrides = super: let self = super.pkgs; in
633+ {
634+ haskell = super.haskell // {
635+ packages = super.haskell.packages // {
636+ ghc784 = super.haskell.packages.ghc784.override {
637+ overrides = self: super: {
638+ ghc-events = self.callPackage ./ghc-events-0.4.3.0.nix {};
639+ };
640+ };
641+ };
642+ };
643+ };
644+}
645+```
646+
647+This code is a little crazy, no doubt, but it's necessary because the intuitive
648+version
649+```nix
650+{ # ...
651+
652+ haskell.packages.ghc784 = super.haskell.packages.ghc784.override {
653+ overrides = self: super: {
654+ ghc-events = self.callPackage ./ghc-events-0.4.3.0.nix {};
655+ };
656+ };
657+}
658+```
659+doesn't do what we want it to: that code replaces the `haskell` package set in
660+Nixpkgs with one that contains only one entry,`packages`, which contains only
661+one entry `ghc784`. This override loses the `haskell.compiler` set, and it
662+loses the `haskell.packages.ghcXYZ` sets for all compilers but GHC 7.8.4. To
663+avoid that problem, we have to perform the convoluted little dance from above,
664+iterating over each step in hierarchy.
665+
666+Once it's accomplished, however, we can install a variant of `ghc-events`
667+that's compiled with GHC 7.8.4:
668+```shell
669+nix-env -f "<nixpkgs>" -iA haskell.packages.ghc784.ghc-events
670+```
671+Unfortunately, it turns out that this build fails again while executing the
672+test suite! Apparently, the release archive on Hackage is missing some data
673+files that the test suite requires, so we cannot run it. We accomplish that by
674+re-generating the Nix expression with the `--no-check` flag:
675+```shell
676+cabal2nix --no-check cabal://ghc-events-0.4.3.0 > ~/.nixpkgs/ghc-events-0.4.3.0.nix
677+```
678+Now the builds succeeds.
679+
680+Of course, in the concrete example of `ghc-events` this whole exercise is not
681+an ideal solution, because `ghc-events` can analyze the output emitted by any
682+version of GHC later than 6.12 regardless of the compiler version that was used
683+to build the `ghc-events` executable, so strictly speaking there's no reason to
684+prefer one built with GHC 7.8.x in the first place. However, for users who
685+cannot use GHC 7.10.x at all for some reason, the approach of downgrading to an
686+older version might be useful.
687+
688+### How to override packages in all compiler-specific package sets
689+
690+In the previous section we learned how to override a package in a single
691+compiler-specific package set. You may have some overrides defined that you want
692+to use across multiple package sets. To accomplish this you could use the
693+technique that we learned in the previous section by repeating the overrides for
694+all the compiler-specific package sets. For example:
695+
696+```nix
697+{
698+ packageOverrides = super: let self = super.pkgs; in
699+ {
700+ haskell = super.haskell // {
701+ packages = super.haskell.packages // {
702+ ghc784 = super.haskell.packages.ghc784.override {
703+ overrides = self: super: {
704+ my-package = ...;
705+ my-other-package = ...;
706+ };
707+ };
708+ ghc822 = super.haskell.packages.ghc784.override {
709+ overrides = self: super: {
710+ my-package = ...;
711+ my-other-package = ...;
712+ };
713+ };
714+ ...
715+ };
716+ };
717+ };
718+}
719+```
720+
721+However there's a more convenient way to override all compiler-specific package
722+sets at once:
723+
724+```nix
725+{
726+ packageOverrides = super: let self = super.pkgs; in
727+ {
728+ haskell = super.haskell // {
729+ packageOverrides = self: super: {
730+ my-package = ...;
731+ my-other-package = ...;
732+ };
733+ };
734+ };
735+}
736+```
737+
738+### How to specify source overrides for your Haskell package
739+
740+When starting a Haskell project you can use `developPackage`
741+to define a derivation for your package at the `root` path
742+as well as source override versions for Hackage packages, like so:
743+
744+```nix
745+# default.nix
746+{ compilerVersion ? "ghc842" }:
747+let
748+ # pinning nixpkgs using new Nix 2.0 builtin `fetchGit`
749+ pkgs = import (fetchGit (import ./version.nix)) { };
750+ compiler = pkgs.haskell.packages."${compilerVersion}";
751+ pkg = compiler.developPackage {
752+ root = ./.;
753+ source-overrides = {
754+ # Let's say the GHC 8.4.2 haskellPackages uses 1.6.0.0 and your test suite is incompatible with >= 1.6.0.0
755+ HUnit = "1.5.0.0";
756+ };
757+ };
758+in pkg
759+```
760+
761+This could be used in place of a simplified `stack.yaml` defining a Nix
762+derivation for your Haskell package.
763+
764+As you can see this allows you to specify only the source version found on
765+Hackage and nixpkgs will take care of the rest.
766+
767+You can also specify `buildInputs` for your Haskell derivation for packages
768+that directly depend on external libraries like so:
769+
770+```nix
771+# default.nix
772+{ compilerVersion ? "ghc842" }:
773+let
774+ # pinning nixpkgs using new Nix 2.0 builtin `fetchGit`
775+ pkgs = import (fetchGit (import ./version.nix)) { };
776+ compiler = pkgs.haskell.packages."${compilerVersion}";
777+ pkg = compiler.developPackage {
778+ root = ./.;
779+ source-overrides = {
780+ HUnit = "1.5.0.0"; # Let's say the GHC 8.4.2 haskellPackages uses 1.6.0.0 and your test suite is incompatible with >= 1.6.0.0
781+ };
782+ };
783+ # in case your package source depends on any libraries directly, not just transitively.
784+ buildInputs = [ zlib ];
785+in pkg.overrideAttrs(attrs: {
786+ buildInputs = attrs.buildInputs ++ buildInputs;
787+})
788+```
789+
790+Notice that you will need to override (via `overrideAttrs` or similar) the
791+derivation returned by the `developPackage` Nix lambda as there is no `buildInputs`
792+named argument you can pass directly into the `developPackage` lambda.
793+
794+### How to recover from GHC's infamous non-deterministic library ID bug
795+
796+GHC and distributed build farms don't get along well:
797+
798+ - https://ghc.haskell.org/trac/ghc/ticket/4012
799+
800+When you see an error like this one
801+```
802+package foo-0.7.1.0 is broken due to missing package
803+text-1.2.0.4-98506efb1b9ada233bb5c2b2db516d91
804+```
805+then you have to download and re-install `foo` and all its dependents from
806+scratch:
807+```shell
808+nix-store -q --referrers /nix/store/*-haskell-text-1.2.0.4 \
809+ | xargs -L 1 nix-store --repair-path
810+```
811+
812+If you're using additional Hydra servers other than `hydra.nixos.org`, then it
813+might be necessary to purge the local caches that store data from those
814+machines to disable these binary channels for the duration of the previous
815+command, i.e. by running:
816+```shell
817+rm ~/.cache/nix/binary-cache*.sqlite
818+```
819+
820+### Builds on Darwin fail with `math.h` not found
821+
822+Users of GHC on Darwin have occasionally reported that builds fail, because the
823+compiler complains about a missing include file:
824+```
825+fatal error: 'math.h' file not found
826+```
827+The issue has been discussed at length in [ticket
828+6390](https://github.com/NixOS/nixpkgs/issues/6390), and so far no good
829+solution has been proposed. As a work-around, users who run into this problem
830+can configure the environment variables
831+```shell
832+export NIX_CFLAGS_COMPILE="-idirafter /usr/include"
833+export NIX_CFLAGS_LINK="-L/usr/lib"
834+```
835+in their `~/.bashrc` file to avoid the compiler error.
836+
837+### Builds using Stack complain about missing system libraries
838+
839+```
840+-- While building package zlib-0.5.4.2 using:
841+ runhaskell -package=Cabal-1.22.4.0 -clear-package-db [... lots of flags ...]
842+Process exited with code: ExitFailure 1
843+Logs have been written to: /home/foo/src/stack-ide/.stack-work/logs/zlib-0.5.4.2.log
844+
845+Configuring zlib-0.5.4.2...
846+Setup.hs: Missing dependency on a foreign library:
847+* Missing (or bad) header file: zlib.h
848+This problem can usually be solved by installing the system package that
849+provides this library (you may need the "-dev" version). If the library is
850+already installed but in a non-standard location then you can use the flags
851+--extra-include-dirs= and --extra-lib-dirs= to specify where it is.
852+If the header file does exist, it may contain errors that are caught by the C
853+compiler at the preprocessing stage. In this case you can re-run configure
854+with the verbosity flag -v3 to see the error messages.
855+```
856+
857+When you run the build inside of the nix-shell environment, the system
858+is configured to find `libz.so` without any special flags -- the compiler
859+and linker "just know" how to find it. Consequently, Cabal won't record
860+any search paths for `libz.so` in the package description, which means
861+that the package works fine inside of nix-shell, but once you leave the
862+shell the shared object can no longer be found. That issue is by no
863+means specific to Stack: you'll have that problem with any other
864+Haskell package that's built inside of nix-shell but run outside of that
865+environment.
866+
867+You can remedy this issue in several ways. The easiest is to add a `nix` section
868+to the `stack.yaml` like the following:
869+```yaml
870+nix:
871+ enable: true
872+ packages: [ zlib ]
873+```
874+
875+Stack's Nix support knows to add `${zlib.out}/lib` and `${zlib.dev}/include`
876+as an `--extra-lib-dirs` and `extra-include-dirs`, respectively.
877+Alternatively, you can achieve the same effect by hand. First of all, run
878+```
879+$ nix-build --no-out-link "<nixpkgs>" -A zlib
880+/nix/store/alsvwzkiw4b7ip38l4nlfjijdvg3fvzn-zlib-1.2.8
881+```
882+to find out the store path of the system's zlib library. Now, you can
883+
884+ 1. add that path (plus a "/lib" suffix) to your `$LD_LIBRARY_PATH`
885+ environment variable to make sure your system linker finds `libz.so`
886+ automatically. It's no pretty solution, but it will work.
887+
888+ 2. As a variant of (1), you can also install any number of system
889+ libraries into your user's profile (or some other profile) and point
890+ `$LD_LIBRARY_PATH` to that profile instead, so that you don't have to
891+ list dozens of those store paths all over the place.
892+
893+ 3. The solution I prefer is to call stack with an appropriate
894+ --extra-lib-dirs flag like so:
895+ ```shell
896+ stack --extra-lib-dirs=/nix/store/alsvwzkiw4b7ip38l4nlfjijdvg3fvzn-zlib-1.2.8/lib build
897+ ```
898+
899+Typically, you'll need `--extra-include-dirs` as well. It's possible
900+to add those flag to the project's `stack.yaml` or your user's
901+global `~/.stack/global/stack.yaml` file so that you don't have to
902+specify them manually every time. But again, you're likely better off
903+using Stack's Nix support instead.
904+
905+The same thing applies to `cabal configure`, of course, if you're
906+building with `cabal-install` instead of Stack.
907+
908+### Creating statically linked binaries
909+
910+There are two levels of static linking. The first option is to configure the
911+build with the Cabal flag `--disable-executable-dynamic`. In Nix expressions,
912+this can be achieved by setting the attribute:
913+```
914+enableSharedExecutables = false;
915+```
916+That gives you a binary with statically linked Haskell libraries and
917+dynamically linked system libraries.
918+
919+To link both Haskell libraries and system libraries statically, the additional
920+flags `--ghc-option=-optl=-static --ghc-option=-optl=-pthread` need to be used.
921+In Nix, this is accomplished with:
922+```
923+configureFlags = [ "--ghc-option=-optl=-static" "--ghc-option=-optl=-pthread" ];
924+```
925+
926+It's important to realize, however, that most system libraries in Nix are
927+built as shared libraries only, i.e. there is just no static library
928+available that Cabal could link!
929+
930+### Building GHC with integer-simple
931+
932+By default GHC implements the Integer type using the
933+[GNU Multiple Precision Arithmetic (GMP) library](https://gmplib.org/).
934+The implementation can be found in the
935+[integer-gmp](http://hackage.haskell.org/package/integer-gmp) package.
936+
937+A potential problem with this is that GMP is licensed under the
938+[GNU Lesser General Public License (LGPL)](http://www.gnu.org/copyleft/lesser.html),
939+a kind of "copyleft" license. According to the terms of the LGPL, paragraph 5,
940+you may distribute a program that is designed to be compiled and dynamically
941+linked with the library under the terms of your choice (i.e., commercially) but
942+if your program incorporates portions of the library, if it is linked
943+statically, then your program is a "derivative"--a "work based on the
944+library"--and according to paragraph 2, section c, you "must cause the whole of
945+the work to be licensed" under the terms of the LGPL (including for free).
946+
947+The LGPL licensing for GMP is a problem for the overall licensing of binary
948+programs compiled with GHC because most distributions (and builds) of GHC use
949+static libraries. (Dynamic libraries are currently distributed only for macOS.)
950+The LGPL licensing situation may be worse: even though
951+[The Glasgow Haskell Compiler License](https://www.haskell.org/ghc/license)
952+is essentially a "free software" license (BSD3), according to
953+paragraph 2 of the LGPL, GHC must be distributed under the terms of the LGPL!
954+
955+To work around these problems GHC can be build with a slower but LGPL-free
956+alternative implemention for Integer called
957+[integer-simple](http://hackage.haskell.org/package/integer-simple).
958+
959+To get a GHC compiler build with `integer-simple` instead of `integer-gmp` use
960+the attribute: `haskell.compiler.integer-simple."${ghcVersion}"`.
961+For example:
962+```
963+$ nix-build -E '(import <nixpkgs> {}).haskell.compiler.integer-simple.ghc802'
964+...
965+$ result/bin/ghc-pkg list | grep integer
966+ integer-simple-0.1.1.1
967+```
968+The following command displays the complete list of GHC compilers build with `integer-simple`:
969+```
970+$ nix-env -f "<nixpkgs>" -qaP -A haskell.compiler.integer-simple
971+haskell.compiler.integer-simple.ghc7102 ghc-7.10.2
972+haskell.compiler.integer-simple.ghc7103 ghc-7.10.3
973+haskell.compiler.integer-simple.ghc722 ghc-7.2.2
974+haskell.compiler.integer-simple.ghc742 ghc-7.4.2
975+haskell.compiler.integer-simple.ghc783 ghc-7.8.3
976+haskell.compiler.integer-simple.ghc784 ghc-7.8.4
977+haskell.compiler.integer-simple.ghc801 ghc-8.0.1
978+haskell.compiler.integer-simple.ghc802 ghc-8.0.2
979+haskell.compiler.integer-simple.ghcHEAD ghc-8.1.20170106
980+```
981+
982+To get a package set supporting `integer-simple` use the attribute:
983+`haskell.packages.integer-simple."${ghcVersion}"`. For example
984+use the following to get the `scientific` package build with `integer-simple`:
985+```shell
986+nix-build -A haskell.packages.integer-simple.ghc802.scientific
987+```
988+
989+### Quality assurance
990+
991+The `haskell.lib` library includes a number of functions for checking for
992+various imperfections in Haskell packages. It's useful to apply these functions
993+to your own Haskell packages and integrate that in a Continuous Integration
994+server like [hydra](https://nixos.org/hydra/) to assure your packages maintain a
995+minimum level of quality. This section discusses some of these functions.
996+
997+#### failOnAllWarnings
998+
999+Applying `haskell.lib.failOnAllWarnings` to a Haskell package enables the
1000+`-Wall` and `-Werror` GHC options to turn all warnings into build failures.
1001+
1002+#### buildStrictly
1003+
1004+Applying `haskell.lib.buildStrictly` to a Haskell package calls
1005+`failOnAllWarnings` on the given package to turn all warnings into build
1006+failures. Additionally the source of your package is gotten from first invoking
1007+`cabal sdist` to ensure all needed files are listed in the Cabal file.
1008+
1009+#### checkUnusedPackages
1010+
1011+Applying `haskell.lib.checkUnusedPackages` to a Haskell package invokes
1012+the [packunused](http://hackage.haskell.org/package/packunused) tool on the
1013+package. `packunused` complains when it finds packages listed as build-depends
1014+in the Cabal file which are redundant. For example:
1015+
1016+```
1017+$ nix-build -E 'let pkgs = import <nixpkgs> {}; in pkgs.haskell.lib.checkUnusedPackages {} pkgs.haskellPackages.scientific'
1018+these derivations will be built:
1019+ /nix/store/3lc51cxj2j57y3zfpq5i69qbzjpvyci1-scientific-0.3.5.1.drv
1020+...
1021+detected package components
1022+~~~~~~~~~~~~~~~~~~~~~~~~~~~
1023+
1024+ - library
1025+ - testsuite(s): test-scientific
1026+ - benchmark(s): bench-scientific*
1027+
1028+(component names suffixed with '*' are not configured to be built)
1029+
1030+library
1031+~~~~~~~
1032+
1033+The following package dependencies seem redundant:
1034+
1035+ - ghc-prim-0.5.0.0
1036+
1037+testsuite(test-scientific)
1038+~~~~~~~~~~~~~~~~~~~~~~~~~~
1039+
1040+no redundant packages dependencies found
1041+
1042+builder for ‘/nix/store/3lc51cxj2j57y3zfpq5i69qbzjpvyci1-scientific-0.3.5.1.drv’ failed with exit code 1
1043+error: build of ‘/nix/store/3lc51cxj2j57y3zfpq5i69qbzjpvyci1-scientific-0.3.5.1.drv’ failed
1044+```
1045+
1046+As you can see, `packunused` finds out that although the testsuite component has
1047+no redundant dependencies the library component of `scientific-0.3.5.1` depends
1048+on `ghc-prim` which is unused in the library.
1049+
1050+### Using hackage2nix with nixpkgs
1051+
1052+Hackage package derivations are found in the
1053+[`hackage-packages.nix`](https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/haskell-modules/hackage-packages.nix)
1054+file within `nixpkgs` and are used as the initial package set for
1055+`haskellPackages`. The `hackage-packages.nix` file is not meant to be edited
1056+by hand, but rather autogenerated by [`hackage2nix`](https://github.com/NixOS/cabal2nix/tree/master/hackage2nix),
1057+which by default uses the [`configuration-hackage2nix.yaml`](https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/haskell-modules/configuration-hackage2nix.yaml)
1058+file to generate all the derivations.
1059+
1060+To modify the contents `configuration-hackage2nix.yaml`, follow the
1061+instructions on [`hackage2nix`](https://github.com/NixOS/cabal2nix/tree/master/hackage2nix).
1062+
1063+## Other resources
1064+
1065+ - The Youtube video [Nix Loves Haskell](https://www.youtube.com/watch?v=BsBhi_r-OeE)
1066+ provides an introduction into Haskell NG aimed at beginners. The slides are
1067+ available at http://cryp.to/nixos-meetup-3-slides.pdf and also -- in a form
1068+ ready for cut & paste -- at
1069+ https://github.com/NixOS/cabal2nix/blob/master/doc/nixos-meetup-3-slides.md.
1070+
1071+ - Another Youtube video is [Escaping Cabal Hell with Nix](https://www.youtube.com/watch?v=mQd3s57n_2Y),
1072+ which discusses the subject of Haskell development with Nix but also provides
1073+ a basic introduction to Nix as well, i.e. it's suitable for viewers with
1074+ almost no prior Nix experience.
1075+
1076+ - Oliver Charles wrote a very nice [Tutorial how to develop Haskell packages with Nix](http://wiki.ocharles.org.uk/Nix).
1077+
1078+ - The *Journey into the Haskell NG infrastructure* series of postings
1079+ describe the new Haskell infrastructure in great detail:
1080+
1081+ - [Part 1](https://nixos.org/nix-dev/2015-January/015591.html)
1082+ explains the differences between the old and the new code and gives
1083+ instructions how to migrate to the new setup.
1084+
1085+ - [Part 2](https://nixos.org/nix-dev/2015-January/015608.html)
1086+ looks in-depth at how to tweak and configure your setup by means of
1087+ overrides.
1088+
1089+ - [Part 3](https://nixos.org/nix-dev/2015-April/016912.html)
1090+ describes the infrastructure that keeps the Haskell package set in Nixpkgs
1091+ up-to-date.
doc/languages-frameworks/idris.section.mdnew file+115
@@ -0,0 +1,115 @@
1+# Idris packages
2+
3+## Installing Idris
4+
5+The easiest way to get a working idris version is to install the `idris` attribute:
6+
7+```
8+$ # On NixOS
9+$ nix-env -i nixos.idris
10+$ # On non-NixOS
11+$ nix-env -i nixpkgs.idris
12+```
13+
14+This however only provides the `prelude` and `base` libraries. To install additional libraries:
15+
16+```
17+$ nix-env -iE 'pkgs: pkgs.idrisPackages.with-packages (with pkgs.idrisPackages; [ contrib pruviloj ])'
18+```
19+
20+To see all available Idris packages:
21+```
22+$ # On NixOS
23+$ nix-env -qaPA nixos.idrisPackages
24+$ # On non-NixOS
25+$ nix-env -qaPA nixpkgs.idrisPackages
26+```
27+
28+Similarly, entering a `nix-shell`:
29+```
30+$ nix-shell -p 'idrisPackages.with-packages (with idrisPackages; [ contrib pruviloj ])'
31+```
32+
33+## Starting Idris with library support
34+
35+To have access to these libraries in idris, call it with an argument `-p <library name>` for each library:
36+
37+```
38+$ nix-shell -p 'idrisPackages.with-packages (with idrisPackages; [ contrib pruviloj ])'
39+[nix-shell:~]$ idris -p contrib -p pruviloj
40+```
41+
42+A listing of all available packages the Idris binary has access to is available via `--listlibs`:
43+
44+```
45+$ idris --listlibs
46+00prelude-idx.ibc
47+pruviloj
48+base
49+contrib
50+prelude
51+00pruviloj-idx.ibc
52+00base-idx.ibc
53+00contrib-idx.ibc
54+```
55+
56+## Building an Idris project with Nix
57+
58+As an example of how a Nix expression for an Idris package can be created, here is the one for `idrisPackages.yaml`:
59+
60+```nix
61+{ build-idris-package
62+, fetchFromGitHub
63+, contrib
64+, lightyear
65+, lib
66+}:
67+build-idris-package {
68+ name = "yaml";
69+ version = "2018-01-25";
70+
71+ # This is the .ipkg file that should be built, defaults to the package name
72+ # In this case it should build `Yaml.ipkg` instead of `yaml.ipkg`
73+ # This is only necessary because the yaml packages ipkg file is
74+ # different from its package name here.
75+ ipkgName = "Yaml";
76+ # Idris dependencies to provide for the build
77+ idrisDeps = [ contrib lightyear ];
78+
79+ src = fetchFromGitHub {
80+ owner = "Heather";
81+ repo = "Idris.Yaml";
82+ rev = "5afa51ffc839844862b8316faba3bafa15656db4";
83+ sha256 = "1g4pi0swmg214kndj85hj50ccmckni7piprsxfdzdfhg87s0avw7";
84+ };
85+
86+ meta = {
87+ description = "Idris YAML lib";
88+ homepage = https://github.com/Heather/Idris.Yaml;
89+ license = lib.licenses.mit;
90+ maintainers = [ lib.maintainers.brainrape ];
91+ };
92+}
93+```
94+
95+Assuming this file is saved as `yaml.nix`, it's buildable using
96+
97+```
98+$ nix-build -E '(import <nixpkgs> {}).idrisPackages.callPackage ./yaml.nix {}'
99+```
100+
101+Or it's possible to use
102+
103+```nix
104+with import <nixpkgs> {};
105+
106+{
107+ yaml = idrisPackages.callPackage ./yaml.nix {};
108+}
109+```
110+
111+in another file (say `default.nix`) to be able to build it with
112+
113+```
114+$ nix-build -A yaml
115+```
doc/languages-frameworks/index.xml+28−31
@@ -1,35 +1,32 @@
11<chapter xmlns="http://docbook.org/ns/docbook"
22 xmlns:xi="http://www.w3.org/2001/XInclude"
33 xml:id="chap-language-support">
4−
5−<title>Support for specific programming languages and frameworks</title>
6−
7−<para>The <link linkend="chap-stdenv">standard build
8−environment</link> makes it easy to build typical Autotools-based
9−packages with very little code. Any other kind of package can be
10−accomodated by overriding the appropriate phases of
11−<literal>stdenv</literal>. However, there are specialised functions
12−in Nixpkgs to easily build packages for other programming languages,
13−such as Perl or Haskell. These are described in this chapter.</para>
14−
15−
16−<xi:include href="beam.xml" />
17−<xi:include href="bower.xml" />
18−<xi:include href="coq.xml" />
19−<xi:include href="go.xml" />
20−<xi:include href="haskell.xml" />
21−<xi:include href="idris.xml" /> <!-- generated from ../../pkgs/development/idris-modules/README.md -->
22−<xi:include href="java.xml" />
23−<xi:include href="lua.xml" />
24−<xi:include href="node.xml" /> <!-- generated from ../../pkgs/development/node-packages/README.md -->
25−<xi:include href="perl.xml" />
26−<xi:include href="python.xml" />
27−<xi:include href="qt.xml" />
28−<xi:include href="r.xml" /> <!-- generated from ../../pkgs/development/r-modules/README.md -->
29−<xi:include href="ruby.xml" />
30−<xi:include href="rust.xml" />
31−<xi:include href="texlive.xml" />
32−<xi:include href="vim.xml" />
33−
34−
4+ <title>Support for specific programming languages and frameworks</title>
5+ <para>
6+ The <link linkend="chap-stdenv">standard build environment</link> makes it
7+ easy to build typical Autotools-based packages with very little code. Any
8+ other kind of package can be accomodated by overriding the appropriate phases
9+ of <literal>stdenv</literal>. However, there are specialised functions in
10+ Nixpkgs to easily build packages for other programming languages, such as
11+ Perl or Haskell. These are described in this chapter.
12+ </para>
13+ <xi:include href="beam.xml" />
14+ <xi:include href="bower.xml" />
15+ <xi:include href="coq.xml" />
16+ <xi:include href="go.xml" />
17+ <xi:include href="haskell.section.xml" />
18+ <xi:include href="idris.section.xml" />
19+ <xi:include href="java.xml" />
20+ <xi:include href="lua.xml" />
21+ <xi:include href="node.section.xml" />
22+ <xi:include href="ocaml.xml" />
23+ <xi:include href="perl.xml" />
24+ <xi:include href="python.section.xml" />
25+ <xi:include href="qt.xml" />
26+ <xi:include href="r.section.xml" />
27+ <xi:include href="ruby.xml" />
28+ <xi:include href="rust.section.xml" />
29+ <xi:include href="texlive.xml" />
30+ <xi:include href="vim.section.xml" />
31+ <xi:include href="emscripten.section.xml" />
3532</chapter>
doc/languages-frameworks/java.xml+50−50
@@ -1,11 +1,10 @@
11<section xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="sec-language-java">
4+ <title>Java</title>
45
5−<title>Java</title>
6−
7−<para>Ant-based Java packages are typically built from source as follows:
8−
6+ <para>
7+ Ant-based Java packages are typically built from source as follows:
98<programlisting>
109stdenv.mkDerivation {
1110 name = "...";
@@ -16,33 +15,36 @@ stdenv.mkDerivation {
1615 buildPhase = "ant";
1716}
1817</programlisting>
19−
20−Note that <varname>jdk</varname> is an alias for the OpenJDK.</para>
21−
22−<para>JAR files that are intended to be used by other packages should
23−be installed in <filename>$out/share/java</filename>. The OpenJDK has
24−a stdenv setup hook that adds any JARs in the
25−<filename>share/java</filename> directories of the build inputs to the
26−<envar>CLASSPATH</envar> environment variable. For instance, if the
27−package <literal>libfoo</literal> installs a JAR named
28−<filename>foo.jar</filename> in its <filename>share/java</filename>
29−directory, and another package declares the attribute
30−
18+ Note that <varname>jdk</varname> is an alias for the OpenJDK (self-built
19+ where available, or pre-built via Zulu). Platforms with OpenJDK not (yet) in
20+ Nixpkgs (<literal>Aarch32</literal>, <literal>Aarch64</literal>) point to the
21+ (unfree) <literal>oraclejdk</literal>.
22+ </para>
23+
24+ <para>
25+ JAR files that are intended to be used by other packages should be installed
26+ in <filename>$out/share/java</filename>. JDKs have a stdenv setup hook that
27+ add any JARs in the <filename>share/java</filename> directories of the build
28+ inputs to the <envar>CLASSPATH</envar> environment variable. For instance, if
29+ the package <literal>libfoo</literal> installs a JAR named
30+ <filename>foo.jar</filename> in its <filename>share/java</filename>
31+ directory, and another package declares the attribute
3132<programlisting>
3233buildInputs = [ jdk libfoo ];
3334</programlisting>
34−
35−then <envar>CLASSPATH</envar> will be set to
36−<filename>/nix/store/...-libfoo/share/java/foo.jar</filename>.</para>
37−
38−<para>Private JARs
39−should be installed in a location like
40−<filename>$out/share/<replaceable>package-name</replaceable></filename>.</para>
41−
42−<para>If your Java package provides a program, you need to generate a
43−wrapper script to run it using the OpenJRE. You can use
44−<literal>makeWrapper</literal> for this:
45−
35+ then <envar>CLASSPATH</envar> will be set to
36+ <filename>/nix/store/...-libfoo/share/java/foo.jar</filename>.
37+ </para>
38+
39+ <para>
40+ Private JARs should be installed in a location like
41+ <filename>$out/share/<replaceable>package-name</replaceable></filename>.
42+ </para>
43+
44+ <para>
45+ If your Java package provides a program, you need to generate a wrapper
46+ script to run it using the OpenJRE. You can use
47+ <literal>makeWrapper</literal> for this:
4648<programlisting>
4749buildInputs = [ makeWrapper ];
4850
@@ -53,32 +55,30 @@ installPhase =
5355 --add-flags "-cp $out/share/java/foo.jar org.foo.Main"
5456 '';
5557</programlisting>
56−
57−Note the use of <literal>jre</literal>, which is the part of the
58−OpenJDK package that contains the Java Runtime Environment. By using
59−<literal>${jre}/bin/java</literal> instead of
60−<literal>${jdk}/bin/java</literal>, you prevent your package from
61−depending on the JDK at runtime.</para>
62−
63−<para>It is possible to use a different Java compiler than
64−<command>javac</command> from the OpenJDK. For instance, to use the
65−Eclipse Java Compiler:
66−
58+ Note the use of <literal>jre</literal>, which is the part of the OpenJDK
59+ package that contains the Java Runtime Environment. By using
60+ <literal>${jre}/bin/java</literal> instead of
61+ <literal>${jdk}/bin/java</literal>, you prevent your package from depending
62+ on the JDK at runtime.
63+ </para>
64+
65+ <para>
66+ Note all JDKs passthru <literal>home</literal>, so if your application
67+ requires environment variables like <envar>JAVA_HOME</envar> being set, that
68+ can be done in a generic fashion with the <literal>--set</literal> argument
69+ of <literal>makeWrapper</literal>:
6770<programlisting>
68−buildInputs = [ jre ant ecj ];
71+ --set JAVA_HOME ${jdk.home}
6972</programlisting>
73+ </para>
7074
71−(Note that here you don’t need the full JDK as an input, but just the
72−JRE.) The ECJ has a stdenv setup hook that sets some environment
73−variables to cause Ant to use ECJ, but this doesn’t work with all Ant
74−files. Similarly, you can use the GNU Java Compiler:
75−
75+ <para>
76+ It is possible to use a different Java compiler than <command>javac</command>
77+ from the OpenJDK. For instance, to use the GNU Java Compiler:
7678<programlisting>
7779buildInputs = [ gcj ant ];
7880</programlisting>
79−
80−Here, Ant will automatically use <command>gij</command> (the GNU Java
81−Runtime) instead of the OpenJRE.</para>
82−
81+ Here, Ant will automatically use <command>gij</command> (the GNU Java
82+ Runtime) instead of the OpenJRE.
83+ </para>
8384</section>
84−
doc/languages-frameworks/lua.xml+20−23
@@ -1,24 +1,22 @@
11<section xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="sec-language-lua">
4+ <title>Lua</title>
45
5−<title>Lua</title>
6−
7−<para>
8− Lua packages are built by the <varname>buildLuaPackage</varname> function. This function is
9− implemented
10− in <link xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/lua-modules/generic/default.nix">
6+ <para>
7+ Lua packages are built by the <varname>buildLuaPackage</varname> function.
8+ This function is implemented in
9+ <link xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/lua-modules/generic/default.nix">
1110 <filename>pkgs/development/lua-modules/generic/default.nix</filename></link>
1211 and works similarly to <varname>buildPerlPackage</varname>. (See
1312 <xref linkend="sec-language-perl"/> for details.)
14−</para>
13+ </para>
1514
16−<para>
17− Lua packages are defined
18− in <link xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/top-level/lua-packages.nix"><filename>pkgs/top-level/lua-packages.nix</filename></link>.
15+ <para>
16+ Lua packages are defined in
17+ <link xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/top-level/lua-packages.nix"><filename>pkgs/top-level/lua-packages.nix</filename></link>.
1918 Most of them are simple. For example:
20−
21− <programlisting>
19+<programlisting>
2220fileSystem = buildLuaPackage {
2321 name = "filesystem-1.6.2";
2422 src = fetchurl {
@@ -32,20 +30,19 @@ fileSystem = buildLuaPackage {
3230 };
3331};
3432 </programlisting>
35−</para>
33+ </para>
3634
37−<para>
35+ <para>
3836 Though, more complicated package should be placed in a seperate file in
3937 <link
4038 xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/lua-modules"><filename>pkgs/development/lua-modules</filename></link>.
41−</para>
42−<para>
43− Lua packages accept additional parameter <varname>disabled</varname>, which defines
44− the condition of disabling package from luaPackages. For example, if package has
45− <varname>disabled</varname> assigned to <literal>lua.luaversion != "5.1"</literal>,
46− it will not be included in any luaPackages except lua51Packages, making it
47− only be built for lua 5.1.
48−</para>
39+ </para>
4940
41+ <para>
42+ Lua packages accept additional parameter <varname>disabled</varname>, which
43+ defines the condition of disabling package from luaPackages. For example, if
44+ package has <varname>disabled</varname> assigned to <literal>lua.luaversion
45+ != "5.1"</literal>, it will not be included in any luaPackages except
46+ lua51Packages, making it only be built for lua 5.1.
47+ </para>
5048</section>
51−
doc/languages-frameworks/node.section.mdnew file+51
@@ -0,0 +1,51 @@
1+Node.js packages
2+================
3+The `pkgs/development/node-packages` folder contains a generated collection of
4+[NPM packages](https://npmjs.com/) that can be installed with the Nix package
5+manager.
6+
7+As a rule of thumb, the package set should only provide *end user* software
8+packages, such as command-line utilities. Libraries should only be added to the
9+package set if there is a non-NPM package that requires it.
10+
11+When it is desired to use NPM libraries in a development project, use the
12+`node2nix` generator directly on the `package.json` configuration file of the
13+project.
14+
15+The package set also provides support for multiple Node.js versions. The policy
16+is that a new package should be added to the collection for the latest stable LTS
17+release (which is currently 8.x), unless there is an explicit reason to support
18+a different release.
19+
20+If your package uses native addons, you need to examine what kind of native
21+build system it uses. Here are some examples:
22+
23+* `node-gyp`
24+* `node-gyp-builder`
25+* `node-pre-gyp`
26+
27+After you have identified the correct system, you need to override your package
28+expression while adding in build system as a build input. For example, `dat`
29+requires `node-gyp-build`, so we override its expression in `default-v8.nix`:
30+
31+```nix
32+dat = nodePackages.dat.override (oldAttrs: {
33+ buildInputs = oldAttrs.buildInputs ++ [ nodePackages.node-gyp-build ];
34+});
35+```
36+
37+To add a package from NPM to nixpkgs:
38+
39+ 1. Modify `pkgs/development/node-packages/node-packages-v8.json` to add, update
40+ or remove package entries. (Or `pkgs/development/node-packages/node-packages-v10.json`
41+ for packages depending on Node.js 10.x)
42+ 2. Run the script: `(cd pkgs/development/node-packages && ./generate.sh)`.
43+ 3. Build your new package to test your changes:
44+ `cd /path/to/nixpkgs && nix-build -A nodePackages.<new-or-updated-package>`.
45+ To build against a specific Node.js version (e.g. 10.x):
46+ `nix-build -A nodePackages_10_x.<new-or-updated-package>`
47+ 4. Add and commit all modified and generated files.
48+
49+For more information about the generation process, consult the
50+[README.md](https://github.com/svanderburg/node2nix) file of the `node2nix`
51+tool.
doc/languages-frameworks/ocaml.xmlnew file+99
@@ -0,0 +1,99 @@
1+<section xmlns="http://docbook.org/ns/docbook"
2+ xmlns:xlink="http://www.w3.org/1999/xlink"
3+ xml:id="sec-language-ocaml">
4+ <title>OCaml</title>
5+
6+ <para>
7+ OCaml libraries should be installed in
8+ <literal>$(out)/lib/ocaml/${ocaml.version}/site-lib/</literal>. Such
9+ directories are automatically added to the <literal>$OCAMLPATH</literal>
10+ environment variable when building another package that depends on them
11+ or when opening a <literal>nix-shell</literal>.
12+ </para>
13+
14+ <para>
15+ Given that most of the OCaml ecosystem is now built with dune,
16+ nixpkgs includes a convenience build support function called
17+ <literal>buildDunePackage</literal> that will build an OCaml package
18+ using dune, OCaml and findlib and any additional dependencies provided
19+ as <literal>buildInputs</literal> or <literal>propagatedBuildInputs</literal>.
20+ </para>
21+
22+ <para>
23+ Here is a simple package example. It defines an (optional) attribute
24+ <literal>minimumOCamlVersion</literal> that will be used to throw a
25+ descriptive evaluation error if building with an older OCaml is attempted.
26+ It uses the <literal>fetchFromGitHub</literal> fetcher to get its source.
27+ It sets the <literal>doCheck</literal> (optional) attribute to
28+ <literal>true</literal> which means that tests will be run with
29+ <literal>dune runtest -p angstrom</literal> after the build
30+ (<literal>dune build -p angstrom</literal>) is complete.
31+ It uses <literal>alcotest</literal> as a build input (because it is needed
32+ to run the tests) and <literal>bigstringaf</literal> and
33+ <literal>result</literal> as propagated build inputs (thus they will also
34+ be available to libraries depending on this library).
35+ The library will be installed using the <literal>angstrom.install</literal>
36+ file that dune generates.
37+ </para>
38+
39+ <programlisting>
40+{ stdenv, fetchFromGitHub, buildDunePackage, alcotest, result, bigstringaf }:
41+
42+buildDunePackage rec {
43+ pname = "angstrom";
44+ version = "0.10.0";
45+
46+ minimumOCamlVersion = "4.03";
47+
48+ src = fetchFromGitHub {
49+ owner = "inhabitedtype";
50+ repo = pname;
51+ rev = version;
52+ sha256 = "0lh6024yf9ds0nh9i93r9m6p5psi8nvrqxl5x7jwl13zb0r9xfpw";
53+ };
54+
55+ buildInputs = [ alcotest ];
56+ propagatedBuildInputs = [ bigstringaf result ];
57+ doCheck = true;
58+
59+ meta = {
60+ homepage = https://github.com/inhabitedtype/angstrom;
61+ description = "OCaml parser combinators built for speed and memory efficiency";
62+ license = stdenv.lib.licenses.bsd3;
63+ maintainers = with stdenv.lib.maintainers; [ sternenseemann ];
64+ };
65+}
66+ </programlisting>
67+
68+ <para>
69+ Here is a second example, this time using a source archive generated with
70+ <literal>dune-release</literal>. It is a good idea to use this archive when
71+ it is available as it will usually contain substituted variables such as a
72+ <literal>%%VERSION%%</literal> field. This library does not depend
73+ on any other OCaml library and no tests are run after building it.
74+ </para>
75+
76+ <programlisting>
77+{ stdenv, fetchurl, buildDunePackage }:
78+
79+buildDunePackage rec {
80+ pname = "wtf8";
81+ version = "1.0.1";
82+
83+ minimumOCamlVersion = "4.01";
84+
85+ src = fetchurl {
86+ url = "https://github.com/flowtype/ocaml-${pname}/releases/download/v${version}/${pname}-${version}.tbz";
87+ sha256 = "1msg3vycd3k8qqj61sc23qks541cxpb97vrnrvrhjnqxsqnh6ygq";
88+ };
89+
90+ meta = with stdenv.lib; {
91+ homepage = https://github.com/flowtype/ocaml-wtf8;
92+ description = "WTF-8 is a superset of UTF-8 that allows unpaired surrogates.";
93+ license = licenses.mit;
94+ maintainers = [ maintainers.eqyiel ];
95+ };
96+}
97+ </programlisting>
98+
99+</section>
doc/languages-frameworks/perl.xml+117−106
@@ -1,24 +1,27 @@
11<section xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="sec-language-perl">
4−
5−<title>Perl</title>
6−
7−<para>Nixpkgs provides a function <varname>buildPerlPackage</varname>,
8−a generic package builder function for any Perl package that has a
9−standard <varname>Makefile.PL</varname>. It’s implemented in <link
10−xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/perl-modules/generic"><filename>pkgs/development/perl-modules/generic</filename></link>.</para>
11−
12−<para>Perl packages from CPAN are defined in <link
4+ <title>Perl</title>
5+
6+ <para>
7+ Nixpkgs provides a function <varname>buildPerlPackage</varname>, a generic
8+ package builder function for any Perl package that has a standard
9+ <varname>Makefile.PL</varname>. It’s implemented in
10+ <link
11+xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/perl-modules/generic"><filename>pkgs/development/perl-modules/generic</filename></link>.
12+ </para>
13+
14+ <para>
15+ Perl packages from CPAN are defined in
16+ <link
1317xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/top-level/perl-packages.nix"><filename>pkgs/top-level/perl-packages.nix</filename></link>,
14−rather than <filename>pkgs/all-packages.nix</filename>. Most Perl
15−packages are so straight-forward to build that they are defined here
16−directly, rather than having a separate function for each package
17−called from <filename>perl-packages.nix</filename>. However, more
18−complicated packages should be put in a separate file, typically in
19−<filename>pkgs/development/perl-modules</filename>. Here is an
20−example of the former:
21−
18+ rather than <filename>pkgs/all-packages.nix</filename>. Most Perl packages
19+ are so straight-forward to build that they are defined here directly, rather
20+ than having a separate function for each package called from
21+ <filename>perl-packages.nix</filename>. However, more complicated packages
22+ should be put in a separate file, typically in
23+ <filename>pkgs/development/perl-modules</filename>. Here is an example of the
24+ former:
2225<programlisting>
2326ClassC3 = buildPerlPackage rec {
2427 name = "Class-C3-0.21";
@@ -28,74 +31,72 @@ ClassC3 = buildPerlPackage rec {
2831 };
2932};
3033</programlisting>
31−
32−Note the use of <literal>mirror://cpan/</literal>, and the
33−<literal>${name}</literal> in the URL definition to ensure that the
34−name attribute is consistent with the source that we’re actually
35−downloading. Perl packages are made available in
36−<filename>all-packages.nix</filename> through the variable
37−<varname>perlPackages</varname>. For instance, if you have a package
38−that needs <varname>ClassC3</varname>, you would typically write
39−
34+ Note the use of <literal>mirror://cpan/</literal>, and the
35+ <literal>${name}</literal> in the URL definition to ensure that the name
36+ attribute is consistent with the source that we’re actually downloading.
37+ Perl packages are made available in <filename>all-packages.nix</filename>
38+ through the variable <varname>perlPackages</varname>. For instance, if you
39+ have a package that needs <varname>ClassC3</varname>, you would typically
40+ write
4041<programlisting>
4142foo = import ../path/to/foo.nix {
4243 inherit stdenv fetchurl ...;
4344 inherit (perlPackages) ClassC3;
4445};
4546</programlisting>
46−
47−in <filename>all-packages.nix</filename>. You can test building a
48−Perl package as follows:
49−
47+ in <filename>all-packages.nix</filename>. You can test building a Perl
48+ package as follows:
5049<screen>
5150$ nix-build -A perlPackages.ClassC3
5251</screen>
53−
54−<varname>buildPerlPackage</varname> adds <literal>perl-</literal> to
55−the start of the name attribute, so the package above is actually
56−called <literal>perl-Class-C3-0.21</literal>. So to install it, you
57−can say:
58−
52+ <varname>buildPerlPackage</varname> adds <literal>perl-</literal> to the
53+ start of the name attribute, so the package above is actually called
54+ <literal>perl-Class-C3-0.21</literal>. So to install it, you can say:
5955<screen>
6056$ nix-env -i perl-Class-C3
6157</screen>
62−
63−(Of course you can also install using the attribute name:
64−<literal>nix-env -i -A perlPackages.ClassC3</literal>.)</para>
65−
66−<para>So what does <varname>buildPerlPackage</varname> do? It does
67−the following:
68−
69−<orderedlist>
70−
71− <listitem><para>In the configure phase, it calls <literal>perl
72− Makefile.PL</literal> to generate a Makefile. You can set the
73− variable <varname>makeMakerFlags</varname> to pass flags to
74− <filename>Makefile.PL</filename></para></listitem>
75−
76− <listitem><para>It adds the contents of the <envar>PERL5LIB</envar>
77− environment variable to <literal>#! .../bin/perl</literal> line of
78− Perl scripts as <literal>-I<replaceable>dir</replaceable></literal>
79− flags. This ensures that a script can find its
80− dependencies.</para></listitem>
81−
82− <listitem><para>In the fixup phase, it writes the propagated build
83− inputs (<varname>propagatedBuildInputs</varname>) to the file
84− <filename>$out/nix-support/propagated-user-env-packages</filename>.
85− <command>nix-env</command> recursively installs all packages listed
86− in this file when you install a package that has it. This ensures
87− that a Perl package can find its dependencies.</para></listitem>
88−
89−</orderedlist>
90−
91−</para>
92−
93−<para><varname>buildPerlPackage</varname> is built on top of
94−<varname>stdenv</varname>, so everything can be customised in the
95−usual way. For instance, the <literal>BerkeleyDB</literal> module has
96−a <varname>preConfigure</varname> hook to generate a configuration
97−file used by <filename>Makefile.PL</filename>:
98−
58+ (Of course you can also install using the attribute name: <literal>nix-env -i
59+ -A perlPackages.ClassC3</literal>.)
60+ </para>
61+
62+ <para>
63+ So what does <varname>buildPerlPackage</varname> do? It does the following:
64+ <orderedlist>
65+ <listitem>
66+ <para>
67+ In the configure phase, it calls <literal>perl Makefile.PL</literal> to
68+ generate a Makefile. You can set the variable
69+ <varname>makeMakerFlags</varname> to pass flags to
70+ <filename>Makefile.PL</filename>
71+ </para>
72+ </listitem>
73+ <listitem>
74+ <para>
75+ It adds the contents of the <envar>PERL5LIB</envar> environment variable
76+ to <literal>#! .../bin/perl</literal> line of Perl scripts as
77+ <literal>-I<replaceable>dir</replaceable></literal> flags. This ensures
78+ that a script can find its dependencies.
79+ </para>
80+ </listitem>
81+ <listitem>
82+ <para>
83+ In the fixup phase, it writes the propagated build inputs
84+ (<varname>propagatedBuildInputs</varname>) to the file
85+ <filename>$out/nix-support/propagated-user-env-packages</filename>.
86+ <command>nix-env</command> recursively installs all packages listed in
87+ this file when you install a package that has it. This ensures that a Perl
88+ package can find its dependencies.
89+ </para>
90+ </listitem>
91+ </orderedlist>
92+ </para>
93+
94+ <para>
95+ <varname>buildPerlPackage</varname> is built on top of
96+ <varname>stdenv</varname>, so everything can be customised in the usual way.
97+ For instance, the <literal>BerkeleyDB</literal> module has a
98+ <varname>preConfigure</varname> hook to generate a configuration file used by
99+ <filename>Makefile.PL</filename>:
99100<programlisting>
100101{ buildPerlPackage, fetchurl, db }:
101102
@@ -108,23 +109,20 @@ buildPerlPackage rec {
108109 };
109110
110111 preConfigure = ''
111− echo "LIB = ${db}/lib" > config.in
112− echo "INCLUDE = ${db}/include" >> config.in
112+ echo "LIB = ${db.out}/lib" > config.in
113+ echo "INCLUDE = ${db.dev}/include" >> config.in
113114 '';
114115}
115116</programlisting>
116−
117−</para>
118−
119−<para>Dependencies on other Perl packages can be specified in the
120−<varname>buildInputs</varname> and
121−<varname>propagatedBuildInputs</varname> attributes. If something is
122−exclusively a build-time dependency, use
123−<varname>buildInputs</varname>; if it’s (also) a runtime dependency,
124−use <varname>propagatedBuildInputs</varname>. For instance, this
125−builds a Perl module that has runtime dependencies on a bunch of other
126−modules:
127−
117+ </para>
118+
119+ <para>
120+ Dependencies on other Perl packages can be specified in the
121+ <varname>buildInputs</varname> and <varname>propagatedBuildInputs</varname>
122+ attributes. If something is exclusively a build-time dependency, use
123+ <varname>buildInputs</varname>; if it’s (also) a runtime dependency, use
124+ <varname>propagatedBuildInputs</varname>. For instance, this builds a Perl
125+ module that has runtime dependencies on a bunch of other modules:
128126<programlisting>
129127ClassC3Componentised = buildPerlPackage rec {
130128 name = "Class-C3-Componentised-1.0004";
@@ -137,24 +135,26 @@ ClassC3Componentised = buildPerlPackage rec {
137135 ];
138136};
139137</programlisting>
138+ </para>
140139
141−</para>
140+ <section xml:id="ssec-generation-from-CPAN">
141+ <title>Generation from CPAN</title>
142142
143−<section xml:id="ssec-generation-from-CPAN"><title>Generation from CPAN</title>
144−
145−<para>Nix expressions for Perl packages can be generated (almost)
146−automatically from CPAN. This is done by the program
147−<command>nix-generate-from-cpan</command>, which can be installed
148−as follows:</para>
143+ <para>
144+ Nix expressions for Perl packages can be generated (almost) automatically
145+ from CPAN. This is done by the program
146+ <command>nix-generate-from-cpan</command>, which can be installed as
147+ follows:
148+ </para>
149149
150150<screen>
151151$ nix-env -i nix-generate-from-cpan
152152</screen>
153153
154−<para>This program takes a Perl module name, looks it up on CPAN,
155−fetches and unpacks the corresponding package, and prints a Nix
156−expression on standard output. For example:
157−
154+ <para>
155+ This program takes a Perl module name, looks it up on CPAN, fetches and
156+ unpacks the corresponding package, and prints a Nix expression on standard
157+ output. For example:
158158<screen>
159159$ nix-generate-from-cpan XML::Simple
160160 XMLSimple = buildPerlPackage rec {
@@ -170,12 +170,23 @@ $ nix-generate-from-cpan XML::Simple
170170 };
171171 };
172172</screen>
173−
174−The output can be pasted into
175−<filename>pkgs/top-level/perl-packages.nix</filename> or wherever else
176−you need it.</para>
177−
173+ The output can be pasted into
174+ <filename>pkgs/top-level/perl-packages.nix</filename> or wherever else you
175+ need it.
176+ </para>
177+ </section>
178+
179+ <section xml:id="ssec-perl-cross-compilation">
180+ <title>Cross-compiling modules</title>
181+
182+ <para>
183+ Nixpkgs has experimental support for cross-compiling Perl modules. In many
184+ cases, it will just work out of the box, even for modules with native
185+ extensions. Sometimes, however, the Makefile.PL for a module may
186+ (indirectly) import a native module. In that case, you will need to make a
187+ stub for that module that will satisfy the Makefile.PL and install it into
188+ <filename>lib/perl5/site_perl/cross_perl/${perl.version}</filename>. See the
189+ <varname>postInstall</varname> for <varname>DBI</varname> for an example.
190+ </para>
191+ </section>
178192</section>
179−
180−</section>
181−
doc/languages-frameworks/python.mddeleted−1024
@@ -1,1024 +0,0 @@
1−# Python
2−
3−## User Guide
4−
5−### Using Python
6−
7−#### Overview
8−
9−Several versions of the Python interpreter are available on Nix, as well as a
10−high amount of packages. The attribute `python` refers to the default
11−interpreter, which is currently CPython 2.7. It is also possible to refer to
12−specific versions, e.g. `python35` refers to CPython 3.5, and `pypy` refers to
13−the default PyPy interpreter.
14−
15−Python is used a lot, and in different ways. This affects also how it is
16−packaged. In the case of Python on Nix, an important distinction is made between
17−whether the package is considered primarily an application, or whether it should
18−be used as a library, i.e., of primary interest are the modules in
19−`site-packages` that should be importable.
20−
21−In the Nixpkgs tree Python applications can be found throughout, depending on
22−what they do, and are called from the main package set. Python libraries,
23−however, are in separate sets, with one set per interpreter version.
24−
25−The interpreters have several common attributes. One of these attributes is
26−`pkgs`, which is a package set of Python libraries for this specific
27−interpreter. E.g., the `toolz` package corresponding to the default interpreter
28−is `python.pkgs.toolz`, and the CPython 3.5 version is `python35.pkgs.toolz`.
29−The main package set contains aliases to these package sets, e.g.
30−`pythonPackages` refers to `python.pkgs` and `python35Packages` to
31−`python35.pkgs`.
32−
33−#### Installing Python and packages
34−
35−The Nix and NixOS manuals explain how packages are generally installed. In the
36−case of Python and Nix, it is important to make a distinction between whether the
37−package is considered an application or a library.
38−
39−Applications on Nix are typically installed into your user
40−profile imperatively using `nix-env -i`, and on NixOS declaratively by adding the
41−package name to `environment.systemPackages` in `/etc/nixos/configuration.nix`.
42−Dependencies such as libraries are automatically installed and should not be
43−installed explicitly.
44−
45−The same goes for Python applications and libraries. Python applications can be
46−installed in your profile. But Python libraries you would like to use for
47−development cannot be installed, at least not individually, because they won't
48−be able to find each other resulting in import errors. Instead, it is possible
49−to create an environment with `python.buildEnv` or `python.withPackages` where
50−the interpreter and other executables are able to find each other and all of the
51−modules.
52−
53−In the following examples we create an environment with Python 3.5, `numpy` and
54−`toolz`. As you may imagine, there is one limitation here, and that's that
55−you can install only one environment at a time. You will notice the complaints
56−about collisions when you try to install a second environment.
57−
58−##### Environment defined in separate `.nix` file
59−
60−Create a file, e.g. `build.nix`, with the following expression
61−```nix
62−with import <nixpkgs> {};
63−
64−python35.withPackages (ps: with ps; [ numpy toolz ])
65−```
66−and install it in your profile with
67−```shell
68−nix-env -if build.nix
69−```
70−Now you can use the Python interpreter, as well as the extra packages (`numpy`,
71−`toolz`) that you added to the environment.
72−
73−##### Environment defined in `~/.config/nixpkgs/config.nix`
74−
75−If you prefer to, you could also add the environment as a package override to the Nixpkgs set, e.g.
76−using `config.nix`,
77−```nix
78−{ # ...
79−
80− packageOverrides = pkgs: with pkgs; {
81− myEnv = python35.withPackages (ps: with ps; [ numpy toolz ]);
82− };
83−}
84−```
85−and install it in your profile with
86−```shell
87−nix-env -iA nixpkgs.myEnv
88−```
89−The environment is is installed by referring to the attribute, and considering
90−the `nixpkgs` channel was used.
91−
92−##### Environment defined in `/etc/nixos/configuration.nix`
93−
94−For the sake of completeness, here's another example how to install the environment system-wide.
95−
96−```nix
97−{ # ...
98−
99− environment.systemPackages = with pkgs; [
100− (python35.withPackages(ps: with ps; [ numpy toolz ]))
101− ];
102−}
103−```
104−
105−#### Temporary Python environment with `nix-shell`
106−
107−The examples in the previous section showed how to install a Python environment
108−into a profile. For development you may need to use multiple environments.
109−`nix-shell` gives the possibility to temporarily load another environment, akin
110−to `virtualenv`.
111−
112−There are two methods for loading a shell with Python packages. The first and recommended method
113−is to create an environment with `python.buildEnv` or `python.withPackages` and load that. E.g.
114−```sh
115−$ nix-shell -p 'python35.withPackages(ps: with ps; [ numpy toolz ])'
116−```
117−opens a shell from which you can launch the interpreter
118−```sh
119−[nix-shell:~] python3
120−```
121−The other method, which is not recommended, does not create an environment and requires you to list the packages directly,
122−
123−```sh
124−$ nix-shell -p python35.pkgs.numpy python35.pkgs.toolz
125−```
126−Again, it is possible to launch the interpreter from the shell.
127−The Python interpreter has the attribute `pkgs` which contains all Python libraries for that specific interpreter.
128−
129−##### Load environment from `.nix` expression
130−As explained in the Nix manual, `nix-shell` can also load an
131−expression from a `.nix` file. Say we want to have Python 3.5, `numpy`
132−and `toolz`, like before, in an environment. Consider a `shell.nix` file
133−with
134−```nix
135−with import <nixpkgs> {};
136−
137−(python35.withPackages (ps: [ps.numpy ps.toolz])).env
138−```
139−Executing `nix-shell` gives you again a Nix shell from which you can run Python.
140−
141−What's happening here?
142−
143−1. We begin with importing the Nix Packages collections. `import <nixpkgs>` imports the `<nixpkgs>` function, `{}` calls it and the `with` statement brings all attributes of `nixpkgs` in the local scope. These attributes form the main package set.
144−2. Then we create a Python 3.5 environment with the `withPackages` function.
145−3. The `withPackages` function expects us to provide a function as an argument that takes the set of all python packages and returns a list of packages to include in the environment. Here, we select the packages `numpy` and `toolz` from the package set.
146−
147−##### Execute command with `--run`
148−A convenient option with `nix-shell` is the `--run`
149−option, with which you can execute a command in the `nix-shell`. We can
150−e.g. directly open a Python shell
151−```sh
152−$ nix-shell -p python35Packages.numpy python35Packages.toolz --run "python3"
153−```
154−or run a script
155−```sh
156−$ nix-shell -p python35Packages.numpy python35Packages.toolz --run "python3 myscript.py"
157−```
158−
159−##### `nix-shell` as shebang
160−In fact, for the second use case, there is a more convenient method. You can
161−add a [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) to your script
162−specifying which dependencies `nix-shell` needs. With the following shebang, you
163−can just execute `./myscript.py`, and it will make available all dependencies and
164−run the script in the `python3` shell.
165−
166−```py
167−#! /usr/bin/env nix-shell
168−#! nix-shell -i python3 -p "python3.withPackages(ps: [ps.numpy])"
169−
170−import numpy
171−
172−print(numpy.__version__)
173−```
174−
175−### Developing with Python
176−
177−Now that you know how to get a working Python environment with Nix, it is time
178−to go forward and start actually developing with Python. We will first have a
179−look at how Python packages are packaged on Nix. Then, we will look at how you
180−can use development mode with your code.
181−
182−#### Packaging a library
183−
184−With Nix all packages are built by functions. The main function in Nix for
185−building Python libraries is `buildPythonPackage`. Let's see how we can build the
186−`toolz` package.
187−
188−```nix
189−{ # ...
190−
191− toolz = buildPythonPackage rec {
192− pname = "toolz";
193− version = "0.7.4";
194−
195− src = fetchPypi {
196− inherit pname version;
197− sha256 = "43c2c9e5e7a16b6c88ba3088a9bfc82f7db8e13378be7c78d6c14a5f8ed05afd";
198− };
199−
200− doCheck = false;
201−
202− meta = {
203− homepage = "http://github.com/pytoolz/toolz/";
204− description = "List processing tools and functional utilities";
205− license = licenses.bsd3;
206− maintainers = with maintainers; [ fridh ];
207− };
208− };
209−}
210−```
211−
212−What happens here? The function `buildPythonPackage` is called and as argument
213−it accepts a set. In this case the set is a recursive set, `rec`. One of the
214−arguments is the name of the package, which consists of a basename (generally
215−following the name on PyPi) and a version. Another argument, `src` specifies the
216−source, which in this case is fetched from PyPI using the helper function
217−`fetchPypi`. The argument `doCheck` is used to set whether tests should be run
218−when building the package. Furthermore, we specify some (optional) meta
219−information. The output of the function is a derivation.
220−
221−An expression for `toolz` can be found in the Nixpkgs repository. As explained
222−in the introduction of this Python section, a derivation of `toolz` is available
223−for each interpreter version, e.g. `python35.pkgs.toolz` refers to the `toolz`
224−derivation corresponding to the CPython 3.5 interpreter.
225−The above example works when you're directly working on
226−`pkgs/top-level/python-packages.nix` in the Nixpkgs repository. Often though,
227−you will want to test a Nix expression outside of the Nixpkgs tree.
228−
229−The following expression creates a derivation for the `toolz` package,
230−and adds it along with a `numpy` package to a Python environment.
231−
232−```nix
233−with import <nixpkgs> {};
234−
235−( let
236− my_toolz = python35.pkgs.buildPythonPackage rec {
237− pname = "toolz";
238− version = "0.7.4";
239−
240− src = python35.pkgs.fetchPypi {
241− inherit pname version;
242− sha256 = "43c2c9e5e7a16b6c88ba3088a9bfc82f7db8e13378be7c78d6c14a5f8ed05afd";
243− };
244−
245− doCheck = false;
246−
247− meta = {
248− homepage = "http://github.com/pytoolz/toolz/";
249− description = "List processing tools and functional utilities";
250− };
251− };
252−
253− in python35.withPackages (ps: [ps.numpy my_toolz])
254−).env
255−```
256−Executing `nix-shell` will result in an environment in which you can use
257−Python 3.5 and the `toolz` package. As you can see we had to explicitly mention
258−for which Python version we want to build a package.
259−
260−So, what did we do here? Well, we took the Nix expression that we used earlier
261−to build a Python environment, and said that we wanted to include our own
262−version of `toolz`, named `my_toolz`. To introduce our own package in the scope
263−of `withPackages` we used a `let` expression. You can see that we used
264−`ps.numpy` to select numpy from the nixpkgs package set (`ps`). We did not take
265−`toolz` from the Nixpkgs package set this time, but instead took our own version
266−that we introduced with the `let` expression.
267−
268−#### Handling dependencies
269−
270−Our example, `toolz`, does not have any dependencies on other Python
271−packages or system libraries. According to the manual, `buildPythonPackage`
272−uses the arguments `buildInputs` and `propagatedBuildInputs` to specify dependencies. If something is
273−exclusively a build-time dependency, then the dependency should be included as a
274−`buildInput`, but if it is (also) a runtime dependency, then it should be added
275−to `propagatedBuildInputs`. Test dependencies are considered build-time dependencies.
276−
277−The following example shows which arguments are given to `buildPythonPackage` in
278−order to build [`datashape`](https://github.com/blaze/datashape).
279−
280−```nix
281−{ # ...
282−
283− datashape = buildPythonPackage rec {
284− pname = "datashape";
285− version = "0.4.7";
286−
287− src = fetchPypi {
288− inherit pname version;
289− sha256 = "14b2ef766d4c9652ab813182e866f493475e65e558bed0822e38bf07bba1a278";
290− };
291−
292− checkInputs = with self; [ pytest ];
293− propagatedBuildInputs = with self; [ numpy multipledispatch dateutil ];
294−
295− meta = {
296− homepage = https://github.com/ContinuumIO/datashape;
297− description = "A data description language";
298− license = licenses.bsd2;
299− maintainers = with maintainers; [ fridh ];
300− };
301− };
302−}
303−```
304−
305−We can see several runtime dependencies, `numpy`, `multipledispatch`, and
306−`dateutil`. Furthermore, we have one `buildInput`, i.e. `pytest`. `pytest` is a
307−test runner and is only used during the `checkPhase` and is therefore not added
308−to `propagatedBuildInputs`.
309−
310−In the previous case we had only dependencies on other Python packages to consider.
311−Occasionally you have also system libraries to consider. E.g., `lxml` provides
312−Python bindings to `libxml2` and `libxslt`. These libraries are only required
313−when building the bindings and are therefore added as `buildInputs`.
314−
315−```nix
316−{ # ...
317−
318− lxml = buildPythonPackage rec {
319− pname = "lxml";
320− version = "3.4.4";
321−
322− src = fetchPypi {
323− inherit pname version;
324− sha256 = "16a0fa97hym9ysdk3rmqz32xdjqmy4w34ld3rm3jf5viqjx65lxk";
325− };
326−
327− buildInputs = with self; [ pkgs.libxml2 pkgs.libxslt ];
328−
329− meta = {
330− description = "Pythonic binding for the libxml2 and libxslt libraries";
331− homepage = http://lxml.de;
332− license = licenses.bsd3;
333− maintainers = with maintainers; [ sjourdois ];
334− };
335− };
336−}
337−```
338−
339−In this example `lxml` and Nix are able to work out exactly where the relevant
340−files of the dependencies are. This is not always the case.
341−
342−The example below shows bindings to The Fastest Fourier Transform in the West, commonly known as
343−FFTW. On Nix we have separate packages of FFTW for the different types of floats
344−(`"single"`, `"double"`, `"long-double"`). The bindings need all three types,
345−and therefore we add all three as `buildInputs`. The bindings don't expect to
346−find each of them in a different folder, and therefore we have to set `LDFLAGS`
347−and `CFLAGS`.
348−
349−```nix
350−{ # ...
351−
352− pyfftw = buildPythonPackage rec {
353− pname = "pyFFTW";
354− version = "0.9.2";
355−
356− src = fetchPypi {
357− inherit pname version;
358− sha256 = "f6bbb6afa93085409ab24885a1a3cdb8909f095a142f4d49e346f2bd1b789074";
359− };
360−
361− buildInputs = [ pkgs.fftw pkgs.fftwFloat pkgs.fftwLongDouble];
362−
363− propagatedBuildInputs = with self; [ numpy scipy ];
364−
365− # Tests cannot import pyfftw. pyfftw works fine though.
366− doCheck = false;
367−
368− preConfigure = ''
369− export LDFLAGS="-L${pkgs.fftw.dev}/lib -L${pkgs.fftwFloat.out}/lib -L${pkgs.fftwLongDouble.out}/lib"
370− export CFLAGS="-I${pkgs.fftw.dev}/include -I${pkgs.fftwFloat.dev}/include -I${pkgs.fftwLongDouble.dev}/include"
371− '';
372−
373− meta = {
374− description = "A pythonic wrapper around FFTW, the FFT library, presenting a unified interface for all the supported transforms";
375− homepage = http://hgomersall.github.com/pyFFTW/;
376− license = with licenses; [ bsd2 bsd3 ];
377− maintainer = with maintainers; [ fridh ];
378− };
379− };
380−}
381−```
382−Note also the line `doCheck = false;`, we explicitly disabled running the test-suite.
383−
384−
385−#### Develop local package
386−
387−As a Python developer you're likely aware of [development mode](http://setuptools.readthedocs.io/en/latest/setuptools.html#development-mode) (`python setup.py develop`);
388−instead of installing the package this command creates a special link to the project code.
389−That way, you can run updated code without having to reinstall after each and every change you make.
390−Development mode is also available. Let's see how you can use it.
391−
392−In the previous Nix expression the source was fetched from an url. We can also refer to a local source instead using
393−`src = ./path/to/source/tree;`
394−
395−If we create a `shell.nix` file which calls `buildPythonPackage`, and if `src`
396−is a local source, and if the local source has a `setup.py`, then development
397−mode is activated.
398−
399−In the following example we create a simple environment that
400−has a Python 3.5 version of our package in it, as well as its dependencies and
401−other packages we like to have in the environment, all specified with `propagatedBuildInputs`.
402−Indeed, we can just add any package we like to have in our environment to `propagatedBuildInputs`.
403−
404−```nix
405−with import <nixpkgs> {};
406−with pkgs.python35Packages;
407−
408−buildPythonPackage rec {
409− name = "mypackage";
410− src = ./path/to/package/source;
411− propagatedBuildInputs = [ pytest numpy pkgs.libsndfile ];
412−}
413−```
414−
415−It is important to note that due to how development mode is implemented on Nix it is not possible to have multiple packages simultaneously in development mode.
416−
417−
418−### Organising your packages
419−
420−So far we discussed how you can use Python on Nix, and how you can develop with
421−it. We've looked at how you write expressions to package Python packages, and we
422−looked at how you can create environments in which specified packages are
423−available.
424−
425−At some point you'll likely have multiple packages which you would
426−like to be able to use in different projects. In order to minimise unnecessary
427−duplication we now look at how you can maintain yourself a repository with your
428−own packages. The important functions here are `import` and `callPackage`.
429−
430−### Including a derivation using `callPackage`
431−
432−Earlier we created a Python environment using `withPackages`, and included the
433−`toolz` package via a `let` expression.
434−Let's split the package definition from the environment definition.
435−
436−We first create a function that builds `toolz` in `~/path/to/toolz/release.nix`
437−
438−```nix
439−{ pkgs, buildPythonPackage }:
440−
441−buildPythonPackage rec {
442− pname = "toolz";
443− version = "0.7.4";
444−
445− src = fetchPypi {
446− inherit pname version;
447− sha256 = "43c2c9e5e7a16b6c88ba3088a9bfc82f7db8e13378be7c78d6c14a5f8ed05afd";
448− };
449−
450− meta = {
451− homepage = "http://github.com/pytoolz/toolz/";
452− description = "List processing tools and functional utilities";
453− license = licenses.bsd3;
454− maintainers = with maintainers; [ fridh ];
455− };
456−}
457−```
458−
459−It takes two arguments, `pkgs` and `buildPythonPackage`.
460−We now call this function using `callPackage` in the definition of our environment
461−
462−```nix
463−with import <nixpkgs> {};
464−
465−( let
466− toolz = pkgs.callPackage /path/to/toolz/release.nix {
467− pkgs = pkgs;
468− buildPythonPackage = pkgs.python35Packages.buildPythonPackage;
469− };
470− in pkgs.python35.withPackages (ps: [ ps.numpy toolz ])
471−).env
472−```
473−
474−Important to remember is that the Python version for which the package is made
475−depends on the `python` derivation that is passed to `buildPythonPackage`. Nix
476−tries to automatically pass arguments when possible, which is why generally you
477−don't explicitly define which `python` derivation should be used. In the above
478−example we use `buildPythonPackage` that is part of the set `python35Packages`,
479−and in this case the `python35` interpreter is automatically used.
480−
481−
482−
483−## Reference
484−
485−### Interpreters
486−
487−Versions 2.7, 3.3, 3.4, 3.5 and 3.6 of the CPython interpreter are available as
488−respectively `python27`, `python34`, `python35` and `python36`. The PyPy interpreter
489−is available as `pypy`. The aliases `python2` and `python3` correspond to respectively `python27` and
490−`python35`. The default interpreter, `python`, maps to `python2`.
491−The Nix expressions for the interpreters can be found in
492−`pkgs/development/interpreters/python`.
493−
494−All packages depending on any Python interpreter get appended
495−`out/{python.sitePackages}` to `$PYTHONPATH` if such directory
496−exists.
497−
498−#### Missing `tkinter` module standard library
499−
500−To reduce closure size the `Tkinter`/`tkinter` is available as a separate package, `pythonPackages.tkinter`.
501−
502−#### Attributes on interpreters packages
503−
504−Each interpreter has the following attributes:
505−
506−- `libPrefix`. Name of the folder in `${python}/lib/` for corresponding interpreter.
507−- `interpreter`. Alias for `${python}/bin/${executable}`.
508−- `buildEnv`. Function to build python interpreter environments with extra packages bundled together. See section *python.buildEnv function* for usage and documentation.
509−- `withPackages`. Simpler interface to `buildEnv`. See section *python.withPackages function* for usage and documentation.
510−- `sitePackages`. Alias for `lib/${libPrefix}/site-packages`.
511−- `executable`. Name of the interpreter executable, e.g. `python3.4`.
512−- `pkgs`. Set of Python packages for that specific interpreter. The package set can be modified by overriding the interpreter and passing `packageOverrides`.
513−
514−### Building packages and applications
515−
516−Python libraries and applications that use `setuptools` or
517−`distutils` are typically build with respectively the `buildPythonPackage` and
518−`buildPythonApplication` functions. These two functions also support installing a `wheel`.
519−
520−All Python packages reside in `pkgs/top-level/python-packages.nix` and all
521−applications elsewhere. In case a package is used as both a library and an application,
522−then the package should be in `pkgs/top-level/python-packages.nix` since only those packages are made
523−available for all interpreter versions. The preferred location for library expressions is in
524−`pkgs/development/python-modules`. It is important that these packages are
525−called from `pkgs/top-level/python-packages.nix` and not elsewhere, to guarantee
526−the right version of the package is built.
527−
528−Based on the packages defined in `pkgs/top-level/python-packages.nix` an
529−attribute set is created for each available Python interpreter. The available
530−sets are
531−
532−* `pkgs.python27Packages`
533−* `pkgs.python34Packages`
534−* `pkgs.python35Packages`
535−* `pkgs.python36Packages`
536−* `pkgs.pypyPackages`
537−
538−and the aliases
539−
540−* `pkgs.python2Packages` pointing to `pkgs.python27Packages`
541−* `pkgs.python3Packages` pointing to `pkgs.python36Packages`
542−* `pkgs.pythonPackages` pointing to `pkgs.python2Packages`
543−
544−#### `buildPythonPackage` function
545−
546−The `buildPythonPackage` function is implemented in
547−`pkgs/development/interpreters/python/build-python-package.nix`
548−
549−The following is an example:
550−```nix
551−
552−buildPythonPackage rec {
553− version = "3.3.1";
554− pname = "pytest";
555−
556− preCheck = ''
557− # don't test bash builtins
558− rm testing/test_argcomplete.py
559− '';
560−
561− src = fetchPypi {
562− inherit pname version;
563− sha256 = "cf8436dc59d8695346fcd3ab296de46425ecab00d64096cebe79fb51ecb2eb93";
564− };
565−
566− checkInputs = [ hypothesis ];
567− buildInputs = [ setuptools_scm ];
568− propagatedBuildInputs = [ attrs py setuptools six pluggy ];
569−
570− meta = with stdenv.lib; {
571− maintainers = with maintainers; [ domenkozar lovek323 madjar lsix ];
572− description = "Framework for writing tests";
573− };
574−}
575−
576−```
577−
578−The `buildPythonPackage` mainly does four things:
579−
580−* In the `buildPhase`, it calls `${python.interpreter} setup.py bdist_wheel` to
581− build a wheel binary zipfile.
582−* In the `installPhase`, it installs the wheel file using `pip install *.whl`.
583−* In the `postFixup` phase, the `wrapPythonPrograms` bash function is called to
584− wrap all programs in the `$out/bin/*` directory to include `$PATH`
585− environment variable and add dependent libraries to script's `sys.path`.
586−* In the `installCheck` phase, `${python.interpreter} setup.py test` is ran.
587−
588−As in Perl, dependencies on other Python packages can be specified in the
589−`buildInputs` and `propagatedBuildInputs` attributes. If something is
590−exclusively a build-time dependency, use `buildInputs`; if it’s (also) a runtime
591−dependency, use `propagatedBuildInputs`.
592−
593−By default tests are run because `doCheck = true`. Test dependencies, like
594−e.g. the test runner, should be added to `buildInputs`.
595−
596−By default `meta.platforms` is set to the same value
597−as the interpreter unless overridden otherwise.
598−
599−##### `buildPythonPackage` parameters
600−
601−All parameters from `mkDerivation` function are still supported.
602−
603−* `namePrefix`: Prepended text to `${name}` parameter. Defaults to `"python3.3-"` for Python 3.3, etc. Set it to `""` if you're packaging an application or a command line tool.
604−* `disabled`: If `true`, package is not build for particular python interpreter version. Grep around `pkgs/top-level/python-packages.nix` for examples.
605−* `setupPyBuildFlags`: List of flags passed to `setup.py build_ext` command.
606−* `pythonPath`: List of packages to be added into `$PYTHONPATH`. Packages in `pythonPath` are not propagated (contrary to `propagatedBuildInputs`).
607−* `preShellHook`: Hook to execute commands before `shellHook`.
608−* `postShellHook`: Hook to execute commands after `shellHook`.
609−* `makeWrapperArgs`: A list of strings. Arguments to be passed to `makeWrapper`, which wraps generated binaries. By default, the arguments to `makeWrapper` set `PATH` and `PYTHONPATH` environment variables before calling the binary. Additional arguments here can allow a developer to set environment variables which will be available when the binary is run. For example, `makeWrapperArgs = ["--set FOO BAR" "--set BAZ QUX"]`.
610−* `installFlags`: A list of strings. Arguments to be passed to `pip install`. To pass options to `python setup.py install`, use `--install-option`. E.g., `installFlags=["--install-option='--cpp_implementation'"].
611−* `format`: Format of the source. Valid options are `setuptools` (default), `flit`, `wheel`, and `other`. `setuptools` is for when the source has a `setup.py` and `setuptools` is used to build a wheel, `flit`, in case `flit` should be used to build a wheel, and `wheel` in case a wheel is provided. In case you need to provide your own `buildPhase` and `installPhase` you can use `other`.
612−* `catchConflicts` If `true`, abort package build if a package name appears more than once in dependency tree. Default is `true`.
613−* `checkInputs` Dependencies needed for running the `checkPhase`. These are added to `buildInputs` when `doCheck = true`.
614−
615−##### Overriding Python packages
616−
617−The `buildPythonPackage` function has a `overridePythonAttrs` method that
618−can be used to override the package. In the following example we create an
619−environment where we have the `blaze` package using an older version of `pandas`.
620−We override first the Python interpreter and pass
621−`packageOverrides` which contains the overrides for packages in the package set.
622−
623−```nix
624−with import <nixpkgs> {};
625−
626−(let
627− python = let
628− packageOverrides = self: super: {
629− pandas = super.pandas.overridePythonAttrs(old: rec {
630− version = "0.19.1";
631− src = super.fetchPypi {
632− pname = "pandas";
633− inherit version;
634− sha256 = "08blshqj9zj1wyjhhw3kl2vas75vhhicvv72flvf1z3jvapgw295";
635− };
636− });
637− };
638− in pkgs.python3.override {inherit packageOverrides;};
639−
640−in python.withPackages(ps: [ps.blaze])).env
641−```
642−
643−#### `buildPythonApplication` function
644−
645−The `buildPythonApplication` function is practically the same as `buildPythonPackage`.
646−The difference is that `buildPythonPackage` by default prefixes the names of the packages with the version of the interpreter.
647−Because with an application we're not interested in multiple version the prefix is dropped.
648−
649−#### python.buildEnv function
650−
651−Python environments can be created using the low-level `pkgs.buildEnv` function.
652−This example shows how to create an environment that has the Pyramid Web Framework.
653−Saving the following as `default.nix`
654−```nix
655−with import <nixpkgs> {};
656−
657−python.buildEnv.override {
658− extraLibs = [ pkgs.pythonPackages.pyramid ];
659− ignoreCollisions = true;
660−}
661−```
662−
663−and running `nix-build` will create
664−```
665−/nix/store/cf1xhjwzmdki7fasgr4kz6di72ykicl5-python-2.7.8-env
666−```
667−
668−with wrapped binaries in `bin/`.
669−
670−You can also use the `env` attribute to create local environments with needed
671−packages installed. This is somewhat comparable to `virtualenv`. For example,
672−running `nix-shell` with the following `shell.nix`
673−```nix
674−with import <nixpkgs> {};
675−
676−(python3.buildEnv.override {
677− extraLibs = with python3Packages; [ numpy requests ];
678−}).env
679−```
680−
681−will drop you into a shell where Python will have the
682−specified packages in its path.
683−
684−
685−##### `python.buildEnv` arguments
686−
687−* `extraLibs`: List of packages installed inside the environment.
688−* `postBuild`: Shell command executed after the build of environment.
689−* `ignoreCollisions`: Ignore file collisions inside the environment (default is `false`).
690−
691−#### python.withPackages function
692−
693−The `python.withPackages` function provides a simpler interface to the `python.buildEnv` functionality.
694−It takes a function as an argument that is passed the set of python packages and returns the list
695−of the packages to be included in the environment. Using the `withPackages` function, the previous
696−example for the Pyramid Web Framework environment can be written like this:
697−```nix
698−with import <nixpkgs> {};
699−
700−python.withPackages (ps: [ps.pyramid])
701−```
702−
703−`withPackages` passes the correct package set for the specific interpreter version as an
704−argument to the function. In the above example, `ps` equals `pythonPackages`.
705−But you can also easily switch to using python3:
706−```nix
707−with import <nixpkgs> {};
708−
709−python3.withPackages (ps: [ps.pyramid])
710−```
711−
712−Now, `ps` is set to `python3Packages`, matching the version of the interpreter.
713−
714−As `python.withPackages` simply uses `python.buildEnv` under the hood, it also supports the `env`
715−attribute. The `shell.nix` file from the previous section can thus be also written like this:
716−```nix
717−with import <nixpkgs> {};
718−
719−(python36.withPackages (ps: [ps.numpy ps.requests])).env
720−```
721−
722−In contrast to `python.buildEnv`, `python.withPackages` does not support the more advanced options
723−such as `ignoreCollisions = true` or `postBuild`. If you need them, you have to use `python.buildEnv`.
724−
725−Python 2 namespace packages may provide `__init__.py` that collide. In that case `python.buildEnv`
726−should be used with `ignoreCollisions = true`.
727−
728−### Development mode
729−
730−Development or editable mode is supported. To develop Python packages
731−`buildPythonPackage` has additional logic inside `shellPhase` to run `pip
732−install -e . --prefix $TMPDIR/`for the package.
733−
734−Warning: `shellPhase` is executed only if `setup.py` exists.
735−
736−Given a `default.nix`:
737−```nix
738−with import <nixpkgs> {};
739−
740−buildPythonPackage { name = "myproject";
741−
742−buildInputs = with pkgs.pythonPackages; [ pyramid ];
743−
744−src = ./.; }
745−```
746−
747−Running `nix-shell` with no arguments should give you
748−the environment in which the package would be built with
749−`nix-build`.
750−
751−Shortcut to setup environments with C headers/libraries and python packages:
752−```shell
753−nix-shell -p pythonPackages.pyramid zlib libjpeg git
754−```
755−
756−Note: There is a boolean value `lib.inNixShell` set to `true` if nix-shell is invoked.
757−
758−### Tools
759−
760−Packages inside nixpkgs are written by hand. However many tools exist in
761−community to help save time. No tool is preferred at the moment.
762−
763−- [python2nix](https://github.com/proger/python2nix) by Vladimir Kirillov
764−- [pypi2nix](https://github.com/garbas/pypi2nix) by Rok Garbas
765−- [pypi2nix](https://github.com/offlinehacker/pypi2nix) by Jaka Hudoklin
766−
767−### Deterministic builds
768−
769−Python 2.7, 3.5 and 3.6 are now built deterministically and 3.4 mostly.
770−Minor modifications had to be made to the interpreters in order to generate
771−deterministic bytecode. This has security implications and is relevant for
772−those using Python in a `nix-shell`.
773−
774−When the environment variable `DETERMINISTIC_BUILD` is set, all bytecode will have timestamp 1.
775−The `buildPythonPackage` function sets `DETERMINISTIC_BUILD=1` and
776−[PYTHONHASHSEED=0](https://docs.python.org/3.5/using/cmdline.html#envvar-PYTHONHASHSEED).
777−Both are also exported in `nix-shell`.
778−
779−
780−### Automatic tests
781−
782−It is recommended to test packages as part of the build process.
783−Source distributions (`sdist`) often include test files, but not always.
784−
785−By default the command `python setup.py test` is run as part of the
786−`checkPhase`, but often it is necessary to pass a custom `checkPhase`. An
787−example of such a situation is when `py.test` is used.
788−
789−#### Common issues
790−
791−- Non-working tests can often be deselected. By default `buildPythonPackage` runs `python setup.py test`.
792− Most python modules follows the standard test protocol where the pytest runner can be used instead.
793− `py.test` supports a `-k` parameter to ignore test methods or classes:
794−
795− ```nix
796− buildPythonPackage {
797− # ...
798− # assumes the tests are located in tests
799− checkInputs = [ pytest ];
800− checkPhase = ''
801− py.test -k 'not function_name and not other_function' tests
802− '';
803− }
804− ```
805−- Unicode issues can typically be fixed by including `glibcLocales` in `buildInputs` and exporting `LC_ALL=en_US.utf-8`.
806−- Tests that attempt to access `$HOME` can be fixed by using the following work-around before running tests (e.g. `preCheck`): `export HOME=$(mktemp -d)`
807−
808−## FAQ
809−
810−### How to solve circular dependencies?
811−
812−Consider the packages `A` and `B` that depend on each other. When packaging `B`,
813−a solution is to override package `A` not to depend on `B` as an input. The same
814−should also be done when packaging `A`.
815−
816−### How to override a Python package?
817−
818−We can override the interpreter and pass `packageOverrides`.
819−In the following example we rename the `pandas` package and build it.
820−```nix
821−with import <nixpkgs> {};
822−
823−(let
824− python = let
825− packageOverrides = self: super: {
826− pandas = super.pandas.overridePythonAttrs(old: {name="foo";});
827− };
828− in pkgs.python35.override {inherit packageOverrides;};
829−
830−in python.withPackages(ps: [ps.pandas])).env
831−```
832−Using `nix-build` on this expression will build an environment that contains the
833−package `pandas` but with the new name `foo`.
834−
835−All packages in the package set will use the renamed package.
836−A typical use case is to switch to another version of a certain package.
837−For example, in the Nixpkgs repository we have multiple versions of `django` and `scipy`.
838−In the following example we use a different version of `scipy` and create an environment that uses it.
839−All packages in the Python package set will now use the updated `scipy` version.
840−
841−```nix
842−with import <nixpkgs> {};
843−
844−( let
845− packageOverrides = self: super: {
846− scipy = super.scipy_0_17;
847− };
848− in (pkgs.python35.override {inherit packageOverrides;}).withPackages (ps: [ps.blaze])
849−).env
850−```
851−The requested package `blaze` depends on `pandas` which itself depends on `scipy`.
852−
853−If you want the whole of Nixpkgs to use your modifications, then you can use `overlays`
854−as explained in this manual. In the following example we build a `inkscape` using a different version of `numpy`.
855−```nix
856−let
857− pkgs = import <nixpkgs> {};
858− newpkgs = import pkgs.path { overlays = [ (pkgsself: pkgssuper: {
859− python27 = let
860− packageOverrides = self: super: {
861− numpy = super.numpy_1_10;
862− };
863− in pkgssuper.python27.override {inherit packageOverrides;};
864− } ) ]; };
865−in newpkgs.inkscape
866−```
867−
868−### `python setup.py bdist_wheel` cannot create .whl
869−
870−Executing `python setup.py bdist_wheel` in a `nix-shell `fails with
871−```
872−ValueError: ZIP does not support timestamps before 1980
873−```
874−This is because files are included that depend on items in the Nix store which have a timestamp of, that is, it corresponds to January the 1st, 1970 at 00:00:00. And as the error informs you, ZIP does not support that.
875−The command `bdist_wheel` takes into account `SOURCE_DATE_EPOCH`, and `nix-shell` sets this to 1. By setting it to a value corresponding to 1980 or later, or by unsetting it, it is possible to build wheels.
876−
877−Use 1980 as timestamp:
878−```shell
879−nix-shell --run "SOURCE_DATE_EPOCH=315532800 python3 setup.py bdist_wheel"
880−```
881−or the current time:
882−```shell
883−nix-shell --run "SOURCE_DATE_EPOCH=$(date +%s) python3 setup.py bdist_wheel"
884−```
885−or unset:
886−```shell
887−nix-shell --run "unset SOURCE_DATE_EPOCH; python3 setup.py bdist_wheel"
888−```
889−
890−### `install_data` / `data_files` problems
891−
892−If you get the following error:
893−```
894−could not create '/nix/store/6l1bvljpy8gazlsw2aw9skwwp4pmvyxw-python-2.7.8/etc':
895−Permission denied
896−```
897−This is a [known bug](https://github.com/pypa/setuptools/issues/130) in `setuptools`.
898−Setuptools `install_data` does not respect `--prefix`. An example of such package using the feature is `pkgs/tools/X11/xpra/default.nix`.
899−As workaround install it as an extra `preInstall` step:
900−```shell
901−${python.interpreter} setup.py install_data --install-dir=$out --root=$out
902−sed -i '/ = data\_files/d' setup.py
903−```
904−
905−### Rationale of non-existent global site-packages
906−
907−On most operating systems a global `site-packages` is maintained. This however
908−becomes problematic if you want to run multiple Python versions or have multiple
909−versions of certain libraries for your projects. Generally, you would solve such
910−issues by creating virtual environments using `virtualenv`.
911−
912−On Nix each package has an isolated dependency tree which, in the case of
913−Python, guarantees the right versions of the interpreter and libraries or
914−packages are available. There is therefore no need to maintain a global `site-packages`.
915−
916−If you want to create a Python environment for development, then the recommended
917−method is to use `nix-shell`, either with or without the `python.buildEnv`
918−function.
919−
920−### How to consume python modules using pip in a virtualenv like I am used to on other Operating Systems ?
921−
922−This is an example of a `default.nix` for a `nix-shell`, which allows to consume a `virtualenv` environment,
923−and install python modules through `pip` the traditional way.
924−
925−Create this `default.nix` file, together with a `requirements.txt` and simply execute `nix-shell`.
926−
927−```nix
928−with import <nixpkgs> {};
929−with pkgs.python27Packages;
930−
931−stdenv.mkDerivation {
932− name = "impurePythonEnv";
933− buildInputs = [
934− # these packages are required for virtualenv and pip to work:
935− #
936− python27Full
937− python27Packages.virtualenv
938− python27Packages.pip
939− # the following packages are related to the dependencies of your python
940− # project.
941− # In this particular example the python modules listed in the
942− # requirements.tx require the following packages to be installed locally
943− # in order to compile any binary extensions they may require.
944− #
945− taglib
946− openssl
947− git
948− libxml2
949− libxslt
950− libzip
951− stdenv
952− zlib ];
953− src = null;
954− shellHook = ''
955− # set SOURCE_DATE_EPOCH so that we can use python wheels
956− SOURCE_DATE_EPOCH=$(date +%s)
957− virtualenv --no-setuptools venv
958− export PATH=$PWD/venv/bin:$PATH
959− pip install -r requirements.txt
960− '';
961−}
962−```
963−
964−Note that the `pip install` is an imperative action. So every time `nix-shell`
965−is executed it will attempt to download the python modules listed in
966−requirements.txt. However these will be cached locally within the `virtualenv`
967−folder and not downloaded again.
968−
969−### How to override a Python package from `configuration.nix`?
970−
971−If you need to change a package's attribute(s) from `configuration.nix` you could do:
972−
973−```nix
974− nixpkgs.config.packageOverrides = superP: {
975− pythonPackages = superP.pythonPackages.override {
976− overrides = self: super: {
977− bepasty-server = super.bepasty-server.overrideAttrs ( oldAttrs: {
978− src = pkgs.fetchgit {
979− url = "https://github.com/bepasty/bepasty-server";
980− sha256 = "9ziqshmsf0rjvdhhca55sm0x8jz76fsf2q4rwh4m6lpcf8wr0nps";
981− rev = "e2516e8cf4f2afb5185337073607eb9e84a61d2d";
982− };
983− });
984− };
985− };
986− };
987−```
988−
989−If you are using the `bepasty-server` package somewhere, for example in `systemPackages` or indirectly from `services.bepasty`, then a `nixos-rebuild switch` will rebuild the system but with the `bepasty-server` package using a different `src` attribute. This way one can modify `python` based software/libraries easily. Using `self` and `super` one can also alter dependencies (`buildInputs`) between the old state (`self`) and new state (`super`).
990−
991−### How to override a Python package using overlays?
992−
993−To alter a python package using overlays, you would use the following approach:
994−
995−```nix
996−self: super:
997−rec {
998− python = super.python.override {
999− packageOverrides = python-self: python-super: {
1000− bepasty-server = python-super.bepasty-server.overrideAttrs ( oldAttrs: {
1001− src = self.pkgs.fetchgit {
1002− url = "https://github.com/bepasty/bepasty-server";
1003− sha256 = "9ziqshmsf0rjvdhhca55sm0x8jz76fsf2q4rwh4m6lpcf8wr0nps";
1004− rev = "e2516e8cf4f2afb5185337073607eb9e84a61d2d";
1005− };
1006− });
1007− };
1008− };
1009− pythonPackages = python.pkgs;
1010−}
1011−```
1012−
1013−## Contributing
1014−
1015−### Contributing guidelines
1016−
1017−Following rules are desired to be respected:
1018−
1019−* Python libraries are called from `python-packages.nix` and packaged with `buildPythonPackage`. The expression of a library should be in `pkgs/development/python-modules/<name>/default.nix`. Libraries in `pkgs/top-level/python-packages.nix` are sorted quasi-alphabetically to avoid merge conflicts.
1020−* Python applications live outside of `python-packages.nix` and are packaged with `buildPythonApplication`.
1021−* Make sure libraries build for all Python interpreters.
1022−* By default we enable tests. Make sure the tests are found and, in the case of libraries, are passing for all interpreters. If certain tests fail they can be disabled individually. Try to avoid disabling the tests altogether. In any case, when you disable tests, leave a comment explaining why.
1023−* Commit names of Python libraries should reflect that they are Python libraries, so write for example `pythonPackages.numpy: 1.11 -> 1.12`.
1024−
doc/languages-frameworks/python.section.mdnew file+1109
@@ -0,0 +1,1109 @@
1+# Python
2+
3+## User Guide
4+
5+### Using Python
6+
7+#### Overview
8+
9+Several versions of the Python interpreter are available on Nix, as well as a
10+high amount of packages. The attribute `python` refers to the default
11+interpreter, which is currently CPython 2.7. It is also possible to refer to
12+specific versions, e.g. `python35` refers to CPython 3.5, and `pypy` refers to
13+the default PyPy interpreter.
14+
15+Python is used a lot, and in different ways. This affects also how it is
16+packaged. In the case of Python on Nix, an important distinction is made between
17+whether the package is considered primarily an application, or whether it should
18+be used as a library, i.e., of primary interest are the modules in
19+`site-packages` that should be importable.
20+
21+In the Nixpkgs tree Python applications can be found throughout, depending on
22+what they do, and are called from the main package set. Python libraries,
23+however, are in separate sets, with one set per interpreter version.
24+
25+The interpreters have several common attributes. One of these attributes is
26+`pkgs`, which is a package set of Python libraries for this specific
27+interpreter. E.g., the `toolz` package corresponding to the default interpreter
28+is `python.pkgs.toolz`, and the CPython 3.5 version is `python35.pkgs.toolz`.
29+The main package set contains aliases to these package sets, e.g.
30+`pythonPackages` refers to `python.pkgs` and `python35Packages` to
31+`python35.pkgs`.
32+
33+#### Installing Python and packages
34+
35+The Nix and NixOS manuals explain how packages are generally installed. In the
36+case of Python and Nix, it is important to make a distinction between whether the
37+package is considered an application or a library.
38+
39+Applications on Nix are typically installed into your user
40+profile imperatively using `nix-env -i`, and on NixOS declaratively by adding the
41+package name to `environment.systemPackages` in `/etc/nixos/configuration.nix`.
42+Dependencies such as libraries are automatically installed and should not be
43+installed explicitly.
44+
45+The same goes for Python applications and libraries. Python applications can be
46+installed in your profile. But Python libraries you would like to use for
47+development cannot be installed, at least not individually, because they won't
48+be able to find each other resulting in import errors. Instead, it is possible
49+to create an environment with `python.buildEnv` or `python.withPackages` where
50+the interpreter and other executables are able to find each other and all of the
51+modules.
52+
53+In the following examples we create an environment with Python 3.5, `numpy` and
54+`toolz`. As you may imagine, there is one limitation here, and that's that
55+you can install only one environment at a time. You will notice the complaints
56+about collisions when you try to install a second environment.
57+
58+##### Environment defined in separate `.nix` file
59+
60+Create a file, e.g. `build.nix`, with the following expression
61+```nix
62+with import <nixpkgs> {};
63+
64+python35.withPackages (ps: with ps; [ numpy toolz ])
65+```
66+and install it in your profile with
67+```shell
68+nix-env -if build.nix
69+```
70+Now you can use the Python interpreter, as well as the extra packages (`numpy`,
71+`toolz`) that you added to the environment.
72+
73+##### Environment defined in `~/.config/nixpkgs/config.nix`
74+
75+If you prefer to, you could also add the environment as a package override to the Nixpkgs set, e.g.
76+using `config.nix`,
77+```nix
78+{ # ...
79+
80+ packageOverrides = pkgs: with pkgs; {
81+ myEnv = python35.withPackages (ps: with ps; [ numpy toolz ]);
82+ };
83+}
84+```
85+and install it in your profile with
86+```shell
87+nix-env -iA nixpkgs.myEnv
88+```
89+The environment is is installed by referring to the attribute, and considering
90+the `nixpkgs` channel was used.
91+
92+##### Environment defined in `/etc/nixos/configuration.nix`
93+
94+For the sake of completeness, here's another example how to install the environment system-wide.
95+
96+```nix
97+{ # ...
98+
99+ environment.systemPackages = with pkgs; [
100+ (python35.withPackages(ps: with ps; [ numpy toolz ]))
101+ ];
102+}
103+```
104+
105+#### Temporary Python environment with `nix-shell`
106+
107+The examples in the previous section showed how to install a Python environment
108+into a profile. For development you may need to use multiple environments.
109+`nix-shell` gives the possibility to temporarily load another environment, akin
110+to `virtualenv`.
111+
112+There are two methods for loading a shell with Python packages. The first and recommended method
113+is to create an environment with `python.buildEnv` or `python.withPackages` and load that. E.g.
114+```sh
115+$ nix-shell -p 'python35.withPackages(ps: with ps; [ numpy toolz ])'
116+```
117+opens a shell from which you can launch the interpreter
118+```sh
119+[nix-shell:~] python3
120+```
121+The other method, which is not recommended, does not create an environment and requires you to list the packages directly,
122+
123+```sh
124+$ nix-shell -p python35.pkgs.numpy python35.pkgs.toolz
125+```
126+Again, it is possible to launch the interpreter from the shell.
127+The Python interpreter has the attribute `pkgs` which contains all Python libraries for that specific interpreter.
128+
129+##### Load environment from `.nix` expression
130+As explained in the Nix manual, `nix-shell` can also load an
131+expression from a `.nix` file. Say we want to have Python 3.5, `numpy`
132+and `toolz`, like before, in an environment. Consider a `shell.nix` file
133+with
134+```nix
135+with import <nixpkgs> {};
136+
137+(python35.withPackages (ps: [ps.numpy ps.toolz])).env
138+```
139+Executing `nix-shell` gives you again a Nix shell from which you can run Python.
140+
141+What's happening here?
142+
143+1. We begin with importing the Nix Packages collections. `import <nixpkgs>` imports the `<nixpkgs>` function, `{}` calls it and the `with` statement brings all attributes of `nixpkgs` in the local scope. These attributes form the main package set.
144+2. Then we create a Python 3.5 environment with the `withPackages` function.
145+3. The `withPackages` function expects us to provide a function as an argument that takes the set of all python packages and returns a list of packages to include in the environment. Here, we select the packages `numpy` and `toolz` from the package set.
146+
147+##### Execute command with `--run`
148+A convenient option with `nix-shell` is the `--run`
149+option, with which you can execute a command in the `nix-shell`. We can
150+e.g. directly open a Python shell
151+```sh
152+$ nix-shell -p python35Packages.numpy python35Packages.toolz --run "python3"
153+```
154+or run a script
155+```sh
156+$ nix-shell -p python35Packages.numpy python35Packages.toolz --run "python3 myscript.py"
157+```
158+
159+##### `nix-shell` as shebang
160+In fact, for the second use case, there is a more convenient method. You can
161+add a [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) to your script
162+specifying which dependencies `nix-shell` needs. With the following shebang, you
163+can just execute `./myscript.py`, and it will make available all dependencies and
164+run the script in the `python3` shell.
165+
166+```py
167+#! /usr/bin/env nix-shell
168+#! nix-shell -i python3 -p "python3.withPackages(ps: [ps.numpy])"
169+
170+import numpy
171+
172+print(numpy.__version__)
173+```
174+
175+### Developing with Python
176+
177+Now that you know how to get a working Python environment with Nix, it is time
178+to go forward and start actually developing with Python. We will first have a
179+look at how Python packages are packaged on Nix. Then, we will look at how you
180+can use development mode with your code.
181+
182+#### Packaging a library
183+
184+With Nix all packages are built by functions. The main function in Nix for
185+building Python libraries is `buildPythonPackage`. Let's see how we can build the
186+`toolz` package.
187+
188+```nix
189+{ lib, buildPythonPackage, fetchPypi }:
190+
191+ toolz = buildPythonPackage rec {
192+ pname = "toolz";
193+ version = "0.7.4";
194+
195+ src = fetchPypi {
196+ inherit pname version;
197+ sha256 = "43c2c9e5e7a16b6c88ba3088a9bfc82f7db8e13378be7c78d6c14a5f8ed05afd";
198+ };
199+
200+ doCheck = false;
201+
202+ meta = with lib; {
203+ homepage = https://github.com/pytoolz/toolz;
204+ description = "List processing tools and functional utilities";
205+ license = licenses.bsd3;
206+ maintainers = with maintainers; [ fridh ];
207+ };
208+ };
209+}
210+```
211+
212+What happens here? The function `buildPythonPackage` is called and as argument
213+it accepts a set. In this case the set is a recursive set, `rec`. One of the
214+arguments is the name of the package, which consists of a basename (generally
215+following the name on PyPi) and a version. Another argument, `src` specifies the
216+source, which in this case is fetched from PyPI using the helper function
217+`fetchPypi`. The argument `doCheck` is used to set whether tests should be run
218+when building the package. Furthermore, we specify some (optional) meta
219+information. The output of the function is a derivation.
220+
221+An expression for `toolz` can be found in the Nixpkgs repository. As explained
222+in the introduction of this Python section, a derivation of `toolz` is available
223+for each interpreter version, e.g. `python35.pkgs.toolz` refers to the `toolz`
224+derivation corresponding to the CPython 3.5 interpreter.
225+The above example works when you're directly working on
226+`pkgs/top-level/python-packages.nix` in the Nixpkgs repository. Often though,
227+you will want to test a Nix expression outside of the Nixpkgs tree.
228+
229+The following expression creates a derivation for the `toolz` package,
230+and adds it along with a `numpy` package to a Python environment.
231+
232+```nix
233+with import <nixpkgs> {};
234+
235+( let
236+ my_toolz = python35.pkgs.buildPythonPackage rec {
237+ pname = "toolz";
238+ version = "0.7.4";
239+
240+ src = python35.pkgs.fetchPypi {
241+ inherit pname version;
242+ sha256 = "43c2c9e5e7a16b6c88ba3088a9bfc82f7db8e13378be7c78d6c14a5f8ed05afd";
243+ };
244+
245+ doCheck = false;
246+
247+ meta = {
248+ homepage = "https://github.com/pytoolz/toolz/";
249+ description = "List processing tools and functional utilities";
250+ };
251+ };
252+
253+ in python35.withPackages (ps: [ps.numpy my_toolz])
254+).env
255+```
256+Executing `nix-shell` will result in an environment in which you can use
257+Python 3.5 and the `toolz` package. As you can see we had to explicitly mention
258+for which Python version we want to build a package.
259+
260+So, what did we do here? Well, we took the Nix expression that we used earlier
261+to build a Python environment, and said that we wanted to include our own
262+version of `toolz`, named `my_toolz`. To introduce our own package in the scope
263+of `withPackages` we used a `let` expression. You can see that we used
264+`ps.numpy` to select numpy from the nixpkgs package set (`ps`). We did not take
265+`toolz` from the Nixpkgs package set this time, but instead took our own version
266+that we introduced with the `let` expression.
267+
268+#### Handling dependencies
269+
270+Our example, `toolz`, does not have any dependencies on other Python packages or
271+system libraries. According to the manual, `buildPythonPackage` uses the
272+arguments `buildInputs` and `propagatedBuildInputs` to specify dependencies. If
273+something is exclusively a build-time dependency, then the dependency should be
274+included as a `buildInput`, but if it is (also) a runtime dependency, then it
275+should be added to `propagatedBuildInputs`. Test dependencies are considered
276+build-time dependencies and passed to `checkInputs`.
277+
278+The following example shows which arguments are given to `buildPythonPackage` in
279+order to build [`datashape`](https://github.com/blaze/datashape).
280+
281+```nix
282+{ # ...
283+
284+ datashape = buildPythonPackage rec {
285+ pname = "datashape";
286+ version = "0.4.7";
287+
288+ src = fetchPypi {
289+ inherit pname version;
290+ sha256 = "14b2ef766d4c9652ab813182e866f493475e65e558bed0822e38bf07bba1a278";
291+ };
292+
293+ checkInputs = with self; [ pytest ];
294+ propagatedBuildInputs = with self; [ numpy multipledispatch dateutil ];
295+
296+ meta = with lib; {
297+ homepage = https://github.com/ContinuumIO/datashape;
298+ description = "A data description language";
299+ license = licenses.bsd2;
300+ maintainers = with maintainers; [ fridh ];
301+ };
302+ };
303+}
304+```
305+
306+We can see several runtime dependencies, `numpy`, `multipledispatch`, and
307+`dateutil`. Furthermore, we have one `buildInput`, i.e. `pytest`. `pytest` is a
308+test runner and is only used during the `checkPhase` and is therefore not added
309+to `propagatedBuildInputs`.
310+
311+In the previous case we had only dependencies on other Python packages to consider.
312+Occasionally you have also system libraries to consider. E.g., `lxml` provides
313+Python bindings to `libxml2` and `libxslt`. These libraries are only required
314+when building the bindings and are therefore added as `buildInputs`.
315+
316+```nix
317+{ # ...
318+
319+ lxml = buildPythonPackage rec {
320+ pname = "lxml";
321+ version = "3.4.4";
322+
323+ src = fetchPypi {
324+ inherit pname version;
325+ sha256 = "16a0fa97hym9ysdk3rmqz32xdjqmy4w34ld3rm3jf5viqjx65lxk";
326+ };
327+
328+ buildInputs = with self; [ pkgs.libxml2 pkgs.libxslt ];
329+
330+ meta = with lib; {
331+ description = "Pythonic binding for the libxml2 and libxslt libraries";
332+ homepage = https://lxml.de;
333+ license = licenses.bsd3;
334+ maintainers = with maintainers; [ sjourdois ];
335+ };
336+ };
337+}
338+```
339+
340+In this example `lxml` and Nix are able to work out exactly where the relevant
341+files of the dependencies are. This is not always the case.
342+
343+The example below shows bindings to The Fastest Fourier Transform in the West, commonly known as
344+FFTW. On Nix we have separate packages of FFTW for the different types of floats
345+(`"single"`, `"double"`, `"long-double"`). The bindings need all three types,
346+and therefore we add all three as `buildInputs`. The bindings don't expect to
347+find each of them in a different folder, and therefore we have to set `LDFLAGS`
348+and `CFLAGS`.
349+
350+```nix
351+{ # ...
352+
353+ pyfftw = buildPythonPackage rec {
354+ pname = "pyFFTW";
355+ version = "0.9.2";
356+
357+ src = fetchPypi {
358+ inherit pname version;
359+ sha256 = "f6bbb6afa93085409ab24885a1a3cdb8909f095a142f4d49e346f2bd1b789074";
360+ };
361+
362+ buildInputs = [ pkgs.fftw pkgs.fftwFloat pkgs.fftwLongDouble];
363+
364+ propagatedBuildInputs = with self; [ numpy scipy ];
365+
366+ # Tests cannot import pyfftw. pyfftw works fine though.
367+ doCheck = false;
368+
369+ preConfigure = ''
370+ export LDFLAGS="-L${pkgs.fftw.dev}/lib -L${pkgs.fftwFloat.out}/lib -L${pkgs.fftwLongDouble.out}/lib"
371+ export CFLAGS="-I${pkgs.fftw.dev}/include -I${pkgs.fftwFloat.dev}/include -I${pkgs.fftwLongDouble.dev}/include"
372+ '';
373+
374+ meta = with lib; {
375+ description = "A pythonic wrapper around FFTW, the FFT library, presenting a unified interface for all the supported transforms";
376+ homepage = http://hgomersall.github.com/pyFFTW;
377+ license = with licenses; [ bsd2 bsd3 ];
378+ maintainers = with maintainers; [ fridh ];
379+ };
380+ };
381+}
382+```
383+Note also the line `doCheck = false;`, we explicitly disabled running the test-suite.
384+
385+
386+#### Develop local package
387+
388+As a Python developer you're likely aware of [development mode](http://setuptools.readthedocs.io/en/latest/setuptools.html#development-mode) (`python setup.py develop`);
389+instead of installing the package this command creates a special link to the project code.
390+That way, you can run updated code without having to reinstall after each and every change you make.
391+Development mode is also available. Let's see how you can use it.
392+
393+In the previous Nix expression the source was fetched from an url. We can also refer to a local source instead using
394+`src = ./path/to/source/tree;`
395+
396+If we create a `shell.nix` file which calls `buildPythonPackage`, and if `src`
397+is a local source, and if the local source has a `setup.py`, then development
398+mode is activated.
399+
400+In the following example we create a simple environment that
401+has a Python 3.5 version of our package in it, as well as its dependencies and
402+other packages we like to have in the environment, all specified with `propagatedBuildInputs`.
403+Indeed, we can just add any package we like to have in our environment to `propagatedBuildInputs`.
404+
405+```nix
406+with import <nixpkgs> {};
407+with pkgs.python35Packages;
408+
409+buildPythonPackage rec {
410+ name = "mypackage";
411+ src = ./path/to/package/source;
412+ propagatedBuildInputs = [ pytest numpy pkgs.libsndfile ];
413+}
414+```
415+
416+It is important to note that due to how development mode is implemented on Nix it is not possible to have multiple packages simultaneously in development mode.
417+
418+
419+### Organising your packages
420+
421+So far we discussed how you can use Python on Nix, and how you can develop with
422+it. We've looked at how you write expressions to package Python packages, and we
423+looked at how you can create environments in which specified packages are
424+available.
425+
426+At some point you'll likely have multiple packages which you would
427+like to be able to use in different projects. In order to minimise unnecessary
428+duplication we now look at how you can maintain a repository with your
429+own packages. The important functions here are `import` and `callPackage`.
430+
431+### Including a derivation using `callPackage`
432+
433+Earlier we created a Python environment using `withPackages`, and included the
434+`toolz` package via a `let` expression.
435+Let's split the package definition from the environment definition.
436+
437+We first create a function that builds `toolz` in `~/path/to/toolz/release.nix`
438+
439+```nix
440+{ lib, pkgs, buildPythonPackage }:
441+
442+buildPythonPackage rec {
443+ pname = "toolz";
444+ version = "0.7.4";
445+
446+ src = fetchPypi {
447+ inherit pname version;
448+ sha256 = "43c2c9e5e7a16b6c88ba3088a9bfc82f7db8e13378be7c78d6c14a5f8ed05afd";
449+ };
450+
451+ meta = with lib; {
452+ homepage = "http://github.com/pytoolz/toolz/";
453+ description = "List processing tools and functional utilities";
454+ license = licenses.bsd3;
455+ maintainers = with maintainers; [ fridh ];
456+ };
457+}
458+```
459+
460+It takes two arguments, `pkgs` and `buildPythonPackage`.
461+We now call this function using `callPackage` in the definition of our environment
462+
463+```nix
464+with import <nixpkgs> {};
465+
466+( let
467+ toolz = pkgs.callPackage /path/to/toolz/release.nix {
468+ pkgs = pkgs;
469+ buildPythonPackage = pkgs.python35Packages.buildPythonPackage;
470+ };
471+ in pkgs.python35.withPackages (ps: [ ps.numpy toolz ])
472+).env
473+```
474+
475+Important to remember is that the Python version for which the package is made
476+depends on the `python` derivation that is passed to `buildPythonPackage`. Nix
477+tries to automatically pass arguments when possible, which is why generally you
478+don't explicitly define which `python` derivation should be used. In the above
479+example we use `buildPythonPackage` that is part of the set `python35Packages`,
480+and in this case the `python35` interpreter is automatically used.
481+
482+## Reference
483+
484+### Interpreters
485+
486+Versions 2.7, 3.5, 3.6 and 3.7 of the CPython interpreter are available as
487+respectively `python27`, `python35`, `python36`, and `python37`. The PyPy
488+interpreter is available as `pypy`. The aliases `python2` and `python3`
489+correspond to respectively `python27` and `python36`. The default interpreter,
490+`python`, maps to `python2`. The Nix expressions for the interpreters can be
491+found in `pkgs/development/interpreters/python`.
492+
493+All packages depending on any Python interpreter get appended
494+`out/{python.sitePackages}` to `$PYTHONPATH` if such directory
495+exists.
496+
497+#### Missing `tkinter` module standard library
498+
499+To reduce closure size the `Tkinter`/`tkinter` is available as a separate package, `pythonPackages.tkinter`.
500+
501+#### Attributes on interpreters packages
502+
503+Each interpreter has the following attributes:
504+
505+- `libPrefix`. Name of the folder in `${python}/lib/` for corresponding interpreter.
506+- `interpreter`. Alias for `${python}/bin/${executable}`.
507+- `buildEnv`. Function to build python interpreter environments with extra packages bundled together. See section *python.buildEnv function* for usage and documentation.
508+- `withPackages`. Simpler interface to `buildEnv`. See section *python.withPackages function* for usage and documentation.
509+- `sitePackages`. Alias for `lib/${libPrefix}/site-packages`.
510+- `executable`. Name of the interpreter executable, e.g. `python3.7`.
511+- `pkgs`. Set of Python packages for that specific interpreter. The package set can be modified by overriding the interpreter and passing `packageOverrides`.
512+
513+### Building packages and applications
514+
515+Python libraries and applications that use `setuptools` or
516+`distutils` are typically build with respectively the `buildPythonPackage` and
517+`buildPythonApplication` functions. These two functions also support installing a `wheel`.
518+
519+All Python packages reside in `pkgs/top-level/python-packages.nix` and all
520+applications elsewhere. In case a package is used as both a library and an application,
521+then the package should be in `pkgs/top-level/python-packages.nix` since only those packages are made
522+available for all interpreter versions. The preferred location for library expressions is in
523+`pkgs/development/python-modules`. It is important that these packages are
524+called from `pkgs/top-level/python-packages.nix` and not elsewhere, to guarantee
525+the right version of the package is built.
526+
527+Based on the packages defined in `pkgs/top-level/python-packages.nix` an
528+attribute set is created for each available Python interpreter. The available
529+sets are
530+
531+* `pkgs.python27Packages`
532+* `pkgs.python35Packages`
533+* `pkgs.python36Packages`
534+* `pkgs.python37Packages`
535+* `pkgs.pypyPackages`
536+
537+and the aliases
538+
539+* `pkgs.python2Packages` pointing to `pkgs.python27Packages`
540+* `pkgs.python3Packages` pointing to `pkgs.python36Packages`
541+* `pkgs.pythonPackages` pointing to `pkgs.python2Packages`
542+
543+#### `buildPythonPackage` function
544+
545+The `buildPythonPackage` function is implemented in
546+`pkgs/development/interpreters/python/build-python-package.nix`
547+
548+The following is an example:
549+```nix
550+{ lib, buildPythonPackage, fetchPypi, hypothesis, setuptools_scm, attrs, py, setuptools, six, pluggy }:
551+
552+buildPythonPackage rec {
553+ pname = "pytest";
554+ version = "3.3.1";
555+
556+ src = fetchPypi {
557+ inherit pname version;
558+ sha256 = "cf8436dc59d8695346fcd3ab296de46425ecab00d64096cebe79fb51ecb2eb93";
559+ };
560+
561+ postPatch = ''
562+ # don't test bash builtins
563+ rm testing/test_argcomplete.py
564+ '';
565+
566+ checkInputs = [ hypothesis ];
567+ buildInputs = [ setuptools_scm ];
568+ propagatedBuildInputs = [ attrs py setuptools six pluggy ];
569+
570+ meta = with lib; {
571+ maintainers = with maintainers; [ domenkozar lovek323 madjar lsix ];
572+ description = "Framework for writing tests";
573+ };
574+}
575+```
576+
577+The `buildPythonPackage` mainly does four things:
578+
579+* In the `buildPhase`, it calls `${python.interpreter} setup.py bdist_wheel` to
580+ build a wheel binary zipfile.
581+* In the `installPhase`, it installs the wheel file using `pip install *.whl`.
582+* In the `postFixup` phase, the `wrapPythonPrograms` bash function is called to
583+ wrap all programs in the `$out/bin/*` directory to include `$PATH`
584+ environment variable and add dependent libraries to script's `sys.path`.
585+* In the `installCheck` phase, `${python.interpreter} setup.py test` is ran.
586+
587+As in Perl, dependencies on other Python packages can be specified in the
588+`buildInputs` and `propagatedBuildInputs` attributes. If something is
589+exclusively a build-time dependency, use `buildInputs`; if it is (also) a runtime
590+dependency, use `propagatedBuildInputs`.
591+
592+By default tests are run because `doCheck = true`. Test dependencies, like
593+e.g. the test runner, should be added to `checkInputs`.
594+
595+By default `meta.platforms` is set to the same value
596+as the interpreter unless overridden otherwise.
597+
598+##### `buildPythonPackage` parameters
599+
600+All parameters from `stdenv.mkDerivation` function are still supported. The following are specific to `buildPythonPackage`:
601+
602+* `catchConflicts ? true`: If `true`, abort package build if a package name appears more than once in dependency tree. Default is `true`.
603+* `checkInputs ? []`: Dependencies needed for running the `checkPhase`. These are added to `buildInputs` when `doCheck = true`.
604+* `disabled` ? false: If `true`, package is not build for the particular Python interpreter version.
605+* `dontWrapPythonPrograms ? false`: Skip wrapping of python programs.
606+* `installFlags ? []`: A list of strings. Arguments to be passed to `pip install`. To pass options to `python setup.py install`, use `--install-option`. E.g., `installFlags=["--install-option='--cpp_implementation'"].
607+* `format ? "setuptools"`: Format of the source. Valid options are `"setuptools"`, `"flit"`, `"wheel"`, and `"other"`. `"setuptools"` is for when the source has a `setup.py` and `setuptools` is used to build a wheel, `flit`, in case `flit` should be used to build a wheel, and `wheel` in case a wheel is provided. Use `other` when a custom `buildPhase` and/or `installPhase` is needed.
608+* `makeWrapperArgs ? []`: A list of strings. Arguments to be passed to `makeWrapper`, which wraps generated binaries. By default, the arguments to `makeWrapper` set `PATH` and `PYTHONPATH` environment variables before calling the binary. Additional arguments here can allow a developer to set environment variables which will be available when the binary is run. For example, `makeWrapperArgs = ["--set FOO BAR" "--set BAZ QUX"]`.
609+* `namePrefix`: Prepends text to `${name}` parameter. In case of libraries, this defaults to `"python3.5-"` for Python 3.5, etc., and in case of applications to `""`.
610+* `pythonPath ? []`: List of packages to be added into `$PYTHONPATH`. Packages in `pythonPath` are not propagated (contrary to `propagatedBuildInputs`).
611+* `preShellHook`: Hook to execute commands before `shellHook`.
612+* `postShellHook`: Hook to execute commands after `shellHook`.
613+* `removeBinByteCode ? true`: Remove bytecode from `/bin`. Bytecode is only created when the filenames end with `.py`.
614+* `setupPyBuildFlags ? []`: List of flags passed to `setup.py build_ext` command.
615+
616+##### Overriding Python packages
617+
618+The `buildPythonPackage` function has a `overridePythonAttrs` method that
619+can be used to override the package. In the following example we create an
620+environment where we have the `blaze` package using an older version of `pandas`.
621+We override first the Python interpreter and pass
622+`packageOverrides` which contains the overrides for packages in the package set.
623+
624+```nix
625+with import <nixpkgs> {};
626+
627+(let
628+ python = let
629+ packageOverrides = self: super: {
630+ pandas = super.pandas.overridePythonAttrs(old: rec {
631+ version = "0.19.1";
632+ src = super.fetchPypi {
633+ pname = "pandas";
634+ inherit version;
635+ sha256 = "08blshqj9zj1wyjhhw3kl2vas75vhhicvv72flvf1z3jvapgw295";
636+ };
637+ });
638+ };
639+ in pkgs.python3.override {inherit packageOverrides;};
640+
641+in python.withPackages(ps: [ps.blaze])).env
642+```
643+
644+#### `buildPythonApplication` function
645+
646+The `buildPythonApplication` function is practically the same as
647+`buildPythonPackage`. The main purpose of this function is to build a Python
648+package where one is interested only in the executables, and not importable
649+modules. For that reason, when adding this package to a `python.buildEnv`, the
650+modules won't be made available.
651+
652+Another difference is that `buildPythonPackage` by default prefixes the names of
653+the packages with the version of the interpreter. Because this is irrelevant for
654+applications, the prefix is omitted.
655+
656+When packaging a python application with `buildPythonApplication`, it should be
657+called with `callPackage` and passed `python` or `pythonPackages` (possibly
658+specifying an interpreter version), like this:
659+
660+```nix
661+{ lib, python3Packages }:
662+
663+python3Packages.buildPythonApplication rec {
664+ pname = "luigi";
665+ version = "2.7.9";
666+
667+ src = python3Packages.fetchPypi {
668+ inherit pname version;
669+ sha256 = "035w8gqql36zlan0xjrzz9j4lh9hs0qrsgnbyw07qs7lnkvbdv9x";
670+ };
671+
672+ propagatedBuildInputs = with python3Packages; [ tornado_4 python-daemon ];
673+
674+ meta = with lib; {
675+ ...
676+ };
677+}
678+```
679+
680+This is then added to `all-packages.nix` just as any other application would be.
681+
682+```nix
683+luigi = callPackage ../applications/networking/cluster/luigi { };
684+```
685+
686+Since the package is an application, a consumer doesn't need to care about
687+python versions or modules, which is why they don't go in `pythonPackages`.
688+
689+#### `toPythonApplication` function
690+
691+A distinction is made between applications and libraries, however, sometimes a
692+package is used as both. In this case the package is added as a library to
693+`python-packages.nix` and as an application to `all-packages.nix`. To reduce
694+duplication the `toPythonApplication` can be used to convert a library to an
695+application.
696+
697+The Nix expression shall use `buildPythonPackage` and be called from
698+`python-packages.nix`. A reference shall be created from `all-packages.nix` to
699+the attribute in `python-packages.nix`, and the `toPythonApplication` shall be
700+applied to the reference:
701+```nix
702+youtube-dl = with pythonPackages; toPythonApplication youtube-dl;
703+```
704+
705+#### `toPythonModule` function
706+
707+In some cases, such as bindings, a package is created using
708+`stdenv.mkDerivation` and added as attribute in `all-packages.nix`.
709+The Python bindings should be made available from `python-packages.nix`.
710+The `toPythonModule` function takes a derivation and makes certain Python-specific modifications.
711+```nix
712+opencv = toPythonModule (pkgs.opencv.override {
713+ enablePython = true;
714+ pythonPackages = self;
715+});
716+```
717+Do pay attention to passing in the right Python version!
718+
719+#### `python.buildEnv` function
720+
721+Python environments can be created using the low-level `pkgs.buildEnv` function.
722+This example shows how to create an environment that has the Pyramid Web Framework.
723+Saving the following as `default.nix`
724+```nix
725+with import <nixpkgs> {};
726+
727+python.buildEnv.override {
728+ extraLibs = [ pkgs.pythonPackages.pyramid ];
729+ ignoreCollisions = true;
730+}
731+```
732+
733+and running `nix-build` will create
734+```
735+/nix/store/cf1xhjwzmdki7fasgr4kz6di72ykicl5-python-2.7.8-env
736+```
737+
738+with wrapped binaries in `bin/`.
739+
740+You can also use the `env` attribute to create local environments with needed
741+packages installed. This is somewhat comparable to `virtualenv`. For example,
742+running `nix-shell` with the following `shell.nix`
743+```nix
744+with import <nixpkgs> {};
745+
746+(python3.buildEnv.override {
747+ extraLibs = with python3Packages; [ numpy requests ];
748+}).env
749+```
750+
751+will drop you into a shell where Python will have the
752+specified packages in its path.
753+
754+
755+##### `python.buildEnv` arguments
756+
757+* `extraLibs`: List of packages installed inside the environment.
758+* `postBuild`: Shell command executed after the build of environment.
759+* `ignoreCollisions`: Ignore file collisions inside the environment (default is `false`).
760+
761+#### `python.withPackages` function
762+
763+The `python.withPackages` function provides a simpler interface to the `python.buildEnv` functionality.
764+It takes a function as an argument that is passed the set of python packages and returns the list
765+of the packages to be included in the environment. Using the `withPackages` function, the previous
766+example for the Pyramid Web Framework environment can be written like this:
767+```nix
768+with import <nixpkgs> {};
769+
770+python.withPackages (ps: [ps.pyramid])
771+```
772+
773+`withPackages` passes the correct package set for the specific interpreter version as an
774+argument to the function. In the above example, `ps` equals `pythonPackages`.
775+But you can also easily switch to using python3:
776+```nix
777+with import <nixpkgs> {};
778+
779+python3.withPackages (ps: [ps.pyramid])
780+```
781+
782+Now, `ps` is set to `python3Packages`, matching the version of the interpreter.
783+
784+As `python.withPackages` simply uses `python.buildEnv` under the hood, it also supports the `env`
785+attribute. The `shell.nix` file from the previous section can thus be also written like this:
786+```nix
787+with import <nixpkgs> {};
788+
789+(python36.withPackages (ps: [ps.numpy ps.requests])).env
790+```
791+
792+In contrast to `python.buildEnv`, `python.withPackages` does not support the more advanced options
793+such as `ignoreCollisions = true` or `postBuild`. If you need them, you have to use `python.buildEnv`.
794+
795+Python 2 namespace packages may provide `__init__.py` that collide. In that case `python.buildEnv`
796+should be used with `ignoreCollisions = true`.
797+
798+### Development mode
799+
800+Development or editable mode is supported. To develop Python packages
801+`buildPythonPackage` has additional logic inside `shellPhase` to run `pip
802+install -e . --prefix $TMPDIR/`for the package.
803+
804+Warning: `shellPhase` is executed only if `setup.py` exists.
805+
806+Given a `default.nix`:
807+```nix
808+with import <nixpkgs> {};
809+
810+buildPythonPackage { name = "myproject";
811+
812+buildInputs = with pkgs.pythonPackages; [ pyramid ];
813+
814+src = ./.; }
815+```
816+
817+Running `nix-shell` with no arguments should give you
818+the environment in which the package would be built with
819+`nix-build`.
820+
821+Shortcut to setup environments with C headers/libraries and python packages:
822+```shell
823+nix-shell -p pythonPackages.pyramid zlib libjpeg git
824+```
825+
826+Note: There is a boolean value `lib.inNixShell` set to `true` if nix-shell is invoked.
827+
828+### Tools
829+
830+Packages inside nixpkgs are written by hand. However many tools exist in
831+community to help save time. No tool is preferred at the moment.
832+
833+- [python2nix](https://github.com/proger/python2nix) by Vladimir Kirillov
834+- [pypi2nix](https://github.com/garbas/pypi2nix) by Rok Garbas
835+- [pypi2nix](https://github.com/offlinehacker/pypi2nix) by Jaka Hudoklin
836+
837+### Deterministic builds
838+
839+The Python interpreters are now built deterministically.
840+Minor modifications had to be made to the interpreters in order to generate
841+deterministic bytecode. This has security implications and is relevant for
842+those using Python in a `nix-shell`.
843+
844+When the environment variable `DETERMINISTIC_BUILD` is set, all bytecode will have timestamp 1.
845+The `buildPythonPackage` function sets `DETERMINISTIC_BUILD=1` and
846+[PYTHONHASHSEED=0](https://docs.python.org/3.5/using/cmdline.html#envvar-PYTHONHASHSEED).
847+Both are also exported in `nix-shell`.
848+
849+
850+### Automatic tests
851+
852+It is recommended to test packages as part of the build process.
853+Source distributions (`sdist`) often include test files, but not always.
854+
855+By default the command `python setup.py test` is run as part of the
856+`checkPhase`, but often it is necessary to pass a custom `checkPhase`. An
857+example of such a situation is when `py.test` is used.
858+
859+#### Common issues
860+
861+- Non-working tests can often be deselected. By default `buildPythonPackage` runs `python setup.py test`.
862+ Most python modules follows the standard test protocol where the pytest runner can be used instead.
863+ `py.test` supports a `-k` parameter to ignore test methods or classes:
864+
865+ ```nix
866+ buildPythonPackage {
867+ # ...
868+ # assumes the tests are located in tests
869+ checkInputs = [ pytest ];
870+ checkPhase = ''
871+ py.test -k 'not function_name and not other_function' tests
872+ '';
873+ }
874+ ```
875+- Unicode issues can typically be fixed by including `glibcLocales` in `buildInputs` and exporting `LC_ALL=en_US.utf-8`.
876+- Tests that attempt to access `$HOME` can be fixed by using the following work-around before running tests (e.g. `preCheck`): `export HOME=$(mktemp -d)`
877+
878+## FAQ
879+
880+### How to solve circular dependencies?
881+
882+Consider the packages `A` and `B` that depend on each other. When packaging `B`,
883+a solution is to override package `A` not to depend on `B` as an input. The same
884+should also be done when packaging `A`.
885+
886+### How to override a Python package?
887+
888+We can override the interpreter and pass `packageOverrides`.
889+In the following example we rename the `pandas` package and build it.
890+```nix
891+with import <nixpkgs> {};
892+
893+(let
894+ python = let
895+ packageOverrides = self: super: {
896+ pandas = super.pandas.overridePythonAttrs(old: {name="foo";});
897+ };
898+ in pkgs.python35.override {inherit packageOverrides;};
899+
900+in python.withPackages(ps: [ps.pandas])).env
901+```
902+Using `nix-build` on this expression will build an environment that contains the
903+package `pandas` but with the new name `foo`.
904+
905+All packages in the package set will use the renamed package.
906+A typical use case is to switch to another version of a certain package.
907+For example, in the Nixpkgs repository we have multiple versions of `django` and `scipy`.
908+In the following example we use a different version of `scipy` and create an environment that uses it.
909+All packages in the Python package set will now use the updated `scipy` version.
910+
911+```nix
912+with import <nixpkgs> {};
913+
914+( let
915+ packageOverrides = self: super: {
916+ scipy = super.scipy_0_17;
917+ };
918+ in (pkgs.python35.override {inherit packageOverrides;}).withPackages (ps: [ps.blaze])
919+).env
920+```
921+The requested package `blaze` depends on `pandas` which itself depends on `scipy`.
922+
923+If you want the whole of Nixpkgs to use your modifications, then you can use `overlays`
924+as explained in this manual. In the following example we build a `inkscape` using a different version of `numpy`.
925+```nix
926+let
927+ pkgs = import <nixpkgs> {};
928+ newpkgs = import pkgs.path { overlays = [ (pkgsself: pkgssuper: {
929+ python27 = let
930+ packageOverrides = self: super: {
931+ numpy = super.numpy_1_10;
932+ };
933+ in pkgssuper.python27.override {inherit packageOverrides;};
934+ } ) ]; };
935+in newpkgs.inkscape
936+```
937+
938+### `python setup.py bdist_wheel` cannot create .whl
939+
940+Executing `python setup.py bdist_wheel` in a `nix-shell `fails with
941+```
942+ValueError: ZIP does not support timestamps before 1980
943+```
944+
945+This is because files from the Nix store (which have a timestamp of the UNIX epoch of January 1, 1970) are included in the .ZIP, but .ZIP archives follow the DOS convention of counting timestamps from 1980.
946+
947+The command `bdist_wheel` reads the `SOURCE_DATE_EPOCH` environment variable, which `nix-shell` sets to 1. Unsetting this variable or giving it a value corresponding to 1980 or later enables building wheels.
948+
949+Use 1980 as timestamp:
950+```shell
951+nix-shell --run "SOURCE_DATE_EPOCH=315532800 python3 setup.py bdist_wheel"
952+```
953+or the current time:
954+```shell
955+nix-shell --run "SOURCE_DATE_EPOCH=$(date +%s) python3 setup.py bdist_wheel"
956+```
957+or unset `SOURCE_DATE_EPOCH`:
958+```shell
959+nix-shell --run "unset SOURCE_DATE_EPOCH; python3 setup.py bdist_wheel"
960+```
961+
962+### `install_data` / `data_files` problems
963+
964+If you get the following error:
965+```
966+could not create '/nix/store/6l1bvljpy8gazlsw2aw9skwwp4pmvyxw-python-2.7.8/etc':
967+Permission denied
968+```
969+This is a [known bug](https://github.com/pypa/setuptools/issues/130) in `setuptools`.
970+Setuptools `install_data` does not respect `--prefix`. An example of such package using the feature is `pkgs/tools/X11/xpra/default.nix`.
971+As workaround install it as an extra `preInstall` step:
972+```shell
973+${python.interpreter} setup.py install_data --install-dir=$out --root=$out
974+sed -i '/ = data\_files/d' setup.py
975+```
976+
977+### Rationale of non-existent global site-packages
978+
979+On most operating systems a global `site-packages` is maintained. This however
980+becomes problematic if you want to run multiple Python versions or have multiple
981+versions of certain libraries for your projects. Generally, you would solve such
982+issues by creating virtual environments using `virtualenv`.
983+
984+On Nix each package has an isolated dependency tree which, in the case of
985+Python, guarantees the right versions of the interpreter and libraries or
986+packages are available. There is therefore no need to maintain a global `site-packages`.
987+
988+If you want to create a Python environment for development, then the recommended
989+method is to use `nix-shell`, either with or without the `python.buildEnv`
990+function.
991+
992+### How to consume python modules using pip in a virtualenv like I am used to on other Operating Systems ?
993+
994+This is an example of a `default.nix` for a `nix-shell`, which allows to consume a `virtualenv` environment,
995+and install python modules through `pip` the traditional way.
996+
997+Create this `default.nix` file, together with a `requirements.txt` and simply execute `nix-shell`.
998+
999+```nix
1000+with import <nixpkgs> {};
1001+with pkgs.python27Packages;
1002+
1003+stdenv.mkDerivation {
1004+ name = "impurePythonEnv";
1005+ buildInputs = [
1006+ # these packages are required for virtualenv and pip to work:
1007+ #
1008+ python27Full
1009+ python27Packages.virtualenv
1010+ python27Packages.pip
1011+ # the following packages are related to the dependencies of your python
1012+ # project.
1013+ # In this particular example the python modules listed in the
1014+ # requirements.txt require the following packages to be installed locally
1015+ # in order to compile any binary extensions they may require.
1016+ #
1017+ taglib
1018+ openssl
1019+ git
1020+ libxml2
1021+ libxslt
1022+ libzip
1023+ stdenv
1024+ zlib ];
1025+ src = null;
1026+ shellHook = ''
1027+ # set SOURCE_DATE_EPOCH so that we can use python wheels
1028+ SOURCE_DATE_EPOCH=$(date +%s)
1029+ virtualenv --no-setuptools venv
1030+ export PATH=$PWD/venv/bin:$PATH
1031+ pip install -r requirements.txt
1032+ '';
1033+}
1034+```
1035+
1036+Note that the `pip install` is an imperative action. So every time `nix-shell`
1037+is executed it will attempt to download the python modules listed in
1038+requirements.txt. However these will be cached locally within the `virtualenv`
1039+folder and not downloaded again.
1040+
1041+### How to override a Python package from `configuration.nix`?
1042+
1043+If you need to change a package's attribute(s) from `configuration.nix` you could do:
1044+
1045+```nix
1046+ nixpkgs.config.packageOverrides = super: {
1047+ python = super.python.override {
1048+ packageOverrides = python-self: python-super: {
1049+ zerobin = python-super.zerobin.overrideAttrs (oldAttrs: {
1050+ src = super.fetchgit {
1051+ url = "https://github.com/sametmax/0bin";
1052+ rev = "a344dbb18fe7a855d0742b9a1cede7ce423b34ec";
1053+ sha256 = "16d769kmnrpbdr0ph0whyf4yff5df6zi4kmwx7sz1d3r6c8p6xji";
1054+ };
1055+ });
1056+ };
1057+ };
1058+ };
1059+```
1060+
1061+`pythonPackages.zerobin` is now globally overridden. All packages and also the
1062+`zerobin` NixOS service use the new definition.
1063+Note that `python-super` refers to the old package set and `python-self`
1064+to the new, overridden version.
1065+
1066+To modify only a Python package set instead of a whole Python derivation, use this snippet:
1067+
1068+```nix
1069+ myPythonPackages = pythonPackages.override {
1070+ overrides = self: super: {
1071+ zerobin = ...;
1072+ };
1073+ }
1074+```
1075+
1076+### How to override a Python package using overlays?
1077+
1078+Use the following overlay template:
1079+
1080+```nix
1081+self: super:
1082+{
1083+ python = super.python.override {
1084+ packageOverrides = python-self: python-super: {
1085+ zerobin = python-super.zerobin.overrideAttrs (oldAttrs: {
1086+ src = super.fetchgit {
1087+ url = "https://github.com/sametmax/0bin";
1088+ rev = "a344dbb18fe7a855d0742b9a1cede7ce423b34ec";
1089+ sha256 = "16d769kmnrpbdr0ph0whyf4yff5df6zi4kmwx7sz1d3r6c8p6xji";
1090+ };
1091+ });
1092+ };
1093+ };
1094+}
1095+```
1096+
1097+## Contributing
1098+
1099+### Contributing guidelines
1100+
1101+Following rules are desired to be respected:
1102+
1103+* Python libraries are called from `python-packages.nix` and packaged with `buildPythonPackage`. The expression of a library should be in `pkgs/development/python-modules/<name>/default.nix`. Libraries in `pkgs/top-level/python-packages.nix` are sorted quasi-alphabetically to avoid merge conflicts.
1104+* Python applications live outside of `python-packages.nix` and are packaged with `buildPythonApplication`.
1105+* Make sure libraries build for all Python interpreters.
1106+* By default we enable tests. Make sure the tests are found and, in the case of libraries, are passing for all interpreters. If certain tests fail they can be disabled individually. Try to avoid disabling the tests altogether. In any case, when you disable tests, leave a comment explaining why.
1107+* Commit names of Python libraries should reflect that they are Python libraries, so write for example `pythonPackages.numpy: 1.11 -> 1.12`.
1108+* Attribute names in `python-packages.nix` should be normalized according to [PEP 0503](https://www.python.org/dev/peps/pep-0503/#normalized-names).
1109+ This means that characters should be converted to lowercase and `.` and `_` should be replaced by a single `-` (foo-bar-baz instead of Foo__Bar.baz )
doc/languages-frameworks/qt.xml+62−46
@@ -1,58 +1,74 @@
11<section xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="sec-language-qt">
4+ <title>Qt</title>
45
5−<title>Qt</title>
6−
7−<para>
8−Qt is a comprehensive desktop and mobile application development toolkit for C++.
9−Legacy support is available for Qt 3 and Qt 4, but all current development uses Qt 5.
10−The Qt 5 packages in Nixpkgs are updated frequently to take advantage of new features,
11−but older versions are typically retained until their support window ends.
12−The most important consideration in packaging Qt-based software is ensuring that each package and all its dependencies use the same version of Qt 5;
13−this consideration motivates most of the tools described below.
14−</para>
15−
16−<section xml:id="ssec-qt-libraries"><title>Packaging Libraries for Nixpkgs</title>
17−
18−<para>
19−Whenever possible, libraries that use Qt 5 should be built with each available version.
20−Packages providing libraries should be added to the top-level function <varname>mkLibsForQt5</varname>,
21−which is used to build a set of libraries for every Qt 5 version.
22−A special <varname>callPackage</varname> function is used in this scope to ensure that the entire dependency tree uses the same Qt 5 version.
23−Import dependencies unqualified, i.e., <literal>qtbase</literal> not <literal>qt5.qtbase</literal>.
24−<emphasis>Do not</emphasis> import a package set such as <literal>qt5</literal> or <literal>libsForQt5</literal>.
25−</para>
26−
27−<para>
28−If a library does not support a particular version of Qt 5, it is best to mark it as broken by setting its <literal>meta.broken</literal> attribute.
29−A package may be marked broken for certain versions by testing the <literal>qtbase.version</literal> attribute, which will always give the current Qt 5 version.
30−</para>
6+ <para>
7+ Qt is a comprehensive desktop and mobile application development toolkit for
8+ C++. Legacy support is available for Qt 3 and Qt 4, but all current
9+ development uses Qt 5. The Qt 5 packages in Nixpkgs are updated frequently to
10+ take advantage of new features, but older versions are typically retained
11+ until their support window ends. The most important consideration in
12+ packaging Qt-based software is ensuring that each package and all its
13+ dependencies use the same version of Qt 5; this consideration motivates most
14+ of the tools described below.
15+ </para>
3116
32−</section>
17+ <section xml:id="ssec-qt-libraries">
18+ <title>Packaging Libraries for Nixpkgs</title>
3319
34−<section xml:id="ssec-qt-applications"><title>Packaging Applications for Nixpkgs</title>
20+ <para>
21+ Whenever possible, libraries that use Qt 5 should be built with each
22+ available version. Packages providing libraries should be added to the
23+ top-level function <varname>mkLibsForQt5</varname>, which is used to build a
24+ set of libraries for every Qt 5 version. A special
25+ <varname>callPackage</varname> function is used in this scope to ensure that
26+ the entire dependency tree uses the same Qt 5 version. Import dependencies
27+ unqualified, i.e., <literal>qtbase</literal> not
28+ <literal>qt5.qtbase</literal>. <emphasis>Do not</emphasis> import a package
29+ set such as <literal>qt5</literal> or <literal>libsForQt5</literal>.
30+ </para>
3531
36−<para>
37−Call your application expression using <literal>libsForQt5.callPackage</literal> instead of <literal>callPackage</literal>.
38−Import dependencies unqualified, i.e., <literal>qtbase</literal> not <literal>qt5.qtbase</literal>.
39−<emphasis>Do not</emphasis> import a package set such as <literal>qt5</literal> or <literal>libsForQt5</literal>.
40−</para>
32+ <para>
33+ If a library does not support a particular version of Qt 5, it is best to
34+ mark it as broken by setting its <literal>meta.broken</literal> attribute. A
35+ package may be marked broken for certain versions by testing the
36+ <literal>qtbase.version</literal> attribute, which will always give the
37+ current Qt 5 version.
38+ </para>
39+ </section>
4140
42−<para>
43−Qt 5 maintains strict backward compatibility, so it is generally best to build an application package against the latest version using the <varname>libsForQt5</varname> library set.
44−In case a package does not build with the latest Qt version, it is possible to pick a set pinned to a particular version, e.g. <varname>libsForQt55</varname> for Qt 5.5, if that is the latest version the package supports.
45−If a package must be pinned to an older Qt version, be sure to file a bug upstream;
46−because Qt is strictly backwards-compatible, any incompatibility is by definition a bug in the application.
47−</para>
41+ <section xml:id="ssec-qt-applications">
42+ <title>Packaging Applications for Nixpkgs</title>
4843
49−<para>
50−When testing applications in Nixpkgs, it is a common practice to build the package with <literal>nix-build</literal> and run it using the created symbolic link.
51−This will not work with Qt applications, however, because they have many hard runtime requirements that can only be guaranteed if the package is actually installed.
52−To test a Qt application, install it with <literal>nix-env</literal> or run it inside <literal>nix-shell</literal>.
53−</para>
44+ <para>
45+ Call your application expression using
46+ <literal>libsForQt5.callPackage</literal> instead of
47+ <literal>callPackage</literal>. Import dependencies unqualified, i.e.,
48+ <literal>qtbase</literal> not <literal>qt5.qtbase</literal>. <emphasis>Do
49+ not</emphasis> import a package set such as <literal>qt5</literal> or
50+ <literal>libsForQt5</literal>.
51+ </para>
5452
55−</section>
53+ <para>
54+ Qt 5 maintains strict backward compatibility, so it is generally best to
55+ build an application package against the latest version using the
56+ <varname>libsForQt5</varname> library set. In case a package does not build
57+ with the latest Qt version, it is possible to pick a set pinned to a
58+ particular version, e.g. <varname>libsForQt55</varname> for Qt 5.5, if that
59+ is the latest version the package supports. If a package must be pinned to
60+ an older Qt version, be sure to file a bug upstream; because Qt is strictly
61+ backwards-compatible, any incompatibility is by definition a bug in the
62+ application.
63+ </para>
5664
65+ <para>
66+ When testing applications in Nixpkgs, it is a common practice to build the
67+ package with <literal>nix-build</literal> and run it using the created
68+ symbolic link. This will not work with Qt applications, however, because
69+ they have many hard runtime requirements that can only be guaranteed if the
70+ package is actually installed. To test a Qt application, install it with
71+ <literal>nix-env</literal> or run it inside <literal>nix-shell</literal>.
72+ </para>
73+ </section>
5774</section>
58−
doc/languages-frameworks/r.section.mdnew file+120
@@ -0,0 +1,120 @@
1+R packages
2+==========
3+
4+## Installation
5+
6+Define an environment for R that contains all the libraries that you'd like to
7+use by adding the following snippet to your $HOME/.config/nixpkgs/config.nix file:
8+
9+```nix
10+{
11+ packageOverrides = super: let self = super.pkgs; in
12+ {
13+
14+ rEnv = super.rWrapper.override {
15+ packages = with self.rPackages; [
16+ devtools
17+ ggplot2
18+ reshape2
19+ yaml
20+ optparse
21+ ];
22+ };
23+ };
24+}
25+```
26+
27+Then you can use `nix-env -f "<nixpkgs>" -iA rEnv` to install it into your user
28+profile. The set of available libraries can be discovered by running the
29+command `nix-env -f "<nixpkgs>" -qaP -A rPackages`. The first column from that
30+output is the name that has to be passed to rWrapper in the code snipped above.
31+
32+However, if you'd like to add a file to your project source to make the
33+environment available for other contributors, you can create a `default.nix`
34+file like so:
35+```nix
36+let
37+ pkgs = import <nixpkgs> {};
38+ stdenv = pkgs.stdenv;
39+in with pkgs; {
40+ myProject = stdenv.mkDerivation {
41+ name = "myProject";
42+ version = "1";
43+ src = if pkgs.lib.inNixShell then null else nix;
44+
45+ buildInputs = with rPackages; [
46+ R
47+ ggplot2
48+ knitr
49+ ];
50+ };
51+}
52+```
53+and then run `nix-shell .` to be dropped into a shell with those packages
54+available.
55+
56+## RStudio
57+
58+RStudio uses a standard set of packages and ignores any custom R
59+environments or installed packages you may have. To create a custom
60+environment, see `rstudioWrapper`, which functions similarly to
61+`rWrapper`:
62+
63+```nix
64+{
65+ packageOverrides = super: let self = super.pkgs; in
66+ {
67+
68+ rstudioEnv = super.rstudioWrapper.override {
69+ packages = with self.rPackages; [
70+ dplyr
71+ ggplot2
72+ reshape2
73+ ];
74+ };
75+ };
76+}
77+```
78+
79+Then like above, `nix-env -f "<nixpkgs>" -iA rstudioEnv` will install
80+this into your user profile.
81+
82+Alternatively, you can create a self-contained `shell.nix` without the need to
83+modify any configuration files:
84+
85+```nix
86+{ pkgs ? import <nixpkgs> {}
87+}:
88+
89+pkgs.rstudioWrapper.override {
90+ packages = with pkgs.rPackages; [ dplyr ggplot2 reshape2 ];
91+}
92+
93+```
94+
95+Executing `nix-shell` will then drop you into an environment equivalent to the
96+one above. If you need additional packages just add them to the list and
97+re-enter the shell.
98+
99+## Updating the package set
100+
101+```bash
102+nix-shell generate-shell.nix
103+
104+Rscript generate-r-packages.R cran > cran-packages.nix.new
105+mv cran-packages.nix.new cran-packages.nix
106+
107+Rscript generate-r-packages.R bioc > bioc-packages.nix.new
108+mv bioc-packages.nix.new bioc-packages.nix
109+```
110+
111+`generate-r-packages.R <repo>` reads `<repo>-packages.nix`, therefor the renaming.
112+
113+
114+## Testing if the Nix-expression could be evaluated
115+
116+```bash
117+nix-build test-evaluation.nix --dry-run
118+```
119+
120+If this exits fine, the expression is ok. If not, you have to edit `default.nix`
doc/languages-frameworks/ruby.xml+47−45
@@ -1,17 +1,19 @@
11<section xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="sec-language-ruby">
4+ <title>Ruby</title>
45
5−<title>Ruby</title>
6+ <para>
7+ There currently is support to bundle applications that are packaged as Ruby
8+ gems. The utility "bundix" allows you to write a
9+ <filename>Gemfile</filename>, let bundler create a
10+ <filename>Gemfile.lock</filename>, and then convert this into a nix
11+ expression that contains all Gem dependencies automatically.
12+ </para>
613
7−<para>There currently is support to bundle applications that are packaged as
8−Ruby gems. The utility "bundix" allows you to write a
9−<filename>Gemfile</filename>, let bundler create a
10−<filename>Gemfile.lock</filename>, and then convert this into a nix
11−expression that contains all Gem dependencies automatically.
12−</para>
13−
14−<para>For example, to package sensu, we did:</para>
14+ <para>
15+ For example, to package sensu, we did:
16+ </para>
1517
1618<screen>
1719<![CDATA[$ cd pkgs/servers/monitoring
@@ -42,17 +44,18 @@ bundlerEnv rec {
4244}]]>
4345</screen>
4446
45−<para>Please check in the <filename>Gemfile</filename>,
46−<filename>Gemfile.lock</filename> and the
47−<filename>gemset.nix</filename> so future updates can be run easily.
48−</para>
47+ <para>
48+ Please check in the <filename>Gemfile</filename>,
49+ <filename>Gemfile.lock</filename> and the <filename>gemset.nix</filename> so
50+ future updates can be run easily.
51+ </para>
4952
50−<para>For tools written in Ruby - i.e. where the desire is to install
51−a package and then execute e.g. <command>rake</command> at the command
52−line, there is an alternative builder called <literal>bundlerApp</literal>.
53−Set up the <filename>gemset.nix</filename> the same way, and then, for
54−example:
55−</para>
53+ <para>
54+ For tools written in Ruby - i.e. where the desire is to install a package and
55+ then execute e.g. <command>rake</command> at the command line, there is an
56+ alternative builder called <literal>bundlerApp</literal>. Set up the
57+ <filename>gemset.nix</filename> the same way, and then, for example:
58+ </para>
5659
5760<screen>
5861<![CDATA[{ lib, bundlerApp }:
@@ -72,31 +75,31 @@ bundlerApp {
7275}]]>
7376</screen>
7477
75−<para>The chief advantage of <literal>bundlerApp</literal> over
76−<literal>bundlerEnv</literal> is the executables introduced in the
77−environment are precisely those selected in the <literal>exes</literal>
78−list, as opposed to <literal>bundlerEnv</literal> which adds all the
79−executables made available by gems in the gemset, which can mean e.g.
80−<command>rspec</command> or <command>rake</command> in unpredictable
81−versions available from various packages.
82−</para>
83−
84−<para>Resulting derivations for both builders also have two helpful
85−attributes, <literal>env</literal> and <literal>wrappedRuby</literal>.
86−The first one allows one to quickly drop into
87−<command>nix-shell</command> with the specified environment present.
88−E.g. <command>nix-shell -A sensu.env</command> would give you an
89−environment with Ruby preset so it has all the libraries necessary
90−for <literal>sensu</literal> in its paths. The second one can be
91−used to make derivations from custom Ruby scripts which have
92−<filename>Gemfile</filename>s with their dependencies specified. It is
93−a derivation with <command>ruby</command> wrapped so it can find all
94−the needed dependencies. For example, to make a derivation
95−<literal>my-script</literal> for a <filename>my-script.rb</filename>
96−(which should be placed in <filename>bin</filename>) you should run
97−<command>bundix</command> as specified above and then use
98−<literal>bundlerEnv</literal> like this:
99−</para>
78+ <para>
79+ The chief advantage of <literal>bundlerApp</literal> over
80+ <literal>bundlerEnv</literal> is the executables introduced in the
81+ environment are precisely those selected in the <literal>exes</literal> list,
82+ as opposed to <literal>bundlerEnv</literal> which adds all the executables
83+ made available by gems in the gemset, which can mean e.g.
84+ <command>rspec</command> or <command>rake</command> in unpredictable versions
85+ available from various packages.
86+ </para>
87+
88+ <para>
89+ Resulting derivations for both builders also have two helpful attributes,
90+ <literal>env</literal> and <literal>wrappedRuby</literal>. The first one
91+ allows one to quickly drop into <command>nix-shell</command> with the
92+ specified environment present. E.g. <command>nix-shell -A sensu.env</command>
93+ would give you an environment with Ruby preset so it has all the libraries
94+ necessary for <literal>sensu</literal> in its paths. The second one can be
95+ used to make derivations from custom Ruby scripts which have
96+ <filename>Gemfile</filename>s with their dependencies specified. It is a
97+ derivation with <command>ruby</command> wrapped so it can find all the needed
98+ dependencies. For example, to make a derivation <literal>my-script</literal>
99+ for a <filename>my-script.rb</filename> (which should be placed in
100+ <filename>bin</filename>) you should run <command>bundix</command> as
101+ specified above and then use <literal>bundlerEnv</literal> like this:
102+ </para>
100103
101104<programlisting>
102105<![CDATA[let env = bundlerEnv {
@@ -118,5 +121,4 @@ in stdenv.mkDerivation {
118121 '';
119122}]]>
120123</programlisting>
121−
122124</section>
doc/languages-frameworks/rust.mddeleted−309
@@ -1,309 +0,0 @@
1−---
2−title: Rust
3−author: Matthias Beyer
4−date: 2017-03-05
5−---
6−
7−# User's Guide to the Rust Infrastructure
8−
9−To install the rust compiler and cargo put
10−
11−```
12−rustc
13−cargo
14−```
15−
16−into the `environment.systemPackages` or bring them into
17−scope with `nix-shell -p rustc cargo`.
18−
19−For daily builds (beta and nightly) use either rustup from
20−nixpkgs or use the [Rust nightlies
21−overlay](#using-the-rust-nightlies-overlay).
22−
23−## Compiling Rust applications with Cargo
24−
25−Rust applications are packaged by using the `buildRustPackage` helper from `rustPlatform`:
26−
27−```
28−rustPlatform.buildRustPackage rec {
29− name = "ripgrep-${version}";
30− version = "0.4.0";
31−
32− src = fetchFromGitHub {
33− owner = "BurntSushi";
34− repo = "ripgrep";
35− rev = "${version}";
36− sha256 = "0y5d1n6hkw85jb3rblcxqas2fp82h3nghssa4xqrhqnz25l799pj";
37− };
38−
39− cargoSha256 = "0q68qyl2h6i0qsz82z840myxlnjay8p1w5z7hfyr8fqp7wgwa9cx";
40−
41− meta = with stdenv.lib; {
42− description = "A fast line-oriented regex search tool, similar to ag and ack";
43− homepage = https://github.com/BurntSushi/ripgrep;
44− license = licenses.unlicense;
45− maintainers = [ maintainers.tailhook ];
46− platforms = platforms.all;
47− };
48−}
49−```
50−
51−`buildRustPackage` requires a `cargoSha256` attribute which is computed over
52−all crate sources of this package. Currently it is obtained by inserting a
53−fake checksum into the expression and building the package once. The correct
54−checksum can be then take from the failed build.
55−
56−To install crates with nix there is also an experimental project called
57−[nixcrates](https://github.com/fractalide/nixcrates).
58−
59−## Compiling Rust crates using Nix instead of Cargo
60−
61−### Simple operation
62−
63−When run, `cargo build` produces a file called `Cargo.lock`,
64−containing pinned versions of all dependencies. Nixpkgs contains a
65−tool called `carnix` (`nix-env -iA nixos.carnix`), which can be used
66−to turn a `Cargo.lock` into a Nix expression.
67−
68−That Nix expression calls `rustc` directly (hence bypassing Cargo),
69−and can be used to compile a crate and all its dependencies. Here is
70−an example for a minimal `hello` crate:
71−
72−
73− $ cargo new hello
74− $ cd hello
75− $ cargo build
76− Compiling hello v0.1.0 (file:///tmp/hello)
77− Finished dev [unoptimized + debuginfo] target(s) in 0.20 secs
78− $ carnix -o hello.nix --src ./. Cargo.lock --standalone
79− $ nix-build hello.nix
80−
81−Now, the file produced by the call to `carnix`, called `hello.nix`, looks like:
82−
83−```
84−# Generated by carnix 0.6.5: carnix -o hello.nix --src ./. Cargo.lock --standalone
85−{ lib, buildPlatform, buildRustCrate, fetchgit }:
86−let kernel = buildPlatform.parsed.kernel.name;
87− # ... (content skipped)
88−in
89−rec {
90− hello = f: hello_0_1_0 { features = hello_0_1_0_features { hello_0_1_0 = f; }; };
91− hello_0_1_0_ = { dependencies?[], buildDependencies?[], features?[] }: buildRustCrate {
92− crateName = "hello";
93− version = "0.1.0";
94− authors = [ "pe@pijul.org <pe@pijul.org>" ];
95− src = ./.;
96− inherit dependencies buildDependencies features;
97− };
98− hello_0_1_0 = { features?(hello_0_1_0_features {}) }: hello_0_1_0_ {};
99− hello_0_1_0_features = f: updateFeatures f (rec {
100− hello_0_1_0.default = (f.hello_0_1_0.default or true);
101− }) [ ];
102−}
103−```
104−
105−In particular, note that the argument given as `--src` is copied
106−verbatim to the source. If we look at a more complicated
107−dependencies, for instance by adding a single line `libc="*"` to our
108−`Cargo.toml`, we first need to run `cargo build` to update the
109−`Cargo.lock`. Then, `carnix` needs to be run again, and produces the
110−following nix file:
111−
112−```
113−# Generated by carnix 0.6.5: carnix -o hello.nix --src ./. Cargo.lock --standalone
114−{ lib, buildPlatform, buildRustCrate, fetchgit }:
115−let kernel = buildPlatform.parsed.kernel.name;
116− # ... (content skipped)
117−in
118−rec {
119− hello = f: hello_0_1_0 { features = hello_0_1_0_features { hello_0_1_0 = f; }; };
120− hello_0_1_0_ = { dependencies?[], buildDependencies?[], features?[] }: buildRustCrate {
121− crateName = "hello";
122− version = "0.1.0";
123− authors = [ "pe@pijul.org <pe@pijul.org>" ];
124− src = ./.;
125− inherit dependencies buildDependencies features;
126− };
127− libc_0_2_36_ = { dependencies?[], buildDependencies?[], features?[] }: buildRustCrate {
128− crateName = "libc";
129− version = "0.2.36";
130− authors = [ "The Rust Project Developers" ];
131− sha256 = "01633h4yfqm0s302fm0dlba469bx8y6cs4nqc8bqrmjqxfxn515l";
132− inherit dependencies buildDependencies features;
133− };
134− hello_0_1_0 = { features?(hello_0_1_0_features {}) }: hello_0_1_0_ {
135− dependencies = mapFeatures features ([ libc_0_2_36 ]);
136− };
137− hello_0_1_0_features = f: updateFeatures f (rec {
138− hello_0_1_0.default = (f.hello_0_1_0.default or true);
139− libc_0_2_36.default = true;
140− }) [ libc_0_2_36_features ];
141− libc_0_2_36 = { features?(libc_0_2_36_features {}) }: libc_0_2_36_ {
142− features = mkFeatures (features.libc_0_2_36 or {});
143− };
144− libc_0_2_36_features = f: updateFeatures f (rec {
145− libc_0_2_36.default = (f.libc_0_2_36.default or true);
146− libc_0_2_36.use_std =
147− (f.libc_0_2_36.use_std or false) ||
148− (f.libc_0_2_36.default or false) ||
149− (libc_0_2_36.default or false);
150− }) [];
151−}
152−```
153−
154−Here, the `libc` crate has no `src` attribute, so `buildRustCrate`
155−will fetch it from [crates.io](https://crates.io). A `sha256`
156−attribute is still needed for Nix purity.
157−
158−### Handling external dependencies
159−
160−Some crates require external libraries. For crates from
161−[crates.io](https://crates.io), such libraries can be specified in
162−`defaultCrateOverrides` package in nixpkgs itself.
163−
164−Starting from that file, one can add more overrides, to add features
165−or build inputs by overriding the hello crate in a seperate file.
166−
167−```
168−with import <nixpkgs> {};
169−((import ./hello.nix).hello {}).override {
170− crateOverrides = defaultCrateOverrides // {
171− hello = attrs: { buildInputs = [ openssl ]; };
172− };
173−}
174−```
175−
176−Here, `crateOverrides` is expected to be a attribute set, where the
177−key is the crate name without version number and the value a function.
178−The function gets all attributes passed to `buildRustCrate` as first
179−argument and returns a set that contains all attribute that should be
180−overwritten.
181−
182−For more complicated cases, such as when parts of the crate's
183−derivation depend on the the crate's version, the `attrs` argument of
184−the override above can be read, as in the following example, which
185−patches the derivation:
186−
187−```
188−with import <nixpkgs> {};
189−((import ./hello.nix).hello {}).override {
190− crateOverrides = defaultCrateOverrides // {
191− hello = attrs: lib.optionalAttrs (lib.versionAtLeast attrs.version "1.0") {
192− postPatch = ''
193− substituteInPlace lib/zoneinfo.rs \
194− --replace "/usr/share/zoneinfo" "${tzdata}/share/zoneinfo"
195− '';
196− };
197− };
198−}
199−```
200−
201−Another situation is when we want to override a nested
202−dependency. This actually works in the exact same way, since the
203−`crateOverrides` parameter is forwarded to the crate's
204−dependencies. For instance, to override the build inputs for crate
205−`libc` in the example above, where `libc` is a dependency of the main
206−crate, we could do:
207−
208−```
209−with import <nixpkgs> {};
210−((import hello.nix).hello {}).override {
211− crateOverrides = defaultCrateOverrides // {
212− libc = attrs: { buildInputs = []; };
213− };
214−}
215−```
216−
217−### Options and phases configuration
218−
219−Actually, the overrides introduced in the previous section are more
220−general. A number of other parameters can be overridden:
221−
222−- The version of rustc used to compile the crate:
223−
224− ```
225− (hello {}).override { rust = pkgs.rust; };
226− ```
227−
228−- Whether to build in release mode or debug mode (release mode by
229− default):
230−
231− ```
232− (hello {}).override { release = false; };
233− ```
234−
235−- Whether to print the commands sent to rustc when building
236− (equivalent to `--verbose` in cargo:
237−
238− ```
239− (hello {}).override { verbose = false; };
240− ```
241−
242−- Extra arguments to be passed to `rustc`:
243−
244− ```
245− (hello {}).override { extraRustcOpts = "-Z debuginfo=2"; };
246− ```
247−
248−- Phases, just like in any other derivation, can be specified using
249− the following attributes: `preUnpack`, `postUnpack`, `prePatch`,
250− `patches`, `postPatch`, `preConfigure` (in the case of a Rust crate,
251− this is run before calling the "build" script), `postConfigure`
252− (after the "build" script),`preBuild`, `postBuild`, `preInstall` and
253− `postInstall`. As an example, here is how to create a new module
254− before running the build script:
255−
256− ```
257− (hello {}).override {
258− preConfigure = ''
259− echo "pub const PATH=\"${hi.out}\";" >> src/path.rs"
260− '';
261− };
262− ```
263−
264−### Features
265−
266−One can also supply features switches. For example, if we want to
267−compile `diesel_cli` only with the `postgres` feature, and no default
268−features, we would write:
269−
270−```
271−(callPackage ./diesel.nix {}).diesel {
272− default = false;
273− postgres = true;
274−}
275−```
276−
277−Where `diesel.nix` is the file generated by Carnix, as explained above.
278−
279−## Using the Rust nightlies overlay
280−
281−Mozilla provides an overlay for nixpkgs to bring a nightly version of Rust into scope.
282−This overlay can _also_ be used to install recent unstable or stable versions
283−of Rust, if desired.
284−
285−To use this overlay, clone
286−[nixpkgs-mozilla](https://github.com/mozilla/nixpkgs-mozilla),
287−and create a symbolic link to the file
288−[rust-overlay.nix](https://github.com/mozilla/nixpkgs-mozilla/blob/master/rust-overlay.nix)
289−in the `~/.config/nixpkgs/overlays` directory.
290−
291− $ git clone https://github.com/mozilla/nixpkgs-mozilla.git
292− $ mkdir -p ~/.config/nixpkgs/overlays
293− $ ln -s $(pwd)/nixpkgs-mozilla/rust-overlay.nix ~/.config/nixpkgs/overlays/rust-overlay.nix
294−
295−The latest version can be installed with the following command:
296−
297− $ nix-env -Ai nixos.latest.rustChannels.stable.rust
298−
299−Or using the attribute with nix-shell:
300−
301− $ nix-shell -p nixos.latest.rustChannels.stable.rust
302−
303−To install the beta or nightly channel, "stable" should be substituted by
304−"nightly" or "beta", or
305−use the function provided by this overlay to pull a version based on a
306−build date.
307−
308−The overlay automatically updates itself as it uses the same source as
309−[rustup](https://www.rustup.rs/).
doc/languages-frameworks/rust.section.mdnew file+395
@@ -0,0 +1,395 @@
1+---
2+title: Rust
3+author: Matthias Beyer
4+date: 2017-03-05
5+---
6+
7+# User's Guide to the Rust Infrastructure
8+
9+To install the rust compiler and cargo put
10+
11+```
12+rustc
13+cargo
14+```
15+
16+into the `environment.systemPackages` or bring them into
17+scope with `nix-shell -p rustc cargo`.
18+
19+> If you are using NixOS and you want to use rust without a nix expression you
20+> probably want to add the following in your `configuration.nix` to build
21+> crates with C dependencies.
22+>
23+> environment.systemPackages = [binutils gcc gnumake openssl pkgconfig]
24+
25+For daily builds (beta and nightly) use either rustup from
26+nixpkgs or use the [Rust nightlies
27+overlay](#using-the-rust-nightlies-overlay).
28+
29+## Compiling Rust applications with Cargo
30+
31+Rust applications are packaged by using the `buildRustPackage` helper from `rustPlatform`:
32+
33+```
34+rustPlatform.buildRustPackage rec {
35+ name = "ripgrep-${version}";
36+ version = "0.4.0";
37+
38+ src = fetchFromGitHub {
39+ owner = "BurntSushi";
40+ repo = "ripgrep";
41+ rev = "${version}";
42+ sha256 = "0y5d1n6hkw85jb3rblcxqas2fp82h3nghssa4xqrhqnz25l799pj";
43+ };
44+
45+ cargoSha256 = "0q68qyl2h6i0qsz82z840myxlnjay8p1w5z7hfyr8fqp7wgwa9cx";
46+
47+ meta = with stdenv.lib; {
48+ description = "A fast line-oriented regex search tool, similar to ag and ack";
49+ homepage = https://github.com/BurntSushi/ripgrep;
50+ license = licenses.unlicense;
51+ maintainers = [ maintainers.tailhook ];
52+ platforms = platforms.all;
53+ };
54+}
55+```
56+
57+`buildRustPackage` requires a `cargoSha256` attribute which is computed over
58+all crate sources of this package. Currently it is obtained by inserting a
59+fake checksum into the expression and building the package once. The correct
60+checksum can be then take from the failed build.
61+
62+When the `Cargo.lock`, provided by upstream, is not in sync with the
63+`Cargo.toml`, it is possible to use `cargoPatches` to update it. All patches
64+added in `cargoPatches` will also be prepended to the patches in `patches` at
65+build-time.
66+
67+## Compiling Rust crates using Nix instead of Cargo
68+
69+### Simple operation
70+
71+When run, `cargo build` produces a file called `Cargo.lock`,
72+containing pinned versions of all dependencies. Nixpkgs contains a
73+tool called `carnix` (`nix-env -iA nixos.carnix`), which can be used
74+to turn a `Cargo.lock` into a Nix expression.
75+
76+That Nix expression calls `rustc` directly (hence bypassing Cargo),
77+and can be used to compile a crate and all its dependencies. Here is
78+an example for a minimal `hello` crate:
79+
80+
81+ $ cargo new hello
82+ $ cd hello
83+ $ cargo build
84+ Compiling hello v0.1.0 (file:///tmp/hello)
85+ Finished dev [unoptimized + debuginfo] target(s) in 0.20 secs
86+ $ carnix -o hello.nix --src ./. Cargo.lock --standalone
87+ $ nix-build hello.nix -A hello_0_1_0
88+
89+Now, the file produced by the call to `carnix`, called `hello.nix`, looks like:
90+
91+```
92+# Generated by carnix 0.6.5: carnix -o hello.nix --src ./. Cargo.lock --standalone
93+{ lib, stdenv, buildRustCrate, fetchgit }:
94+let kernel = stdenv.buildPlatform.parsed.kernel.name;
95+ # ... (content skipped)
96+in
97+rec {
98+ hello = f: hello_0_1_0 { features = hello_0_1_0_features { hello_0_1_0 = f; }; };
99+ hello_0_1_0_ = { dependencies?[], buildDependencies?[], features?[] }: buildRustCrate {
100+ crateName = "hello";
101+ version = "0.1.0";
102+ authors = [ "pe@pijul.org <pe@pijul.org>" ];
103+ src = ./.;
104+ inherit dependencies buildDependencies features;
105+ };
106+ hello_0_1_0 = { features?(hello_0_1_0_features {}) }: hello_0_1_0_ {};
107+ hello_0_1_0_features = f: updateFeatures f (rec {
108+ hello_0_1_0.default = (f.hello_0_1_0.default or true);
109+ }) [ ];
110+}
111+```
112+
113+In particular, note that the argument given as `--src` is copied
114+verbatim to the source. If we look at a more complicated
115+dependencies, for instance by adding a single line `libc="*"` to our
116+`Cargo.toml`, we first need to run `cargo build` to update the
117+`Cargo.lock`. Then, `carnix` needs to be run again, and produces the
118+following nix file:
119+
120+```
121+# Generated by carnix 0.6.5: carnix -o hello.nix --src ./. Cargo.lock --standalone
122+{ lib, stdenv, buildRustCrate, fetchgit }:
123+let kernel = stdenv.buildPlatform.parsed.kernel.name;
124+ # ... (content skipped)
125+in
126+rec {
127+ hello = f: hello_0_1_0 { features = hello_0_1_0_features { hello_0_1_0 = f; }; };
128+ hello_0_1_0_ = { dependencies?[], buildDependencies?[], features?[] }: buildRustCrate {
129+ crateName = "hello";
130+ version = "0.1.0";
131+ authors = [ "pe@pijul.org <pe@pijul.org>" ];
132+ src = ./.;
133+ inherit dependencies buildDependencies features;
134+ };
135+ libc_0_2_36_ = { dependencies?[], buildDependencies?[], features?[] }: buildRustCrate {
136+ crateName = "libc";
137+ version = "0.2.36";
138+ authors = [ "The Rust Project Developers" ];
139+ sha256 = "01633h4yfqm0s302fm0dlba469bx8y6cs4nqc8bqrmjqxfxn515l";
140+ inherit dependencies buildDependencies features;
141+ };
142+ hello_0_1_0 = { features?(hello_0_1_0_features {}) }: hello_0_1_0_ {
143+ dependencies = mapFeatures features ([ libc_0_2_36 ]);
144+ };
145+ hello_0_1_0_features = f: updateFeatures f (rec {
146+ hello_0_1_0.default = (f.hello_0_1_0.default or true);
147+ libc_0_2_36.default = true;
148+ }) [ libc_0_2_36_features ];
149+ libc_0_2_36 = { features?(libc_0_2_36_features {}) }: libc_0_2_36_ {
150+ features = mkFeatures (features.libc_0_2_36 or {});
151+ };
152+ libc_0_2_36_features = f: updateFeatures f (rec {
153+ libc_0_2_36.default = (f.libc_0_2_36.default or true);
154+ libc_0_2_36.use_std =
155+ (f.libc_0_2_36.use_std or false) ||
156+ (f.libc_0_2_36.default or false) ||
157+ (libc_0_2_36.default or false);
158+ }) [];
159+}
160+```
161+
162+Here, the `libc` crate has no `src` attribute, so `buildRustCrate`
163+will fetch it from [crates.io](https://crates.io). A `sha256`
164+attribute is still needed for Nix purity.
165+
166+### Handling external dependencies
167+
168+Some crates require external libraries. For crates from
169+[crates.io](https://crates.io), such libraries can be specified in
170+`defaultCrateOverrides` package in nixpkgs itself.
171+
172+Starting from that file, one can add more overrides, to add features
173+or build inputs by overriding the hello crate in a seperate file.
174+
175+```
176+with import <nixpkgs> {};
177+((import ./hello.nix).hello {}).override {
178+ crateOverrides = defaultCrateOverrides // {
179+ hello = attrs: { buildInputs = [ openssl ]; };
180+ };
181+}
182+```
183+
184+Here, `crateOverrides` is expected to be a attribute set, where the
185+key is the crate name without version number and the value a function.
186+The function gets all attributes passed to `buildRustCrate` as first
187+argument and returns a set that contains all attribute that should be
188+overwritten.
189+
190+For more complicated cases, such as when parts of the crate's
191+derivation depend on the the crate's version, the `attrs` argument of
192+the override above can be read, as in the following example, which
193+patches the derivation:
194+
195+```
196+with import <nixpkgs> {};
197+((import ./hello.nix).hello {}).override {
198+ crateOverrides = defaultCrateOverrides // {
199+ hello = attrs: lib.optionalAttrs (lib.versionAtLeast attrs.version "1.0") {
200+ postPatch = ''
201+ substituteInPlace lib/zoneinfo.rs \
202+ --replace "/usr/share/zoneinfo" "${tzdata}/share/zoneinfo"
203+ '';
204+ };
205+ };
206+}
207+```
208+
209+Another situation is when we want to override a nested
210+dependency. This actually works in the exact same way, since the
211+`crateOverrides` parameter is forwarded to the crate's
212+dependencies. For instance, to override the build inputs for crate
213+`libc` in the example above, where `libc` is a dependency of the main
214+crate, we could do:
215+
216+```
217+with import <nixpkgs> {};
218+((import hello.nix).hello {}).override {
219+ crateOverrides = defaultCrateOverrides // {
220+ libc = attrs: { buildInputs = []; };
221+ };
222+}
223+```
224+
225+### Options and phases configuration
226+
227+Actually, the overrides introduced in the previous section are more
228+general. A number of other parameters can be overridden:
229+
230+- The version of rustc used to compile the crate:
231+
232+ ```
233+ (hello {}).override { rust = pkgs.rust; };
234+ ```
235+
236+- Whether to build in release mode or debug mode (release mode by
237+ default):
238+
239+ ```
240+ (hello {}).override { release = false; };
241+ ```
242+
243+- Whether to print the commands sent to rustc when building
244+ (equivalent to `--verbose` in cargo:
245+
246+ ```
247+ (hello {}).override { verbose = false; };
248+ ```
249+
250+- Extra arguments to be passed to `rustc`:
251+
252+ ```
253+ (hello {}).override { extraRustcOpts = "-Z debuginfo=2"; };
254+ ```
255+
256+- Phases, just like in any other derivation, can be specified using
257+ the following attributes: `preUnpack`, `postUnpack`, `prePatch`,
258+ `patches`, `postPatch`, `preConfigure` (in the case of a Rust crate,
259+ this is run before calling the "build" script), `postConfigure`
260+ (after the "build" script),`preBuild`, `postBuild`, `preInstall` and
261+ `postInstall`. As an example, here is how to create a new module
262+ before running the build script:
263+
264+ ```
265+ (hello {}).override {
266+ preConfigure = ''
267+ echo "pub const PATH=\"${hi.out}\";" >> src/path.rs"
268+ '';
269+ };
270+ ```
271+
272+### Features
273+
274+One can also supply features switches. For example, if we want to
275+compile `diesel_cli` only with the `postgres` feature, and no default
276+features, we would write:
277+
278+```
279+(callPackage ./diesel.nix {}).diesel {
280+ default = false;
281+ postgres = true;
282+}
283+```
284+
285+Where `diesel.nix` is the file generated by Carnix, as explained above.
286+
287+
288+## Setting Up `nix-shell`
289+Oftentimes you want to develop code from within `nix-shell`. Unfortunately
290+`buildRustCrate` does not support common `nix-shell` operations directly
291+(see [this issue](https://github.com/NixOS/nixpkgs/issues/37945))
292+so we will use `stdenv.mkDerivation` instead.
293+
294+Using the example `hello` project above, we want to do the following:
295+- Have access to `cargo` and `rustc`
296+- Have the `openssl` library available to a crate through it's _normal_
297+ compilation mechanism (`pkg-config`).
298+
299+A typical `shell.nix` might look like:
300+
301+```
302+with import <nixpkgs> {};
303+
304+stdenv.mkDerivation {
305+ name = "rust-env";
306+ buildInputs = [
307+ rustc cargo
308+
309+ # Example Additional Dependencies
310+ pkgconfig openssl
311+ ];
312+
313+ # Set Environment Variables
314+ RUST_BACKTRACE = 1;
315+}
316+```
317+
318+You should now be able to run the following:
319+```
320+$ nix-shell --pure
321+$ cargo build
322+$ cargo test
323+```
324+
325+### Controlling Rust Version Inside `nix-shell`
326+To control your rust version (i.e. use nightly) from within `shell.nix` (or
327+other nix expressions) you can use the following `shell.nix`
328+
329+```
330+# Latest Nightly
331+with import <nixpkgs> {};
332+let src = fetchFromGitHub {
333+ owner = "mozilla";
334+ repo = "nixpkgs-mozilla";
335+ # commit from: 2018-03-27
336+ rev = "2945b0b6b2fd19e7d23bac695afd65e320efcebe";
337+ sha256 = "034m1dryrzh2lmjvk3c0krgip652dql46w5yfwpvh7gavd3iypyw";
338+ };
339+in
340+with import "${src.out}/rust-overlay.nix" pkgs pkgs;
341+stdenv.mkDerivation {
342+ name = "rust-env";
343+ buildInputs = [
344+ # Note: to use use stable, just replace `nightly` with `stable`
345+ latest.rustChannels.nightly.rust
346+
347+ # Add some extra dependencies from `pkgs`
348+ pkgconfig openssl
349+ ];
350+
351+ # Set Environment Variables
352+ RUST_BACKTRACE = 1;
353+}
354+```
355+
356+Now run:
357+```
358+$ rustc --version
359+rustc 1.26.0-nightly (188e693b3 2018-03-26)
360+```
361+
362+To see that you are using nightly.
363+
364+
365+## Using the Rust nightlies overlay
366+
367+Mozilla provides an overlay for nixpkgs to bring a nightly version of Rust into scope.
368+This overlay can _also_ be used to install recent unstable or stable versions
369+of Rust, if desired.
370+
371+To use this overlay, clone
372+[nixpkgs-mozilla](https://github.com/mozilla/nixpkgs-mozilla),
373+and create a symbolic link to the file
374+[rust-overlay.nix](https://github.com/mozilla/nixpkgs-mozilla/blob/master/rust-overlay.nix)
375+in the `~/.config/nixpkgs/overlays` directory.
376+
377+ $ git clone https://github.com/mozilla/nixpkgs-mozilla.git
378+ $ mkdir -p ~/.config/nixpkgs/overlays
379+ $ ln -s $(pwd)/nixpkgs-mozilla/rust-overlay.nix ~/.config/nixpkgs/overlays/rust-overlay.nix
380+
381+The latest version can be installed with the following command:
382+
383+ $ nix-env -Ai nixos.latest.rustChannels.stable.rust
384+
385+Or using the attribute with nix-shell:
386+
387+ $ nix-shell -p nixos.latest.rustChannels.stable.rust
388+
389+To install the beta or nightly channel, "stable" should be substituted by
390+"nightly" or "beta", or
391+use the function provided by this overlay to pull a version based on a
392+build date.
393+
394+The overlay automatically updates itself as it uses the same source as
395+[rustup](https://www.rustup.rs/).
doc/languages-frameworks/texlive.xml+72−33
@@ -1,27 +1,42 @@
11<section xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="sec-language-texlive">
4+ <title>TeX Live</title>
45
5−<title>TeX Live</title>
6+ <para>
7+ Since release 15.09 there is a new TeX Live packaging that lives entirely
8+ under attribute <varname>texlive</varname>.
9+ </para>
10+
11+ <section xml:id="sec-language-texlive-users-guide">
12+ <title>User's guide</title>
613
7−<para>Since release 15.09 there is a new TeX Live packaging that lives entirely under attribute <varname>texlive</varname>.</para>
8−<section><title>User's guide</title>
914 <itemizedlist>
10− <listitem><para>
11− For basic usage just pull <varname>texlive.combined.scheme-basic</varname> for an environment with basic LaTeX support.</para></listitem>
12− <listitem><para>
13− It typically won't work to use separately installed packages together.
14− Instead, you can build a custom set of packages like this:
15− <programlisting>
15+ <listitem>
16+ <para>
17+ For basic usage just pull <varname>texlive.combined.scheme-basic</varname>
18+ for an environment with basic LaTeX support.
19+ </para>
20+ </listitem>
21+ <listitem>
22+ <para>
23+ It typically won't work to use separately installed packages together.
24+ Instead, you can build a custom set of packages like this:
25+<programlisting>
1626texlive.combine {
1727 inherit (texlive) scheme-small collection-langkorean algorithms cm-super;
1828}
1929 </programlisting>
20− There are all the schemes, collections and a few thousand packages, as defined upstream (perhaps with tiny differences).
21− </para></listitem>
22− <listitem><para>
23− By default you only get executables and files needed during runtime, and a little documentation for the core packages. To change that, you need to add <varname>pkgFilter</varname> function to <varname>combine</varname>.
24− <programlisting>
30+ There are all the schemes, collections and a few thousand packages, as
31+ defined upstream (perhaps with tiny differences).
32+ </para>
33+ </listitem>
34+ <listitem>
35+ <para>
36+ By default you only get executables and files needed during runtime, and a
37+ little documentation for the core packages. To change that, you need to
38+ add <varname>pkgFilter</varname> function to <varname>combine</varname>.
39+<programlisting>
2540texlive.combine {
2641 # inherit (texlive) whatever-you-want;
2742 pkgFilter = pkg:
@@ -30,31 +45,55 @@ texlive.combine {
3045 # there are also other attributes: version, name
3146}
3247 </programlisting>
33− </para></listitem>
34− <listitem><para>
35− You can list packages e.g. by <command>nix-repl</command>.
36− <programlisting>
48+ </para>
49+ </listitem>
50+ <listitem>
51+ <para>
52+ You can list packages e.g. by <command>nix-repl</command>.
53+<programlisting>
3754$ nix-repl
3855nix-repl> :l &lt;nixpkgs>
3956nix-repl> texlive.collection-&lt;TAB>
4057 </programlisting>
41− </para></listitem>
58+ </para>
59+ </listitem>
60+ <listitem>
61+ <para>
62+ Note that the wrapper assumes that the result has a chance to be useful.
63+ For example, the core executables should be present, as well as some core
64+ data files. The supported way of ensuring this is by including some
65+ scheme, for example <varname>scheme-basic</varname>, into the combination.
66+ </para>
67+ </listitem>
4268 </itemizedlist>
43−</section>
69+ </section>
70+
71+ <section xml:id="sec-language-texlive-known-problems">
72+ <title>Known problems</title>
4473
45−<section><title>Known problems</title>
4674 <itemizedlist>
47− <listitem><para>
48− Some tools are still missing, e.g. luajittex;</para></listitem>
49− <listitem><para>
50− some apps aren't packaged/tested yet (asymptote, biber, etc.);</para></listitem>
51− <listitem><para>
52− feature/bug: when a package is rejected by <varname>pkgFilter</varname>, its dependencies are still propagated;</para></listitem>
53− <listitem><para>
54− in case of any bugs or feature requests, file a github issue or better a pull request and /cc @vcunat.</para></listitem>
75+ <listitem>
76+ <para>
77+ Some tools are still missing, e.g. luajittex;
78+ </para>
79+ </listitem>
80+ <listitem>
81+ <para>
82+ some apps aren't packaged/tested yet (asymptote, biber, etc.);
83+ </para>
84+ </listitem>
85+ <listitem>
86+ <para>
87+ feature/bug: when a package is rejected by <varname>pkgFilter</varname>,
88+ its dependencies are still propagated;
89+ </para>
90+ </listitem>
91+ <listitem>
92+ <para>
93+ in case of any bugs or feature requests, file a github issue or better a
94+ pull request and /cc @vcunat.
95+ </para>
96+ </listitem>
5597 </itemizedlist>
98+ </section>
5699</section>
57−
58−
59−</section>
60−
doc/languages-frameworks/vim.mddeleted−135
@@ -1,135 +0,0 @@
1−---
2−title: User's Guide for Vim in Nixpkgs
3−author: Marc Weber
4−date: 2016-06-25
5−---
6−# User's Guide to Vim Plugins/Addons/Bundles/Scripts in Nixpkgs
7−
8−You'll get a vim(-your-suffix) in PATH also loading the plugins you want.
9−Loading can be deferred; see examples.
10−
11−Vim packages, VAM (=vim-addon-manager) and Pathogen are supported to load
12−packages.
13−
14−## Custom configuration
15−
16−Adding custom .vimrc lines can be done using the following code:
17−
18−```
19−vim_configurable.customize {
20− name = "vim-with-plugins";
21−
22− vimrcConfig.customRC = ''
23− set hidden
24− '';
25−}
26−```
27−
28−## Vim packages
29−
30−To store you plugins in Vim packages the following example can be used:
31−
32−```
33−vim_configurable.customize {
34− vimrcConfig.packages.myVimPackage = with pkgs.vimPlugins; {
35− # loaded on launch
36− start = [ youcompleteme fugitive ];
37− # manually loadable by calling `:packadd $plugin-name`
38− opt = [ phpCompletion elm-vim ];
39− # To automatically load a plugin when opening a filetype, add vimrc lines like:
40− # autocmd FileType php :packadd phpCompletion
41− }
42−};
43−```
44−
45−## VAM
46−
47−### dependencies by Vim plugins
48−
49−VAM introduced .json files supporting dependencies without versioning
50−assuming that "using latest version" is ok most of the time.
51−
52−### Example
53−
54−First create a vim-scripts file having one plugin name per line. Example:
55−
56− "tlib"
57− {'name': 'vim-addon-sql'}
58− {'filetype_regex': '\%(vim)$', 'names': ['reload', 'vim-dev-plugin']}
59−
60−Such vim-scripts file can be read by VAM as well like this:
61−
62− call vam#Scripts(expand('~/.vim-scripts'), {})
63−
64−Create a default.nix file:
65−
66− { nixpkgs ? import <nixpkgs> {}, compiler ? "ghc7102" }:
67− nixpkgs.vim_configurable.customize { name = "vim"; vimrcConfig.vam.pluginDictionaries = [ "vim-addon-vim2nix" ]; }
68−
69−Create a generate.vim file:
70−
71− ActivateAddons vim-addon-vim2nix
72− let vim_scripts = "vim-scripts"
73− call nix#ExportPluginsForNix({
74− \ 'path_to_nixpkgs': eval('{"'.substitute(substitute(substitute($NIX_PATH, ':', ',', 'g'), '=',':', 'g'), '\([:,]\)', '"\1"',"g").'"}')["nixpkgs"],
75− \ 'cache_file': '/tmp/vim2nix-cache',
76− \ 'try_catch': 0,
77− \ 'plugin_dictionaries': ["vim-addon-manager"]+map(readfile(vim_scripts), 'eval(v:val)')
78− \ })
79−
80−Then run
81−
82− nix-shell -p vimUtils.vim_with_vim2nix --command "vim -c 'source generate.vim'"
83−
84−You should get a Vim buffer with the nix derivations (output1) and vam.pluginDictionaries (output2).
85−You can add your vim to your system's configuration file like this and start it by "vim-my":
86−
87− my-vim =
88− let plugins = let inherit (vimUtils) buildVimPluginFrom2Nix; in {
89− copy paste output1 here
90− }; in vim_configurable.customize {
91− name = "vim-my";
92−
93− vimrcConfig.vam.knownPlugins = plugins; # optional
94− vimrcConfig.vam.pluginDictionaries = [
95− copy paste output2 here
96− ];
97−
98− # Pathogen would be
99− # vimrcConfig.pathogen.knownPlugins = plugins; # plugins
100− # vimrcConfig.pathogen.pluginNames = ["tlib"];
101− };
102−
103−
104−Sample output1:
105−
106− "reload" = buildVimPluginFrom2Nix { # created by nix#NixDerivation
107− name = "reload";
108− src = fetchgit {
109− url = "git://github.com/xolox/vim-reload";
110− rev = "0a601a668727f5b675cb1ddc19f6861f3f7ab9e1";
111− sha256 = "0vb832l9yxj919f5hfg6qj6bn9ni57gnjd3bj7zpq7d4iv2s4wdh";
112− };
113− dependencies = ["nim-misc"];
114−
115− };
116− [...]
117−
118−Sample output2:
119−
120− [
121− ''vim-addon-manager''
122− ''tlib''
123− { "name" = ''vim-addon-sql''; }
124− { "filetype_regex" = ''\%(vim)$$''; "names" = [ ''reload'' ''vim-dev-plugin'' ]; }
125− ]
126−
127−
128−## Important repositories
129−
130−- [vim-pi](https://bitbucket.org/vimcommunity/vim-pi) is a plugin repository
131− from VAM plugin manager meant to be used by others as well used by
132−
133−- [vim2nix](http://github.com/MarcWeber/vim-addon-vim2nix) which generates the
134− .nix code
135−
doc/languages-frameworks/vim.section.mdnew file+235
@@ -0,0 +1,235 @@
1+---
2+title: User's Guide for Vim in Nixpkgs
3+author: Marc Weber
4+date: 2016-06-25
5+---
6+# User's Guide to Vim Plugins/Addons/Bundles/Scripts in Nixpkgs
7+
8+Both Neovim and Vim can be configured to include your favorite plugins
9+and additional libraries.
10+
11+Loading can be deferred; see examples.
12+
13+At the moment we support three different methods for managing plugins:
14+
15+- Vim packages (*recommend*)
16+- VAM (=vim-addon-manager)
17+- Pathogen
18+- vim-plug
19+
20+## Custom configuration
21+
22+Adding custom .vimrc lines can be done using the following code:
23+
24+```
25+vim_configurable.customize {
26+ # `name` specifies the name of the executable and package
27+ name = "vim-with-plugins";
28+
29+ vimrcConfig.customRC = ''
30+ set hidden
31+ '';
32+}
33+```
34+
35+This configuration is used when vim is invoked with the command specified as name, in this case `vim-with-plugins`.
36+
37+For Neovim the `configure` argument can be overridden to achieve the same:
38+
39+```
40+neovim.override {
41+ configure = {
42+ customRC = ''
43+ # here your custom configuration goes!
44+ '';
45+ };
46+}
47+```
48+
49+## Managing plugins with Vim packages
50+
51+To store you plugins in Vim packages the following example can be used:
52+
53+```
54+vim_configurable.customize {
55+ vimrcConfig.packages.myVimPackage = with pkgs.vimPlugins; {
56+ # loaded on launch
57+ start = [ youcompleteme fugitive ];
58+ # manually loadable by calling `:packadd $plugin-name`
59+ opt = [ phpCompletion elm-vim ];
60+ # To automatically load a plugin when opening a filetype, add vimrc lines like:
61+ # autocmd FileType php :packadd phpCompletion
62+ };
63+}
64+```
65+
66+For Neovim the syntax is:
67+
68+```
69+neovim.override {
70+ configure = {
71+ customRC = ''
72+ # here your custom configuration goes!
73+ '';
74+ packages.myVimPackage = with pkgs.vimPlugins; {
75+ # see examples below how to use custom packages
76+ start = [ ];
77+ opt = [ ];
78+ };
79+ };
80+}
81+```
82+
83+The resulting package can be added to `packageOverrides` in `~/.nixpkgs/config.nix` to make it installable:
84+
85+```
86+{
87+ packageOverrides = pkgs: with pkgs; {
88+ myVim = vim_configurable.customize {
89+ # `name` specifies the name of the executable and package
90+ name = "vim-with-plugins";
91+ # add here code from the example section
92+ };
93+ myNeovim = neovim.override {
94+ configure = {
95+ # add here code from the example section
96+ };
97+ };
98+ };
99+}
100+```
101+
102+After that you can install your special grafted `myVim` or `myNeovim` packages.
103+
104+## Managing plugins with vim-plug
105+
106+To use [vim-plug](https://github.com/junegunn/vim-plug) to manage your Vim
107+plugins the following example can be used:
108+
109+```
110+vim_configurable.customize {
111+ vimrcConfig.packages.myVimPackage = with pkgs.vimPlugins; {
112+ # loaded on launch
113+ plug.plugins = [ youcompleteme fugitive phpCompletion elm-vim ];
114+ };
115+}
116+```
117+
118+For Neovim the syntax is:
119+
120+```
121+neovim.override {
122+ configure = {
123+ customRC = ''
124+ # here your custom configuration goes!
125+ '';
126+ plug.plugins = with pkgs.vimPlugins; [
127+ vim-go
128+ ];
129+ };
130+}
131+```
132+
133+## Managing plugins with VAM
134+
135+### Handling dependencies of Vim plugins
136+
137+VAM introduced .json files supporting dependencies without versioning
138+assuming that "using latest version" is ok most of the time.
139+
140+### Example
141+
142+First create a vim-scripts file having one plugin name per line. Example:
143+
144+ "tlib"
145+ {'name': 'vim-addon-sql'}
146+ {'filetype_regex': '\%(vim)$', 'names': ['reload', 'vim-dev-plugin']}
147+
148+Such vim-scripts file can be read by VAM as well like this:
149+
150+ call vam#Scripts(expand('~/.vim-scripts'), {})
151+
152+Create a default.nix file:
153+
154+ { nixpkgs ? import <nixpkgs> {}, compiler ? "ghc7102" }:
155+ nixpkgs.vim_configurable.customize { name = "vim"; vimrcConfig.vam.pluginDictionaries = [ "vim-addon-vim2nix" ]; }
156+
157+Create a generate.vim file:
158+
159+ ActivateAddons vim-addon-vim2nix
160+ let vim_scripts = "vim-scripts"
161+ call nix#ExportPluginsForNix({
162+ \ 'path_to_nixpkgs': eval('{"'.substitute(substitute(substitute($NIX_PATH, ':', ',', 'g'), '=',':', 'g'), '\([:,]\)', '"\1"',"g").'"}')["nixpkgs"],
163+ \ 'cache_file': '/tmp/vim2nix-cache',
164+ \ 'try_catch': 0,
165+ \ 'plugin_dictionaries': ["vim-addon-manager"]+map(readfile(vim_scripts), 'eval(v:val)')
166+ \ })
167+
168+Then run
169+
170+ nix-shell -p vimUtils.vim_with_vim2nix --command "vim -c 'source generate.vim'"
171+
172+You should get a Vim buffer with the nix derivations (output1) and vam.pluginDictionaries (output2).
173+You can add your vim to your system's configuration file like this and start it by "vim-my":
174+
175+ my-vim =
176+ let plugins = let inherit (vimUtils) buildVimPluginFrom2Nix; in {
177+ copy paste output1 here
178+ }; in vim_configurable.customize {
179+ name = "vim-my";
180+
181+ vimrcConfig.vam.knownPlugins = plugins; # optional
182+ vimrcConfig.vam.pluginDictionaries = [
183+ copy paste output2 here
184+ ];
185+
186+ # Pathogen would be
187+ # vimrcConfig.pathogen.knownPlugins = plugins; # plugins
188+ # vimrcConfig.pathogen.pluginNames = ["tlib"];
189+ };
190+
191+
192+Sample output1:
193+
194+ "reload" = buildVimPluginFrom2Nix { # created by nix#NixDerivation
195+ name = "reload";
196+ src = fetchgit {
197+ url = "git://github.com/xolox/vim-reload";
198+ rev = "0a601a668727f5b675cb1ddc19f6861f3f7ab9e1";
199+ sha256 = "0vb832l9yxj919f5hfg6qj6bn9ni57gnjd3bj7zpq7d4iv2s4wdh";
200+ };
201+ dependencies = ["nim-misc"];
202+
203+ };
204+ [...]
205+
206+Sample output2:
207+
208+ [
209+ ''vim-addon-manager''
210+ ''tlib''
211+ { "name" = ''vim-addon-sql''; }
212+ { "filetype_regex" = ''\%(vim)$$''; "names" = [ ''reload'' ''vim-dev-plugin'' ]; }
213+ ]
214+
215+
216+## Adding new plugins to nixpkgs
217+
218+In `pkgs/misc/vim-plugins/vim-plugin-names` we store the plugin names
219+for all vim plugins we automatically generate plugins for.
220+The format of this file `github username/github repository`:
221+For example https://github.com/scrooloose/nerdtree becomes `scrooloose/nerdtree`.
222+After adding your plugin to this file run the `./update.py` in the same folder.
223+This will updated a file called `generated.nix` and make your plugin accessible in the
224+`vimPlugins` attribute set (`vimPlugins.nerdtree` in our example).
225+If additional steps to the build process of the plugin are required, add an
226+override to the `pkgs/misc/vim-plugins/default.nix` in the same directory.
227+
228+## Important repositories
229+
230+- [vim-pi](https://bitbucket.org/vimcommunity/vim-pi) is a plugin repository
231+ from VAM plugin manager meant to be used by others as well used by
232+
233+- [vim2nix](http://github.com/MarcWeber/vim-addon-vim2nix) which generates the
234+ .nix code
235+
doc/lib-function-locations.nixnew file+85
@@ -0,0 +1,85 @@
1+{ pkgs ? (import ./.. { }), nixpkgs ? { }}:
2+let
3+ revision = pkgs.lib.trivial.revisionWithDefault (nixpkgs.revision or "master");
4+
5+ libDefPos = set:
6+ builtins.map
7+ (name: {
8+ name = name;
9+ location = builtins.unsafeGetAttrPos name set;
10+ })
11+ (builtins.attrNames set);
12+
13+ libset = toplib:
14+ builtins.map
15+ (subsetname: {
16+ subsetname = subsetname;
17+ functions = libDefPos toplib."${subsetname}";
18+ })
19+ (builtins.filter
20+ (name: builtins.isAttrs toplib."${name}")
21+ (builtins.attrNames toplib));
22+
23+ nixpkgsLib = pkgs.lib;
24+
25+ flattenedLibSubset = { subsetname, functions }:
26+ builtins.map
27+ (fn: {
28+ name = "lib.${subsetname}.${fn.name}";
29+ value = fn.location;
30+ })
31+ functions;
32+
33+ locatedlibsets = libs: builtins.map flattenedLibSubset (libset libs);
34+ removeFilenamePrefix = prefix: filename:
35+ let
36+ prefixLen = (builtins.stringLength prefix) + 1; # +1 to remove the leading /
37+ filenameLen = builtins.stringLength filename;
38+ substr = builtins.substring prefixLen filenameLen filename;
39+ in substr;
40+
41+ removeNixpkgs = removeFilenamePrefix (builtins.toString pkgs.path);
42+
43+ liblocations =
44+ builtins.filter
45+ (elem: elem.value != null)
46+ (nixpkgsLib.lists.flatten
47+ (locatedlibsets nixpkgsLib));
48+
49+ fnLocationRelative = { name, value }:
50+ {
51+ inherit name;
52+ value = value // { file = removeNixpkgs value.file; };
53+ };
54+
55+ relativeLocs = (builtins.map fnLocationRelative liblocations);
56+ sanitizeId = builtins.replaceStrings
57+ [ "'" ]
58+ [ "-prime" ];
59+
60+ urlPrefix = "https://github.com/NixOS/nixpkgs/blob/${revision}";
61+ xmlstrings = (nixpkgsLib.strings.concatMapStrings
62+ ({ name, value }:
63+ ''
64+ <section><title>${name}</title>
65+ <para xml:id="${sanitizeId name}">
66+ Located at
67+ <link
68+ xlink:href="${urlPrefix}/${value.file}#L${builtins.toString value.line}">${value.file}:${builtins.toString value.line}</link>
69+ in <literal>&lt;nixpkgs&gt;</literal>.
70+ </para>
71+ </section>
72+ '')
73+ relativeLocs);
74+
75+in pkgs.writeText
76+ "locations.xml"
77+ ''
78+ <section xmlns="http://docbook.org/ns/docbook"
79+ xmlns:xlink="http://www.w3.org/1999/xlink"
80+ version="5">
81+ <title>All the locations for every lib function</title>
82+ <para>This file is only for inclusion by other files.</para>
83+ ${xmlstrings}
84+ </section>
85+ ''
doc/manual.xml+21−26
@@ -1,29 +1,24 @@
11<book xmlns="http://docbook.org/ns/docbook"
22 xmlns:xi="http://www.w3.org/2001/XInclude">
3−
4− <info>
5−
6− <title>Nixpkgs Contributors Guide</title>
7−
8− <subtitle>Version <xi:include href=".version" parse="text" /></subtitle>
9−
10− </info>
11−
12− <xi:include href="introduction.xml" />
13− <xi:include href="quick-start.xml" />
14− <xi:include href="stdenv.xml" />
15− <xi:include href="multiple-output.xml" />
16− <xi:include href="cross-compilation.xml" />
17− <xi:include href="configuration.xml" />
18− <xi:include href="functions.xml" />
19− <xi:include href="meta.xml" />
20− <xi:include href="languages-frameworks/index.xml" />
21− <xi:include href="platform-notes.xml" />
22− <xi:include href="package-notes.xml" />
23− <xi:include href="overlays.xml" />
24− <xi:include href="coding-conventions.xml" />
25− <xi:include href="submitting-changes.xml" />
26− <xi:include href="reviewing-contributions.xml" />
27− <xi:include href="contributing.xml" />
28−
3+ <info>
4+ <title>Nixpkgs Contributors Guide</title>
5+ <subtitle>Version <xi:include href=".version" parse="text" />
6+ </subtitle>
7+ </info>
8+ <xi:include href="introduction.chapter.xml" />
9+ <xi:include href="quick-start.xml" />
10+ <xi:include href="stdenv.xml" />
11+ <xi:include href="multiple-output.xml" />
12+ <xi:include href="cross-compilation.xml" />
13+ <xi:include href="configuration.xml" />
14+ <xi:include href="functions.xml" />
15+ <xi:include href="meta.xml" />
16+ <xi:include href="languages-frameworks/index.xml" />
17+ <xi:include href="platform-notes.xml" />
18+ <xi:include href="package-notes.xml" />
19+ <xi:include href="overlays.xml" />
20+ <xi:include href="coding-conventions.xml" />
21+ <xi:include href="submitting-changes.xml" />
22+ <xi:include href="reviewing-contributions.xml" />
23+ <xi:include href="contributing.xml" />
2924</book>
doc/meta.xml+366−256
@@ -1,37 +1,34 @@
11<chapter xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="chap-meta">
4−
5−<title>Meta-attributes</title>
6−
7−<para>Nix packages can declare <emphasis>meta-attributes</emphasis>
8−that contain information about a package such as a description, its
9−homepage, its license, and so on. For instance, the GNU Hello package
10−has a <varname>meta</varname> declaration like this:
11−
4+ <title>Meta-attributes</title>
5+ <para>
6+ Nix packages can declare <emphasis>meta-attributes</emphasis> that contain
7+ information about a package such as a description, its homepage, its license,
8+ and so on. For instance, the GNU Hello package has a <varname>meta</varname>
9+ declaration like this:
1210<programlisting>
13−meta = {
11+meta = with stdenv.lib; {
1412 description = "A program that produces a familiar, friendly greeting";
1513 longDescription = ''
1614 GNU Hello is a program that prints "Hello, world!" when you run it.
1715 It is fully customizable.
1816 '';
1917 homepage = http://www.gnu.org/software/hello/manual/;
20− license = stdenv.lib.licenses.gpl3Plus;
21− maintainers = [ stdenv.lib.maintainers.eelco ];
22− platforms = stdenv.lib.platforms.all;
18+ license = licenses.gpl3Plus;
19+ maintainers = [ maintainers.eelco ];
20+ platforms = platforms.all;
2321};
2422</programlisting>
25−
26−</para>
27−
28−<para>Meta-attributes are not passed to the builder of the package.
29−Thus, a change to a meta-attribute doesn’t trigger a recompilation of
30−the package. The value of a meta-attribute must be a string.</para>
31−
32−<para>The meta-attributes of a package can be queried from the
33−command-line using <command>nix-env</command>:
34−
23+ </para>
24+ <para>
25+ Meta-attributes are not passed to the builder of the package. Thus, a change
26+ to a meta-attribute doesn’t trigger a recompilation of the package. The
27+ value of a meta-attribute must be a string.
28+ </para>
29+ <para>
30+ The meta-attributes of a package can be queried from the command-line using
31+ <command>nix-env</command>:
3532<screen>
3633$ nix-env -qa hello --json
3734{
@@ -53,7 +50,7 @@ $ nix-env -qa hello --json
5350 "x86_64-linux",
5451 "armv5tel-linux",
5552 "armv7l-linux",
56− "mips64el-linux",
53+ "mips32-linux",
5754 "x86_64-darwin",
5855 "i686-cygwin",
5956 "i686-freebsd",
@@ -70,252 +67,365 @@ $ nix-env -qa hello --json
7067
7168
7269</screen>
73−
74−<command>nix-env</command> knows about the
75−<varname>description</varname> field specifically:
76−
70+ <command>nix-env</command> knows about the <varname>description</varname>
71+ field specifically:
7772<screen>
7873$ nix-env -qa hello --description
7974hello-2.3 A program that produces a familiar, friendly greeting
8075</screen>
81−
82−</para>
83−
84−
85−<section xml:id="sec-standard-meta-attributes"><title>Standard
86−meta-attributes</title>
87−
88−<para>It is expected that each meta-attribute is one of the following:</para>
89−
90−<variablelist>
91−
92− <varlistentry>
93− <term><varname>description</varname></term>
94− <listitem><para>A short (one-line) description of the package.
95− This is shown by <command>nix-env -q --description</command> and
96− also on the Nixpkgs release pages.</para>
97−
98− <para>Don’t include a period at the end. Don’t include newline
99− characters. Capitalise the first character. For brevity, don’t
100− repeat the name of package — just describe what it does.</para>
101−
102− <para>Wrong: <literal>"libpng is a library that allows you to decode PNG images."</literal></para>
103−
104− <para>Right: <literal>"A library for decoding PNG images"</literal></para>
105−
76+ </para>
77+ <section xml:id="sec-standard-meta-attributes">
78+ <title>Standard meta-attributes</title>
79+
80+ <para>
81+ It is expected that each meta-attribute is one of the following:
82+ </para>
83+
84+ <variablelist>
85+ <varlistentry>
86+ <term>
87+ <varname>description</varname>
88+ </term>
89+ <listitem>
90+ <para>
91+ A short (one-line) description of the package. This is shown by
92+ <command>nix-env -q --description</command> and also on the Nixpkgs
93+ release pages.
94+ </para>
95+ <para>
96+ Don’t include a period at the end. Don’t include newline characters.
97+ Capitalise the first character. For brevity, don’t repeat the name of
98+ package — just describe what it does.
99+ </para>
100+ <para>
101+ Wrong: <literal>"libpng is a library that allows you to decode PNG
102+ images."</literal>
103+ </para>
104+ <para>
105+ Right: <literal>"A library for decoding PNG images"</literal>
106+ </para>
106107 </listitem>
107− </varlistentry>
108−
109− <varlistentry>
110− <term><varname>longDescription</varname></term>
111− <listitem><para>An arbitrarily long description of the
112− package.</para></listitem>
113− </varlistentry>
114−
115− <varlistentry>
116− <term><varname>branch</varname></term>
117− <listitem><para>Release branch. Used to specify that a package is not
118− going to receive updates that are not in this branch; for example, Linux
119− kernel 3.0 is supposed to be updated to 3.0.X, not 3.1.</para></listitem>
120− </varlistentry>
121−
122− <varlistentry>
123− <term><varname>homepage</varname></term>
124− <listitem><para>The package’s homepage. Example:
125− <literal>http://www.gnu.org/software/hello/manual/</literal></para></listitem>
126− </varlistentry>
127−
128− <varlistentry>
129− <term><varname>downloadPage</varname></term>
130− <listitem><para>The page where a link to the current version can be found. Example:
131− <literal>http://ftp.gnu.org/gnu/hello/</literal></para></listitem>
132− </varlistentry>
133−
134− <varlistentry>
135− <term><varname>license</varname></term>
108+ </varlistentry>
109+ <varlistentry>
110+ <term>
111+ <varname>longDescription</varname>
112+ </term>
136113 <listitem>
137− <para>
138− The license, or licenses, for the package. One from the attribute set
139− defined in <link
114+ <para>
115+ An arbitrarily long description of the package.
116+ </para>
117+ </listitem>
118+ </varlistentry>
119+ <varlistentry>
120+ <term>
121+ <varname>branch</varname>
122+ </term>
123+ <listitem>
124+ <para>
125+ Release branch. Used to specify that a package is not going to receive
126+ updates that are not in this branch; for example, Linux kernel 3.0 is
127+ supposed to be updated to 3.0.X, not 3.1.
128+ </para>
129+ </listitem>
130+ </varlistentry>
131+ <varlistentry>
132+ <term>
133+ <varname>homepage</varname>
134+ </term>
135+ <listitem>
136+ <para>
137+ The package’s homepage. Example:
138+ <literal>http://www.gnu.org/software/hello/manual/</literal>
139+ </para>
140+ </listitem>
141+ </varlistentry>
142+ <varlistentry>
143+ <term>
144+ <varname>downloadPage</varname>
145+ </term>
146+ <listitem>
147+ <para>
148+ The page where a link to the current version can be found. Example:
149+ <literal>http://ftp.gnu.org/gnu/hello/</literal>
150+ </para>
151+ </listitem>
152+ </varlistentry>
153+ <varlistentry>
154+ <term>
155+ <varname>license</varname>
156+ </term>
157+ <listitem>
158+ <para>
159+ The license, or licenses, for the package. One from the attribute set
160+ defined in
161+ <link
140162 xlink:href="https://github.com/NixOS/nixpkgs/blob/master/lib/licenses.nix">
141− <filename>nixpkgs/lib/licenses.nix</filename></link>. At this moment
142− using both a list of licenses and a single license is valid. If the
143− license field is in the form of a list representation, then it means
144− that parts of the package are licensed differently. Each license
145− should preferably be referenced by their attribute. The non-list
146− attribute value can also be a space delimited string representation of
147− the contained attribute shortNames or spdxIds. The following are all valid
148− examples:
149− <itemizedlist>
150− <listitem><para>Single license referenced by attribute (preferred)
151− <literal>stdenv.lib.licenses.gpl3</literal>.
152− </para></listitem>
153− <listitem><para>Single license referenced by its attribute shortName (frowned upon)
154− <literal>"gpl3"</literal>.
155− </para></listitem>
156− <listitem><para>Single license referenced by its attribute spdxId (frowned upon)
157− <literal>"GPL-3.0"</literal>.
158− </para></listitem>
159− <listitem><para>Multiple licenses referenced by attribute (preferred)
160− <literal>with stdenv.lib.licenses; [ asl20 free ofl ]</literal>.
161− </para></listitem>
162− <listitem><para>Multiple licenses referenced as a space delimited string of attribute shortNames (frowned upon)
163− <literal>"asl20 free ofl"</literal>.
164− </para></listitem>
165− </itemizedlist>
166− For details, see <xref linkend='sec-meta-license'/>.
167− </para>
163+ <filename>nixpkgs/lib/licenses.nix</filename></link>. At this moment
164+ using both a list of licenses and a single license is valid. If the
165+ license field is in the form of a list representation, then it means that
166+ parts of the package are licensed differently. Each license should
167+ preferably be referenced by their attribute. The non-list attribute value
168+ can also be a space delimited string representation of the contained
169+ attribute shortNames or spdxIds. The following are all valid examples:
170+ <itemizedlist>
171+ <listitem>
172+ <para>
173+ Single license referenced by attribute (preferred)
174+ <literal>stdenv.lib.licenses.gpl3</literal>.
175+ </para>
176+ </listitem>
177+ <listitem>
178+ <para>
179+ Single license referenced by its attribute shortName (frowned upon)
180+ <literal>"gpl3"</literal>.
181+ </para>
182+ </listitem>
183+ <listitem>
184+ <para>
185+ Single license referenced by its attribute spdxId (frowned upon)
186+ <literal>"GPL-3.0"</literal>.
187+ </para>
188+ </listitem>
189+ <listitem>
190+ <para>
191+ Multiple licenses referenced by attribute (preferred) <literal>with
192+ stdenv.lib.licenses; [ asl20 free ofl ]</literal>.
193+ </para>
194+ </listitem>
195+ <listitem>
196+ <para>
197+ Multiple licenses referenced as a space delimited string of attribute
198+ shortNames (frowned upon) <literal>"asl20 free ofl"</literal>.
199+ </para>
200+ </listitem>
201+ </itemizedlist>
202+ For details, see <xref linkend='sec-meta-license'/>.
203+ </para>
168204 </listitem>
169− </varlistentry>
170−
171− <varlistentry>
172− <term><varname>maintainers</varname></term>
173− <listitem><para>A list of names and e-mail addresses of the
174− maintainers of this Nix expression. If
175− you would like to be a maintainer of a package, you may want to add
176− yourself to <link
177− xlink:href="https://github.com/NixOS/nixpkgs/blob/master/lib/maintainers.nix"><filename>nixpkgs/lib/maintainers.nix</filename></link>
178− and write something like <literal>[ stdenv.lib.maintainers.alice
179− stdenv.lib.maintainers.bob ]</literal>.</para></listitem>
180− </varlistentry>
181−
182− <varlistentry>
183− <term><varname>priority</varname></term>
184− <listitem><para>The <emphasis>priority</emphasis> of the package,
185− used by <command>nix-env</command> to resolve file name conflicts
186− between packages. See the Nix manual page for
187− <command>nix-env</command> for details. Example:
188− <literal>"10"</literal> (a low-priority
189− package).</para></listitem>
190− </varlistentry>
191−
192− <varlistentry>
193− <term><varname>platforms</varname></term>
194− <listitem><para>The list of Nix platform types on which the
195− package is supported. Hydra builds packages according to the
196− platform specified. If no platform is specified, the package does
197− not have prebuilt binaries. An example is:
198−
205+ </varlistentry>
206+ <varlistentry>
207+ <term>
208+ <varname>maintainers</varname>
209+ </term>
210+ <listitem>
211+ <para>
212+ A list of names and e-mail addresses of the maintainers of this Nix
213+ expression. If you would like to be a maintainer of a package, you may
214+ want to add yourself to
215+ <link
216+ xlink:href="https://github.com/NixOS/nixpkgs/blob/master/maintainers/maintainer-list.nix"><filename>nixpkgs/maintainers/maintainer-list.nix</filename></link>
217+ and write something like <literal>[ stdenv.lib.maintainers.alice
218+ stdenv.lib.maintainers.bob ]</literal>.
219+ </para>
220+ </listitem>
221+ </varlistentry>
222+ <varlistentry>
223+ <term>
224+ <varname>priority</varname>
225+ </term>
226+ <listitem>
227+ <para>
228+ The <emphasis>priority</emphasis> of the package, used by
229+ <command>nix-env</command> to resolve file name conflicts between
230+ packages. See the Nix manual page for <command>nix-env</command> for
231+ details. Example: <literal>"10"</literal> (a low-priority package).
232+ </para>
233+ </listitem>
234+ </varlistentry>
235+ <varlistentry>
236+ <term>
237+ <varname>platforms</varname>
238+ </term>
239+ <listitem>
240+ <para>
241+ The list of Nix platform types on which the package is supported. Hydra
242+ builds packages according to the platform specified. If no platform is
243+ specified, the package does not have prebuilt binaries. An example is:
199244<programlisting>
200245meta.platforms = stdenv.lib.platforms.linux;
201246</programlisting>
202−
203− Attribute Set <varname>stdenv.lib.platforms</varname> defines
204− <link xlink:href="https://github.com/NixOS/nixpkgs/blob/master/lib/systems/doubles.nix">
205− various common lists</link> of platforms types.</para></listitem>
206− </varlistentry>
207−
208− <varlistentry>
209− <term><varname>hydraPlatforms</varname></term>
210− <listitem><para>The list of Nix platform types for which the Hydra
211− instance at <literal>hydra.nixos.org</literal> will build the
212− package. (Hydra is the Nix-based continuous build system.) It
213− defaults to the value of <varname>meta.platforms</varname>. Thus,
214− the only reason to set <varname>meta.hydraPlatforms</varname> is
215− if you want <literal>hydra.nixos.org</literal> to build the
216− package on a subset of <varname>meta.platforms</varname>, or not
217− at all, e.g.
218−
247+ Attribute Set <varname>stdenv.lib.platforms</varname> defines
248+ <link xlink:href="https://github.com/NixOS/nixpkgs/blob/master/lib/systems/doubles.nix">
249+ various common lists</link> of platforms types.
250+ </para>
251+ </listitem>
252+ </varlistentry>
253+ <varlistentry>
254+ <term>
255+ <varname>tests</varname>
256+ </term>
257+ <listitem>
258+ <warning>
259+ <para>
260+ This attribute is special in that it is not actually under the
261+ <literal>meta</literal> attribute set but rather under the
262+ <literal>passthru</literal> attribute set. This is due to a current
263+ limitation of Nix, and will change as soon as Nixpkgs will be able to
264+ depend on a new enough version of Nix. See
265+ <link xlink:href="https://github.com/NixOS/nix/issues/2532">the relevant
266+ issue</link> for more details.
267+ </para>
268+ </warning>
269+ <para>
270+ An attribute set with as values tests. A test is a derivation, which
271+ builds successfully when the test passes, and fails to build otherwise. A
272+ derivation that is a test needs to have <literal>meta.timeout</literal>
273+ defined.
274+ </para>
275+ <para>
276+ The NixOS tests are available as <literal>nixosTests</literal> in
277+ parameters of derivations. For instance, the OpenSMTPD derivation
278+ includes lines similar to:
279+<programlisting>
280+{ /* ... */, nixosTests }:
281+{
282+ # ...
283+ passthru.tests = {
284+ basic-functionality-and-dovecot-integration = nixosTests.opensmtpd;
285+ };
286+}
287+</programlisting>
288+ </para>
289+ </listitem>
290+ </varlistentry>
291+ <varlistentry>
292+ <term>
293+ <varname>timeout</varname>
294+ </term>
295+ <listitem>
296+ <para>
297+ A timeout (in seconds) for building the derivation. If the derivation
298+ takes longer than this time to build, it can fail due to breaking the
299+ timeout. However, all computers do not have the same computing power,
300+ hence some builders may decide to apply a multiplicative factor to this
301+ value. When filling this value in, try to keep it approximately
302+ consistent with other values already present in
303+ <literal>nixpkgs</literal>.
304+ </para>
305+ </listitem>
306+ </varlistentry>
307+ <varlistentry>
308+ <term>
309+ <varname>hydraPlatforms</varname>
310+ </term>
311+ <listitem>
312+ <para>
313+ The list of Nix platform types for which the Hydra instance at
314+ <literal>hydra.nixos.org</literal> will build the package. (Hydra is the
315+ Nix-based continuous build system.) It defaults to the value of
316+ <varname>meta.platforms</varname>. Thus, the only reason to set
317+ <varname>meta.hydraPlatforms</varname> is if you want
318+ <literal>hydra.nixos.org</literal> to build the package on a subset of
319+ <varname>meta.platforms</varname>, or not at all, e.g.
219320<programlisting>
220321meta.platforms = stdenv.lib.platforms.linux;
221322meta.hydraPlatforms = [];
222323</programlisting>
223−
224− </para></listitem>
225− </varlistentry>
226−
227− <varlistentry>
228− <term><varname>broken</varname></term>
229− <listitem><para>If set to <literal>true</literal>, the package is
230− marked as “broken”, meaning that it won’t show up in
231− <literal>nix-env -qa</literal>, and cannot be built or installed.
232− Such packages should be removed from Nixpkgs eventually unless
233− they are fixed.</para></listitem>
234− </varlistentry>
235−
236− <varlistentry>
237− <term><varname>updateWalker</varname></term>
238− <listitem><para>If set to <literal>true</literal>, the package is
239− tested to be updated correctly by the <literal>update-walker.sh</literal>
240− script without additional settings. Such packages have
241− <varname>meta.version</varname> set and their homepage (or
242− the page specified by <varname>meta.downloadPage</varname>) contains
243− a direct link to the package tarball.</para></listitem>
244− </varlistentry>
245−
246−</variablelist>
247−
248−
249−</section>
250−
251−
252−<section xml:id="sec-meta-license"><title>Licenses</title>
253−
254−<para>The <varname>meta.license</varname> attribute should preferrably contain
255−a value from <varname>stdenv.lib.licenses</varname> defined in
256−<link xlink:href="https://github.com/NixOS/nixpkgs/blob/master/lib/licenses.nix">
257−<filename>nixpkgs/lib/licenses.nix</filename></link>,
258−or in-place license description of the same format if the license is
259−unlikely to be useful in another expression.</para>
260−
261−<para>Although it's typically better to indicate the specific license,
262−a few generic options are available:
263−
264−<variablelist>
265−
266− <varlistentry>
267− <term><varname>stdenv.lib.licenses.free</varname>,
268− <varname>"free"</varname></term>
269−
270− <listitem><para>Catch-all for free software licenses not listed
271− above.</para></listitem>
272− </varlistentry>
273−
274− <varlistentry>
275− <term><varname>stdenv.lib.licenses.unfreeRedistributable</varname>,
276− <varname>"unfree-redistributable"</varname></term>
277−
278− <listitem><para>Unfree package that can be redistributed in binary
279− form. That is, it’s legal to redistribute the
280− <emphasis>output</emphasis> of the derivation. This means that
281− the package can be included in the Nixpkgs
282− channel.</para>
283−
284− <para>Sometimes proprietary software can only be redistributed
285− unmodified. Make sure the builder doesn’t actually modify the
286− original binaries; otherwise we’re breaking the license. For
287− instance, the NVIDIA X11 drivers can be redistributed unmodified,
288− but our builder applies <command>patchelf</command> to make them
289− work. Thus, its license is <varname>"unfree"</varname> and it
290− cannot be included in the Nixpkgs channel.</para></listitem>
291− </varlistentry>
292−
293− <varlistentry>
294− <term><varname>stdenv.lib.licenses.unfree</varname>,
295− <varname>"unfree"</varname></term>
296−
297− <listitem><para>Unfree package that cannot be redistributed. You
298− can build it yourself, but you cannot redistribute the output of
299− the derivation. Thus it cannot be included in the Nixpkgs
300− channel.</para></listitem>
301− </varlistentry>
302−
303− <varlistentry>
304− <term><varname>stdenv.lib.licenses.unfreeRedistributableFirmware</varname>,
305− <varname>"unfree-redistributable-firmware"</varname></term>
306−
307− <listitem><para>This package supplies unfree, redistributable
308− firmware. This is a separate value from
309− <varname>unfree-redistributable</varname> because not everybody
310− cares whether firmware is free.</para></listitem>
311− </varlistentry>
312−
313−</variablelist>
314−
315−</para>
316−
317−
318−</section>
319−
320−
324+ </para>
325+ </listitem>
326+ </varlistentry>
327+ <varlistentry>
328+ <term>
329+ <varname>broken</varname>
330+ </term>
331+ <listitem>
332+ <para>
333+ If set to <literal>true</literal>, the package is marked as “broken”,
334+ meaning that it won’t show up in <literal>nix-env -qa</literal>, and
335+ cannot be built or installed. Such packages should be removed from
336+ Nixpkgs eventually unless they are fixed.
337+ </para>
338+ </listitem>
339+ </varlistentry>
340+ <varlistentry>
341+ <term>
342+ <varname>updateWalker</varname>
343+ </term>
344+ <listitem>
345+ <para>
346+ If set to <literal>true</literal>, the package is tested to be updated
347+ correctly by the <literal>update-walker.sh</literal> script without
348+ additional settings. Such packages have <varname>meta.version</varname>
349+ set and their homepage (or the page specified by
350+ <varname>meta.downloadPage</varname>) contains a direct link to the
351+ package tarball.
352+ </para>
353+ </listitem>
354+ </varlistentry>
355+ </variablelist>
356+ </section>
357+ <section xml:id="sec-meta-license">
358+ <title>Licenses</title>
359+
360+ <para>
361+ The <varname>meta.license</varname> attribute should preferrably contain a
362+ value from <varname>stdenv.lib.licenses</varname> defined in
363+ <link xlink:href="https://github.com/NixOS/nixpkgs/blob/master/lib/licenses.nix">
364+ <filename>nixpkgs/lib/licenses.nix</filename></link>, or in-place license
365+ description of the same format if the license is unlikely to be useful in
366+ another expression.
367+ </para>
368+
369+ <para>
370+ Although it's typically better to indicate the specific license, a few
371+ generic options are available:
372+ <variablelist>
373+ <varlistentry>
374+ <term>
375+ <varname>stdenv.lib.licenses.free</varname>, <varname>"free"</varname>
376+ </term>
377+ <listitem>
378+ <para>
379+ Catch-all for free software licenses not listed above.
380+ </para>
381+ </listitem>
382+ </varlistentry>
383+ <varlistentry>
384+ <term>
385+ <varname>stdenv.lib.licenses.unfreeRedistributable</varname>, <varname>"unfree-redistributable"</varname>
386+ </term>
387+ <listitem>
388+ <para>
389+ Unfree package that can be redistributed in binary form. That is, it’s
390+ legal to redistribute the <emphasis>output</emphasis> of the derivation.
391+ This means that the package can be included in the Nixpkgs channel.
392+ </para>
393+ <para>
394+ Sometimes proprietary software can only be redistributed unmodified.
395+ Make sure the builder doesn’t actually modify the original binaries;
396+ otherwise we’re breaking the license. For instance, the NVIDIA X11
397+ drivers can be redistributed unmodified, but our builder applies
398+ <command>patchelf</command> to make them work. Thus, its license is
399+ <varname>"unfree"</varname> and it cannot be included in the Nixpkgs
400+ channel.
401+ </para>
402+ </listitem>
403+ </varlistentry>
404+ <varlistentry>
405+ <term>
406+ <varname>stdenv.lib.licenses.unfree</varname>, <varname>"unfree"</varname>
407+ </term>
408+ <listitem>
409+ <para>
410+ Unfree package that cannot be redistributed. You can build it yourself,
411+ but you cannot redistribute the output of the derivation. Thus it cannot
412+ be included in the Nixpkgs channel.
413+ </para>
414+ </listitem>
415+ </varlistentry>
416+ <varlistentry>
417+ <term>
418+ <varname>stdenv.lib.licenses.unfreeRedistributableFirmware</varname>, <varname>"unfree-redistributable-firmware"</varname>
419+ </term>
420+ <listitem>
421+ <para>
422+ This package supplies unfree, redistributable firmware. This is a
423+ separate value from <varname>unfree-redistributable</varname> because
424+ not everybody cares whether firmware is free.
425+ </para>
426+ </listitem>
427+ </varlistentry>
428+ </variablelist>
429+ </para>
430+ </section>
321431</chapter>
doc/multiple-output.xml+300−80
@@ -5,99 +5,319 @@
55<chapter xmlns="http://docbook.org/ns/docbook"
66 xmlns:xlink="http://www.w3.org/1999/xlink"
77 xml:id="chap-multiple-output">
8+ <title>Multiple-output packages</title>
9+ <section xml:id="sec-multiple-outputs-introduction">
10+ <title>Introduction</title>
811
9−<title>Multiple-output packages</title>
12+ <para>
13+ The Nix language allows a derivation to produce multiple outputs, which is
14+ similar to what is utilized by other Linux distribution packaging systems.
15+ The outputs reside in separate nix store paths, so they can be mostly
16+ handled independently of each other, including passing to build inputs,
17+ garbage collection or binary substitution. The exception is that building
18+ from source always produces all the outputs.
19+ </para>
1020
11−<section><title>Introduction</title>
12− <para>The Nix language allows a derivation to produce multiple outputs, which is similar to what is utilized by other Linux distribution packaging systems. The outputs reside in separate nix store paths, so they can be mostly handled independently of each other, including passing to build inputs, garbage collection or binary substitution. The exception is that building from source always produces all the outputs.</para>
13− <para>The main motivation is to save disk space by reducing runtime closure sizes; consequently also sizes of substituted binaries get reduced. Splitting can be used to have more granular runtime dependencies, for example the typical reduction is to split away development-only files, as those are typically not needed during runtime. As a result, closure sizes of many packages can get reduced to a half or even much less.</para>
14− <note><para>The reduction effects could be instead achieved by building the parts in completely separate derivations. That would often additionally reduce build-time closures, but it tends to be much harder to write such derivations, as build systems typically assume all parts are being built at once. This compromise approach of single source package producing multiple binary packages is also utilized often by rpm and deb.</para></note>
15−</section>
21+ <para>
22+ The main motivation is to save disk space by reducing runtime closure sizes;
23+ consequently also sizes of substituted binaries get reduced. Splitting can
24+ be used to have more granular runtime dependencies, for example the typical
25+ reduction is to split away development-only files, as those are typically
26+ not needed during runtime. As a result, closure sizes of many packages can
27+ get reduced to a half or even much less.
28+ </para>
29+
30+ <note>
31+ <para>
32+ The reduction effects could be instead achieved by building the parts in
33+ completely separate derivations. That would often additionally reduce
34+ build-time closures, but it tends to be much harder to write such
35+ derivations, as build systems typically assume all parts are being built at
36+ once. This compromise approach of single source package producing multiple
37+ binary packages is also utilized often by rpm and deb.
38+ </para>
39+ </note>
40+ </section>
41+ <section xml:id="sec-multiple-outputs-installing">
42+ <title>Installing a split package</title>
43+
44+ <para>
45+ When installing a package via <varname>systemPackages</varname> or
46+ <command>nix-env</command> you have several options:
47+ </para>
1648
17−<section><title>Installing a split package</title>
18− <para>When installing a package via <varname>systemPackages</varname> or <command>nix-env</command> you have several options:</para>
1949 <itemizedlist>
20− <listitem><para>You can install particular outputs explicitly, as each is available in the Nix language as an attribute of the package. The <varname>outputs</varname> attribute contains a list of output names.</para></listitem>
21− <listitem><para>You can let it use the default outputs. These are handled by <varname>meta.outputsToInstall</varname> attribute that contains a list of output names.</para>
22− <para>TODO: more about tweaking the attribute, etc.</para></listitem>
23− <listitem><para>NixOS provides configuration option <varname>environment.extraOutputsToInstall</varname> that allows adding extra outputs of <varname>environment.systemPackages</varname> atop the default ones. It's mainly meant for documentation and debug symbols, and it's also modified by specific options.</para>
24− <note><para>At this moment there is no similar configurability for packages installed by <command>nix-env</command>. You can still use approach from <xref linkend="sec-modify-via-packageOverrides" /> to override <varname>meta.outputsToInstall</varname> attributes, but that's a rather inconvenient way.</para></note>
25− </listitem>
50+ <listitem>
51+ <para>
52+ You can install particular outputs explicitly, as each is available in the
53+ Nix language as an attribute of the package. The
54+ <varname>outputs</varname> attribute contains a list of output names.
55+ </para>
56+ </listitem>
57+ <listitem>
58+ <para>
59+ You can let it use the default outputs. These are handled by
60+ <varname>meta.outputsToInstall</varname> attribute that contains a list of
61+ output names.
62+ </para>
63+ <para>
64+ TODO: more about tweaking the attribute, etc.
65+ </para>
66+ </listitem>
67+ <listitem>
68+ <para>
69+ NixOS provides configuration option
70+ <varname>environment.extraOutputsToInstall</varname> that allows adding
71+ extra outputs of <varname>environment.systemPackages</varname> atop the
72+ default ones. It's mainly meant for documentation and debug symbols, and
73+ it's also modified by specific options.
74+ </para>
75+ <note>
76+ <para>
77+ At this moment there is no similar configurability for packages installed
78+ by <command>nix-env</command>. You can still use approach from
79+ <xref linkend="sec-modify-via-packageOverrides" /> to override
80+ <varname>meta.outputsToInstall</varname> attributes, but that's a rather
81+ inconvenient way.
82+ </para>
83+ </note>
84+ </listitem>
2685 </itemizedlist>
27−</section>
86+ </section>
87+ <section xml:id="sec-multiple-outputs-using-split-packages">
88+ <title>Using a split package</title>
2889
29−<section><title>Using a split package</title>
30− <para>In the Nix language the individual outputs can be reached explicitly as attributes, e.g. <varname>coreutils.info</varname>, but the typical case is just using packages as build inputs.</para>
31− <para>When a multiple-output derivation gets into a build input of another derivation, the <varname>dev</varname> output is added if it exists, otherwise the first output is added. In addition to that, <varname>propagatedBuildOutputs</varname> of that package which by default contain <varname>$outputBin</varname> and <varname>$outputLib</varname> are also added. (See <xref linkend="multiple-output-file-type-groups" />.)</para>
32−</section>
90+ <para>
91+ In the Nix language the individual outputs can be reached explicitly as
92+ attributes, e.g. <varname>coreutils.info</varname>, but the typical case is
93+ just using packages as build inputs.
94+ </para>
3395
96+ <para>
97+ When a multiple-output derivation gets into a build input of another
98+ derivation, the <varname>dev</varname> output is added if it exists,
99+ otherwise the first output is added. In addition to that,
100+ <varname>propagatedBuildOutputs</varname> of that package which by default
101+ contain <varname>$outputBin</varname> and <varname>$outputLib</varname> are
102+ also added. (See <xref linkend="multiple-output-file-type-groups" />.)
103+ </para>
104+ </section>
105+ <section xml:id="sec-multiple-outputs-">
106+ <title>Writing a split derivation</title>
34107
35−<section><title>Writing a split derivation</title>
36− <para>Here you find how to write a derivation that produces multiple outputs.</para>
37− <para>In nixpkgs there is a framework supporting multiple-output derivations. It tries to cover most cases by default behavior. You can find the source separated in &lt;<filename>nixpkgs/pkgs/build-support/setup-hooks/multiple-outputs.sh</filename>&gt;; it's relatively well-readable. The whole machinery is triggered by defining the <varname>outputs</varname> attribute to contain the list of desired output names (strings).</para>
38− <programlisting>outputs = [ "bin" "dev" "out" "doc" ];</programlisting>
39− <para>Often such a single line is enough. For each output an equally named environment variable is passed to the builder and contains the path in nix store for that output. By convention, the first output should contain the executable programs provided by the package as that output is used by Nix in string conversions, allowing references to binaries like <literal>${pkgs.perl}/bin/perl</literal> to always work. Typically you also want to have the main <varname>out</varname> output, as it catches any files that didn't get elsewhere.</para>
108+ <para>
109+ Here you find how to write a derivation that produces multiple outputs.
110+ </para>
40111
41− <note><para>There is a special handling of the <varname>debug</varname> output, described at <xref linkend="stdenv-separateDebugInfo" />.</para></note>
112+ <para>
113+ In nixpkgs there is a framework supporting multiple-output derivations. It
114+ tries to cover most cases by default behavior. You can find the source
115+ separated in
116+ &lt;<filename>nixpkgs/pkgs/build-support/setup-hooks/multiple-outputs.sh</filename>&gt;;
117+ it's relatively well-readable. The whole machinery is triggered by defining
118+ the <varname>outputs</varname> attribute to contain the list of desired
119+ output names (strings).
120+ </para>
42121
43− <section xml:id="multiple-output-file-type-groups">
44− <title>File type groups</title>
45− <para>The support code currently recognizes some particular kinds of outputs and either instructs the build system of the package to put files into their desired outputs or it moves the files during the fixup phase. Each group of file types has an <varname>outputFoo</varname> variable specifying the output name where they should go. If that variable isn't defined by the derivation writer, it is guessed &ndash; a default output name is defined, falling back to other possibilities if the output isn't defined.</para>
46− <variablelist>
47−
48− <varlistentry><term><varname>
49− $outputDev</varname></term><listitem><para>
50− is for development-only files. These include C(++) headers, pkg-config, cmake and aclocal files. They go to <varname>dev</varname> or <varname>out</varname> by default.
51− </para></listitem>
52− </varlistentry>
53−
54− <varlistentry><term><varname>
55− $outputBin</varname></term><listitem><para>
56− is meant for user-facing binaries, typically residing in bin/. They go to <varname>bin</varname> or <varname>out</varname> by default.
57− </para></listitem></varlistentry>
58−
59− <varlistentry><term><varname>
60− $outputLib</varname></term><listitem><para>
61− is meant for libraries, typically residing in <filename>lib/</filename> and <filename>libexec/</filename>. They go to <varname>lib</varname> or <varname>out</varname> by default.
62− </para></listitem></varlistentry>
63−
64− <varlistentry><term><varname>
65− $outputDoc</varname></term><listitem><para>
66− is for user documentation, typically residing in <filename>share/doc/</filename>. It goes to <varname>doc</varname> or <varname>out</varname> by default.
67− </para></listitem></varlistentry>
68−
69− <varlistentry><term><varname>
70− $outputDevdoc</varname></term><listitem><para>
71− is for <emphasis>developer</emphasis> documentation. Currently we count gtk-doc and devhelp books in there. It goes to <varname>devdoc</varname> or is removed (!) by default. This is because e.g. gtk-doc tends to be rather large and completely unused by nixpkgs users.
72− </para></listitem></varlistentry>
73−
74− <varlistentry><term><varname>
75− $outputMan</varname></term><listitem><para>
76− is for man pages (except for section 3). They go to <varname>man</varname> or <varname>$outputBin</varname> by default.
77− </para></listitem></varlistentry>
78−
79− <varlistentry><term><varname>
80− $outputDevman</varname></term><listitem><para>
81− is for section 3 man pages. They go to <varname>devman</varname> or <varname>$outputMan</varname> by default.
82− </para></listitem></varlistentry>
83−
84− <varlistentry><term><varname>
85− $outputInfo</varname></term><listitem><para>
86− is for info pages. They go to <varname>info</varname> or <varname>$outputBin</varname> by default.
87− </para></listitem></varlistentry>
88−
89− </variablelist>
122+<programlisting>outputs = [ "bin" "dev" "out" "doc" ];</programlisting>
123+
124+ <para>
125+ Often such a single line is enough. For each output an equally named
126+ environment variable is passed to the builder and contains the path in nix
127+ store for that output. Typically you also want to have the main
128+ <varname>out</varname> output, as it catches any files that didn't get
129+ elsewhere.
130+ </para>
131+
132+ <note>
133+ <para>
134+ There is a special handling of the <varname>debug</varname> output,
135+ described at <xref linkend="stdenv-separateDebugInfo" />.
136+ </para>
137+ </note>
138+
139+ <section xml:id="multiple-output-file-binaries-first-convention">
140+ <title><quote>Binaries first</quote></title>
141+
142+ <para>
143+ A commonly adopted convention in <literal>nixpkgs</literal> is that
144+ executables provided by the package are contained within its first output.
145+ This convention allows the dependent packages to reference the executables
146+ provided by packages in a uniform manner. For instance, provided with the
147+ knowledge that the <literal>perl</literal> package contains a
148+ <literal>perl</literal> executable it can be referenced as
149+ <literal>${pkgs.perl}/bin/perl</literal> within a Nix derivation that needs
150+ to execute a Perl script.
151+ </para>
152+
153+ <para>
154+ The <literal>glibc</literal> package is a deliberate single exception to
155+ the <quote>binaries first</quote> convention. The <literal>glibc</literal>
156+ has <literal>libs</literal> as its first output allowing the libraries
157+ provided by <literal>glibc</literal> to be referenced directly (e.g.
158+ <literal>${stdenv.glibc}/lib/ld-linux-x86-64.so.2</literal>). The
159+ executables provided by <literal>glibc</literal> can be accessed via its
160+ <literal>bin</literal> attribute (e.g.
161+ <literal>${stdenv.glibc.bin}/bin/ldd</literal>).
162+ </para>
163+
164+ <para>
165+ The reason for why <literal>glibc</literal> deviates from the convention is
166+ because referencing a library provided by <literal>glibc</literal> is a
167+ very common operation among Nix packages. For instance, third-party
168+ executables packaged by Nix are typically patched and relinked with the
169+ relevant version of <literal>glibc</literal> libraries from Nix packages
170+ (please see the documentation on
171+ <link xlink:href="https://nixos.org/patchelf.html">patchelf</link> for more
172+ details).
173+ </para>
90174 </section>
91175
92− <section><title>Common caveats</title>
93− <itemizedlist>
94− <listitem><para>Some configure scripts don't like some of the parameters passed by default by the framework, e.g. <literal>--docdir=/foo/bar</literal>. You can disable this by setting <literal>setOutputFlags = false;</literal>.</para></listitem>
95− <listitem><para>The outputs of a single derivation can retain references to each other, but note that circular references are not allowed. (And each strongly-connected component would act as a single output anyway.)</para></listitem>
96− <listitem><para>Most of split packages contain their core functionality in libraries. These libraries tend to refer to various kind of data that typically gets into <varname>out</varname>, e.g. locale strings, so there is often no advantage in separating the libraries into <varname>lib</varname>, as keeping them in <varname>out</varname> is easier.</para></listitem>
97− <listitem><para>Some packages have hidden assumptions on install paths, which complicates splitting.</para></listitem>
98− </itemizedlist>
176+ <section xml:id="multiple-output-file-type-groups">
177+ <title>File type groups</title>
178+
179+ <para>
180+ The support code currently recognizes some particular kinds of outputs and
181+ either instructs the build system of the package to put files into their
182+ desired outputs or it moves the files during the fixup phase. Each group of
183+ file types has an <varname>outputFoo</varname> variable specifying the
184+ output name where they should go. If that variable isn't defined by the
185+ derivation writer, it is guessed &ndash; a default output name is defined,
186+ falling back to other possibilities if the output isn't defined.
187+ </para>
188+
189+ <variablelist>
190+ <varlistentry>
191+ <term>
192+ <varname> $outputDev</varname>
193+ </term>
194+ <listitem>
195+ <para>
196+ is for development-only files. These include C(++) headers, pkg-config,
197+ cmake and aclocal files. They go to <varname>dev</varname> or
198+ <varname>out</varname> by default.
199+ </para>
200+ </listitem>
201+ </varlistentry>
202+ <varlistentry>
203+ <term>
204+ <varname> $outputBin</varname>
205+ </term>
206+ <listitem>
207+ <para>
208+ is meant for user-facing binaries, typically residing in bin/. They go
209+ to <varname>bin</varname> or <varname>out</varname> by default.
210+ </para>
211+ </listitem>
212+ </varlistentry>
213+ <varlistentry>
214+ <term>
215+ <varname> $outputLib</varname>
216+ </term>
217+ <listitem>
218+ <para>
219+ is meant for libraries, typically residing in <filename>lib/</filename>
220+ and <filename>libexec/</filename>. They go to <varname>lib</varname> or
221+ <varname>out</varname> by default.
222+ </para>
223+ </listitem>
224+ </varlistentry>
225+ <varlistentry>
226+ <term>
227+ <varname> $outputDoc</varname>
228+ </term>
229+ <listitem>
230+ <para>
231+ is for user documentation, typically residing in
232+ <filename>share/doc/</filename>. It goes to <varname>doc</varname> or
233+ <varname>out</varname> by default.
234+ </para>
235+ </listitem>
236+ </varlistentry>
237+ <varlistentry>
238+ <term>
239+ <varname> $outputDevdoc</varname>
240+ </term>
241+ <listitem>
242+ <para>
243+ is for <emphasis>developer</emphasis> documentation. Currently we count
244+ gtk-doc and devhelp books in there. It goes to <varname>devdoc</varname>
245+ or is removed (!) by default. This is because e.g. gtk-doc tends to be
246+ rather large and completely unused by nixpkgs users.
247+ </para>
248+ </listitem>
249+ </varlistentry>
250+ <varlistentry>
251+ <term>
252+ <varname> $outputMan</varname>
253+ </term>
254+ <listitem>
255+ <para>
256+ is for man pages (except for section 3). They go to
257+ <varname>man</varname> or <varname>$outputBin</varname> by default.
258+ </para>
259+ </listitem>
260+ </varlistentry>
261+ <varlistentry>
262+ <term>
263+ <varname> $outputDevman</varname>
264+ </term>
265+ <listitem>
266+ <para>
267+ is for section 3 man pages. They go to <varname>devman</varname> or
268+ <varname>$outputMan</varname> by default.
269+ </para>
270+ </listitem>
271+ </varlistentry>
272+ <varlistentry>
273+ <term>
274+ <varname> $outputInfo</varname>
275+ </term>
276+ <listitem>
277+ <para>
278+ is for info pages. They go to <varname>info</varname> or
279+ <varname>$outputBin</varname> by default.
280+ </para>
281+ </listitem>
282+ </varlistentry>
283+ </variablelist>
99284 </section>
100285
101−</section><!--Writing a split derivation-->
286+ <section xml:id="sec-multiple-outputs-caveats">
287+ <title>Common caveats</title>
102288
289+ <itemizedlist>
290+ <listitem>
291+ <para>
292+ Some configure scripts don't like some of the parameters passed by
293+ default by the framework, e.g. <literal>--docdir=/foo/bar</literal>. You
294+ can disable this by setting <literal>setOutputFlags = false;</literal>.
295+ </para>
296+ </listitem>
297+ <listitem>
298+ <para>
299+ The outputs of a single derivation can retain references to each other,
300+ but note that circular references are not allowed. (And each
301+ strongly-connected component would act as a single output anyway.)
302+ </para>
303+ </listitem>
304+ <listitem>
305+ <para>
306+ Most of split packages contain their core functionality in libraries.
307+ These libraries tend to refer to various kind of data that typically gets
308+ into <varname>out</varname>, e.g. locale strings, so there is often no
309+ advantage in separating the libraries into <varname>lib</varname>, as
310+ keeping them in <varname>out</varname> is easier.
311+ </para>
312+ </listitem>
313+ <listitem>
314+ <para>
315+ Some packages have hidden assumptions on install paths, which complicates
316+ splitting.
317+ </para>
318+ </listitem>
319+ </itemizedlist>
320+ </section>
321+ </section>
322+<!--Writing a split derivation-->
103323</chapter>
doc/old/cross.txt+2−2
@@ -64,7 +64,7 @@ stdenv.mkDerivation {
6464 sha256 = "1ian3kwh2vg6hr3ymrv48s04gijs539vzrq62xr76bxbhbwnz2np";
6565 };
6666 inherit noSysDirs;
67− configureFlags = "--target=arm-linux";
67+ configureFlags = [ "--target=arm-linux" ];
6868}
6969---
7070
@@ -78,7 +78,7 @@ Step 2: build kernel headers for the target architecture
7878---
7979{stdenv, fetchurl}:
8080
81−assert stdenv.system == "i686-linux";
81+assert stdenv.buildPlatform.system == "i686-linux";
8282
8383stdenv.mkDerivation {
8484 name = "linux-headers-2.6.13.1-arm";
doc/overlays.xml+172−111
@@ -1,95 +1,148 @@
11<chapter xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="chap-overlays">
4−
5−<title>Overlays</title>
6−
7−<para>This chapter describes how to extend and change Nixpkgs packages using
8−overlays. Overlays are used to add layers in the fix-point used by Nixpkgs
9−to compose the set of all packages.</para>
10−
11−<para>Nixpkgs can be configured with a list of overlays, which are
12−applied in order. This means that the order of the overlays can be significant
13−if multiple layers override the same package.</para>
14−
4+ <title>Overlays</title>
5+ <para>
6+ This chapter describes how to extend and change Nixpkgs packages using
7+ overlays. Overlays are used to add layers in the fix-point used by Nixpkgs to
8+ compose the set of all packages.
9+ </para>
10+ <para>
11+ Nixpkgs can be configured with a list of overlays, which are applied in
12+ order. This means that the order of the overlays can be significant if
13+ multiple layers override the same package.
14+ </para>
1515<!--============================================================-->
16−
17−<section xml:id="sec-overlays-install">
18−<title>Installing overlays</title>
19−
20−<para>The list of overlays is determined as follows.</para>
21−
22−<para>If the <varname>overlays</varname> argument is not provided explicitly, we look for overlays in a path. The path
23−is determined as follows:
24−
25−<orderedlist>
26−
27− <listitem>
28− <para>First, if an <varname>overlays</varname> argument to the nixpkgs function itself is given,
29− then that is used.</para>
30−
31− <para>This can be passed explicitly when importing nipxkgs, for example
32− <literal>import &lt;nixpkgs> { overlays = [ overlay1 overlay2 ]; }</literal>.</para>
33− </listitem>
34−
35− <listitem>
36− <para>Otherwise, if the Nix path entry <literal>&lt;nixpkgs-overlays></literal> exists, we look for overlays
37− at that path, as described below.</para>
38−
39− <para>See the section on <literal>NIX_PATH</literal> in the Nix manual for more details on how to
40− set a value for <literal>&lt;nixpkgs-overlays>.</literal></para>
41− </listitem>
42−
43− <listitem>
44− <para>If one of <filename>~/.config/nixpkgs/overlays.nix</filename> and
45− <filename>~/.config/nixpkgs/overlays/</filename> exists, then we look for overlays at that path, as
46− described below. It is an error if both exist.</para>
47− </listitem>
48−
49−</orderedlist>
50−</para>
51−
52−<para>If we are looking for overlays at a path, then there are two cases:
53−<itemizedlist>
54− <listitem>
55− <para>If the path is a file, then the file is imported as a Nix expression and used as the list of
56− overlays.</para>
57− </listitem>
58−
59− <listitem>
60− <para>If the path is a directory, then we take the content of the directory, order it
61− lexicographically, and attempt to interpret each as an overlay by:
16+ <section xml:id="sec-overlays-install">
17+ <title>Installing overlays</title>
18+
19+ <para>
20+ The list of overlays can be set either explicitly in a Nix expression, or
21+ through <literal>&lt;nixpkgs-overlays></literal> or user configuration
22+ files.
23+ </para>
24+
25+ <section xml:id="sec-overlays-argument">
26+ <title>Set overlays in NixOS or Nix expressions</title>
27+
28+ <para>
29+ On a NixOS system the value of the <literal>nixpkgs.overlays</literal>
30+ option, if present, is passed to the system Nixpkgs directly as an
31+ argument. Note that this does not affect the overlays for non-NixOS
32+ operations (e.g. <literal>nix-env</literal>), which are
33+ <link xlink:href="#sec-overlays-lookup">looked</link> up independently.
34+ </para>
35+
36+ <para>
37+ The list of overlays can be passed explicitly when importing nixpkgs, for
38+ example <literal>import &lt;nixpkgs> { overlays = [ overlay1 overlay2 ];
39+ }</literal>.
40+ </para>
41+
42+ <para>
43+ Further overlays can be added by calling the <literal>pkgs.extend</literal>
44+ or <literal>pkgs.appendOverlays</literal>, although it is often preferable
45+ to avoid these functions, because they recompute the Nixpkgs fixpoint,
46+ which is somewhat expensive to do.
47+ </para>
48+ </section>
49+
50+ <section xml:id="sec-overlays-lookup">
51+ <title>Install overlays via configuration lookup</title>
52+
53+ <para>
54+ The list of overlays is determined as follows.
55+ </para>
56+
57+ <para>
58+ <orderedlist>
59+ <listitem>
60+ <para>
61+ First, if an
62+ <link xlink:href="#sec-overlays-argument"><varname>overlays</varname>
63+ argument</link> to the nixpkgs function itself is given, then that is
64+ used and no path lookup will be performed.
65+ </para>
66+ </listitem>
67+ <listitem>
68+ <para>
69+ Otherwise, if the Nix path entry
70+ <literal>&lt;nixpkgs-overlays></literal> exists, we look for overlays at
71+ that path, as described below.
72+ </para>
73+ <para>
74+ See the section on <literal>NIX_PATH</literal> in the Nix manual for
75+ more details on how to set a value for
76+ <literal>&lt;nixpkgs-overlays>.</literal>
77+ </para>
78+ </listitem>
79+ <listitem>
80+ <para>
81+ If one of <filename>~/.config/nixpkgs/overlays.nix</filename> and
82+ <filename>~/.config/nixpkgs/overlays/</filename> exists, then we look
83+ for overlays at that path, as described below. It is an error if both
84+ exist.
85+ </para>
86+ </listitem>
87+ </orderedlist>
88+ </para>
89+
90+ <para>
91+ If we are looking for overlays at a path, then there are two cases:
6292 <itemizedlist>
63− <listitem>
64− <para>Importing the file, if it is a <literal>.nix</literal> file.</para>
65− </listitem>
66− <listitem>
67− <para>Importing a top-level <filename>default.nix</filename> file, if it is a directory.</para>
68− </listitem>
93+ <listitem>
94+ <para>
95+ If the path is a file, then the file is imported as a Nix expression and
96+ used as the list of overlays.
97+ </para>
98+ </listitem>
99+ <listitem>
100+ <para>
101+ If the path is a directory, then we take the content of the directory,
102+ order it lexicographically, and attempt to interpret each as an overlay
103+ by:
104+ <itemizedlist>
105+ <listitem>
106+ <para>
107+ Importing the file, if it is a <literal>.nix</literal> file.
108+ </para>
109+ </listitem>
110+ <listitem>
111+ <para>
112+ Importing a top-level <filename>default.nix</filename> file, if it is
113+ a directory.
114+ </para>
115+ </listitem>
116+ </itemizedlist>
117+ </para>
118+ </listitem>
69119 </itemizedlist>
70− </para>
71− </listitem>
72−</itemizedlist>
73−</para>
74−
75−<para>On a NixOS system the value of the <literal>nixpkgs.overlays</literal> option, if present,
76−is passed to the system Nixpkgs directly as an argument. Note that this does not affect the overlays for
77−non-NixOS operations (e.g. <literal>nix-env</literal>), which are looked up independently.</para>
78−
79−<para>The <filename>overlays.nix</filename> option therefore provides a convenient way to use the same
80−overlays for a NixOS system configuration and user configuration: the same file can be used
81−as <filename>overlays.nix</filename> and imported as the value of <literal>nixpkgs.overlays</literal>.</para>
82−
83−</section>
84−
120+ </para>
121+
122+ <para>
123+ Because overlays that are set in NixOS configuration do not affect
124+ non-NixOS operations such as <literal>nix-env</literal>, the
125+ <filename>overlays.nix</filename> option provides a convenient way to use
126+ the same overlays for a NixOS system configuration and user configuration:
127+ the same file can be used as <filename>overlays.nix</filename> and imported
128+ as the value of <literal>nixpkgs.overlays</literal>.
129+ </para>
130+
131+<!-- TODO: Example of sharing overlays between NixOS configuration
132+ and configuration lookup. Also reference the example
133+ from the sec-overlays-argument paragraph about NixOS.
134+ -->
135+ </section>
136+ </section>
85137<!--============================================================-->
138+ <section xml:id="sec-overlays-definition">
139+ <title>Defining overlays</title>
86140
87−<section xml:id="sec-overlays-definition">
88−<title>Defining overlays</title>
89−
90−<para>Overlays are Nix functions which accept two arguments,
91−conventionally called <varname>self</varname> and <varname>super</varname>,
92−and return a set of packages. For example, the following is a valid overlay.</para>
141+ <para>
142+ Overlays are Nix functions which accept two arguments, conventionally called
143+ <varname>self</varname> and <varname>super</varname>, and return a set of
144+ packages. For example, the following is a valid overlay.
145+ </para>
93146
94147<programlisting>
95148self: super:
@@ -104,31 +157,39 @@ self: super:
104157}
105158</programlisting>
106159
107−<para>The first argument (<varname>self</varname>) corresponds to the final package
108−set. You should use this set for the dependencies of all packages specified in your
109−overlay. For example, all the dependencies of <varname>rr</varname> in the example above come
110−from <varname>self</varname>, as well as the overridden dependencies used in the
111−<varname>boost</varname> override.</para>
112−
113−<para>The second argument (<varname>super</varname>)
114−corresponds to the result of the evaluation of the previous stages of
115−Nixpkgs. It does not contain any of the packages added by the current
116−overlay, nor any of the following overlays. This set should be used either
117−to refer to packages you wish to override, or to access functions defined
118−in Nixpkgs. For example, the original recipe of <varname>boost</varname>
119−in the above example, comes from <varname>super</varname>, as well as the
120−<varname>callPackage</varname> function.</para>
121−
122−<para>The value returned by this function should be a set similar to
123−<filename>pkgs/top-level/all-packages.nix</filename>, containing
124−overridden and/or new packages.</para>
125−
126−<para>Overlays are similar to other methods for customizing Nixpkgs, in particular
127−the <literal>packageOverrides</literal> attribute described in <xref linkend="sec-modify-via-packageOverrides"/>.
128−Indeed, <literal>packageOverrides</literal> acts as an overlay with only the
129−<varname>super</varname> argument. It is therefore appropriate for basic use,
130−but overlays are more powerful and easier to distribute.</para>
131−
132−</section>
133−
160+ <para>
161+ The first argument (<varname>self</varname>) corresponds to the final
162+ package set. You should use this set for the dependencies of all packages
163+ specified in your overlay. For example, all the dependencies of
164+ <varname>rr</varname> in the example above come from
165+ <varname>self</varname>, as well as the overridden dependencies used in the
166+ <varname>boost</varname> override.
167+ </para>
168+
169+ <para>
170+ The second argument (<varname>super</varname>) corresponds to the result of
171+ the evaluation of the previous stages of Nixpkgs. It does not contain any of
172+ the packages added by the current overlay, nor any of the following
173+ overlays. This set should be used either to refer to packages you wish to
174+ override, or to access functions defined in Nixpkgs. For example, the
175+ original recipe of <varname>boost</varname> in the above example, comes from
176+ <varname>super</varname>, as well as the <varname>callPackage</varname>
177+ function.
178+ </para>
179+
180+ <para>
181+ The value returned by this function should be a set similar to
182+ <filename>pkgs/top-level/all-packages.nix</filename>, containing overridden
183+ and/or new packages.
184+ </para>
185+
186+ <para>
187+ Overlays are similar to other methods for customizing Nixpkgs, in particular
188+ the <literal>packageOverrides</literal> attribute described in
189+ <xref linkend="sec-modify-via-packageOverrides"/>. Indeed,
190+ <literal>packageOverrides</literal> acts as an overlay with only the
191+ <varname>super</varname> argument. It is therefore appropriate for basic
192+ use, but overlays are more powerful and easier to distribute.
193+ </para>
194+ </section>
134195</chapter>
doc/overrides.cssnew file+9
@@ -0,0 +1,9 @@
1+.docbook .xref img[src^=images\/callouts\/],
2+.screen img,
3+.programlisting img {
4+ width: 1em;
5+}
6+
7+.calloutlist img {
8+ width: 1.5em;
9+}
doc/package-notes.xml+653−485
@@ -1,272 +1,239 @@
11<chapter xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="chap-package-notes">
4−
5−<title>Package Notes</title>
6−
7−<para>This chapter contains information about how to use and maintain
8−the Nix expressions for a number of specific packages, such as the
9−Linux kernel or X.org.</para>
10−
11−
4+ <title>Package Notes</title>
5+ <para>
6+ This chapter contains information about how to use and maintain the Nix
7+ expressions for a number of specific packages, such as the Linux kernel or
8+ X.org.
9+ </para>
1210<!--============================================================-->
11+ <section xml:id="sec-linux-kernel">
12+ <title>Linux kernel</title>
1313
14−<section xml:id="sec-linux-kernel">
15−
16−<title>Linux kernel</title>
17−
18−<para>The Nix expressions to build the Linux kernel are in <link
19−xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/os-specific/linux/kernel"><filename>pkgs/os-specific/linux/kernel</filename></link>.</para>
20−
21−<para>The function that builds the kernel has an argument
22−<varname>kernelPatches</varname> which should be a list of
23−<literal>{name, patch, extraConfig}</literal> attribute sets, where
24−<varname>name</varname> is the name of the patch (which is included in
25−the kernel’s <varname>meta.description</varname> attribute),
26−<varname>patch</varname> is the patch itself (possibly compressed),
27−and <varname>extraConfig</varname> (optional) is a string specifying
28−extra options to be concatenated to the kernel configuration file
29−(<filename>.config</filename>).</para>
14+ <para>
15+ The Nix expressions to build the Linux kernel are in
16+ <link
17+xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/os-specific/linux/kernel"><filename>pkgs/os-specific/linux/kernel</filename></link>.
18+ </para>
3019
31−<para>The kernel derivation exports an attribute
32−<varname>features</varname> specifying whether optional functionality
33−is or isn’t enabled. This is used in NixOS to implement
34−kernel-specific behaviour. For instance, if the kernel has the
35−<varname>iwlwifi</varname> feature (i.e. has built-in support for
36−Intel wireless chipsets), then NixOS doesn’t have to build the
37−external <varname>iwlwifi</varname> package:
20+ <para>
21+ The function that builds the kernel has an argument
22+ <varname>kernelPatches</varname> which should be a list of <literal>{name,
23+ patch, extraConfig}</literal> attribute sets, where <varname>name</varname>
24+ is the name of the patch (which is included in the kernel’s
25+ <varname>meta.description</varname> attribute), <varname>patch</varname> is
26+ the patch itself (possibly compressed), and <varname>extraConfig</varname>
27+ (optional) is a string specifying extra options to be concatenated to the
28+ kernel configuration file (<filename>.config</filename>).
29+ </para>
3830
31+ <para>
32+ The kernel derivation exports an attribute <varname>features</varname>
33+ specifying whether optional functionality is or isn’t enabled. This is
34+ used in NixOS to implement kernel-specific behaviour. For instance, if the
35+ kernel has the <varname>iwlwifi</varname> feature (i.e. has built-in support
36+ for Intel wireless chipsets), then NixOS doesn’t have to build the
37+ external <varname>iwlwifi</varname> package:
3938<programlisting>
4039modulesTree = [kernel]
4140 ++ pkgs.lib.optional (!kernel.features ? iwlwifi) kernelPackages.iwlwifi
4241 ++ ...;
4342</programlisting>
43+ </para>
4444
45−</para>
46−
47−<para>How to add a new (major) version of the Linux kernel to Nixpkgs:
48−
49−<orderedlist>
50−
51− <listitem>
52− <para>Copy the old Nix expression
53− (e.g. <filename>linux-2.6.21.nix</filename>) to the new one
54− (e.g. <filename>linux-2.6.22.nix</filename>) and update it.</para>
55− </listitem>
56−
57− <listitem>
58− <para>Add the new kernel to <filename>all-packages.nix</filename>
59− (e.g., create an attribute
60− <varname>kernel_2_6_22</varname>).</para>
61− </listitem>
62−
63− <listitem>
64− <para>Now we’re going to update the kernel configuration. First
65− unpack the kernel. Then for each supported platform
66− (<literal>i686</literal>, <literal>x86_64</literal>,
67− <literal>uml</literal>) do the following:
68−
45+ <para>
46+ How to add a new (major) version of the Linux kernel to Nixpkgs:
47+ <orderedlist>
48+ <listitem>
49+ <para>
50+ Copy the old Nix expression (e.g. <filename>linux-2.6.21.nix</filename>)
51+ to the new one (e.g. <filename>linux-2.6.22.nix</filename>) and update
52+ it.
53+ </para>
54+ </listitem>
55+ <listitem>
56+ <para>
57+ Add the new kernel to <filename>all-packages.nix</filename> (e.g., create
58+ an attribute <varname>kernel_2_6_22</varname>).
59+ </para>
60+ </listitem>
61+ <listitem>
62+ <para>
63+ Now we’re going to update the kernel configuration. First unpack the
64+ kernel. Then for each supported platform (<literal>i686</literal>,
65+ <literal>x86_64</literal>, <literal>uml</literal>) do the following:
6966 <orderedlist>
70−
71− <listitem>
72− <para>Make an copy from the old
73− config (e.g. <filename>config-2.6.21-i686-smp</filename>) to
74− the new one
75− (e.g. <filename>config-2.6.22-i686-smp</filename>).</para>
76− </listitem>
77−
78− <listitem>
79− <para>Copy the config file for this platform
80− (e.g. <filename>config-2.6.22-i686-smp</filename>) to
81− <filename>.config</filename> in the kernel source tree.
82− </para>
83− </listitem>
84−
85− <listitem>
86− <para>Run <literal>make oldconfig
87− ARCH=<replaceable>{i386,x86_64,um}</replaceable></literal>
88− and answer all questions. (For the uml configuration, also
89− add <literal>SHELL=bash</literal>.) Make sure to keep the
90− configuration consistent between platforms (i.e. don’t
91− enable some feature on <literal>i686</literal> and disable
92− it on <literal>x86_64</literal>).
93− </para>
94− </listitem>
95−
96− <listitem>
97− <para>If needed you can also run <literal>make
98− menuconfig</literal>:
99−
100− <screen>
67+ <listitem>
68+ <para>
69+ Make an copy from the old config (e.g.
70+ <filename>config-2.6.21-i686-smp</filename>) to the new one (e.g.
71+ <filename>config-2.6.22-i686-smp</filename>).
72+ </para>
73+ </listitem>
74+ <listitem>
75+ <para>
76+ Copy the config file for this platform (e.g.
77+ <filename>config-2.6.22-i686-smp</filename>) to
78+ <filename>.config</filename> in the kernel source tree.
79+ </para>
80+ </listitem>
81+ <listitem>
82+ <para>
83+ Run <literal>make oldconfig
84+ ARCH=<replaceable>{i386,x86_64,um}</replaceable></literal> and answer
85+ all questions. (For the uml configuration, also add
86+ <literal>SHELL=bash</literal>.) Make sure to keep the configuration
87+ consistent between platforms (i.e. don’t enable some feature on
88+ <literal>i686</literal> and disable it on <literal>x86_64</literal>).
89+ </para>
90+ </listitem>
91+ <listitem>
92+ <para>
93+ If needed you can also run <literal>make menuconfig</literal>:
94+<screen>
10195$ nix-env -i ncurses
10296$ export NIX_CFLAGS_LINK=-lncurses
10397$ make menuconfig ARCH=<replaceable>arch</replaceable></screen>
104−
105− </para>
106− </listitem>
107−
108− <listitem>
109− <para>Copy <filename>.config</filename> over the new config
110− file (e.g. <filename>config-2.6.22-i686-smp</filename>).</para>
111− </listitem>
112−
98+ </para>
99+ </listitem>
100+ <listitem>
101+ <para>
102+ Copy <filename>.config</filename> over the new config file (e.g.
103+ <filename>config-2.6.22-i686-smp</filename>).
104+ </para>
105+ </listitem>
113106 </orderedlist>
114−
115− </para>
116−
117− </listitem>
118−
119− <listitem>
120− <para>Test building the kernel: <literal>nix-build -A
121− kernel_2_6_22</literal>. If it compiles, ship it! For extra
122− credit, try booting NixOS with it.</para>
123− </listitem>
124−
125− <listitem>
126− <para>It may be that the new kernel requires updating the external
127− kernel modules and kernel-dependent packages listed in the
128− <varname>linuxPackagesFor</varname> function in
129− <filename>all-packages.nix</filename> (such as the NVIDIA drivers,
130− AUFS, etc.). If the updated packages aren’t backwards compatible
131− with older kernels, you may need to keep the older versions
132− around.</para>
133− </listitem>
134−
135−</orderedlist>
136−
137−</para>
138−
139−</section>
140−
141−
107+ </para>
108+ </listitem>
109+ <listitem>
110+ <para>
111+ Test building the kernel: <literal>nix-build -A kernel_2_6_22</literal>.
112+ If it compiles, ship it! For extra credit, try booting NixOS with it.
113+ </para>
114+ </listitem>
115+ <listitem>
116+ <para>
117+ It may be that the new kernel requires updating the external kernel
118+ modules and kernel-dependent packages listed in the
119+ <varname>linuxPackagesFor</varname> function in
120+ <filename>all-packages.nix</filename> (such as the NVIDIA drivers, AUFS,
121+ etc.). If the updated packages aren’t backwards compatible with older
122+ kernels, you may need to keep the older versions around.
123+ </para>
124+ </listitem>
125+ </orderedlist>
126+ </para>
127+ </section>
142128<!--============================================================-->
129+ <section xml:id="sec-xorg">
130+ <title>X.org</title>
143131
144−<section xml:id="sec-xorg">
145−
146−<title>X.org</title>
147−
148−<para>The Nix expressions for the X.org packages reside in
149−<filename>pkgs/servers/x11/xorg/default.nix</filename>. This file is
150−automatically generated from lists of tarballs in an X.org release.
151−As such it should not be modified directly; rather, you should modify
152−the lists, the generator script or the file
153−<filename>pkgs/servers/x11/xorg/overrides.nix</filename>, in which you
154−can override or add to the derivations produced by the
155−generator.</para>
156−
157−<para>The generator is invoked as follows:
132+ <para>
133+ The Nix expressions for the X.org packages reside in
134+ <filename>pkgs/servers/x11/xorg/default.nix</filename>. This file is
135+ automatically generated from lists of tarballs in an X.org release. As such
136+ it should not be modified directly; rather, you should modify the lists, the
137+ generator script or the file
138+ <filename>pkgs/servers/x11/xorg/overrides.nix</filename>, in which you can
139+ override or add to the derivations produced by the generator.
140+ </para>
158141
142+ <para>
143+ The generator is invoked as follows:
159144<screen>
160145$ cd pkgs/servers/x11/xorg
161146$ cat tarballs-7.5.list extra.list old.list \
162147 | perl ./generate-expr-from-tarballs.pl
163148</screen>
149+ For each of the tarballs in the <filename>.list</filename> files, the script
150+ downloads it, unpacks it, and searches its <filename>configure.ac</filename>
151+ and <filename>*.pc.in</filename> files for dependencies. This information is
152+ used to generate <filename>default.nix</filename>. The generator caches
153+ downloaded tarballs between runs. Pay close attention to the <literal>NOT
154+ FOUND: <replaceable>name</replaceable></literal> messages at the end of the
155+ run, since they may indicate missing dependencies. (Some might be optional
156+ dependencies, however.)
157+ </para>
164158
165−For each of the tarballs in the <filename>.list</filename> files, the
166−script downloads it, unpacks it, and searches its
167−<filename>configure.ac</filename> and <filename>*.pc.in</filename>
168−files for dependencies. This information is used to generate
169−<filename>default.nix</filename>. The generator caches downloaded
170−tarballs between runs. Pay close attention to the <literal>NOT FOUND:
171−<replaceable>name</replaceable></literal> messages at the end of the
172−run, since they may indicate missing dependencies. (Some might be
173−optional dependencies, however.)</para>
174−
175−<para>A file like <filename>tarballs-7.5.list</filename> contains all
176−tarballs in a X.org release. It can be generated like this:
177−
159+ <para>
160+ A file like <filename>tarballs-7.5.list</filename> contains all tarballs in
161+ a X.org release. It can be generated like this:
178162<screen>
179163$ export i="mirror://xorg/X11R7.4/src/everything/"
180164$ cat $(PRINT_PATH=1 nix-prefetch-url $i | tail -n 1) \
181165 | perl -e 'while (&lt;>) { if (/(href|HREF)="([^"]*.bz2)"/) { print "$ENV{'i'}$2\n"; }; }' \
182166 | sort > tarballs-7.4.list
183167</screen>
168+ <filename>extra.list</filename> contains libraries that aren’t part of
169+ X.org proper, but are closely related to it, such as
170+ <literal>libxcb</literal>. <filename>old.list</filename> contains some
171+ packages that were removed from X.org, but are still needed by some people
172+ or by other packages (such as <varname>imake</varname>).
173+ </para>
184174
185−<filename>extra.list</filename> contains libraries that aren’t part of
186−X.org proper, but are closely related to it, such as
187−<literal>libxcb</literal>. <filename>old.list</filename> contains
188−some packages that were removed from X.org, but are still needed by
189−some people or by other packages (such as
190−<varname>imake</varname>).</para>
191−
192−<para>If the expression for a package requires derivation attributes
193−that the generator cannot figure out automatically (say,
194−<varname>patches</varname> or a <varname>postInstall</varname> hook),
195−you should modify
196−<filename>pkgs/servers/x11/xorg/overrides.nix</filename>.</para>
197−
198−</section>
199−
200−
201−
175+ <para>
176+ If the expression for a package requires derivation attributes that the
177+ generator cannot figure out automatically (say, <varname>patches</varname>
178+ or a <varname>postInstall</varname> hook), you should modify
179+ <filename>pkgs/servers/x11/xorg/overrides.nix</filename>.
180+ </para>
181+ </section>
202182<!--============================================================-->
203−
204183<!--
205−<section>
184+<section xml:id="sec-package-notes-gnome">
206185 <title>Gnome</title>
207186 <para>* Expression is auto-generated</para>
208187 <para>* How to update</para>
209188</section>
210189-->
211−
212−
213190<!--============================================================-->
214−
215191<!--
216−<section>
192+<section xml:id="sec-package-notes-gcc">
217193 <title>GCC</title>
218194 <para>…</para>
219195</section>
220196-->
221−
222197<!--============================================================-->
223−
224−<section xml:id="sec-eclipse">
225−
198+ <section xml:id="sec-eclipse">
226199 <title>Eclipse</title>
227200
228201 <para>
229− The Nix expressions related to the Eclipse platform and IDE are in
230− <link xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/editors/eclipse"><filename>pkgs/applications/editors/eclipse</filename></link>.
202+ The Nix expressions related to the Eclipse platform and IDE are in
203+ <link xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/editors/eclipse"><filename>pkgs/applications/editors/eclipse</filename></link>.
231204 </para>
232205
233206 <para>
234− Nixpkgs provides a number of packages that will install Eclipse in
235− its various forms, these range from the bare-bones Eclipse
236− Platform to the more fully featured Eclipse SDK or Scala-IDE
237− packages and multiple version are often available. It is possible
238− to list available Eclipse packages by issuing the command:
239−
207+ Nixpkgs provides a number of packages that will install Eclipse in its
208+ various forms, these range from the bare-bones Eclipse Platform to the more
209+ fully featured Eclipse SDK or Scala-IDE packages and multiple version are
210+ often available. It is possible to list available Eclipse packages by
211+ issuing the command:
240212<screen>
241213$ nix-env -f '&lt;nixpkgs&gt;' -qaP -A eclipses --description
242214</screen>
243−
244− Once an Eclipse variant is installed it can be run using the
245− <command>eclipse</command> command, as expected. From within
246− Eclipse it is then possible to install plugins in the usual manner
247− by either manually specifying an Eclipse update site or by
248− installing the Marketplace Client plugin and using it to discover
249− and install other plugins. This installation method provides an
250− Eclipse installation that closely resemble a manually installed
251− Eclipse.
215+ Once an Eclipse variant is installed it can be run using the
216+ <command>eclipse</command> command, as expected. From within Eclipse it is
217+ then possible to install plugins in the usual manner by either manually
218+ specifying an Eclipse update site or by installing the Marketplace Client
219+ plugin and using it to discover and install other plugins. This installation
220+ method provides an Eclipse installation that closely resemble a manually
221+ installed Eclipse.
252222 </para>
253223
254224 <para>
255− If you prefer to install plugins in a more declarative manner then
256− Nixpkgs also offer a number of Eclipse plugins that can be
257− installed in an <emphasis>Eclipse environment</emphasis>. This
258− type of environment is created using the function
259− <varname>eclipseWithPlugins</varname> found inside the
260− <varname>nixpkgs.eclipses</varname> attribute set. This function
261− takes as argument <literal>{ eclipse, plugins ? [], jvmArgs ? []
262− }</literal> where <varname>eclipse</varname> is a one of the
263− Eclipse packages described above, <varname>plugins</varname> is a
264− list of plugin derivations, and <varname>jvmArgs</varname> is a
265− list of arguments given to the JVM running the Eclipse. For
266− example, say you wish to install the latest Eclipse Platform with
267− the popular Eclipse Color Theme plugin and also allow Eclipse to
268− use more RAM. You could then add
269−
225+ If you prefer to install plugins in a more declarative manner then Nixpkgs
226+ also offer a number of Eclipse plugins that can be installed in an
227+ <emphasis>Eclipse environment</emphasis>. This type of environment is
228+ created using the function <varname>eclipseWithPlugins</varname> found
229+ inside the <varname>nixpkgs.eclipses</varname> attribute set. This function
230+ takes as argument <literal>{ eclipse, plugins ? [], jvmArgs ? [] }</literal>
231+ where <varname>eclipse</varname> is a one of the Eclipse packages described
232+ above, <varname>plugins</varname> is a list of plugin derivations, and
233+ <varname>jvmArgs</varname> is a list of arguments given to the JVM running
234+ the Eclipse. For example, say you wish to install the latest Eclipse
235+ Platform with the popular Eclipse Color Theme plugin and also allow Eclipse
236+ to use more RAM. You could then add
270237<screen>
271238packageOverrides = pkgs: {
272239 myEclipse = with pkgs.eclipses; eclipseWithPlugins {
@@ -276,42 +243,38 @@ packageOverrides = pkgs: {
276243 };
277244}
278245</screen>
279−
280− to your Nixpkgs configuration
281− (<filename>~/.config/nixpkgs/config.nix</filename>) and install it by
282− running <command>nix-env -f '&lt;nixpkgs&gt;' -iA
283− myEclipse</command> and afterward run Eclipse as usual. It is
284− possible to find out which plugins are available for installation
285− using <varname>eclipseWithPlugins</varname> by running
286−
246+ to your Nixpkgs configuration
247+ (<filename>~/.config/nixpkgs/config.nix</filename>) and install it by
248+ running <command>nix-env -f '&lt;nixpkgs&gt;' -iA myEclipse</command> and
249+ afterward run Eclipse as usual. It is possible to find out which plugins are
250+ available for installation using <varname>eclipseWithPlugins</varname> by
251+ running
287252<screen>
288253$ nix-env -f '&lt;nixpkgs&gt;' -qaP -A eclipses.plugins --description
289254</screen>
290255 </para>
291256
292257 <para>
293− If there is a need to install plugins that are not available in
294− Nixpkgs then it may be possible to define these plugins outside
295− Nixpkgs using the <varname>buildEclipseUpdateSite</varname> and
296− <varname>buildEclipsePlugin</varname> functions found in the
297− <varname>nixpkgs.eclipses.plugins</varname> attribute set. Use the
298− <varname>buildEclipseUpdateSite</varname> function to install a
299− plugin distributed as an Eclipse update site. This function takes
300− <literal>{ name, src }</literal> as argument where
301− <literal>src</literal> indicates the Eclipse update site archive.
302− All Eclipse features and plugins within the downloaded update site
303− will be installed. When an update site archive is not available
304− then the <varname>buildEclipsePlugin</varname> function can be
305− used to install a plugin that consists of a pair of feature and
306− plugin JARs. This function takes an argument <literal>{ name,
307− srcFeature, srcPlugin }</literal> where
308− <literal>srcFeature</literal> and <literal>srcPlugin</literal> are
309− the feature and plugin JARs, respectively.
258+ If there is a need to install plugins that are not available in Nixpkgs then
259+ it may be possible to define these plugins outside Nixpkgs using the
260+ <varname>buildEclipseUpdateSite</varname> and
261+ <varname>buildEclipsePlugin</varname> functions found in the
262+ <varname>nixpkgs.eclipses.plugins</varname> attribute set. Use the
263+ <varname>buildEclipseUpdateSite</varname> function to install a plugin
264+ distributed as an Eclipse update site. This function takes <literal>{ name,
265+ src }</literal> as argument where <literal>src</literal> indicates the
266+ Eclipse update site archive. All Eclipse features and plugins within the
267+ downloaded update site will be installed. When an update site archive is not
268+ available then the <varname>buildEclipsePlugin</varname> function can be
269+ used to install a plugin that consists of a pair of feature and plugin JARs.
270+ This function takes an argument <literal>{ name, srcFeature, srcPlugin
271+ }</literal> where <literal>srcFeature</literal> and
272+ <literal>srcPlugin</literal> are the feature and plugin JARs, respectively.
310273 </para>
311274
312275 <para>
313− Expanding the previous example with two plugins using the above
314− functions we have
276+ Expanding the previous example with two plugins using the above functions we
277+ have
315278<screen>
316279packageOverrides = pkgs: {
317280 myEclipse = with pkgs.eclipses; eclipseWithPlugins {
@@ -343,210 +306,218 @@ packageOverrides = pkgs: {
343306}
344307</screen>
345308 </para>
309+ </section>
310+ <section xml:id="sec-elm">
311+ <title>Elm</title>
346312
347−</section>
348−
349−<section xml:id="sec-elm">
350−
351−<title>Elm</title>
352−
353−<para>
354−The Nix expressions for Elm reside in
355−<filename>pkgs/development/compilers/elm</filename>. They are generated
356−automatically by <command>update-elm.rb</command> script. One should
357−specify versions of Elm packages inside the script, clear the
358−<filename>packages</filename> directory and run the script from inside it.
359−<literal>elm-reactor</literal> is special because it also has Elm package
360−dependencies. The process is not automated very much for now -- you should
361−get the <literal>elm-reactor</literal> source tree (e.g. with
362−<command>nix-shell</command>) and run <command>elm2nix.rb</command> inside
363−it. Place the resulting <filename>package.nix</filename> file into
364−<filename>packages/elm-reactor-elm.nix</filename>.
365−</para>
366−
367−</section>
368−
369−<section xml:id="sec-shell-helpers">
370−
371−<title>Interactive shell helpers</title>
372−
373−<para>
374− Some packages provide the shell integration to be more useful. But
375− unlike other systems, nix doesn't have a standard share directory
376− location. This is why a bunch <command>PACKAGE-share</command>
377− scripts are shipped that print the location of the corresponding
378− shared folder.
379−
380− Current list of such packages is as following:
313+ <para>
314+ The Nix expressions for Elm reside in
315+ <filename>pkgs/development/compilers/elm</filename>. They are generated
316+ automatically by <command>update-elm.rb</command> script. One should specify
317+ versions of Elm packages inside the script, clear the
318+ <filename>packages</filename> directory and run the script from inside it.
319+ <literal>elm-reactor</literal> is special because it also has Elm package
320+ dependencies. The process is not automated very much for now -- you should
321+ get the <literal>elm-reactor</literal> source tree (e.g. with
322+ <command>nix-shell</command>) and run <command>elm2nix.rb</command> inside
323+ it. Place the resulting <filename>package.nix</filename> file into
324+ <filename>packages/elm-reactor-elm.nix</filename>.
325+ </para>
326+ </section>
327+ <section xml:id="sec-shell-helpers">
328+ <title>Interactive shell helpers</title>
381329
382− <itemizedlist>
330+ <para>
331+ Some packages provide the shell integration to be more useful. But unlike
332+ other systems, nix doesn't have a standard share directory location. This is
333+ why a bunch <command>PACKAGE-share</command> scripts are shipped that print
334+ the location of the corresponding shared folder. Current list of such
335+ packages is as following:
336+ <itemizedlist>
383337 <listitem>
384− <para>
385− <literal>autojump</literal>: <command>autojump-share</command>
386− </para>
338+ <para>
339+ <literal>autojump</literal>: <command>autojump-share</command>
340+ </para>
387341 </listitem>
388342 <listitem>
389− <para>
390− <literal>fzf</literal>: <command>fzf-share</command>
391− </para>
343+ <para>
344+ <literal>fzf</literal>: <command>fzf-share</command>
345+ </para>
392346 </listitem>
393− </itemizedlist>
394−
395− E.g. <literal>autojump</literal> can then used in the .bashrc like this:
347+ </itemizedlist>
348+ E.g. <literal>autojump</literal> can then used in the .bashrc like this:
396349<screen>
397350 source "$(autojump-share)/autojump.bash"
398351</screen>
399−</para>
400−
401−</section>
402−
403−<section xml:id="sec-steam">
404−
405−<title>Steam</title>
406−
407−<section xml:id="sec-steam-nix">
408−
409−<title>Steam in Nix</title>
410−
411−<para>
412− Steam is distributed as a <filename>.deb</filename> file, for now only
413− as an i686 package (the amd64 package only has documentation).
414− When unpacked, it has a script called <filename>steam</filename> that
415− in ubuntu (their target distro) would go to <filename>/usr/bin
416− </filename>. When run for the first time, this script copies some
417− files to the user's home, which include another script that is the
418− ultimate responsible for launching the steam binary, which is also
419− in $HOME.
420−</para>
421−<para>
422− Nix problems and constraints:
423−<itemizedlist>
424− <listitem><para>We don't have <filename>/bin/bash</filename> and many
425− scripts point there. Similarly for <filename>/usr/bin/python</filename>
426− .</para></listitem>
427− <listitem><para>We don't have the dynamic loader in <filename>/lib
428− </filename>.</para></listitem>
429− <listitem><para>The <filename>steam.sh</filename> script in $HOME can
430− not be patched, as it is checked and rewritten by steam.</para></listitem>
431− <listitem><para>The steam binary cannot be patched, it's also checked.</para></listitem>
432−</itemizedlist>
433−</para>
434−<para>
435− The current approach to deploy Steam in NixOS is composing a FHS-compatible
436− chroot environment, as documented
437− <link xlink:href="http://sandervanderburg.blogspot.nl/2013/09/composing-fhs-compatible-chroot.html">here</link>.
438− This allows us to have binaries in the expected paths without disrupting the system,
439− and to avoid patching them to work in a non FHS environment.
440−</para>
441−
442−</section>
443−
444−<section xml:id="sec-steam-play">
445−
446−<title>How to play</title>
447−
448−<para>
449− For 64-bit systems it's important to have
450− <programlisting>hardware.opengl.driSupport32Bit = true;</programlisting>
451− in your <filename>/etc/nixos/configuration.nix</filename>. You'll also need
452− <programlisting>hardware.pulseaudio.support32Bit = true;</programlisting>
453− if you are using PulseAudio - this will enable 32bit ALSA apps integration.
454− To use the Steam controller, you need to add
455− <programlisting>services.udev.extraRules = ''
456− SUBSYSTEM=="usb", ATTRS{idVendor}=="28de", MODE="0666"
457− KERNEL=="uinput", MODE="0660", GROUP="users", OPTIONS+="static_node=uinput"
458− '';</programlisting>
459− to your configuration.
460−</para>
461−
462−</section>
463−
464−<section xml:id="sec-steam-troub">
465−
466−<title>Troubleshooting</title>
467−
468−<para>
469−<variablelist>
470−
471− <varlistentry>
472− <term>Steam fails to start. What do I do?</term>
473− <listitem><para>Try to run
474− <programlisting>strace steam</programlisting>
475− to see what is causing steam to fail.</para></listitem>
476− </varlistentry>
477−
478− <varlistentry>
479− <term>Using the FOSS Radeon or nouveau (nvidia) drivers</term>
480− <listitem><itemizedlist>
481− <listitem><para>The <literal>newStdcpp</literal> parameter
482− was removed since NixOS 17.09 and should not be needed anymore.
483− </para></listitem>
484−
485− <listitem><para>
486− Steam ships statically linked with a version of libcrypto that
487− conflics with the one dynamically loaded by radeonsi_dri.so.
488− If you get the error
489− <programlisting>steam.sh: line 713: 7842 Segmentation fault (core dumped)</programlisting>
490− have a look at <link xlink:href="https://github.com/NixOS/nixpkgs/pull/20269">this pull request</link>.
491− </para></listitem>
492−
493− </itemizedlist></listitem></varlistentry>
494−
495− <varlistentry>
496− <term>Java</term>
497− <listitem><orderedlist>
498− <listitem><para>
499− There is no java in steam chrootenv by default. If you get a message like
500− <programlisting>/home/foo/.local/share/Steam/SteamApps/common/towns/towns.sh: line 1: java: command not found</programlisting>
501− You need to add
502− <programlisting> steam.override { withJava = true; };</programlisting>
503− to your configuration.
504− </para></listitem>
505− </orderedlist></listitem></varlistentry>
506−
507−</variablelist>
508−</para>
509−
510−</section>
511−
512−<section xml:id="sec-steam-run">
513−
514−<title>steam-run</title>
515−<para>
516−The FHS-compatible chroot used for steam can also be used to run
517−other linux games that expect a FHS environment.
518−To do it, add
352+ </para>
353+ </section>
354+ <section xml:id="sec-steam">
355+ <title>Steam</title>
356+
357+ <section xml:id="sec-steam-nix">
358+ <title>Steam in Nix</title>
359+
360+ <para>
361+ Steam is distributed as a <filename>.deb</filename> file, for now only as
362+ an i686 package (the amd64 package only has documentation). When unpacked,
363+ it has a script called <filename>steam</filename> that in ubuntu (their
364+ target distro) would go to <filename>/usr/bin </filename>. When run for the
365+ first time, this script copies some files to the user's home, which include
366+ another script that is the ultimate responsible for launching the steam
367+ binary, which is also in $HOME.
368+ </para>
369+
370+ <para>
371+ Nix problems and constraints:
372+ <itemizedlist>
373+ <listitem>
374+ <para>
375+ We don't have <filename>/bin/bash</filename> and many scripts point
376+ there. Similarly for <filename>/usr/bin/python</filename> .
377+ </para>
378+ </listitem>
379+ <listitem>
380+ <para>
381+ We don't have the dynamic loader in <filename>/lib </filename>.
382+ </para>
383+ </listitem>
384+ <listitem>
385+ <para>
386+ The <filename>steam.sh</filename> script in $HOME can not be patched, as
387+ it is checked and rewritten by steam.
388+ </para>
389+ </listitem>
390+ <listitem>
391+ <para>
392+ The steam binary cannot be patched, it's also checked.
393+ </para>
394+ </listitem>
395+ </itemizedlist>
396+ </para>
397+
398+ <para>
399+ The current approach to deploy Steam in NixOS is composing a FHS-compatible
400+ chroot environment, as documented
401+ <link xlink:href="http://sandervanderburg.blogspot.nl/2013/09/composing-fhs-compatible-chroot.html">here</link>.
402+ This allows us to have binaries in the expected paths without disrupting
403+ the system, and to avoid patching them to work in a non FHS environment.
404+ </para>
405+ </section>
406+
407+ <section xml:id="sec-steam-play">
408+ <title>How to play</title>
409+
410+ <para>
411+ For 64-bit systems it's important to have
412+<programlisting>hardware.opengl.driSupport32Bit = true;</programlisting>
413+ in your <filename>/etc/nixos/configuration.nix</filename>. You'll also need
414+<programlisting>hardware.pulseaudio.support32Bit = true;</programlisting>
415+ if you are using PulseAudio - this will enable 32bit ALSA apps integration.
416+ To use the Steam controller or other Steam supported controllers such as
417+ the DualShock 4 or Nintendo Switch Pro, you need to add
418+<programlisting>hardware.steam-hardware.enable = true;</programlisting>
419+ to your configuration.
420+ </para>
421+ </section>
422+
423+ <section xml:id="sec-steam-troub">
424+ <title>Troubleshooting</title>
425+
426+ <para>
427+ <variablelist>
428+ <varlistentry>
429+ <term>
430+ Steam fails to start. What do I do?
431+ </term>
432+ <listitem>
433+ <para>
434+ Try to run
435+<programlisting>strace steam</programlisting>
436+ to see what is causing steam to fail.
437+ </para>
438+ </listitem>
439+ </varlistentry>
440+ <varlistentry>
441+ <term>
442+ Using the FOSS Radeon or nouveau (nvidia) drivers
443+ </term>
444+ <listitem>
445+ <itemizedlist>
446+ <listitem>
447+ <para>
448+ The <literal>newStdcpp</literal> parameter was removed since NixOS
449+ 17.09 and should not be needed anymore.
450+ </para>
451+ </listitem>
452+ <listitem>
453+ <para>
454+ Steam ships statically linked with a version of libcrypto that
455+ conflics with the one dynamically loaded by radeonsi_dri.so. If you
456+ get the error
457+<programlisting>steam.sh: line 713: 7842 Segmentation fault (core dumped)</programlisting>
458+ have a look at
459+ <link xlink:href="https://github.com/NixOS/nixpkgs/pull/20269">this
460+ pull request</link>.
461+ </para>
462+ </listitem>
463+ </itemizedlist>
464+ </listitem>
465+ </varlistentry>
466+ <varlistentry>
467+ <term>
468+ Java
469+ </term>
470+ <listitem>
471+ <orderedlist>
472+ <listitem>
473+ <para>
474+ There is no java in steam chrootenv by default. If you get a message
475+ like
476+<programlisting>/home/foo/.local/share/Steam/SteamApps/common/towns/towns.sh: line 1: java: command not found</programlisting>
477+ You need to add
478+<programlisting> steam.override { withJava = true; };</programlisting>
479+ to your configuration.
480+ </para>
481+ </listitem>
482+ </orderedlist>
483+ </listitem>
484+ </varlistentry>
485+ </variablelist>
486+ </para>
487+ </section>
488+
489+ <section xml:id="sec-steam-run">
490+ <title>steam-run</title>
491+
492+ <para>
493+ The FHS-compatible chroot used for steam can also be used to run other
494+ linux games that expect a FHS environment. To do it, add
519495<programlisting>pkgs.(steam.override {
520496 nativeOnly = true;
521497 newStdcpp = true;
522498 }).run</programlisting>
523−to your configuration, rebuild, and run the game with
499+ to your configuration, rebuild, and run the game with
524500<programlisting>steam-run ./foo</programlisting>
525−</para>
526−
527−</section>
528−
529−</section>
530−
531−<section xml:id="sec-emacs">
532−
533−<title>Emacs</title>
534−
535−<section xml:id="sec-emacs-config">
536−
537−<title>Configuring Emacs</title>
538−
539−<para>
540− The Emacs package comes with some extra helpers to make it easier to
541− configure. <varname>emacsWithPackages</varname> allows you to manage
542− packages from ELPA. This means that you will not have to install
543− that packages from within Emacs. For instance, if you wanted to use
544− <literal>company</literal>, <literal>counsel</literal>,
545− <literal>flycheck</literal>, <literal>ivy</literal>,
546− <literal>magit</literal>, <literal>projectile</literal>, and
547− <literal>use-package</literal> you could use this as a
548− <filename>~/.config/nixpkgs/config.nix</filename> override:
549−</para>
501+ </para>
502+ </section>
503+ </section>
504+ <section xml:id="sec-emacs">
505+ <title>Emacs</title>
506+
507+ <section xml:id="sec-emacs-config">
508+ <title>Configuring Emacs</title>
509+
510+ <para>
511+ The Emacs package comes with some extra helpers to make it easier to
512+ configure. <varname>emacsWithPackages</varname> allows you to manage
513+ packages from ELPA. This means that you will not have to install that
514+ packages from within Emacs. For instance, if you wanted to use
515+ <literal>company</literal>, <literal>counsel</literal>,
516+ <literal>flycheck</literal>, <literal>ivy</literal>,
517+ <literal>magit</literal>, <literal>projectile</literal>, and
518+ <literal>use-package</literal> you could use this as a
519+ <filename>~/.config/nixpkgs/config.nix</filename> override:
520+ </para>
550521
551522<screen>
552523{
@@ -564,17 +535,17 @@ to your configuration, rebuild, and run the game with
564535}
565536</screen>
566537
567−<para>
568− You can install it like any other packages via <command>nix-env -iA
569− myEmacs</command>. However, this will only install those packages.
570− It will not <literal>configure</literal> them for us. To do this, we
571− need to provide a configuration file. Luckily, it is possible to do
572− this from within Nix! By modifying the above example, we can make
573− Emacs load a custom config file. The key is to create a package that
574− provide a <filename>default.el</filename> file in
575− <filename>/share/emacs/site-start/</filename>. Emacs knows to load
576− this file automatically when it starts.
577−</para>
538+ <para>
539+ You can install it like any other packages via <command>nix-env -iA
540+ myEmacs</command>. However, this will only install those packages. It will
541+ not <literal>configure</literal> them for us. To do this, we need to
542+ provide a configuration file. Luckily, it is possible to do this from
543+ within Nix! By modifying the above example, we can make Emacs load a custom
544+ config file. The key is to create a package that provide a
545+ <filename>default.el</filename> file in
546+ <filename>/share/emacs/site-start/</filename>. Emacs knows to load this
547+ file automatically when it starts.
548+ </para>
578549
579550<screen>
580551{
@@ -654,72 +625,269 @@ cp ${myEmacsConfig} $out/share/emacs/site-lisp/default.el
654625}
655626</screen>
656627
657−<para>
658− This provides a fairly full Emacs start file. It will load in
659− addition to the user's presonal config. You can always disable it by
660− passing <command>-q</command> to the Emacs command.
661−</para>
662−
663−<para>
664− Sometimes <varname>emacsWithPackages</varname> is not enough, as
665− this package set has some priorities imposed on packages (with
666− the lowest priority assigned to Melpa Unstable, and the highest for
667− packages manually defined in
668− <filename>pkgs/top-level/emacs-packages.nix</filename>). But you
669− can't control this priorities when some package is installed as a
670− dependency. You can override it on per-package-basis, providing all
671− the required dependencies manually - but it's tedious and there is
672− always a possibility that an unwanted dependency will sneak in
673− through some other package. To completely override such a package
674− you can use <varname>overrideScope</varname>.
675−</para>
628+ <para>
629+ This provides a fairly full Emacs start file. It will load in addition to
630+ the user's presonal config. You can always disable it by passing
631+ <command>-q</command> to the Emacs command.
632+ </para>
633+
634+ <para>
635+ Sometimes <varname>emacsWithPackages</varname> is not enough, as this
636+ package set has some priorities imposed on packages (with the lowest
637+ priority assigned to Melpa Unstable, and the highest for packages manually
638+ defined in <filename>pkgs/top-level/emacs-packages.nix</filename>). But you
639+ can't control this priorities when some package is installed as a
640+ dependency. You can override it on per-package-basis, providing all the
641+ required dependencies manually - but it's tedious and there is always a
642+ possibility that an unwanted dependency will sneak in through some other
643+ package. To completely override such a package you can use
644+ <varname>overrideScope'</varname>.
645+ </para>
676646
677647<screen>
678−overrides = super: self: rec {
648+overrides = self: super: rec {
679649 haskell-mode = self.melpaPackages.haskell-mode;
680650 ...
681651};
682−((emacsPackagesNgGen emacs).overrideScope overrides).emacsWithPackages (p: with p; [
652+((emacsPackagesNgGen emacs).overrideScope' overrides).emacsWithPackages (p: with p; [
683653 # here both these package will use haskell-mode of our own choice
684654 ghc-mod
685655 dante
686656])
687657</screen>
658+ </section>
659+ </section>
660+ <section xml:id="sec-weechat">
661+ <title>Weechat</title>
688662
689−</section>
690−
691−</section>
692−
693−<section xml:id="sec-weechat">
694−<title>Weechat</title>
695−<para>
696−Weechat can be configured to include your choice of plugins, reducing its
697−closure size from the default configuration which includes all available
698−plugins. To make use of this functionality, install an expression that
699−overrides its configuration such as
663+ <para>
664+ Weechat can be configured to include your choice of plugins, reducing its
665+ closure size from the default configuration which includes all available
666+ plugins. To make use of this functionality, install an expression that
667+ overrides its configuration such as
700668<programlisting>weechat.override {configure = {availablePlugins, ...}: {
701669 plugins = with availablePlugins; [ python perl ];
702670 }
703671}</programlisting>
704−</para>
705−<para>
706−The plugins currently available are <literal>python</literal>,
707−<literal>perl</literal>, <literal>ruby</literal>, <literal>guile</literal>,
708−<literal>tcl</literal> and <literal>lua</literal>.
709−</para>
710−<para>
711−The python plugin allows the addition of extra libraries. For instance,
712−the <literal>inotify.py</literal> script in weechat-scripts requires
713−D-Bus or libnotify, and the <literal>fish.py</literal> script requires
714−pycrypto. To use these scripts, use the <literal>python</literal>
715−plugin's <literal>withPackages</literal> attribute:
716−<programlisting>weechat.override {configure = {availablePlugins, ...}: {
672+ If the <literal>configure</literal> function returns an attrset without the
673+ <literal>plugins</literal> attribute, <literal>availablePlugins</literal>
674+ will be used automatically.
675+ </para>
676+
677+ <para>
678+ The plugins currently available are <literal>python</literal>,
679+ <literal>perl</literal>, <literal>ruby</literal>, <literal>guile</literal>,
680+ <literal>tcl</literal> and <literal>lua</literal>.
681+ </para>
682+
683+ <para>
684+ The python and perl plugins allows the addition of extra libraries. For
685+ instance, the <literal>inotify.py</literal> script in weechat-scripts
686+ requires D-Bus or libnotify, and the <literal>fish.py</literal> script
687+ requires pycrypto. To use these scripts, use the plugin's
688+ <literal>withPackages</literal> attribute:
689+<programlisting>weechat.override { configure = {availablePlugins, ...}: {
717690 plugins = with availablePlugins; [
718691 (python.withPackages (ps: with ps; [ pycrypto python-dbus ]))
719692 ];
720− }
693+ };
721694}
722695</programlisting>
723−</para>
724−</section>
696+ </para>
697+
698+ <para>
699+ In order to also keep all default plugins installed, it is possible to use
700+ the following method:
701+<programlisting>weechat.override { configure = { availablePlugins, ... }: {
702+ plugins = builtins.attrValues (availablePlugins // {
703+ python = availablePlugins.python.withPackages (ps: with ps; [ pycrypto python-dbus ]);
704+ });
705+}; }
706+</programlisting>
707+ </para>
708+
709+ <para>
710+ WeeChat allows to set defaults on startup using the
711+ <literal>--run-command</literal>. The <literal>configure</literal> method
712+ can be used to pass commands to the program:
713+<programlisting>weechat.override {
714+ configure = { availablePlugins, ... }: {
715+ init = ''
716+ /set foo bar
717+ /server add freenode chat.freenode.org
718+ '';
719+ };
720+}</programlisting>
721+ Further values can be added to the list of commands when running
722+ <literal>weechat --run-command "your-commands"</literal>.
723+ </para>
724+
725+ <para>
726+ Additionally it's possible to specify scripts to be loaded when starting
727+ <literal>weechat</literal>. These will be loaded before the commands from
728+ <literal>init</literal>:
729+<programlisting>weechat.override {
730+ configure = { availablePlugins, ... }: {
731+ scripts = with pkgs.weechatScripts; [
732+ weechat-xmpp weechat-matrix-bridge wee-slack
733+ ];
734+ init = ''
735+ /set plugins.var.python.jabber.key "val"
736+ '':
737+ };
738+}</programlisting>
739+ </para>
740+
741+ <para>
742+ In <literal>nixpkgs</literal> there's a subpackage which contains
743+ derivations for WeeChat scripts. Such derivations expect a
744+ <literal>passthru.scripts</literal> attribute which contains a list of all
745+ scripts inside the store path. Furthermore all scripts have to live in
746+ <literal>$out/share</literal>. An exemplary derivation looks like this:
747+<programlisting>{ stdenv, fetchurl }:
748+
749+stdenv.mkDerivation {
750+ name = "exemplary-weechat-script";
751+ src = fetchurl {
752+ url = "https://scripts.tld/your-scripts.tar.gz";
753+ sha256 = "...";
754+ };
755+ passthru.scripts = [ "foo.py" "bar.lua" ];
756+ installPhase = ''
757+ mkdir $out/share
758+ cp foo.py $out/share
759+ cp bar.lua $out/share
760+ '';
761+}</programlisting>
762+ </para>
763+ </section>
764+ <section xml:id="sec-citrix">
765+ <title>Citrix Receiver</title>
766+
767+ <para>
768+ The <link xlink:href="https://www.citrix.com/products/receiver/">Citrix
769+ Receiver</link> is a remote desktop viewer which provides access to
770+ <link xlink:href="https://www.citrix.com/products/xenapp-xendesktop/">XenDesktop</link>
771+ installations.
772+ </para>
773+
774+ <section xml:id="sec-citrix-base">
775+ <title>Basic usage</title>
776+
777+ <para>
778+ The tarball archive needs to be downloaded manually as the licenses
779+ agreements of the vendor need to be accepted first. This is available at
780+ the
781+ <link xlink:href="https://www.citrix.com/downloads/citrix-receiver/">download
782+ page at citrix.com</link>. Then run <literal>nix-prefetch-url
783+ file://$PWD/linuxx64-$version.tar.gz</literal>. With the archive available
784+ in the store the package can be built and installed with Nix.
785+ </para>
786+
787+ <para>
788+ <emphasis>Note: it's recommended to install <literal>Citrix
789+ Receiver</literal> using <literal>nix-env -i</literal> or globally to
790+ ensure that the <literal>.desktop</literal> files are installed properly
791+ into <literal>$XDG_CONFIG_DIRS</literal>. Otherwise it won't be possible to
792+ open <literal>.ica</literal> files automatically from the browser to start
793+ a Citrix connection.</emphasis>
794+ </para>
795+ </section>
796+
797+ <section xml:id="sec-citrix-custom-certs">
798+ <title>Custom certificates</title>
799+
800+ <para>
801+ The <literal>Citrix Receiver</literal> in <literal>nixpkgs</literal> trusts
802+ several certificates
803+ <link xlink:href="https://curl.haxx.se/docs/caextract.html">from the
804+ Mozilla database</link> by default. However several companies using Citrix
805+ might require their own corporate certificate. On distros with imperative
806+ packaging these certs can be stored easily in
807+ <link xlink:href="https://developer-docs.citrix.com/projects/receiver-for-linux-command-reference/en/13.7/"><literal>$ICAROOT</literal></link>,
808+ however this directory is a store path in <literal>nixpkgs</literal>. In
809+ order to work around this issue the package provides a simple mechanism to
810+ add custom certificates without rebuilding the entire package using
811+ <literal>symlinkJoin</literal>:
812+<programlisting>
813+<![CDATA[with import <nixpkgs> { config.allowUnfree = true; };
814+let extraCerts = [ ./custom-cert-1.pem ./custom-cert-2.pem /* ... */ ]; in
815+citrix_receiver.override {
816+ inherit extraCerts;
817+}]]>
818+</programlisting>
819+ </para>
820+ </section>
821+ </section>
822+ <section xml:id="sec-ibus-typing-booster">
823+ <title>ibus-engines.typing-booster</title>
824+
825+ <para>
826+ This package is an ibus-based completion method to speed up typing.
827+ </para>
828+
829+ <section xml:id="sec-ibus-typing-booster-activate">
830+ <title>Activating the engine</title>
831+
832+ <para>
833+ IBus needs to be configured accordingly to activate
834+ <literal>typing-booster</literal>. The configuration depends on the desktop
835+ manager in use. For detailed instructions, please refer to the
836+ <link xlink:href="https://mike-fabian.github.io/ibus-typing-booster/documentation.html">upstream
837+ docs</link>.
838+ </para>
839+
840+ <para>
841+ On NixOS you need to explicitly enable <literal>ibus</literal> with given
842+ engines before customizing your desktop to use
843+ <literal>typing-booster</literal>. This can be achieved using the
844+ <literal>ibus</literal> module:
845+<programlisting>{ pkgs, ... }: {
846+ i18n.inputMethod = {
847+ enabled = "ibus";
848+ ibus.engines = with pkgs.ibus-engines; [ typing-booster ];
849+ };
850+}</programlisting>
851+ </para>
852+ </section>
853+
854+ <section xml:id="sec-ibus-typing-booster-customize-hunspell">
855+ <title>Using custom hunspell dictionaries</title>
856+
857+ <para>
858+ The IBus engine is based on <literal>hunspell</literal> to support
859+ completion in many languages. By default the dictionaries
860+ <literal>de-de</literal>, <literal>en-us</literal>,
861+ <literal>es-es</literal>, <literal>it-it</literal>,
862+ <literal>sv-se</literal> and <literal>sv-fi</literal> are in use. To add
863+ another dictionary, the package can be overridden like this:
864+<programlisting>ibus-engines.typing-booster.override {
865+ langs = [ "de-at" "en-gb" ];
866+}</programlisting>
867+ </para>
868+
869+ <para>
870+ <emphasis>Note: each language passed to <literal>langs</literal> must be an
871+ attribute name in <literal>pkgs.hunspellDicts</literal>.</emphasis>
872+ </para>
873+ </section>
874+
875+ <section xml:id="sec-ibus-typing-booster-emoji-picker">
876+ <title>Built-in emoji picker</title>
877+
878+ <para>
879+ The <literal>ibus-engines.typing-booster</literal> package contains a
880+ program named <literal>emoji-picker</literal>. To display all emojis
881+ correctly, a special font such as <literal>noto-fonts-emoji</literal> is
882+ needed:
883+ </para>
884+
885+ <para>
886+ On NixOS it can be installed using the following expression:
887+<programlisting>{ pkgs, ... }: {
888+ fonts.fonts = with pkgs; [ noto-fonts-emoji ];
889+}</programlisting>
890+ </para>
891+ </section>
892+ </section>
725893</chapter>
doc/platform-notes.xml+68−46
@@ -1,27 +1,25 @@
11<chapter xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="chap-platform-nodes">
4+ <title>Platform Notes</title>
5+ <section xml:id="sec-darwin">
6+ <title>Darwin (macOS)</title>
47
5−<title>Platform Notes</title>
8+ <para>
9+ Some common issues when packaging software for darwin:
10+ </para>
611
7−<section xml:id="sec-darwin">
8−
9−<title>Darwin (macOS)</title>
10−<para>Some common issues when packaging software for darwin:</para>
11−
12−<itemizedlist>
13−
14− <listitem>
12+ <itemizedlist>
13+ <listitem>
1514 <para>
16− The darwin <literal>stdenv</literal> uses clang instead of gcc.
17− When referring to the compiler <varname>$CC</varname> or <command>cc</command>
18− will work in both cases. Some builds hardcode gcc/g++ in their
19− build scripts, that can usually be fixed with using something
20− like <literal>makeFlags = [ "CC=cc" ];</literal> or by patching
21− the build scripts.
15+ The darwin <literal>stdenv</literal> uses clang instead of gcc. When
16+ referring to the compiler <varname>$CC</varname> or <command>cc</command>
17+ will work in both cases. Some builds hardcode gcc/g++ in their build
18+ scripts, that can usually be fixed with using something like
19+ <literal>makeFlags = [ "CC=cc" ];</literal> or by patching the build
20+ scripts.
2221 </para>
23−
24− <programlisting>
22+<programlisting>
2523 stdenv.mkDerivation {
2624 name = "libfoo-1.2.3";
2725 # ...
@@ -30,36 +28,63 @@
3028 '';
3129 }
3230 </programlisting>
33− </listitem>
34−
35− <listitem>
31+ </listitem>
32+ <listitem>
3633 <para>
37− On darwin libraries are linked using absolute paths, libraries
38− are resolved by their <literal>install_name</literal> at link
39− time. Sometimes packages won't set this correctly causing the
40− library lookups to fail at runtime. This can be fixed by adding
41− extra linker flags or by running <command>install_name_tool -id</command>
42− during the <function>fixupPhase</function>.
34+ On darwin libraries are linked using absolute paths, libraries are
35+ resolved by their <literal>install_name</literal> at link time. Sometimes
36+ packages won't set this correctly causing the library lookups to fail at
37+ runtime. This can be fixed by adding extra linker flags or by running
38+ <command>install_name_tool -id</command> during the
39+ <function>fixupPhase</function>.
4340 </para>
44−
45− <programlisting>
41+<programlisting>
4642 stdenv.mkDerivation {
4743 name = "libfoo-1.2.3";
4844 # ...
4945 makeFlags = stdenv.lib.optional stdenv.isDarwin "LDFLAGS=-Wl,-install_name,$(out)/lib/libfoo.dylib";
5046 }
5147 </programlisting>
52− </listitem>
53−
54− <listitem>
48+ </listitem>
49+ <listitem>
5550 <para>
56− Some packages assume xcode is available and use <command>xcrun</command>
57− to resolve build tools like <command>clang</command>, etc.
58− This causes errors like <code>xcode-select: error: no developer tools were found at '/Applications/Xcode.app'</code>
59− while the build doesn't actually depend on xcode.
51+ Even if the libraries are linked using absolute paths and resolved via
52+ their <literal>install_name</literal> correctly, tests can sometimes fail
53+ to run binaries. This happens because the <varname>checkPhase</varname>
54+ runs before the libraries are installed.
6055 </para>
61−
62− <programlisting>
56+ <para>
57+ This can usually be solved by running the tests after the
58+ <varname>installPhase</varname> or alternatively by using
59+ <varname>DYLD_LIBRARY_PATH</varname>. More information about this variable
60+ can be found in the <citerefentry>
61+ <refentrytitle>dyld</refentrytitle>
62+ <manvolnum>1</manvolnum></citerefentry> manpage.
63+ </para>
64+<programlisting>
65+ dyld: Library not loaded: /nix/store/7hnmbscpayxzxrixrgxvvlifzlxdsdir-jq-1.5-lib/lib/libjq.1.dylib
66+ Referenced from: /private/tmp/nix-build-jq-1.5.drv-0/jq-1.5/tests/../jq
67+ Reason: image not found
68+ ./tests/jqtest: line 5: 75779 Abort trap: 6
69+ </programlisting>
70+<programlisting>
71+ stdenv.mkDerivation {
72+ name = "libfoo-1.2.3";
73+ # ...
74+ doInstallCheck = true;
75+ installCheckTarget = "check";
76+ }
77+ </programlisting>
78+ </listitem>
79+ <listitem>
80+ <para>
81+ Some packages assume xcode is available and use <command>xcrun</command>
82+ to resolve build tools like <command>clang</command>, etc. This causes
83+ errors like <code>xcode-select: error: no developer tools were found at
84+ '/Applications/Xcode.app'</code> while the build doesn't actually depend
85+ on xcode.
86+ </para>
87+<programlisting>
6388 stdenv.mkDerivation {
6489 name = "libfoo-1.2.3";
6590 # ...
@@ -69,15 +94,12 @@
6994 '';
7095 }
7196 </programlisting>
72−
7397 <para>
74− The package <literal>xcbuild</literal> can be used to build projects
75− that really depend on Xcode, however projects that build some kind of
76− graphical interface won't work without using Xcode in an impure way.
98+ The package <literal>xcbuild</literal> can be used to build projects that
99+ really depend on Xcode, however projects that build some kind of graphical
100+ interface won't work without using Xcode in an impure way.
77101 </para>
78− </listitem>
79−
80−</itemizedlist>
81−</section>
82−
102+ </listitem>
103+ </itemizedlist>
104+ </section>
83105</chapter>
doc/quick-start.xml+185−189
@@ -1,223 +1,219 @@
11<chapter xmlns="http://docbook.org/ns/docbook"
22 xmlns:xlink="http://www.w3.org/1999/xlink"
33 xml:id="chap-quick-start">
4−
5−<title>Quick Start to Adding a Package</title>
6−
7−<para>To add a package to Nixpkgs:
8−
9−<orderedlist>
10−
11− <listitem>
12− <para>Checkout the Nixpkgs source tree:
13−
4+ <title>Quick Start to Adding a Package</title>
5+ <para>
6+ To add a package to Nixpkgs:
7+ <orderedlist>
8+ <listitem>
9+ <para>
10+ Checkout the Nixpkgs source tree:
1411<screen>
15−$ git clone git://github.com/NixOS/nixpkgs.git
12+$ git clone https://github.com/NixOS/nixpkgs
1613$ cd nixpkgs</screen>
17−
1814 </para>
19− </listitem>
20−
21− <listitem>
22− <para>Find a good place in the Nixpkgs tree to add the Nix
23− expression for your package. For instance, a library package
24− typically goes into
25− <filename>pkgs/development/libraries/<replaceable>pkgname</replaceable></filename>,
26− while a web browser goes into
27− <filename>pkgs/applications/networking/browsers/<replaceable>pkgname</replaceable></filename>.
28− See <xref linkend="sec-organisation" /> for some hints on the tree
29− organisation. Create a directory for your package, e.g.
30−
15+ </listitem>
16+ <listitem>
17+ <para>
18+ Find a good place in the Nixpkgs tree to add the Nix expression for your
19+ package. For instance, a library package typically goes into
20+ <filename>pkgs/development/libraries/<replaceable>pkgname</replaceable></filename>,
21+ while a web browser goes into
22+ <filename>pkgs/applications/networking/browsers/<replaceable>pkgname</replaceable></filename>.
23+ See <xref linkend="sec-organisation" /> for some hints on the tree
24+ organisation. Create a directory for your package, e.g.
3125<screen>
3226$ mkdir pkgs/development/libraries/libfoo</screen>
33−
3427 </para>
35− </listitem>
36−
37− <listitem>
38− <para>In the package directory, create a Nix expression — a piece
39− of code that describes how to build the package. In this case, it
40− should be a <emphasis>function</emphasis> that is called with the
41− package dependencies as arguments, and returns a build of the
42− package in the Nix store. The expression should usually be called
43− <filename>default.nix</filename>.
44−
28+ </listitem>
29+ <listitem>
30+ <para>
31+ In the package directory, create a Nix expression — a piece of code that
32+ describes how to build the package. In this case, it should be a
33+ <emphasis>function</emphasis> that is called with the package dependencies
34+ as arguments, and returns a build of the package in the Nix store. The
35+ expression should usually be called <filename>default.nix</filename>.
4536<screen>
4637$ emacs pkgs/development/libraries/libfoo/default.nix
4738$ git add pkgs/development/libraries/libfoo/default.nix</screen>
48−
4939 </para>
50−
51− <para>You can have a look at the existing Nix expressions under
52− <filename>pkgs/</filename> to see how it’s done. Here are some
53− good ones:
54−
55− <itemizedlist>
56−
57− <listitem>
58− <para>GNU Hello: <link
40+ <para>
41+ You can have a look at the existing Nix expressions under
42+ <filename>pkgs/</filename> to see how it’s done. Here are some good
43+ ones:
44+ <itemizedlist>
45+ <listitem>
46+ <para>
47+ GNU Hello:
48+ <link
5949 xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/misc/hello/default.nix"><filename>pkgs/applications/misc/hello/default.nix</filename></link>.
60− Trivial package, which specifies some <varname>meta</varname>
61− attributes which is good practice.</para>
62− </listitem>
63−
64− <listitem>
65− <para>GNU cpio: <link
50+ Trivial package, which specifies some <varname>meta</varname>
51+ attributes which is good practice.
52+ </para>
53+ </listitem>
54+ <listitem>
55+ <para>
56+ GNU cpio:
57+ <link
6658 xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/archivers/cpio/default.nix"><filename>pkgs/tools/archivers/cpio/default.nix</filename></link>.
67− Also a simple package. The generic builder in
68− <varname>stdenv</varname> does everything for you. It has
69− no dependencies beyond <varname>stdenv</varname>.</para>
70− </listitem>
71−
72− <listitem>
73− <para>GNU Multiple Precision arithmetic library (GMP): <link
59+ Also a simple package. The generic builder in <varname>stdenv</varname>
60+ does everything for you. It has no dependencies beyond
61+ <varname>stdenv</varname>.
62+ </para>
63+ </listitem>
64+ <listitem>
65+ <para>
66+ GNU Multiple Precision arithmetic library (GMP):
67+ <link
7468 xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/libraries/gmp/5.1.x.nix"><filename>pkgs/development/libraries/gmp/5.1.x.nix</filename></link>.
75− Also done by the generic builder, but has a dependency on
76− <varname>m4</varname>.</para>
77− </listitem>
78−
79− <listitem>
80− <para>Pan, a GTK-based newsreader: <link
69+ Also done by the generic builder, but has a dependency on
70+ <varname>m4</varname>.
71+ </para>
72+ </listitem>
73+ <listitem>
74+ <para>
75+ Pan, a GTK-based newsreader:
76+ <link
8177 xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/networking/newsreaders/pan/default.nix"><filename>pkgs/applications/networking/newsreaders/pan/default.nix</filename></link>.
82− Has an optional dependency on <varname>gtkspell</varname>,
83− which is only built if <varname>spellCheck</varname> is
84− <literal>true</literal>.</para>
85− </listitem>
86−
87− <listitem>
88− <para>Apache HTTPD: <link
78+ Has an optional dependency on <varname>gtkspell</varname>, which is
79+ only built if <varname>spellCheck</varname> is <literal>true</literal>.
80+ </para>
81+ </listitem>
82+ <listitem>
83+ <para>
84+ Apache HTTPD:
85+ <link
8986 xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/servers/http/apache-httpd/2.4.nix"><filename>pkgs/servers/http/apache-httpd/2.4.nix</filename></link>.
90− A bunch of optional features, variable substitutions in the
91− configure flags, a post-install hook, and miscellaneous
92− hackery.</para>
93− </listitem>
94−
95− <listitem>
96− <para>Thunderbird: <link
87+ A bunch of optional features, variable substitutions in the configure
88+ flags, a post-install hook, and miscellaneous hackery.
89+ </para>
90+ </listitem>
91+ <listitem>
92+ <para>
93+ Thunderbird:
94+ <link
9795 xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/networking/mailreaders/thunderbird/default.nix"><filename>pkgs/applications/networking/mailreaders/thunderbird/default.nix</filename></link>.
98− Lots of dependencies.</para>
99− </listitem>
100−
101− <listitem>
102− <para>JDiskReport, a Java utility: <link
96+ Lots of dependencies.
97+ </para>
98+ </listitem>
99+ <listitem>
100+ <para>
101+ JDiskReport, a Java utility:
102+ <link
103103 xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/misc/jdiskreport/default.nix"><filename>pkgs/tools/misc/jdiskreport/default.nix</filename></link>
104− (and the <link
104+ (and the
105+ <link
105106 xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/misc/jdiskreport/builder.sh">builder</link>).
106− Nixpkgs doesn’t have a decent <varname>stdenv</varname> for
107− Java yet so this is pretty ad-hoc.</para>
108− </listitem>
109−
110− <listitem>
111− <para>XML::Simple, a Perl module: <link
107+ Nixpkgs doesn’t have a decent <varname>stdenv</varname> for Java yet
108+ so this is pretty ad-hoc.
109+ </para>
110+ </listitem>
111+ <listitem>
112+ <para>
113+ XML::Simple, a Perl module:
114+ <link
112115 xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/top-level/perl-packages.nix"><filename>pkgs/top-level/perl-packages.nix</filename></link>
113− (search for the <varname>XMLSimple</varname> attribute).
114− Most Perl modules are so simple to build that they are
115− defined directly in <filename>perl-packages.nix</filename>;
116− no need to make a separate file for them.</para>
117− </listitem>
118−
119− <listitem>
120− <para>Adobe Reader: <link
116+ (search for the <varname>XMLSimple</varname> attribute). Most Perl
117+ modules are so simple to build that they are defined directly in
118+ <filename>perl-packages.nix</filename>; no need to make a separate file
119+ for them.
120+ </para>
121+ </listitem>
122+ <listitem>
123+ <para>
124+ Adobe Reader:
125+ <link
121126 xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/misc/adobe-reader/default.nix"><filename>pkgs/applications/misc/adobe-reader/default.nix</filename></link>.
122− Shows how binary-only packages can be supported. In
123− particular the <link
127+ Shows how binary-only packages can be supported. In particular the
128+ <link
124129 xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/misc/adobe-reader/builder.sh">builder</link>
125− uses <command>patchelf</command> to set the RUNPATH and ELF
126− interpreter of the executables so that the right libraries
127− are found at runtime.</para>
128− </listitem>
129−
130− </itemizedlist>
131−
130+ uses <command>patchelf</command> to set the RUNPATH and ELF interpreter
131+ of the executables so that the right libraries are found at runtime.
132+ </para>
133+ </listitem>
134+ </itemizedlist>
132135 </para>
133−
134− <para>Some notes:
135−
136− <itemizedlist>
137−
138− <listitem>
139− <para>All <varname linkend="chap-meta">meta</varname>
140− attributes are optional, but it’s still a good idea to
141− provide at least the <varname>description</varname>,
142− <varname>homepage</varname> and <varname
143− linkend="sec-meta-license">license</varname>.</para>
144− </listitem>
145−
146− <listitem>
147− <para>You can use <command>nix-prefetch-url</command> (or similar nix-prefetch-git, etc)
148− <replaceable>url</replaceable> to get the SHA-256 hash of
149− source distributions. There are similar commands as <command>nix-prefetch-git</command> and
150− <command>nix-prefetch-hg</command> available in <literal>nix-prefetch-scripts</literal> package.</para>
151− </listitem>
152−
153− <listitem>
154− <para>A list of schemes for <literal>mirror://</literal>
155− URLs can be found in <link
156− xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/fetchurl/mirrors.nix"><filename>pkgs/build-support/fetchurl/mirrors.nix</filename></link>.</para>
157− </listitem>
158−
159− </itemizedlist>
160−
136+ <para>
137+ Some notes:
138+ <itemizedlist>
139+ <listitem>
140+ <para>
141+ All <varname linkend="chap-meta">meta</varname> attributes are
142+ optional, but it’s still a good idea to provide at least the
143+ <varname>description</varname>, <varname>homepage</varname> and
144+ <varname
145+ linkend="sec-meta-license">license</varname>.
146+ </para>
147+ </listitem>
148+ <listitem>
149+ <para>
150+ You can use <command>nix-prefetch-url</command>
151+ <replaceable>url</replaceable> to get the
152+ SHA-256 hash of source distributions. There are similar commands as
153+ <command>nix-prefetch-git</command> and
154+ <command>nix-prefetch-hg</command> available in
155+ <literal>nix-prefetch-scripts</literal> package.
156+ </para>
157+ </listitem>
158+ <listitem>
159+ <para>
160+ A list of schemes for <literal>mirror://</literal> URLs can be found in
161+ <link
162+ xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/fetchurl/mirrors.nix"><filename>pkgs/build-support/fetchurl/mirrors.nix</filename></link>.
163+ </para>
164+ </listitem>
165+ </itemizedlist>
161166 </para>
162−
163− <para>The exact syntax and semantics of the Nix expression
164− language, including the built-in function, are described in the
165− Nix manual in the <link
167+ <para>
168+ The exact syntax and semantics of the Nix expression language, including
169+ the built-in function, are described in the Nix manual in the
170+ <link
166171 xlink:href="http://hydra.nixos.org/job/nix/trunk/tarball/latest/download-by-type/doc/manual/#chap-writing-nix-expressions">chapter
167− on writing Nix expressions</link>.</para>
168−
169− </listitem>
170−
171− <listitem>
172− <para>Add a call to the function defined in the previous step to
173− <link
172+ on writing Nix expressions</link>.
173+ </para>
174+ </listitem>
175+ <listitem>
176+ <para>
177+ Add a call to the function defined in the previous step to
178+ <link
174179 xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/top-level/all-packages.nix"><filename>pkgs/top-level/all-packages.nix</filename></link>
175− with some descriptive name for the variable,
176− e.g. <varname>libfoo</varname>.
177−
178− <screen>
180+ with some descriptive name for the variable, e.g.
181+ <varname>libfoo</varname>.
182+<screen>
179183$ emacs pkgs/top-level/all-packages.nix</screen>
180−
181184 </para>
182−
183− <para>The attributes in that file are sorted by category (like
184− “Development / Libraries”) that more-or-less correspond to the
185− directory structure of Nixpkgs, and then by attribute name.</para>
186− </listitem>
187−
188− <listitem>
189− <para>To test whether the package builds, run the following command
190− from the root of the nixpkgs source tree:
191−
192− <screen>
185+ <para>
186+ The attributes in that file are sorted by category (like “Development /
187+ Libraries”) that more-or-less correspond to the directory structure of
188+ Nixpkgs, and then by attribute name.
189+ </para>
190+ </listitem>
191+ <listitem>
192+ <para>
193+ To test whether the package builds, run the following command from the
194+ root of the nixpkgs source tree:
195+<screen>
193196$ nix-build -A libfoo</screen>
194−
195− where <varname>libfoo</varname> should be the variable name
196− defined in the previous step. You may want to add the flag
197− <option>-K</option> to keep the temporary build directory in case
198− something fails. If the build succeeds, a symlink
199− <filename>./result</filename> to the package in the Nix store is
200− created.</para>
201− </listitem>
202−
203− <listitem>
204− <para>If you want to install the package into your profile
205− (optional), do
206−
207− <screen>
197+ where <varname>libfoo</varname> should be the variable name defined in the
198+ previous step. You may want to add the flag <option>-K</option> to keep
199+ the temporary build directory in case something fails. If the build
200+ succeeds, a symlink <filename>./result</filename> to the package in the
201+ Nix store is created.
202+ </para>
203+ </listitem>
204+ <listitem>
205+ <para>
206+ If you want to install the package into your profile (optional), do
207+<screen>
208208$ nix-env -f . -iA libfoo</screen>
209−
210209 </para>
211− </listitem>
212−
213− <listitem>
214− <para>Optionally commit the new package and open a pull request, or send a patch to
215− <literal>https://groups.google.com/forum/#!forum/nix-devel</literal>.</para>
216− </listitem>
217−
218−
219−</orderedlist>
220−
221−</para>
222−
210+ </listitem>
211+ <listitem>
212+ <para>
213+ Optionally commit the new package and open a pull request, or send a patch
214+ to <literal>https://groups.google.com/forum/#!forum/nix-devel</literal>.
215+ </para>
216+ </listitem>
217+ </orderedlist>
218+ </para>
223219</chapter>
doc/release-notes.xml+710−643
@@ -1,164 +1,177 @@
11<?xml version="1.0" encoding="UTF-8"?>
22<article xmlns="http://docbook.org/ns/docbook"
33 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>
7+
8+ <para>
9+ In preparation for the switch from Subversion to Git, this release is mainly
10+ the prevent the Nixpkgs version number from going backwards. (This would
11+ happen because prerelease version numbers produced for the Git repository
12+ are lower than those for the Subversion repository.)
13+ </para>
414
5−<title>Nixpkgs Release Notes</title>
6−
7−
8−<section><title>Release 0.14 (June 4, 2012)</title>
9−
10−<para>In preparation for the switch from Subversion to Git, this
11−release is mainly the prevent the Nixpkgs version number from going
12−backwards. (This would happen because prerelease version numbers
13−produced for the Git repository are lower than those for the
14−Subversion repository.)</para>
15−
16−<para>Since the last release, there have been thousands of changes and
17−new packages by numerous contributors. For details, see the commit
18−logs.</para>
19−
20−</section>
21−
22−
23−<section><title>Release 0.13 (February 5, 2010)</title>
24−
25−<para>As always, there are many changes. Some of the most important
26−updates are:
27−
28−<itemizedlist>
29−
30− <listitem><para>Glibc 2.9.</para></listitem>
31−
32− <listitem><para>GCC 4.3.3.</para></listitem>
33−
34− <listitem><para>Linux 2.6.32.</para></listitem>
35−
36− <listitem><para>X.org 7.5.</para></listitem>
37−
38− <listitem><para>KDE 4.3.4.</para></listitem>
39−
40−</itemizedlist>
41−
42−</para>
43−
44−
45−</section>
46−
47−
48−<section><title>Release 0.12 (April 24, 2009)</title>
49−
50−<para>There are way too many additions to Nixpkgs since the last
51−release to list here: for example, the number of packages on Linux has
52−increased from 1002 to 2159. However, some specific improvements are
53−worth listing:
54−
55−<itemizedlist>
56−
57− <listitem><para>Nixpkgs now has a manual. In particular, it
58− describes the standard build environment in
59− detail.</para></listitem>
60−
61− <listitem><para>Major new packages:
62−
63− <itemizedlist>
64−
65− <listitem><para>KDE 4.</para></listitem>
66−
67− <listitem><para>TeXLive.</para></listitem>
68−
69− <listitem><para>VirtualBox.</para></listitem>
70−
71− </itemizedlist>
72−
73− … and many others.
74−
75− </para></listitem>
76−
77− <listitem><para>Important updates:
78−
79− <itemizedlist>
80−
81− <listitem><para>Glibc 2.7.</para></listitem>
82−
83− <listitem><para>GCC 4.2.4.</para></listitem>
84−
85− <listitem><para>Linux 2.6.25 — 2.6.28.</para></listitem>
86−
87− <listitem><para>Firefox 3.</para></listitem>
88−
89− <listitem><para>X.org 7.3.</para></listitem>
90−
91− </itemizedlist>
92−
93− </para></listitem>
94−
95− <listitem><para>Support for building derivations in a virtual
96− machine, including RPM and Debian builds in automatically generated
97− VM images. See
98− <filename>pkgs/build-support/vm/default.nix</filename> for
99− details.</para></listitem>
100−
101− <listitem><para>Improved support for building Haskell
102− packages.</para></listitem>
103−
104−</itemizedlist>
105−
106−</para>
107−
108−<para>The following people contributed to this release:
109−
110−Andres Löh,
111−Arie Middelkoop,
112−Armijn Hemel,
113−Eelco Dolstra,
114−Lluís Batlle,
115−Ludovic Courtès,
116−Marc Weber,
117−Mart Kolthof,
118−Martin Bravenboer,
119−Michael Raskin,
120−Nicolas Pierron,
121−Peter Simons,
122−Pjotr Prins,
123−Rob Vermaas,
124−Sander van der Burg,
125−Tobias Hammerschmidt,
126−Valentin David,
127−Wouter den Breejen and
128−Yury G. Kudryashov.
129−
130−In addition, several people contributed patches on the
131−<literal>nix-dev</literal> mailing list.</para>
132−
133−</section>
134−
135−
136−<section><title>Release 0.11 (September 11, 2007)</title>
137−
138−<para>This release has the following improvements:
139−
140−<itemizedlist>
141−
142−
143− <listitem><para>The standard build environment
144− (<literal>stdenv</literal>) is now pure on the
145− <literal>x86_64-linux</literal> and <literal>powerpc-linux</literal>
146− platforms, just as on <literal>i686-linux</literal>. (Purity means
147− that building and using the standard environment has no dependencies
148− outside of the Nix store. For instance, it doesn’t require an
149− external C compiler such as <filename>/usr/bin/gcc</filename>.)
150− Also, the statically linked binaries used in the bootstrap process
151− are now automatically reproducible, making it easy to update the
152− bootstrap tools and to add support for other Linux platforms. See
153− <filename>pkgs/stdenv/linux/make-bootstrap-tools.nix</filename> for
154− details.</para></listitem>
155−
156−
157− <listitem><para>Hook variables in the generic builder are now
158− executed using the <function>eval</function> shell command. This
159− has a major advantage: you can write hooks directly in Nix
160− expressions. For instance, rather than writing a builder like this:
15+ <para>
16+ Since the last release, there have been thousands of changes and new
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>
22+
23+ <para>
24+ As always, there are many changes. Some of the most important updates are:
25+ <itemizedlist>
26+ <listitem>
27+ <para>
28+ Glibc 2.9.
29+ </para>
30+ </listitem>
31+ <listitem>
32+ <para>
33+ GCC 4.3.3.
34+ </para>
35+ </listitem>
36+ <listitem>
37+ <para>
38+ Linux 2.6.32.
39+ </para>
40+ </listitem>
41+ <listitem>
42+ <para>
43+ X.org 7.5.
44+ </para>
45+ </listitem>
46+ <listitem>
47+ <para>
48+ KDE 4.3.4.
49+ </para>
50+ </listitem>
51+ </itemizedlist>
52+ </para>
53+ </section>
54+ <section xml:id="release-notes-0.12">
55+ <title>Release 0.12 (April 24, 2009)</title>
56+
57+ <para>
58+ There are way too many additions to Nixpkgs since the last release to list
59+ here: for example, the number of packages on Linux has increased from 1002
60+ to 2159. However, some specific improvements are worth listing:
61+ <itemizedlist>
62+ <listitem>
63+ <para>
64+ Nixpkgs now has a manual. In particular, it describes the standard build
65+ environment in detail.
66+ </para>
67+ </listitem>
68+ <listitem>
69+ <para>
70+ Major new packages:
71+ <itemizedlist>
72+ <listitem>
73+ <para>
74+ KDE 4.
75+ </para>
76+ </listitem>
77+ <listitem>
78+ <para>
79+ TeXLive.
80+ </para>
81+ </listitem>
82+ <listitem>
83+ <para>
84+ VirtualBox.
85+ </para>
86+ </listitem>
87+ </itemizedlist>
88+ … and many others.
89+ </para>
90+ </listitem>
91+ <listitem>
92+ <para>
93+ Important updates:
94+ <itemizedlist>
95+ <listitem>
96+ <para>
97+ Glibc 2.7.
98+ </para>
99+ </listitem>
100+ <listitem>
101+ <para>
102+ GCC 4.2.4.
103+ </para>
104+ </listitem>
105+ <listitem>
106+ <para>
107+ Linux 2.6.25 — 2.6.28.
108+ </para>
109+ </listitem>
110+ <listitem>
111+ <para>
112+ Firefox 3.
113+ </para>
114+ </listitem>
115+ <listitem>
116+ <para>
117+ X.org 7.3.
118+ </para>
119+ </listitem>
120+ </itemizedlist>
121+ </para>
122+ </listitem>
123+ <listitem>
124+ <para>
125+ Support for building derivations in a virtual machine, including RPM and
126+ Debian builds in automatically generated VM images. See
127+ <filename>pkgs/build-support/vm/default.nix</filename> for details.
128+ </para>
129+ </listitem>
130+ <listitem>
131+ <para>
132+ Improved support for building Haskell packages.
133+ </para>
134+ </listitem>
135+ </itemizedlist>
136+ </para>
161137
138+ <para>
139+ The following people contributed to this release: Andres Löh, Arie
140+ Middelkoop, Armijn Hemel, Eelco Dolstra, Lluís Batlle, Ludovic Courtès,
141+ Marc Weber, Mart Kolthof, Martin Bravenboer, Michael Raskin, Nicolas
142+ Pierron, Peter Simons, Pjotr Prins, Rob Vermaas, Sander van der Burg, Tobias
143+ Hammerschmidt, Valentin David, Wouter den Breejen and Yury G. Kudryashov. In
144+ addition, several people contributed patches on the
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>
150+
151+ <para>
152+ This release has the following improvements:
153+ <itemizedlist>
154+ <listitem>
155+ <para>
156+ The standard build environment (<literal>stdenv</literal>) is now pure on
157+ the <literal>x86_64-linux</literal> and <literal>powerpc-linux</literal>
158+ platforms, just as on <literal>i686-linux</literal>. (Purity means that
159+ building and using the standard environment has no dependencies outside
160+ of the Nix store. For instance, it doesn’t require an external C
161+ compiler such as <filename>/usr/bin/gcc</filename>.) Also, the statically
162+ linked binaries used in the bootstrap process are now automatically
163+ reproducible, making it easy to update the bootstrap tools and to add
164+ support for other Linux platforms. See
165+ <filename>pkgs/stdenv/linux/make-bootstrap-tools.nix</filename> for
166+ details.
167+ </para>
168+ </listitem>
169+ <listitem>
170+ <para>
171+ Hook variables in the generic builder are now executed using the
172+ <function>eval</function> shell command. This has a major advantage: you
173+ can write hooks directly in Nix expressions. For instance, rather than
174+ writing a builder like this:
162175<programlisting>
163176source $stdenv/setup
164177
@@ -169,290 +182,311 @@ postInstall() {
169182}
170183
171184genericBuild</programlisting>
172−
173− (the <literal>gzip</literal> builder), you can just add this
174− attribute to the derivation:
175−
185+ (the <literal>gzip</literal> builder), you can just add this attribute to
186+ the derivation:
176187<programlisting>
177188postInstall = "ln -sf gzip $out/bin/gunzip; ln -sf gzip $out/bin/zcat";</programlisting>
178−
179− and so a separate build script becomes unnecessary. This should
180− allow us to get rid of most builders in Nixpkgs.</para></listitem>
181−
182−
183− <listitem><para>It is now possible to have the generic builder pass
184− arguments to <command>configure</command> and
185− <command>make</command> that contain whitespace. Previously, for
186− example, you could say in a builder,
187−
189+ and so a separate build script becomes unnecessary. This should allow us
190+ to get rid of most builders in Nixpkgs.
191+ </para>
192+ </listitem>
193+ <listitem>
194+ <para>
195+ It is now possible to have the generic builder pass arguments to
196+ <command>configure</command> and <command>make</command> that contain
197+ whitespace. Previously, for example, you could say in a builder,
188198<programlisting>
189199configureFlags="CFLAGS=-O0"</programlisting>
190−
191− but not
192−
200+ but not
193201<programlisting>
194202configureFlags="CFLAGS=-O0 -g"</programlisting>
195−
196− since the <literal>-g</literal> would be interpreted as a separate
197− argument to <command>configure</command>. Now you can say
198−
203+ since the <literal>-g</literal> would be interpreted as a separate
204+ argument to <command>configure</command>. Now you can say
199205<programlisting>
200206configureFlagsArray=("CFLAGS=-O0 -g")</programlisting>
201−
202− or similarly
203−
207+ or similarly
204208<programlisting>
205209configureFlagsArray=("CFLAGS=-O0 -g" "LDFLAGS=-L/foo -L/bar")</programlisting>
206−
207− which does the right thing. Idem for <literal>makeFlags</literal>,
208− <literal>installFlags</literal>, <literal>checkFlags</literal> and
209− <literal>distFlags</literal>.</para>
210−
211− <para>Unfortunately you can't pass arrays to Bash through the
212− environment, so you can't put the array above in a Nix expression,
213− e.g.,
214−
210+ which does the right thing. Idem for <literal>makeFlags</literal>,
211+ <literal>installFlags</literal>, <literal>checkFlags</literal> and
212+ <literal>distFlags</literal>.
213+ </para>
214+ <para>
215+ Unfortunately you can't pass arrays to Bash through the environment, so
216+ you can't put the array above in a Nix expression, e.g.,
215217<programlisting>
216218configureFlagsArray = ["CFLAGS=-O0 -g"];</programlisting>
217−
218− since it would just be flattened to a since string. However, you
219− <emphasis>can</emphasis> use the inline hooks described above:
220−
219+ since it would just be flattened to a since string. However, you
220+ <emphasis>can</emphasis> use the inline hooks described above:
221221<programlisting>
222222preConfigure = "configureFlagsArray=(\"CFLAGS=-O0 -g\")";</programlisting>
223−
224− </para></listitem>
225−
226−
227− <listitem><para>The function <function>fetchurl</function> now has
228− support for two different kinds of mirroring of files. First, it
229− has support for <emphasis>content-addressable mirrors</emphasis>.
230− For example, given the <function>fetchurl</function> call
231−
223+ </para>
224+ </listitem>
225+ <listitem>
226+ <para>
227+ The function <function>fetchurl</function> now has support for two
228+ different kinds of mirroring of files. First, it has support for
229+ <emphasis>content-addressable mirrors</emphasis>. For example, given the
230+ <function>fetchurl</function> call
232231<programlisting>
233232fetchurl {
234233 url = http://releases.mozilla.org/<replaceable>...</replaceable>/firefox-2.0.0.6-source.tar.bz2;
235234 sha1 = "eb72f55e4a8bf08e8c6ef227c0ade3d068ba1082";
236235}</programlisting>
237−
238− <function>fetchurl</function> will first try to download this file
239− from <link
236+ <function>fetchurl</function> will first try to download this file from
237+ <link
240238 xlink:href="http://tarballs.nixos.org/sha1/eb72f55e4a8bf08e8c6ef227c0ade3d068ba1082"/>.
241− If that file doesn’t exist, it will try the original URL. In
242− general, the “content-addressed” location is
243− <replaceable>mirror</replaceable><literal>/</literal><replaceable>hash-type</replaceable><literal>/</literal><replaceable>hash</replaceable>.
244− There is currently only one content-addressable mirror (<link
239+ If that file doesn’t exist, it will try the original URL. In general,
240+ the “content-addressed” location is
241+ <replaceable>mirror</replaceable><literal>/</literal><replaceable>hash-type</replaceable><literal>/</literal><replaceable>hash</replaceable>.
242+ There is currently only one content-addressable mirror
243+ (<link
245244 xlink:href="http://tarballs.nixos.org"/>), but more can be
246− specified in the <varname>hashedMirrors</varname> attribute in
247− <filename>pkgs/build-support/fetchurl/mirrors.nix</filename>, or by
248− setting the <envar>NIX_HASHED_MIRRORS</envar> environment variable
249− to a whitespace-separated list of URLs.</para>
250−
251− <para>Second, <function>fetchurl</function> has support for
252− widely-mirrored distribution sites such as SourceForge or the Linux
253− kernel archives. Given a URL of the form
254− <literal>mirror://<replaceable>site</replaceable>/<replaceable>path</replaceable></literal>,
255− it will try to download <replaceable>path</replaceable> from a
256− configurable list of mirrors for <replaceable>site</replaceable>.
257− (This idea was borrowed from Gentoo Linux.) Example:
245+ specified in the <varname>hashedMirrors</varname> attribute in
246+ <filename>pkgs/build-support/fetchurl/mirrors.nix</filename>, or by
247+ setting the <envar>NIX_HASHED_MIRRORS</envar> environment variable to a
248+ whitespace-separated list of URLs.
249+ </para>
250+ <para>
251+ Second, <function>fetchurl</function> has support for widely-mirrored
252+ distribution sites such as SourceForge or the Linux kernel archives.
253+ Given a URL of the form
254+ <literal>mirror://<replaceable>site</replaceable>/<replaceable>path</replaceable></literal>,
255+ it will try to download <replaceable>path</replaceable> from a
256+ configurable list of mirrors for <replaceable>site</replaceable>. (This
257+ idea was borrowed from Gentoo Linux.) Example:
258258<programlisting>
259259fetchurl {
260260 url = mirror://gnu/gcc/gcc-4.2.0/gcc-core-4.2.0.tar.bz2;
261261 sha256 = "0ykhzxhr8857dr97z0j9wyybfz1kjr71xk457cfapfw5fjas4ny1";
262262}</programlisting>
263− Currently <replaceable>site</replaceable> can be
264− <literal>sourceforge</literal>, <literal>gnu</literal> and
265− <literal>kernel</literal>. The list of mirrors is defined in
266− <filename>pkgs/build-support/fetchurl/mirrors.nix</filename>. You
267− can override the list of mirrors for a particular site by setting
268− the environment variable
269− <envar>NIX_MIRRORS_<replaceable>site</replaceable></envar>, e.g.
263+ Currently <replaceable>site</replaceable> can be
264+ <literal>sourceforge</literal>, <literal>gnu</literal> and
265+ <literal>kernel</literal>. The list of mirrors is defined in
266+ <filename>pkgs/build-support/fetchurl/mirrors.nix</filename>. You can
267+ override the list of mirrors for a particular site by setting the
268+ environment variable
269+ <envar>NIX_MIRRORS_<replaceable>site</replaceable></envar>, e.g.
270270<programlisting>
271271export NIX_MIRRORS_sourceforge=http://osdn.dl.sourceforge.net/sourceforge/</programlisting>
272+ </para>
273+ </listitem>
274+ <listitem>
275+ <para>
276+ Important updates:
277+ <itemizedlist>
278+ <listitem>
279+ <para>
280+ Glibc 2.5.
281+ </para>
282+ </listitem>
283+ <listitem>
284+ <para>
285+ GCC 4.1.2.
286+ </para>
287+ </listitem>
288+ <listitem>
289+ <para>
290+ Gnome 2.16.3.
291+ </para>
292+ </listitem>
293+ <listitem>
294+ <para>
295+ X11R7.2.
296+ </para>
297+ </listitem>
298+ <listitem>
299+ <para>
300+ Linux 2.6.21.7 and 2.6.22.6.
301+ </para>
302+ </listitem>
303+ <listitem>
304+ <para>
305+ Emacs 22.1.
306+ </para>
307+ </listitem>
308+ </itemizedlist>
309+ </para>
310+ </listitem>
311+ <listitem>
312+ <para>
313+ Major new packages:
314+ <itemizedlist>
315+ <listitem>
316+ <para>
317+ KDE 3.5.6 Base.
318+ </para>
319+ </listitem>
320+ <listitem>
321+ <para>
322+ Wine 0.9.43.
323+ </para>
324+ </listitem>
325+ <listitem>
326+ <para>
327+ OpenOffice 2.2.1.
328+ </para>
329+ </listitem>
330+ <listitem>
331+ <para>
332+ Many Linux system packages to support NixOS.
333+ </para>
334+ </listitem>
335+ </itemizedlist>
336+ </para>
337+ </listitem>
338+ </itemizedlist>
272339 </para>
273340
274− </listitem>
275−
276−
277− <listitem><para>Important updates:
278−
279− <itemizedlist>
280−
281− <listitem><para>Glibc 2.5.</para></listitem>
282−
283− <listitem><para>GCC 4.1.2.</para></listitem>
284−
285− <listitem><para>Gnome 2.16.3.</para></listitem>
286−
287− <listitem><para>X11R7.2.</para></listitem>
288−
289− <listitem><para>Linux 2.6.21.7 and 2.6.22.6.</para></listitem>
290−
291− <listitem><para>Emacs 22.1.</para></listitem>
292−
293− </itemizedlist>
294−
295− </para></listitem>
296−
297−
298− <listitem><para>Major new packages:
299−
300− <itemizedlist>
301−
302− <listitem><para>KDE 3.5.6 Base.</para></listitem>
303−
304− <listitem><para>Wine 0.9.43.</para></listitem>
305−
306− <listitem><para>OpenOffice 2.2.1.</para></listitem>
307−
308− <listitem><para>Many Linux system packages to support
309− NixOS.</para></listitem>
310−
311− </itemizedlist>
312−
313− </para></listitem>
314−
315−</itemizedlist>
316−
317−</para>
318−
319−<para>The following people contributed to this release:
320−
321− Andres Löh,
322− Arie Middelkoop,
323− Armijn Hemel,
324− Eelco Dolstra,
325− Marc Weber,
326− Mart Kolthof,
327− Martin Bravenboer,
328− Michael Raskin,
329− Wouter den Breejen and
330− Yury G. Kudryashov.
331−
332−</para>
333−
334−</section>
335−
336−
337−<section><title>Release 0.10 (October 12, 2006)</title>
338−
339−<note><para>This release of Nixpkgs requires <link
340−xlink:href='http://nixos.org/releases/nix/nix-0.10/'>Nix
341−0.10</link> or higher.</para></note>
342−
343−<para>This release has the following improvements:</para>
344−
345−<itemizedlist>
346−
347− <listitem><para><filename>pkgs/system/all-packages-generic.nix</filename>
348− is gone, we now just have
349− <filename>pkgs/top-level/all-packages.nix</filename> that contains
350− all available packages. This should cause much less confusion with
351− users. <filename>all-packages.nix</filename> is a function that by
352− default returns packages for the current platform, but you can
353− override this by specifying a different <varname>system</varname>
354− argument.</para></listitem>
355−
356− <listitem><para>Certain packages in Nixpkgs are now
357− user-configurable through a configuration file, i.e., without having
358− to edit the Nix expressions in Nixpkgs. For instance, the Firefox
359− provided in the Nixpkgs channel is built without the RealPlayer
360− plugin (for legal reasons). Previously, you could easily enable
361− RealPlayer support by editing the call to the Firefox function in
362− <filename>all-packages.nix</filename>, but such changes are not
363− respected when Firefox is subsequently updated through the Nixpkgs
364− channel.</para>
365−
366− <para>The Nixpkgs configuration file (found in
367− <filename>~/.nixpkgs/config.nix</filename> or through the
368− <envar>NIXPKGS_CONFIG</envar> environment variable) is an attribute
369− set that contains configuration options that
370− <filename>all-packages.nix</filename> reads and uses for certain
371− packages. For instance, the following configuration file:
341+ <para>
342+ The following people contributed to this release: Andres Löh, Arie
343+ Middelkoop, Armijn Hemel, Eelco Dolstra, Marc Weber, Mart Kolthof, Martin
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>
349+
350+ <note>
351+ <para>
352+ This release of Nixpkgs requires
353+ <link
354+xlink:href='http://nixos.org/releases/nix/nix-0.10/'>Nix 0.10</link>
355+ or higher.
356+ </para>
357+ </note>
358+
359+ <para>
360+ This release has the following improvements:
361+ </para>
372362
363+ <itemizedlist>
364+ <listitem>
365+ <para>
366+ <filename>pkgs/system/all-packages-generic.nix</filename> is gone, we now
367+ just have <filename>pkgs/top-level/all-packages.nix</filename> that
368+ contains all available packages. This should cause much less confusion
369+ with users. <filename>all-packages.nix</filename> is a function that by
370+ default returns packages for the current platform, but you can override
371+ this by specifying a different <varname>system</varname> argument.
372+ </para>
373+ </listitem>
374+ <listitem>
375+ <para>
376+ Certain packages in Nixpkgs are now user-configurable through a
377+ configuration file, i.e., without having to edit the Nix expressions in
378+ Nixpkgs. For instance, the Firefox provided in the Nixpkgs channel is
379+ built without the RealPlayer plugin (for legal reasons). Previously, you
380+ could easily enable RealPlayer support by editing the call to the Firefox
381+ function in <filename>all-packages.nix</filename>, but such changes are
382+ not respected when Firefox is subsequently updated through the Nixpkgs
383+ channel.
384+ </para>
385+ <para>
386+ The Nixpkgs configuration file (found in
387+ <filename>~/.nixpkgs/config.nix</filename> or through the
388+ <envar>NIXPKGS_CONFIG</envar> environment variable) is an attribute set
389+ that contains configuration options that
390+ <filename>all-packages.nix</filename> reads and uses for certain packages.
391+ For instance, the following configuration file:
373392<programlisting>
374393{
375394 firefox = {
376395 enableRealPlayer = true;
377396 };
378397}</programlisting>
379−
380− persistently enables RealPlayer support in the Firefox
381− build.</para>
382−
383− <para>(Actually, <literal>firefox.enableRealPlayer</literal> is the
384− <emphasis>only</emphasis> configuration option currently available,
385− but more are sure to be added.)</para></listitem>
386−
387− <listitem><para>Support for new platforms:
388−
389− <itemizedlist>
390−
391− <listitem><para><literal>i686-cygwin</literal>, i.e., Windows
392− (using <link xlink:href="http://www.cygwin.com/">Cygwin</link>).
393− The standard environment on <literal>i686-cygwin</literal> by
394− default builds binaries for the Cygwin environment (i.e., it
395− uses Cygwin tools and produces executables that use the Cygwin
396− library). However, there is also a standard environment that
397− produces binaries that use <link
398− xlink:href="http://www.mingw.org/">MinGW</link>. You can use it
399− by calling <filename>all-package.nix</filename> with the
400− <varname>stdenvType</varname> argument set to
401− <literal>"i686-mingw"</literal>.</para></listitem>
402−
403− <listitem><para><literal>i686-darwin</literal>, i.e., Mac OS X
404− on Intel CPUs.</para></listitem>
405−
406− <listitem><para><literal>powerpc-linux</literal>.</para></listitem>
407−
408− <listitem><para><literal>x86_64-linux</literal>, i.e., Linux on
409− 64-bit AMD/Intel CPUs. Unlike <literal>i686-linux</literal>,
410− this platform doesn’t have a pure <literal>stdenv</literal>
411− yet.</para></listitem>
412−
413− </itemizedlist>
414−
398+ persistently enables RealPlayer support in the Firefox build.
415399 </para>
416−
417− </listitem>
418−
419− <listitem><para>The default compiler is now GCC 4.1.1.</para></listitem>
420−
421− <listitem><para>X11 updated to X.org’s X11R7.1.</para></listitem>
422−
423− <listitem><para>Notable new packages:
424−
425− <itemizedlist>
426−
427− <listitem><para>Opera.</para></listitem>
428−
429− <listitem><para>Microsoft Visual C++ 2005 Express Edition and
430− the Windows SDK.</para></listitem>
431−
432− </itemizedlist>
433−
434− In total there are now around 809 packages in Nixpkgs.</para>
435−
436− </listitem>
437−
438−
439− <listitem><para>It is now <emphasis>much</emphasis> easier to
440− override the default C compiler and other tools in
441− <literal>stdenv</literal> for specific packages.
442− <filename>all-packages.nix</filename> provides two utility
443− functions for this purpose: <function>overrideGCC</function> and
444− <function>overrideInStdenv</function>. Both take a
445− <literal>stdenv</literal> and return an augmented
446− <literal>stdenv</literal>; the formed changes the C compiler, and
447− the latter adds additional packages to the front of
448− <literal>stdenv</literal>’s initial <envar>PATH</envar>, allowing
449− tools to be overridden.</para>
450−
451− <para>For instance, the package <varname>strategoxt</varname>
452− doesn’t build with the GNU Make in <literal>stdenv</literal>
453− (version 3.81), so we call it with an augmented
454− <literal>stdenv</literal> that uses GNU Make 3.80:
455−
400+ <para>
401+ (Actually, <literal>firefox.enableRealPlayer</literal> is the
402+ <emphasis>only</emphasis> configuration option currently available, but
403+ more are sure to be added.)
404+ </para>
405+ </listitem>
406+ <listitem>
407+ <para>
408+ Support for new platforms:
409+ <itemizedlist>
410+ <listitem>
411+ <para>
412+ <literal>i686-cygwin</literal>, i.e., Windows (using
413+ <link xlink:href="http://www.cygwin.com/">Cygwin</link>). The standard
414+ environment on <literal>i686-cygwin</literal> by default builds
415+ binaries for the Cygwin environment (i.e., it uses Cygwin tools and
416+ produces executables that use the Cygwin library). However, there is
417+ also a standard environment that produces binaries that use
418+ <link
419+ xlink:href="http://www.mingw.org/">MinGW</link>. You can
420+ use it by calling <filename>all-package.nix</filename> with the
421+ <varname>stdenvType</varname> argument set to
422+ <literal>"i686-mingw"</literal>.
423+ </para>
424+ </listitem>
425+ <listitem>
426+ <para>
427+ <literal>i686-darwin</literal>, i.e., Mac OS X on Intel CPUs.
428+ </para>
429+ </listitem>
430+ <listitem>
431+ <para>
432+ <literal>powerpc-linux</literal>.
433+ </para>
434+ </listitem>
435+ <listitem>
436+ <para>
437+ <literal>x86_64-linux</literal>, i.e., Linux on 64-bit AMD/Intel CPUs.
438+ Unlike <literal>i686-linux</literal>, this platform doesn’t have a
439+ pure <literal>stdenv</literal> yet.
440+ </para>
441+ </listitem>
442+ </itemizedlist>
443+ </para>
444+ </listitem>
445+ <listitem>
446+ <para>
447+ The default compiler is now GCC 4.1.1.
448+ </para>
449+ </listitem>
450+ <listitem>
451+ <para>
452+ X11 updated to X.org’s X11R7.1.
453+ </para>
454+ </listitem>
455+ <listitem>
456+ <para>
457+ Notable new packages:
458+ <itemizedlist>
459+ <listitem>
460+ <para>
461+ Opera.
462+ </para>
463+ </listitem>
464+ <listitem>
465+ <para>
466+ Microsoft Visual C++ 2005 Express Edition and the Windows SDK.
467+ </para>
468+ </listitem>
469+ </itemizedlist>
470+ In total there are now around 809 packages in Nixpkgs.
471+ </para>
472+ </listitem>
473+ <listitem>
474+ <para>
475+ It is now <emphasis>much</emphasis> easier to override the default C
476+ compiler and other tools in <literal>stdenv</literal> for specific
477+ packages. <filename>all-packages.nix</filename> provides two utility
478+ functions for this purpose: <function>overrideGCC</function> and
479+ <function>overrideInStdenv</function>. Both take a
480+ <literal>stdenv</literal> and return an augmented
481+ <literal>stdenv</literal>; the formed changes the C compiler, and the
482+ latter adds additional packages to the front of
483+ <literal>stdenv</literal>’s initial <envar>PATH</envar>, allowing tools
484+ to be overridden.
485+ </para>
486+ <para>
487+ For instance, the package <varname>strategoxt</varname> doesn’t build
488+ with the GNU Make in <literal>stdenv</literal> (version 3.81), so we call
489+ it with an augmented <literal>stdenv</literal> that uses GNU Make 3.80:
456490<programlisting>
457491strategoxt = (import ../development/compilers/strategoxt) {
458492 inherit fetchurl pkgconfig sdf aterm;
@@ -460,44 +494,37 @@ strategoxt = (import ../development/compilers/strategoxt) {
460494};
461495
462496gnumake380 = <replaceable>...</replaceable>;</programlisting>
463−
464− Likewise, there are many packages that don’t compile with the
465− default GCC (4.1.1), but that’s easily fixed:
466−
497+ Likewise, there are many packages that don’t compile with the default
498+ GCC (4.1.1), but that’s easily fixed:
467499<programlisting>
468500exult = import ../games/exult {
469501 inherit fetchurl SDL SDL_mixer zlib libpng unzip;
470502 stdenv = overrideGCC stdenv gcc34;
471503};</programlisting>
472−
473− </para></listitem>
474−
475−
476− <listitem><para>It has also become much easier to experiment with
477− changes to the <literal>stdenv</literal> setup script (which notably
478− contains the generic builder). Since edits to
479− <filename>pkgs/stdenv/generic/setup.sh</filename> trigger a rebuild
480− of <emphasis>everything</emphasis>, this was formerly quite painful.
481− But now <literal>stdenv</literal> contains a function to
482− “regenerate” <literal>stdenv</literal> with a different setup
483− script, allowing the use of a different setup script for specific
484− packages:
485−
504+ </para>
505+ </listitem>
506+ <listitem>
507+ <para>
508+ It has also become much easier to experiment with changes to the
509+ <literal>stdenv</literal> setup script (which notably contains the generic
510+ builder). Since edits to <filename>pkgs/stdenv/generic/setup.sh</filename>
511+ trigger a rebuild of <emphasis>everything</emphasis>, this was formerly
512+ quite painful. But now <literal>stdenv</literal> contains a function to
513+ “regenerate” <literal>stdenv</literal> with a different setup script,
514+ allowing the use of a different setup script for specific packages:
486515<programlisting>
487516pkg = import <replaceable>...</replaceable> {
488517 stdenv = stdenv.regenerate ./my-setup.sh;
489518 <replaceable>...</replaceable>
490519}</programlisting>
491−
492− </para></listitem>
493−
494−
495− <listitem><para>Packages can now have a human-readable
496− <emphasis>description</emphasis> field. Package descriptions are
497− shown by <literal>nix-env -qa --description</literal>. In addition,
498− they’re shown on the Nixpkgs release page. A description can be
499− added to a package as follows:
500−
520+ </para>
521+ </listitem>
522+ <listitem>
523+ <para>
524+ Packages can now have a human-readable <emphasis>description</emphasis>
525+ field. Package descriptions are shown by <literal>nix-env -qa
526+ --description</literal>. In addition, they’re shown on the Nixpkgs
527+ release page. A description can be added to a package as follows:
501528<programlisting>
502529stdenv.mkDerivation {
503530 name = "exult-1.2";
@@ -506,228 +533,268 @@ stdenv.mkDerivation {
506533 description = "A reimplementation of the Ultima VII game engine";
507534 };
508535}</programlisting>
509−
510− The <varname>meta</varname> attribute is not passed to the builder,
511− so changes to the description do not trigger a rebuild. Additional
512− <varname>meta</varname> attributes may be defined in the future
513− (such as the URL of the package’s homepage, the license,
514− etc.).</para></listitem>
515−
516−</itemizedlist>
517−
518−
519−<para>The following people contributed to this release:
520−
521− Andres Löh,
522− Armijn Hemel,
523− Christof Douma,
524− Eelco Dolstra,
525− Eelco Visser,
526− Mart Kolthof,
527− Martin Bravenboer,
528− Merijn de Jonge,
529− Rob Vermaas and
530− Roy van den Broek.
531−
532−</para>
533−
534−</section>
535−
536−
537−<section><title>Release 0.9 (January 31, 2006)</title>
538−
539−<para>There have been zillions of changes since the last release of
540−Nixpkgs. Many packages have been added or updated. The following are
541−some of the more notable changes:</para>
542−
543−<itemizedlist>
544−
545− <listitem><para>Distribution files have been moved to <link
546− xlink:href="http://nixos.org/" />.</para></listitem>
547−
548− <listitem><para>The C library on Linux, Glibc, has been updated to
549− version 2.3.6.</para></listitem>
550−
551− <listitem><para>The default compiler is now GCC 3.4.5. GCC 4.0.2 is
552− also available.</para></listitem>
553−
554− <listitem><para>The old, unofficial Xlibs has been replaced by the
555− official modularised X11 distribution from X.org, i.e., X11R7.0.
556− X11R7.0 consists of 287 (!) packages, all of which are in Nixpkgs
557− though not all have been tested. It is now possible to build a
558− working X server (previously we only had X client libraries). We
559− use a fully Nixified X server on NixOS.</para></listitem>
560−
561− <listitem><para>The Sun JDK 5 has been purified, i.e., it doesn’t
562− require any non-Nix components such as
563− <filename>/lib/ld-linux.so.2</filename>. This means that Java
564− applications such as Eclipse and Azureus can run on
565− NixOS.</para></listitem>
566−
567− <listitem><para>Hardware-accelerated OpenGL support, used by games
568− like Quake 3 (which is now built from source).</para></listitem>
569−
570− <listitem><para>Improved support for FreeBSD on
571− x86.</para></listitem>
572−
573− <listitem><para>Improved Haskell support; e.g., the GHC build is now
574− pure.</para></listitem>
575−
576− <listitem><para>Some support for cross-compilation: cross-compiling
577− builds of GCC and Binutils, and cross-compiled builds of the C
578− library uClibc.</para></listitem>
579−
580− <listitem><para>Notable new packages:
581−
582− <itemizedlist>
583−
584− <listitem><para>teTeX, including support for building LaTeX
585− documents using Nix (with automatic dependency
586− determination).</para></listitem>
587−
588− <listitem><para>Ruby.</para></listitem>
589−
590− <listitem><para>System-level packages to support NixOS,
591− e.g. Grub, GNU <literal>parted</literal> and so
592− on.</para></listitem>
593−
594− <listitem><para><literal>ecj</literal>, the Eclipse Compiler for
595− Java, so we finally have a freely distributable compiler that
596− supports Java 5.0.</para></listitem>
597−
598− <listitem><para><literal>php</literal>.</para></listitem>
599−
600− <listitem><para>The GIMP.</para></listitem>
601−
602− <listitem><para>Inkscape.</para></listitem>
603−
604− <listitem><para>GAIM.</para></listitem>
605−
606− <listitem><para><literal>kdelibs</literal>. This allows us to
607− add KDE-based packages (such as
608− <literal>kcachegrind</literal>).</para></listitem>
609−
610− </itemizedlist>
611−
612− </para></listitem>
613−
614−</itemizedlist>
615−
616−<para>The following people contributed to this release:
617−
618− Andres Löh,
619− Armijn Hemel,
620− Bogdan Dumitriu,
621− Christof Douma,
622− Eelco Dolstra,
623− Eelco Visser,
624− Mart Kolthof,
625− Martin Bravenboer,
626− Rob Vermaas and
627− Roy van den Broek.
628−
629−</para>
630−
631−</section>
632−
633−
634−<section><title>Release 0.8 (April 11, 2005)</title>
635−
636−<para>This release is mostly to remain synchronised with the changed
637−hashing scheme in Nix 0.8.</para>
638−
639−<para>Notable updates:
640−
641−<itemizedlist>
642−
643− <listitem><para>Adobe Reader 7.0</para></listitem>
644−
645− <listitem><para>Various security updates (zlib 1.2.2, etc.)</para></listitem>
646−
647−</itemizedlist>
648−
649−</para>
650−
651−</section>
652−
653−
654−<section><title>Release 0.7 (March 14, 2005)</title>
655−
656−<itemizedlist>
657−
658−<listitem>
659−
660− <para>The bootstrap process for the standard build
661− environment on Linux (stdenv-linux) has been improved. It is no
662− longer dependent in its initial bootstrap stages on the system
663− Glibc, GCC, and other tools. Rather, Nixpkgs contains a statically
664− linked bash and curl, and uses that to download other statically
665− linked tools. These are then used to build a Glibc and dynamically
666− linked versions of all other tools.</para>
667−
668− <para>This change also makes the bootstrap process faster. For
669− instance, GCC is built only once instead of three times.</para>
670−
671− <para>(Contributed by Armijn Hemel.)</para>
672−
673−</listitem>
674−
675−<listitem>
676−
677− <para>Tarballs used by Nixpkgs are now obtained from the same server
678− that hosts Nixpkgs (<link
679− xlink:href="http://catamaran.labs.cs.uu.nl/" />). This reduces the
680− risk of packages being unbuildable due to moved or deleted files on
681− various servers.</para>
682−
683−</listitem>
684−
685−<listitem>
686−
687− <para>There now is a generic mechanism for building Perl modules.
688− See the various Perl modules defined in
689− pkgs/system/all-packages-generic.nix.</para>
690−
691−</listitem>
692−
693−<listitem>
694−
695− <para>Notable new packages:
696−
697− <itemizedlist>
698−
699− <listitem><para>Qt 3</para></listitem>
700− <listitem><para>MySQL</para></listitem>
701− <listitem><para>MythTV</para></listitem>
702− <listitem><para>Mono</para></listitem>
703− <listitem><para>MonoDevelop (alpha)</para></listitem>
704− <listitem><para>Xine</para></listitem>
705−
536+ The <varname>meta</varname> attribute is not passed to the builder, so
537+ changes to the description do not trigger a rebuild. Additional
538+ <varname>meta</varname> attributes may be defined in the future (such as
539+ the URL of the package’s homepage, the license, etc.).
540+ </para>
541+ </listitem>
706542 </itemizedlist>
707543
544+ <para>
545+ The following people contributed to this release: Andres Löh, Armijn Hemel,
546+ Christof Douma, Eelco Dolstra, Eelco Visser, Mart Kolthof, Martin
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>
552+
553+ <para>
554+ There have been zillions of changes since the last release of Nixpkgs. Many
555+ packages have been added or updated. The following are some of the more
556+ notable changes:
708557 </para>
709−
710−</listitem>
711−
712−<listitem>
713−
714− <para>Notable updates:
715558
716559 <itemizedlist>
717−
718− <listitem><para>GCC 3.4.3</para></listitem>
719− <listitem><para>Glibc 2.3.4</para></listitem>
720− <listitem><para>GTK 2.6</para></listitem>
721−
560+ <listitem>
561+ <para>
562+ Distribution files have been moved to
563+ <link
564+ xlink:href="http://nixos.org/" />.
565+ </para>
566+ </listitem>
567+ <listitem>
568+ <para>
569+ The C library on Linux, Glibc, has been updated to version 2.3.6.
570+ </para>
571+ </listitem>
572+ <listitem>
573+ <para>
574+ The default compiler is now GCC 3.4.5. GCC 4.0.2 is also available.
575+ </para>
576+ </listitem>
577+ <listitem>
578+ <para>
579+ The old, unofficial Xlibs has been replaced by the official modularised
580+ X11 distribution from X.org, i.e., X11R7.0. X11R7.0 consists of 287 (!)
581+ packages, all of which are in Nixpkgs though not all have been tested. It
582+ is now possible to build a working X server (previously we only had X
583+ client libraries). We use a fully Nixified X server on NixOS.
584+ </para>
585+ </listitem>
586+ <listitem>
587+ <para>
588+ The Sun JDK 5 has been purified, i.e., it doesn’t require any non-Nix
589+ components such as <filename>/lib/ld-linux.so.2</filename>. This means
590+ that Java applications such as Eclipse and Azureus can run on NixOS.
591+ </para>
592+ </listitem>
593+ <listitem>
594+ <para>
595+ Hardware-accelerated OpenGL support, used by games like Quake 3 (which is
596+ now built from source).
597+ </para>
598+ </listitem>
599+ <listitem>
600+ <para>
601+ Improved support for FreeBSD on x86.
602+ </para>
603+ </listitem>
604+ <listitem>
605+ <para>
606+ Improved Haskell support; e.g., the GHC build is now pure.
607+ </para>
608+ </listitem>
609+ <listitem>
610+ <para>
611+ Some support for cross-compilation: cross-compiling builds of GCC and
612+ Binutils, and cross-compiled builds of the C library uClibc.
613+ </para>
614+ </listitem>
615+ <listitem>
616+ <para>
617+ Notable new packages:
618+ <itemizedlist>
619+ <listitem>
620+ <para>
621+ teTeX, including support for building LaTeX documents using Nix (with
622+ automatic dependency determination).
623+ </para>
624+ </listitem>
625+ <listitem>
626+ <para>
627+ Ruby.
628+ </para>
629+ </listitem>
630+ <listitem>
631+ <para>
632+ System-level packages to support NixOS, e.g. Grub, GNU
633+ <literal>parted</literal> and so on.
634+ </para>
635+ </listitem>
636+ <listitem>
637+ <para>
638+ <literal>ecj</literal>, the Eclipse Compiler for Java, so we finally
639+ have a freely distributable compiler that supports Java 5.0.
640+ </para>
641+ </listitem>
642+ <listitem>
643+ <para>
644+ <literal>php</literal>.
645+ </para>
646+ </listitem>
647+ <listitem>
648+ <para>
649+ The GIMP.
650+ </para>
651+ </listitem>
652+ <listitem>
653+ <para>
654+ Inkscape.
655+ </para>
656+ </listitem>
657+ <listitem>
658+ <para>
659+ GAIM.
660+ </para>
661+ </listitem>
662+ <listitem>
663+ <para>
664+ <literal>kdelibs</literal>. This allows us to add KDE-based packages
665+ (such as <literal>kcachegrind</literal>).
666+ </para>
667+ </listitem>
668+ </itemizedlist>
669+ </para>
670+ </listitem>
722671 </itemizedlist>
723672
673+ <para>
674+ The following people contributed to this release: Andres Löh, Armijn Hemel,
675+ Bogdan Dumitriu, Christof Douma, Eelco Dolstra, Eelco Visser, Mart Kolthof,
676+ Martin Bravenboer, Rob Vermaas and Roy van den Broek.
724677 </para>
678+ </section>
679+ <section xml:id="release-notes-0.8">
680+ <title>Release 0.8 (April 11, 2005)</title>
725681
726−</listitem>
727−
728−</itemizedlist>
682+ <para>
683+ This release is mostly to remain synchronised with the changed hashing
684+ scheme in Nix 0.8.
685+ </para>
729686
730−</section>
687+ <para>
688+ Notable updates:
689+ <itemizedlist>
690+ <listitem>
691+ <para>
692+ Adobe Reader 7.0
693+ </para>
694+ </listitem>
695+ <listitem>
696+ <para>
697+ Various security updates (zlib 1.2.2, etc.)
698+ </para>
699+ </listitem>
700+ </itemizedlist>
701+ </para>
702+ </section>
703+ <section xml:id="release-notes-0.7">
704+ <title>Release 0.7 (March 14, 2005)</title>
731705
732−
706+ <itemizedlist>
707+ <listitem>
708+ <para>
709+ The bootstrap process for the standard build environment on Linux
710+ (stdenv-linux) has been improved. It is no longer dependent in its initial
711+ bootstrap stages on the system Glibc, GCC, and other tools. Rather,
712+ Nixpkgs contains a statically linked bash and curl, and uses that to
713+ download other statically linked tools. These are then used to build a
714+ Glibc and dynamically linked versions of all other tools.
715+ </para>
716+ <para>
717+ This change also makes the bootstrap process faster. For instance, GCC is
718+ built only once instead of three times.
719+ </para>
720+ <para>
721+ (Contributed by Armijn Hemel.)
722+ </para>
723+ </listitem>
724+ <listitem>
725+ <para>
726+ Tarballs used by Nixpkgs are now obtained from the same server that hosts
727+ Nixpkgs (<link
728+ xlink:href="http://catamaran.labs.cs.uu.nl/" />). This
729+ reduces the risk of packages being unbuildable due to moved or deleted
730+ files on various servers.
731+ </para>
732+ </listitem>
733+ <listitem>
734+ <para>
735+ There now is a generic mechanism for building Perl modules. See the
736+ various Perl modules defined in pkgs/system/all-packages-generic.nix.
737+ </para>
738+ </listitem>
739+ <listitem>
740+ <para>
741+ Notable new packages:
742+ <itemizedlist>
743+ <listitem>
744+ <para>
745+ Qt 3
746+ </para>
747+ </listitem>
748+ <listitem>
749+ <para>
750+ MySQL
751+ </para>
752+ </listitem>
753+ <listitem>
754+ <para>
755+ MythTV
756+ </para>
757+ </listitem>
758+ <listitem>
759+ <para>
760+ Mono
761+ </para>
762+ </listitem>
763+ <listitem>
764+ <para>
765+ MonoDevelop (alpha)
766+ </para>
767+ </listitem>
768+ <listitem>
769+ <para>
770+ Xine
771+ </para>
772+ </listitem>
773+ </itemizedlist>
774+ </para>
775+ </listitem>
776+ <listitem>
777+ <para>
778+ Notable updates:
779+ <itemizedlist>
780+ <listitem>
781+ <para>
782+ GCC 3.4.3
783+ </para>
784+ </listitem>
785+ <listitem>
786+ <para>
787+ Glibc 2.3.4
788+ </para>
789+ </listitem>
790+ <listitem>
791+ <para>
792+ GTK 2.6
793+ </para>
794+ </listitem>
795+ </itemizedlist>
796+ </para>
797+ </listitem>
798+ </itemizedlist>
799+ </section>
733800</article>
doc/reviewing-contributions.xml+488−263

This diff is too big to show here.

doc/shell.mddeleted−20

This diff is too big to show here.

doc/shell.nixnew file+5

This diff is too big to show here.

doc/stdenv.xml+2515−1850

This diff is too big to show here.

doc/style.css+23−7

This diff is too big to show here.

doc/submitting-changes.xml+463−399

This diff is too big to show here.

lib/asserts.nixnew file+44

This diff is too big to show here.

lib/attrsets.nix+16−11

This diff is too big to show here.

lib/composable-derivation.nix+1−1

This diff is too big to show here.

lib/customisation.nix+5−15

This diff is too big to show here.

lib/debug.nix+194−66

This diff is too big to show here.

lib/default.nix+40−34

This diff is too big to show here.

lib/generators.nix+106−16

This diff is too big to show here.

lib/kernel.nixnew file+57

This diff is too big to show here.

lib/licenses.nix+94−1

This diff is too big to show here.

lib/lists.nix+195−48

This diff is too big to show here.

lib/maintainers.nixdeleted−799

This diff is too big to show here.

lib/meta.nix+19

This diff is too big to show here.

lib/minver.nix+1−1

This diff is too big to show here.

lib/modules.nix+86−49

This diff is too big to show here.

lib/options.nix+99−26

This diff is too big to show here.

lib/sources.nix+7−3

This diff is too big to show here.

lib/strings.nix+215−59

This diff is too big to show here.

lib/systems/default.nix+41−6

This diff is too big to show here.

lib/systems/doubles.nix+11−7

This diff is too big to show here.

lib/systems/examples.nix+114−23

This diff is too big to show here.

lib/systems/for-meta.nixnew file+37

This diff is too big to show here.

lib/systems/inspect.nix+46−33

This diff is too big to show here.

lib/systems/parse.nix+105−31

This diff is too big to show here.

lib/systems/platforms.nix+149−235

This diff is too big to show here.

lib/tests/check-eval.nixnew file+7

This diff is too big to show here.

lib/tests/misc.nix+89−8

This diff is too big to show here.

lib/tests/modules.sh+12−1

This diff is too big to show here.

lib/tests/modules/declare-coerced-value-unsound.nixnew file+10

This diff is too big to show here.

lib/tests/modules/define-value-string-arbitrary.nixnew file+3

This diff is too big to show here.

lib/tests/modules/define-value-string-bigint.nixnew file+3

This diff is too big to show here.

lib/tests/modules/loaOf-with-long-list.nixnew file+19

This diff is too big to show here.

lib/tests/modules/loaOf-with-many-list-merges.nixnew file+19

This diff is too big to show here.

lib/tests/release.nix+1−2

This diff is too big to show here.

lib/tests/systems.nix+15−14

This diff is too big to show here.

lib/trivial.nix+174−47

This diff is too big to show here.

lib/types.nix+52−22

This diff is too big to show here.

lib/versions.nixnew file+47

This diff is too big to show here.

lib/zip-int-bits.nixnew file+39

This diff is too big to show here.

maintainers/maintainer-list.nixnew file+4895

This diff is too big to show here.

maintainers/scripts/all-tarballs.nix+3−5

This diff is too big to show here.

maintainers/scripts/check-maintainer-github-handles.shnew file+66

This diff is too big to show here.

maintainers/scripts/copy-tarballs.pl+8−2

This diff is too big to show here.

maintainers/scripts/gnome.shdeleted−192

This diff is too big to show here.

maintainers/scripts/hydra-eval-failures.py+20−15

This diff is too big to show here.

maintainers/scripts/nix-generate-from-cpan.nix+1−1

This diff is too big to show here.

maintainers/scripts/nixpkgs-lint.pl+2−1

This diff is too big to show here.

maintainers/scripts/update-python-libraries+3−3

This diff is too big to show here.

maintainers/scripts/update.nix+45−17

This diff is too big to show here.

maintainers/scripts/vanity.sh+1−1

This diff is too big to show here.

nixos/doc/manual/.gitignorenew file+2

This diff is too big to show here.

nixos/doc/manual/Makefilenew file+29

This diff is too big to show here.

nixos/doc/manual/administration/boot-problems.xml+83−58

This diff is too big to show here.

nixos/doc/manual/administration/cleaning-store.xml+40−39

This diff is too big to show here.

nixos/doc/manual/administration/container-networking.xml+39−38

This diff is too big to show here.

nixos/doc/manual/administration/containers.xml+28−28

This diff is too big to show here.

nixos/doc/manual/administration/control-groups.xml+38−46

This diff is too big to show here.

nixos/doc/manual/administration/declarative-containers.xml+44−44

This diff is too big to show here.

nixos/doc/manual/administration/imperative-containers.xml+66−83

This diff is too big to show here.

nixos/doc/manual/administration/logging.xml+21−30

This diff is too big to show here.

nixos/doc/manual/administration/maintenance-mode.xml+7−9

This diff is too big to show here.

nixos/doc/manual/administration/network-problems.xml+14−20

This diff is too big to show here.

nixos/doc/manual/administration/rebooting.xml+20−29

This diff is too big to show here.

nixos/doc/manual/administration/rollback.xml+23−30

This diff is too big to show here.

nixos/doc/manual/administration/running.xml+15−18

This diff is too big to show here.

nixos/doc/manual/administration/service-mgmt.xml+31−42

This diff is too big to show here.

nixos/doc/manual/administration/store-corruption.xml+23−24

This diff is too big to show here.

nixos/doc/manual/administration/troubleshooting.xml+10−12

This diff is too big to show here.

nixos/doc/manual/administration/user-sessions.xml+15−23

This diff is too big to show here.

nixos/doc/manual/configuration/abstractions.xml+57−67

This diff is too big to show here.

nixos/doc/manual/configuration/ad-hoc-network-config.xml+8−12

This diff is too big to show here.

nixos/doc/manual/configuration/ad-hoc-packages.xml+38−40

This diff is too big to show here.

nixos/doc/manual/configuration/adding-custom-packages.xml+28−39

This diff is too big to show here.

nixos/doc/manual/configuration/config-file.xml+131−138

This diff is too big to show here.

nixos/doc/manual/configuration/config-syntax.xml+18−20

This diff is too big to show here.

nixos/doc/manual/configuration/configuration.xml+20−26

This diff is too big to show here.

nixos/doc/manual/configuration/customizing-packages.xml+61−68

This diff is too big to show here.

nixos/doc/manual/configuration/declarative-packages.xml+26−26

This diff is too big to show here.

nixos/doc/manual/configuration/file-systems.xml+35−35

This diff is too big to show here.

nixos/doc/manual/configuration/firewall.xml+21−35

This diff is too big to show here.

nixos/doc/manual/configuration/ipv4-config.xml+30−31

This diff is too big to show here.

nixos/doc/manual/configuration/ipv6-config.xml+29−25

This diff is too big to show here.

nixos/doc/manual/configuration/linux-kernel.xml+99−51

This diff is too big to show here.

nixos/doc/manual/configuration/luks-file-systems.xml+15−21

This diff is too big to show here.

nixos/doc/manual/configuration/modularity.xml+81−93

This diff is too big to show here.

nixos/doc/manual/configuration/network-manager.xml+32−29

This diff is too big to show here.

nixos/doc/manual/configuration/networking.xml+12−15

This diff is too big to show here.

nixos/doc/manual/configuration/package-mgmt.xml+25−28

This diff is too big to show here.

nixos/doc/manual/configuration/profiles.xmlnew file+39

This diff is too big to show here.

nixos/doc/manual/configuration/profiles/all-hardware.xmlnew file+20

This diff is too big to show here.

nixos/doc/manual/configuration/profiles/base.xmlnew file+15

This diff is too big to show here.

nixos/doc/manual/configuration/profiles/clone-config.xmlnew file+14

This diff is too big to show here.

nixos/doc/manual/configuration/profiles/demo.xmlnew file+13

This diff is too big to show here.

nixos/doc/manual/configuration/profiles/docker-container.xmlnew file+15

This diff is too big to show here.

nixos/doc/manual/configuration/profiles/graphical.xmlnew file+21

This diff is too big to show here.

nixos/doc/manual/configuration/profiles/hardened.xmlnew file+22

This diff is too big to show here.

nixos/doc/manual/configuration/profiles/headless.xmlnew file+18

This diff is too big to show here.

nixos/doc/manual/configuration/profiles/installation-device.xmlnew file+35

This diff is too big to show here.

nixos/doc/manual/configuration/profiles/minimal.xmlnew file+17

This diff is too big to show here.

nixos/doc/manual/configuration/profiles/qemu-guest.xmlnew file+16

This diff is too big to show here.

nixos/doc/manual/configuration/ssh.xml+14−19

This diff is too big to show here.

nixos/doc/manual/configuration/summary.xml+202−167

This diff is too big to show here.

nixos/doc/manual/configuration/user-mgmt.xml+64−76

This diff is too big to show here.

nixos/doc/manual/configuration/wireless.xml+24−32

This diff is too big to show here.

nixos/doc/manual/configuration/x-windows.xml+101−105

This diff is too big to show here.

nixos/doc/manual/configuration/xfce.xml+57−79

This diff is too big to show here.

nixos/doc/manual/default.nix+40−23

This diff is too big to show here.

nixos/doc/manual/development/assertions.xml+29−35

This diff is too big to show here.

nixos/doc/manual/development/building-nixos.xml+15−20

This diff is too big to show here.

nixos/doc/manual/development/building-parts.xml+87−79

This diff is too big to show here.

nixos/doc/manual/development/debugging-nixos-tests.xmlnew file+37

This diff is too big to show here.

nixos/doc/manual/development/development.xml+14−17

This diff is too big to show here.

nixos/doc/manual/development/importing-modules.xmlnew file+56

This diff is too big to show here.

nixos/doc/manual/development/meta-attributes.xml+28−27

This diff is too big to show here.

nixos/doc/manual/development/nixos-tests.xml+13−13

This diff is too big to show here.

nixos/doc/manual/development/option-declarations.xml+146−113

This diff is too big to show here.

nixos/doc/manual/development/option-def.xml+49−62

This diff is too big to show here.

nixos/doc/manual/development/option-types.xml+681−421

This diff is too big to show here.

nixos/doc/manual/development/releases.xml+215−209

This diff is too big to show here.

nixos/doc/manual/development/replace-modules.xml+26−22

This diff is too big to show here.

nixos/doc/manual/development/running-nixos-tests-interactively.xml+22−21

This diff is too big to show here.

nixos/doc/manual/development/running-nixos-tests.xml+13−18

This diff is too big to show here.

nixos/doc/manual/development/sources.xml+50−67

This diff is too big to show here.

nixos/doc/manual/development/testing-installer.xml+11−16

This diff is too big to show here.

nixos/doc/manual/development/writing-documentation.xml+140−138

This diff is too big to show here.

nixos/doc/manual/development/writing-modules.xml+95−94

This diff is too big to show here.

nixos/doc/manual/development/writing-nixos-tests.xml+366−253

This diff is too big to show here.

nixos/doc/manual/installation/changing-config.xml+58−75

This diff is too big to show here.

nixos/doc/manual/installation/installation.xml+11−15

This diff is too big to show here.

nixos/doc/manual/installation/installing-behind-a-proxy.xmlnew file+48

This diff is too big to show here.

nixos/doc/manual/installation/installing-from-other-distro.xmlnew file+356

This diff is too big to show here.

nixos/doc/manual/installation/installing-pxe.xml+33−31

This diff is too big to show here.

nixos/doc/manual/installation/installing-usb.xml+22−41

This diff is too big to show here.

nixos/doc/manual/installation/installing-virtualbox-guest.xml+61−43

This diff is too big to show here.

nixos/doc/manual/installation/installing.xml+490−337

This diff is too big to show here.

nixos/doc/manual/installation/obtaining.xml+45−39

This diff is too big to show here.

nixos/doc/manual/installation/upgrading.xml+102−109

This diff is too big to show here.

nixos/doc/manual/man-configuration.xml+26−33

This diff is too big to show here.

nixos/doc/manual/man-nixos-build-vms.xml+86−76

This diff is too big to show here.

nixos/doc/manual/man-nixos-enter.xmlnew file+138

This diff is too big to show here.

nixos/doc/manual/man-nixos-generate-config.xml+152−146

This diff is too big to show here.

nixos/doc/manual/man-nixos-install.xml+230−186

This diff is too big to show here.

nixos/doc/manual/man-nixos-option.xml+101−98

This diff is too big to show here.

nixos/doc/manual/man-nixos-rebuild.xml+423−354

This diff is too big to show here.

nixos/doc/manual/man-nixos-version.xml+97−82

This diff is too big to show here.

nixos/doc/manual/man-pages.xml+16−28

This diff is too big to show here.

nixos/doc/manual/manual.xml+41−40

This diff is too big to show here.

nixos/doc/manual/options-to-docbook.xsl+11−8

This diff is too big to show here.

nixos/doc/manual/postprocess-option-descriptions.xslnew file+115

This diff is too big to show here.

nixos/doc/manual/release-notes/release-notes.xml+16−16

This diff is too big to show here.

nixos/doc/manual/release-notes/rl-1310.xml+4−4

This diff is too big to show here.

nixos/doc/manual/release-notes/rl-1404.xml+150−131

This diff is too big to show here.

nixos/doc/manual/release-notes/rl-1412.xml+454−164

This diff is too big to show here.

nixos/doc/manual/release-notes/rl-1509.xml+640−381

This diff is too big to show here.

nixos/doc/manual/release-notes/rl-1603.xml+529−311

This diff is too big to show here.

nixos/doc/manual/release-notes/rl-1609.xml+205−167

This diff is too big to show here.

nixos/doc/manual/release-notes/rl-1703.xml+685−382

This diff is too big to show here.

nixos/doc/manual/release-notes/rl-1709.xml+732−444

This diff is too big to show here.

nixos/doc/manual/release-notes/rl-1803.xml+777−306

This diff is too big to show here.

nixos/doc/manual/release-notes/rl-1809.xmlnew file+932

This diff is too big to show here.

nixos/doc/manual/release-notes/rl-1903.xmlnew file+265

This diff is too big to show here.

nixos/doc/manual/shell.nixnew file+8

This diff is too big to show here.

nixos/doc/manual/style.cssdeleted−267

This diff is too big to show here.

nixos/doc/varlistentry-fixer.rbnew file+124

This diff is too big to show here.

nixos/doc/xmlformat.confnew file+73

This diff is too big to show here.

nixos/lib/build-vms.nix+14−6

This diff is too big to show here.

nixos/lib/eval-config.nix+9−4

This diff is too big to show here.

nixos/lib/make-channel.nix+4

This diff is too big to show here.

nixos/lib/make-disk-image.nix+26−25

This diff is too big to show here.

nixos/lib/make-ext4-fs.nix+20−10

This diff is too big to show here.

nixos/lib/make-iso9660-image.nix+4−5

This diff is too big to show here.

nixos/lib/make-iso9660-image.sh+3−4

This diff is too big to show here.

nixos/lib/make-squashfs.nix+5−37

This diff is too big to show here.

nixos/lib/make-system-tarball.nix+12−4

This diff is too big to show here.

nixos/lib/make-system-tarball.sh+2−3

This diff is too big to show here.

nixos/lib/qemu-flags.nix+10−6

This diff is too big to show here.

nixos/lib/test-driver/Machine.pm+19−6

This diff is too big to show here.

nixos/lib/testing.nix+22−9

This diff is too big to show here.

pkgs/development/libraries/javascript/jquery-ui/default.nix → nixos/lib/testing/jquery-ui.nixrenamed

The content is the same.

pkgs/development/libraries/javascript/jquery/default.nix → nixos/lib/testing/jquery.nixrenamed

The content is the same.

nixos/maintainers/option-usages.nix+5−5

This diff is too big to show here.

nixos/maintainers/scripts/azure/create-azure.sh+1−1

This diff is too big to show here.

nixos/maintainers/scripts/ec2/amazon-image.nix+5

This diff is too big to show here.

nixos/maintainers/scripts/ec2/create-amis.sh+3−2

This diff is too big to show here.

nixos/maintainers/scripts/gce/create-gce.sh+2−2

This diff is too big to show here.

nixos/modules/config/fonts/fontconfig-ultimate.nix+1−3

This diff is too big to show here.

nixos/modules/config/gnu.nix+2−2

This diff is too big to show here.

nixos/modules/config/gtk/gtk-icon-cache.nixnew file+86

This diff is too big to show here.

nixos/modules/config/i18n.nix+1−1

This diff is too big to show here.

nixos/modules/config/iproute2.nixnew file+32

This diff is too big to show here.

nixos/modules/config/krb5/default.nix+1−1

This diff is too big to show here.

nixos/modules/config/ldap.nix+2−2

This diff is too big to show here.

nixos/modules/config/networking.nix+47−32

This diff is too big to show here.

nixos/modules/config/no-x-libs.nix+12−12

This diff is too big to show here.

nixos/modules/config/nsswitch.nix+10−10

This diff is too big to show here.

nixos/modules/config/power-management.nix+1−1

This diff is too big to show here.

nixos/modules/config/pulseaudio.nix+34−8

This diff is too big to show here.

nixos/modules/config/shells-environment.nix+29−13

This diff is too big to show here.

nixos/modules/config/sysctl.nix+1−1

This diff is too big to show here.

nixos/modules/config/system-path.nix+11−26

This diff is too big to show here.

nixos/modules/config/unix-odbc-drivers.nix+1−1

This diff is too big to show here.

nixos/modules/config/users-groups.nix+34−33

This diff is too big to show here.

nixos/modules/config/vpnc.nix+1−1

This diff is too big to show here.

nixos/modules/config/xdg/autostart.nixnew file+22

This diff is too big to show here.

nixos/modules/config/xdg/icons.nixnew file+27

This diff is too big to show here.

nixos/modules/config/xdg/menus.nixnew file+25

This diff is too big to show here.

nixos/modules/config/xdg/mime.nixnew file+36

This diff is too big to show here.

nixos/modules/config/zram.nix+5−5

This diff is too big to show here.

nixos/modules/hardware/all-firmware.nix+2−1

This diff is too big to show here.

nixos/modules/hardware/brightnessctl.nixnew file+30

This diff is too big to show here.

nixos/modules/hardware/ckb-next.nixnew file+49

This diff is too big to show here.

nixos/modules/hardware/ckb.nixdeleted−40

This diff is too big to show here.

nixos/modules/hardware/digitalbitbox.nixnew file+30

This diff is too big to show here.

nixos/modules/hardware/network/smc-2632w/default.nix+1−1

This diff is too big to show here.

nixos/modules/hardware/network/zydas-zd1211.nix+1−1

This diff is too big to show here.

nixos/modules/hardware/nitrokey.nix+1−1

This diff is too big to show here.

nixos/modules/hardware/onlykey.nixnew file+33

This diff is too big to show here.

nixos/modules/hardware/onlykey.udevnew file+4

This diff is too big to show here.

nixos/modules/hardware/opengl.nix+98−89

This diff is too big to show here.

nixos/modules/hardware/steam-hardware.nixnew file+25

This diff is too big to show here.

nixos/modules/hardware/video/amdgpu-pro.nix+17−3

This diff is too big to show here.

nixos/modules/hardware/video/ati.nix+2−2

This diff is too big to show here.

nixos/modules/hardware/video/capture/mwprocapture.nix+1−1

This diff is too big to show here.

nixos/modules/hardware/video/nvidia.nix+129−22

This diff is too big to show here.

nixos/modules/hardware/video/uvcvideo/default.nixnew file+64

This diff is too big to show here.

nixos/modules/hardware/video/uvcvideo/uvcdynctrl-udev-rules.nixnew file+44

This diff is too big to show here.

nixos/modules/i18n/input-method/default.nix+1−1

This diff is too big to show here.

nixos/modules/i18n/input-method/default.xml+210−109

This diff is too big to show here.

nixos/modules/installer/cd-dvd/channel.nix+2

This diff is too big to show here.

nixos/modules/installer/cd-dvd/installation-cd-base.nix+2−3

This diff is too big to show here.

nixos/modules/installer/cd-dvd/installation-cd-graphical-base.nixnew file+49

This diff is too big to show here.

nixos/modules/installer/cd-dvd/installation-cd-graphical-gnome.nix+3−60

This diff is too big to show here.

nixos/modules/installer/cd-dvd/installation-cd-graphical-kde-new-kernel.nix+1−1

This diff is too big to show here.

nixos/modules/installer/cd-dvd/installation-cd-graphical-kde.nix+10−39

This diff is too big to show here.

nixos/modules/installer/cd-dvd/installation-cd-minimal-new-kernel.nix+1−1

This diff is too big to show here.

nixos/modules/installer/cd-dvd/installation-cd-minimal.nix+3−1

This diff is too big to show here.

nixos/modules/installer/cd-dvd/iso-image.nix+270−54

This diff is too big to show here.

nixos/modules/installer/cd-dvd/sd-image-aarch64.nix+2−7

This diff is too big to show here.

nixos/modules/installer/cd-dvd/sd-image-armv7l-multiplatform.nix+2−7

This diff is too big to show here.

nixos/modules/installer/cd-dvd/sd-image-raspberrypi.nix+21−13

This diff is too big to show here.

nixos/modules/installer/cd-dvd/sd-image.nix+54−15

This diff is too big to show here.

nixos/modules/installer/cd-dvd/system-tarball-fuloong2f.nix+1−1

This diff is too big to show here.

nixos/modules/installer/cd-dvd/system-tarball-sheevaplug.nix+1−1

This diff is too big to show here.

nixos/modules/installer/netboot/netboot-base.nix+1−4

This diff is too big to show here.

nixos/modules/installer/netboot/netboot-minimal.nix+1−1

This diff is too big to show here.

nixos/modules/installer/netboot/netboot.nix+3−4

This diff is too big to show here.

nixos/modules/installer/scan/detected.nix+1−1

This diff is too big to show here.

nixos/modules/installer/scan/not-detected.nix+3−6

This diff is too big to show here.

nixos/modules/installer/tools/nix-fallback-paths.nix+4−4

This diff is too big to show here.

nixos/modules/installer/tools/nixos-build-vms/build-vms.nix+5−1

This diff is too big to show here.

nixos/modules/installer/tools/nixos-enter.shnew file+61

This diff is too big to show here.

nixos/modules/installer/tools/nixos-generate-config.pl+15−6

This diff is too big to show here.

nixos/modules/installer/tools/nixos-install.sh+69−131

This diff is too big to show here.

nixos/modules/installer/tools/nixos-option.sh+12−4

This diff is too big to show here.

nixos/modules/installer/tools/nixos-prepare-root.shdeleted−104

This diff is too big to show here.

nixos/modules/installer/tools/nixos-rebuild.sh+1−1

This diff is too big to show here.

nixos/modules/installer/tools/tools.nix+11−23

This diff is too big to show here.

nixos/modules/installer/virtualbox-demo.nix+43−2

This diff is too big to show here.

nixos/modules/misc/assertions.nix+1−1

This diff is too big to show here.

nixos/modules/misc/documentation.nixnew file+199

This diff is too big to show here.

nixos/modules/misc/extra-arguments.nix+1−1

This diff is too big to show here.

nixos/modules/misc/ids.nix+74−18

This diff is too big to show here.

nixos/modules/misc/label.nix+1−1

This diff is too big to show here.

nixos/modules/misc/lib.nix+1−1

This diff is too big to show here.

nixos/modules/misc/locate.nix+17−4

This diff is too big to show here.

nixos/modules/misc/meta.nix+1−1

This diff is too big to show here.

nixos/modules/misc/nixpkgs.nix+112−20

This diff is too big to show here.

nixos/modules/misc/passthru.nix+1−1

This diff is too big to show here.

nixos/modules/misc/version.nix+6−11

This diff is too big to show here.

nixos/modules/module-list.nix+98−24

This diff is too big to show here.

nixos/modules/profiles/all-hardware.nix+2−2

This diff is too big to show here.

nixos/modules/profiles/base.nix+7−4

This diff is too big to show here.

nixos/modules/profiles/clone-config.nix+9−1

This diff is too big to show here.

nixos/modules/profiles/demo.nix+8−2

This diff is too big to show here.

nixos/modules/profiles/docker-container.nix+1−3

This diff is too big to show here.

nixos/modules/profiles/graphical.nix+6−3

This diff is too big to show here.

nixos/modules/profiles/hardened.nix+7−13

This diff is too big to show here.

nixos/modules/profiles/headless.nix+1−1

This diff is too big to show here.

nixos/modules/profiles/installation-device.nix+14−5

This diff is too big to show here.

nixos/modules/profiles/minimal.nix+2−4

This diff is too big to show here.

nixos/modules/profiles/qemu-guest.nix+1−1

This diff is too big to show here.

nixos/modules/programs/adb.nix+2−2

This diff is too big to show here.

nixos/modules/programs/atop.nix+1−1

This diff is too big to show here.

nixos/modules/programs/bash/bash.nix+20−12

This diff is too big to show here.

nixos/modules/programs/bcc.nix+1−1

This diff is too big to show here.

nixos/modules/programs/chromium.nix+5

This diff is too big to show here.

nixos/modules/programs/dconf.nix+3−1

This diff is too big to show here.

nixos/modules/programs/digitalbitbox/default.nixnew file+39

This diff is too big to show here.

nixos/modules/programs/digitalbitbox/doc.xmlnew file+74

This diff is too big to show here.

nixos/modules/programs/dmrconfig.nixnew file+38

This diff is too big to show here.

nixos/modules/programs/environment.nix+1−4

This diff is too big to show here.

nixos/modules/programs/firejail.nixnew file+48

This diff is too big to show here.

nixos/modules/programs/fish.nix+18−14

This diff is too big to show here.

nixos/modules/programs/gphoto2.nix+2−2

This diff is too big to show here.

nixos/modules/programs/iftop.nixnew file+18

This diff is too big to show here.

nixos/modules/programs/info.nixdeleted−30

This diff is too big to show here.

nixos/modules/programs/less.nix+15−2

This diff is too big to show here.

nixos/modules/programs/light.nix+3−2

This diff is too big to show here.

nixos/modules/programs/man.nixdeleted−31

This diff is too big to show here.

nixos/modules/programs/mosh.nix+18

This diff is too big to show here.

nixos/modules/programs/npm.nix+3−1

This diff is too big to show here.

nixos/modules/programs/nylas-mail.nix−1

This diff is too big to show here.

nixos/modules/programs/plotinus.xml+22−17

This diff is too big to show here.

nixos/modules/programs/rootston.nixdeleted−103

This diff is too big to show here.

nixos/modules/programs/screen.nix+3−1

This diff is too big to show here.

nixos/modules/programs/sedutil.nixnew file+18

This diff is too big to show here.

nixos/modules/programs/shell.nix+19−31

This diff is too big to show here.

nixos/modules/programs/singularity.nixnew file+20

This diff is too big to show here.

nixos/modules/programs/ssh.nix+26−5

This diff is too big to show here.

nixos/modules/programs/sway-beta.nixnew file+79

This diff is too big to show here.

nixos/modules/programs/sway.nix+1−1

This diff is too big to show here.

nixos/modules/programs/systemtap.nix+1−1

This diff is too big to show here.

nixos/modules/programs/thefuck.nix+3−3

This diff is too big to show here.

nixos/modules/programs/tmux.nix+1−1

This diff is too big to show here.

nixos/modules/programs/udevil.nixnew file+14

This diff is too big to show here.

nixos/modules/programs/wavemon.nixnew file+28

This diff is too big to show here.

nixos/modules/programs/wireshark.nix+1−1

This diff is too big to show here.

nixos/modules/programs/xonsh.nix−2

This diff is too big to show here.

nixos/modules/programs/xss-lock.nixnew file+26

This diff is too big to show here.

nixos/modules/programs/yabar.nix+15−2

This diff is too big to show here.

nixos/modules/programs/zsh/oh-my-zsh.nix+47−5

This diff is too big to show here.

nixos/modules/programs/zsh/oh-my-zsh.xmlnew file+155

This diff is too big to show here.

nixos/modules/programs/zsh/zsh-autosuggestions.nixnew file+60

This diff is too big to show here.

nixos/modules/programs/zsh/zsh.nix+27−19

This diff is too big to show here.

nixos/modules/rename.nix+72−14

This diff is too big to show here.

nixos/modules/security/acme.nix+85−43

This diff is too big to show here.

nixos/modules/security/acme.xml+63−57

This diff is too big to show here.

nixos/modules/security/apparmor-suid.nix+1−1

This diff is too big to show here.

nixos/modules/security/audit.nix+3−3

This diff is too big to show here.

nixos/modules/security/dhparams.nix+149−81

This diff is too big to show here.

nixos/modules/security/duosec.nix+2−2

This diff is too big to show here.

nixos/modules/security/hidepid.nix+1−1

This diff is too big to show here.

nixos/modules/security/hidepid.xml+22−27

This diff is too big to show here.

nixos/modules/security/lock-kernel-modules.nix+4

This diff is too big to show here.

nixos/modules/security/misc.nixnew file+39

This diff is too big to show here.

nixos/modules/security/oath.nix+1−1

This diff is too big to show here.

nixos/modules/security/pam.nix+23−5

This diff is too big to show here.

nixos/modules/security/pam_mount.nix+1−1

This diff is too big to show here.

nixos/modules/security/pam_usb.nix−2

This diff is too big to show here.

nixos/modules/security/polkit.nix+6−6

This diff is too big to show here.

nixos/modules/security/rngd.nix+1−3

This diff is too big to show here.

nixos/modules/security/rtkit.nix+1−1

This diff is too big to show here.

nixos/modules/security/sudo.nix+7−4

This diff is too big to show here.

nixos/modules/security/wrappers/default.nix−29

This diff is too big to show here.

nixos/modules/security/wrappers/wrapper.c+1−1

This diff is too big to show here.

nixos/modules/services/admin/oxidized.nixnew file+116

This diff is too big to show here.

nixos/modules/services/admin/salt/master.nix+3

This diff is too big to show here.

nixos/modules/services/admin/salt/minion.nix+16−5

This diff is too big to show here.

nixos/modules/services/amqp/activemq/default.nix+2−2

This diff is too big to show here.

nixos/modules/services/amqp/rabbitmq.nix+92−21

This diff is too big to show here.

nixos/modules/services/audio/alsa.nix+8−7

This diff is too big to show here.

nixos/modules/services/audio/liquidsoap.nix+2−2

This diff is too big to show here.

nixos/modules/services/audio/mopidy.nix+2−2

This diff is too big to show here.

nixos/modules/services/audio/mpd.nix+10−7

This diff is too big to show here.

nixos/modules/services/audio/slimserver.nix+2−1

This diff is too big to show here.

nixos/modules/services/audio/squeezelite.nix+1−1

This diff is too big to show here.

nixos/modules/services/backup/almir.nixdeleted−173

This diff is too big to show here.

nixos/modules/services/backup/bacula.nix+22−21

This diff is too big to show here.

nixos/modules/services/backup/borgbackup.nixnew file+616

This diff is too big to show here.

nixos/modules/services/backup/crashplan-small-business.nix−1

This diff is too big to show here.

nixos/modules/services/backup/crashplan.nix−1

This diff is too big to show here.

nixos/modules/services/backup/duplicati.nixnew file+57

This diff is too big to show here.

nixos/modules/services/backup/mysql-backup.nix+1−1

This diff is too big to show here.

nixos/modules/services/backup/postgresql-backup.nix+47−17

This diff is too big to show here.

nixos/modules/services/backup/restic-rest-server.nixnew file+107

This diff is too big to show here.

nixos/modules/services/backup/restic.nixnew file+160

This diff is too big to show here.

nixos/modules/services/backup/tarsnap.nix+60−7

This diff is too big to show here.

nixos/modules/services/backup/znapzend.nix+1−8

This diff is too big to show here.

nixos/modules/services/cluster/fleet.nixdeleted−150

This diff is too big to show here.

nixos/modules/services/cluster/hadoop/conf.nixnew file+31

This diff is too big to show here.

nixos/modules/services/cluster/hadoop/default.nixnew file+60

This diff is too big to show here.

nixos/modules/services/cluster/hadoop/hdfs.nixnew file+73

This diff is too big to show here.

nixos/modules/services/cluster/hadoop/yarn.nixnew file+74

This diff is too big to show here.

nixos/modules/services/cluster/kubernetes/dashboard.nix+200−39

This diff is too big to show here.

nixos/modules/services/cluster/kubernetes/default.nix+100−47

This diff is too big to show here.

nixos/modules/services/cluster/kubernetes/dns.nix+196−187

This diff is too big to show here.

nixos/modules/services/cluster/panamax.nixdeleted−156

This diff is too big to show here.

nixos/modules/services/computing/boinc/client.nix+45−1

This diff is too big to show here.

nixos/modules/services/computing/slurm/slurm.nix+188−19

This diff is too big to show here.

nixos/modules/services/continuous-integration/buildbot/master.nix+51−20

This diff is too big to show here.

nixos/modules/services/continuous-integration/buildbot/worker.nix+68−13

This diff is too big to show here.

nixos/modules/services/continuous-integration/buildkite-agent.nix+3−3

This diff is too big to show here.

nixos/modules/services/continuous-integration/gitlab-runner.nix+2−2

This diff is too big to show here.

nixos/modules/services/continuous-integration/gocd-agent/default.nix+2−2

This diff is too big to show here.

nixos/modules/services/continuous-integration/gocd-server/default.nix+4−4

This diff is too big to show here.

nixos/modules/services/continuous-integration/hydra/default.nix+4−4

This diff is too big to show here.

nixos/modules/services/continuous-integration/jenkins/default.nix+10−3

This diff is too big to show here.

nixos/modules/services/continuous-integration/jenkins/slave.nix+3−3

This diff is too big to show here.

nixos/modules/services/databases/4store-endpoint.nix+2−2

This diff is too big to show here.

nixos/modules/services/databases/4store.nix+2−2

This diff is too big to show here.

nixos/modules/services/databases/aerospike.nixnew file+155

This diff is too big to show here.

nixos/modules/services/databases/cassandra.nix+243−400

This diff is too big to show here.

nixos/modules/services/databases/clickhouse.nix+2−2

This diff is too big to show here.

nixos/modules/services/databases/couchdb.nix+2−2

This diff is too big to show here.

nixos/modules/services/databases/firebird.nix+2−2

This diff is too big to show here.

nixos/modules/services/databases/foundationdb.nixnew file+416

This diff is too big to show here.

nixos/modules/services/databases/foundationdb.xmlnew file+443

This diff is too big to show here.

nixos/modules/services/databases/hbase.nix+2−2

This diff is too big to show here.

nixos/modules/services/databases/influxdb.nix+2−2

This diff is too big to show here.

nixos/modules/services/databases/memcached.nix+1−1

This diff is too big to show here.

nixos/modules/services/databases/monetdb.nixnew file+100

This diff is too big to show here.

nixos/modules/services/databases/mongodb.nix+1−1

This diff is too big to show here.

nixos/modules/services/databases/mysql.nix+19−17

This diff is too big to show here.

nixos/modules/services/databases/neo4j.nix+590−87

This diff is too big to show here.

nixos/modules/services/databases/openldap.nix+48−8

This diff is too big to show here.

nixos/modules/services/databases/opentsdb.nix+2−2

This diff is too big to show here.

nixos/modules/services/databases/pgmanage.nix+28−44

This diff is too big to show here.

nixos/modules/services/databases/postgresql.nix+13−15

This diff is too big to show here.

nixos/modules/services/databases/postgresql.xml+50−50

This diff is too big to show here.

nixos/modules/services/databases/redis.nix+1−1

This diff is too big to show here.

nixos/modules/services/databases/rethinkdb.nix+2−2

This diff is too big to show here.

nixos/modules/services/databases/riak-cs.nix+1−1

This diff is too big to show here.

nixos/modules/services/databases/riak.nix+2−2

This diff is too big to show here.

nixos/modules/services/databases/stanchion.nix+2−2

This diff is too big to show here.

nixos/modules/services/databases/virtuoso.nix+1−1

This diff is too big to show here.

nixos/modules/services/desktops/accountsservice.nix+8−2

This diff is too big to show here.

nixos/modules/services/desktops/bamf.nixnew file+23

This diff is too big to show here.

nixos/modules/services/desktops/flatpak.nixnew file+52

This diff is too big to show here.

nixos/modules/services/desktops/flatpak.xmlnew file+56

This diff is too big to show here.

nixos/modules/services/desktops/geoclue2.nix+32−7

This diff is too big to show here.

nixos/modules/services/desktops/gnome3/at-spi2-core.nix+3−3

This diff is too big to show here.

nixos/modules/services/desktops/gnome3/evolution-data-server.nix+3−3

This diff is too big to show here.

nixos/modules/services/desktops/gnome3/gnome-keyring.nix+2−2

This diff is too big to show here.

nixos/modules/services/desktops/gnome3/gnome-online-accounts.nix+2−2

This diff is too big to show here.

nixos/modules/services/desktops/gnome3/gnome-terminal-server.nix+3−3

This diff is too big to show here.

nixos/modules/services/desktops/gnome3/rygel.nixnew file+30

This diff is too big to show here.

nixos/modules/services/desktops/gsignond.nixnew file+43

This diff is too big to show here.

nixos/modules/services/desktops/pipewire.nix+18−4

This diff is too big to show here.

nixos/modules/services/desktops/profile-sync-daemon.nix+34−102

This diff is too big to show here.

nixos/modules/services/desktops/telepathy.nix+2−2

This diff is too big to show here.

nixos/modules/services/desktops/zeitgeist.nixnew file+26

This diff is too big to show here.

nixos/modules/services/development/bloop.nixnew file+37

This diff is too big to show here.

nixos/modules/services/development/hoogle.nix+7−1

This diff is too big to show here.

nixos/modules/services/development/jupyter/default.nixnew file+185

This diff is too big to show here.

nixos/modules/services/development/jupyter/kernel-options.nixnew file+60

This diff is too big to show here.

nixos/modules/services/editors/emacs.nix+21−2

This diff is too big to show here.

nixos/modules/services/editors/emacs.xml+409−442

This diff is too big to show here.

nixos/modules/services/editors/infinoted.nix+6−6

This diff is too big to show here.

nixos/modules/services/games/minecraft-server.nix+1−1

This diff is too big to show here.

nixos/modules/services/games/minetest-server.nix+4−1

This diff is too big to show here.

nixos/modules/services/games/terraria.nix+15−5

This diff is too big to show here.

nixos/modules/services/hardware/actkbd.nix+1−1

This diff is too big to show here.

nixos/modules/services/hardware/bluetooth.nix+11−1

This diff is too big to show here.

nixos/modules/services/hardware/fwupd.nix+9−6

This diff is too big to show here.

nixos/modules/services/hardware/lcd.nixnew file+172

This diff is too big to show here.

nixos/modules/services/hardware/lirc.nixnew file+89

This diff is too big to show here.

nixos/modules/services/hardware/nvidia-optimus.nix+1−1

This diff is too big to show here.

nixos/modules/services/hardware/pcscd.nix+2−2

This diff is too big to show here.

nixos/modules/services/hardware/ratbagd.nixnew file+32

This diff is too big to show here.

nixos/modules/services/hardware/sane.nix+2−2

This diff is too big to show here.

nixos/modules/services/hardware/sane_extra_backends/brscan4.nix+1−1

This diff is too big to show here.

nixos/modules/services/hardware/tcsd.nix+2−2

This diff is too big to show here.

nixos/modules/services/hardware/thermald.nix+29−7

This diff is too big to show here.

nixos/modules/services/hardware/thinkfan.nix+46−9

This diff is too big to show here.

nixos/modules/services/hardware/trezord.nix+9−3

This diff is too big to show here.

nixos/modules/services/hardware/triggerhappy.nixnew file+114

This diff is too big to show here.

nixos/modules/services/hardware/udev.nix+1−3

This diff is too big to show here.

nixos/modules/services/hardware/udisks2.nix+2−9

This diff is too big to show here.

nixos/modules/services/hardware/undervolt.nixnew file+134

This diff is too big to show here.

nixos/modules/services/hardware/upower.nix+26

This diff is too big to show here.

nixos/modules/services/hardware/usbmuxd.nix+3−3

This diff is too big to show here.

nixos/modules/services/logging/graylog.nix+2−2

This diff is too big to show here.

nixos/modules/services/logging/journaldriver.nixnew file+112

This diff is too big to show here.

nixos/modules/services/logging/journalwatch.nix+3−3

This diff is too big to show here.

nixos/modules/services/logging/logcheck.nix+1−1

This diff is too big to show here.

nixos/modules/services/logging/logstash.nix+6−37

This diff is too big to show here.

nixos/modules/services/logging/syslog-ng.nix+2

This diff is too big to show here.

nixos/modules/services/mail/clamsmtp.nix+2

This diff is too big to show here.

nixos/modules/services/mail/dkimproxy-out.nix+2

This diff is too big to show here.

nixos/modules/services/mail/dovecot.nix+15−8

This diff is too big to show here.

nixos/modules/services/mail/dspam.nix+2−2

This diff is too big to show here.

nixos/modules/services/mail/exim.nix+17−6

This diff is too big to show here.

nixos/modules/services/mail/mail.nix+1−1

This diff is too big to show here.

nixos/modules/services/mail/mailhog.nix+1−1

This diff is too big to show here.

nixos/modules/services/mail/mlmmj.nix+2−2

This diff is too big to show here.

nixos/modules/services/mail/nullmailer.nix+2−2

This diff is too big to show here.

nixos/modules/services/mail/opendkim.nix+2−2

This diff is too big to show here.

nixos/modules/services/mail/opensmtpd.nix+12−5

This diff is too big to show here.

nixos/modules/services/mail/postfix.nix+19−3

This diff is too big to show here.

nixos/modules/services/mail/postgrey.nix+2−2

This diff is too big to show here.

nixos/modules/services/mail/postsrsd.nix+2−2

This diff is too big to show here.

nixos/modules/services/mail/rmilter.nix+9−6

This diff is too big to show here.

nixos/modules/services/mail/rspamd.nix+161−94

This diff is too big to show here.

nixos/modules/services/mail/spamassassin.nix+2−2

This diff is too big to show here.

nixos/modules/services/misc/airsonic.nix+20−1

This diff is too big to show here.

nixos/modules/services/misc/apache-kafka.nix+1−1

This diff is too big to show here.

nixos/modules/services/misc/autorandr.nix+21−3

This diff is too big to show here.

nixos/modules/services/misc/bepasty.nix+2−2

This diff is too big to show here.

nixos/modules/services/misc/calibre-server.nix+2−2

This diff is too big to show here.

nixos/modules/services/misc/cfdyndns.nix+2−2

This diff is too big to show here.

nixos/modules/services/misc/cgminer.nix+1−1

This diff is too big to show here.

nixos/modules/services/misc/clipmenu.nixnew file+31

This diff is too big to show here.

nixos/modules/services/misc/couchpotato.nix+2−2

This diff is too big to show here.

nixos/modules/services/misc/defaultUnicornConfig.rb+52−188

This diff is too big to show here.

nixos/modules/services/misc/dictd.nix+2−2

This diff is too big to show here.

nixos/modules/services/misc/disnix.nix+11−15

This diff is too big to show here.

nixos/modules/services/misc/docker-registry.nix+92−10

This diff is too big to show here.

nixos/modules/services/misc/dysnomia.nix+25−28

This diff is too big to show here.

nixos/modules/services/misc/emby.nix+16−10

This diff is too big to show here.

nixos/modules/services/misc/errbot.nix+2−2

This diff is too big to show here.

nixos/modules/services/misc/etcd.nix+1−1

This diff is too big to show here.

nixos/modules/services/misc/exhibitor.nix+4−2

This diff is too big to show here.

nixos/modules/services/misc/felix.nix+2−2

This diff is too big to show here.

nixos/modules/services/misc/folding-at-home.nix+2−2

This diff is too big to show here.

nixos/modules/services/misc/gammu-smsd.nix+1−1

This diff is too big to show here.

nixos/modules/services/misc/geoip-updater.nix+2−2

This diff is too big to show here.

nixos/modules/services/misc/gitea.nix+140−13

This diff is too big to show here.

nixos/modules/services/misc/gitit.nix+7−7

This diff is too big to show here.

nixos/modules/services/misc/gitlab.nix+120−141

This diff is too big to show here.

nixos/modules/services/misc/gitlab.xml+93−88

This diff is too big to show here.

nixos/modules/services/misc/gitolite.nix+2−2

This diff is too big to show here.

nixos/modules/services/misc/gitweb.nixnew file+59

This diff is too big to show here.

nixos/modules/services/misc/gogs.nix+5−2

This diff is too big to show here.

nixos/modules/services/misc/gollum.nix+2−2

This diff is too big to show here.

nixos/modules/services/misc/gpsd.nix+12−3

This diff is too big to show here.

nixos/modules/services/misc/home-assistant.nix+61−11

This diff is too big to show here.

nixos/modules/services/misc/ihaskell.nix+6−6

This diff is too big to show here.

nixos/modules/services/misc/jackett.nix+3−3

This diff is too big to show here.

nixos/modules/services/misc/leaps.nix+1−1

This diff is too big to show here.

nixos/modules/services/misc/lidarr.nixnew file+46

This diff is too big to show here.

nixos/modules/services/misc/logkeys.nix+8−1

This diff is too big to show here.

nixos/modules/services/misc/mathics.nix+5−5

This diff is too big to show here.

nixos/modules/services/misc/matrix-synapse.nix+11−11

This diff is too big to show here.

nixos/modules/services/misc/mediatomb.nix+2−3

This diff is too big to show here.

nixos/modules/services/misc/mesos-slave.nix+3−3

This diff is too big to show here.

nixos/modules/services/misc/nix-daemon.nix+42−21

This diff is too big to show here.

nixos/modules/services/misc/nix-gc.nix+1−1

This diff is too big to show here.

nixos/modules/services/misc/nix-optimise.nix+3−1

This diff is too big to show here.

nixos/modules/services/misc/nix-ssh-serve.nix+19−9

This diff is too big to show here.

nixos/modules/services/misc/nixos-manual.nix+29−100

This diff is too big to show here.

nixos/modules/services/misc/nzbget.nix+3−3

This diff is too big to show here.

nixos/modules/services/misc/octoprint.nix+2−2

This diff is too big to show here.

nixos/modules/services/misc/osrm.nix+1−1

This diff is too big to show here.

nixos/modules/services/misc/packagekit.nix−3

This diff is too big to show here.

nixos/modules/services/misc/parsoid.nix+3−1

This diff is too big to show here.

nixos/modules/services/misc/plex.nix+2−3

This diff is too big to show here.

nixos/modules/services/misc/plexpy.nix+1−1

This diff is too big to show here.

nixos/modules/services/misc/pykms.nix+2−2

This diff is too big to show here.

nixos/modules/services/misc/radarr.nix+3−3

This diff is too big to show here.

nixos/modules/services/misc/redmine.nix+241−121

This diff is too big to show here.

nixos/modules/services/misc/ripple-data-api.nix+1−1

This diff is too big to show here.

nixos/modules/services/misc/rippled.nix+1−1

This diff is too big to show here.

nixos/modules/services/misc/safeeyes.nixnew file+50

This diff is too big to show here.

nixos/modules/services/misc/serviio.nixnew file+92

This diff is too big to show here.

nixos/modules/services/misc/sickbeard.nixnew file+92

This diff is too big to show here.

nixos/modules/services/misc/siproxd.nix+1−1

This diff is too big to show here.

nixos/modules/services/misc/sonarr.nix+3−3

This diff is too big to show here.

nixos/modules/services/misc/ssm-agent.nix+1−1

This diff is too big to show here.

nixos/modules/services/misc/subsonic.nix+3−3

This diff is too big to show here.

nixos/modules/services/misc/synergy.nix+6−6

This diff is too big to show here.

nixos/modules/services/misc/sysprof.nixnew file+19

This diff is too big to show here.

nixos/modules/services/misc/taskserver/default.nix+1−11

This diff is too big to show here.

nixos/modules/services/misc/taskserver/doc.xml+104−113

This diff is too big to show here.

nixos/modules/services/misc/uhub.nix+2−2

This diff is too big to show here.

nixos/modules/services/misc/weechat.nixnew file+58

This diff is too big to show here.

nixos/modules/services/misc/weechat.xmlnew file+66

This diff is too big to show here.

nixos/modules/services/misc/xmr-stak.nix+40−20

This diff is too big to show here.

nixos/modules/services/misc/zookeeper.nix+1−1

This diff is too big to show here.

nixos/modules/services/monitoring/alerta.nixnew file+116

This diff is too big to show here.

nixos/modules/services/monitoring/apcupsd.nix+1−1

This diff is too big to show here.

nixos/modules/services/monitoring/bosun.nix+2−2

This diff is too big to show here.

nixos/modules/services/monitoring/collectd.nix+1−1

This diff is too big to show here.

nixos/modules/services/monitoring/datadog-agent.nixnew file+271

This diff is too big to show here.

nixos/modules/services/monitoring/dd-agent/dd-agent.nix+49−47

This diff is too big to show here.

nixos/modules/services/monitoring/fusion-inventory.nix+1−1

This diff is too big to show here.

nixos/modules/services/monitoring/grafana-reporter.nixnew file+66

This diff is too big to show here.

nixos/modules/services/monitoring/grafana.nix+127−10

This diff is too big to show here.

nixos/modules/services/monitoring/graphite.nix+15−23

This diff is too big to show here.

nixos/modules/services/monitoring/heapster.nix+1−1

This diff is too big to show here.

nixos/modules/services/monitoring/incron.nixnew file+98

This diff is too big to show here.

nixos/modules/services/monitoring/kapacitor.nixnew file+192

This diff is too big to show here.

nixos/modules/services/monitoring/monit.nix+20−27

This diff is too big to show here.

nixos/modules/services/monitoring/munin.nix+8−8

This diff is too big to show here.

nixos/modules/services/monitoring/nagios.nix+1−1

This diff is too big to show here.

nixos/modules/services/monitoring/netdata.nix+6−2

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/alertmanager.nix+18−5

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/blackbox-exporter.nixdeleted−68

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/collectd-exporter.nixdeleted−128

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/default.nix+36−8

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/exporters.nixnew file+178

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/exporters.xmlnew file+187

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/exporters/blackbox.nixnew file+31

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/exporters/collectd.nixnew file+78

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/exporters/dnsmasq.nixnew file+39

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/exporters/dovecot.nixnew file+50

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/exporters/fritzbox.nixnew file+39

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/exporters/json.nixnew file+36

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/exporters/minio.nixnew file+65

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/exporters/nginx.nixnew file+47

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/exporters/node.nixnew file+40

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/exporters/postfix.nixnew file+81

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/exporters/snmp.nixnew file+71

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/exporters/surfboard.nixnew file+32

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/exporters/tor.nixnew file+40

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/exporters/unifi.nixnew file+67

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/exporters/varnish.nixnew file+88

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/fritzbox-exporter.nixdeleted−76

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/json-exporter.nixdeleted−74

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/minio-exporter.nixdeleted−117

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/nginx-exporter.nixdeleted−78

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/node-exporter.nixdeleted−87

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/snmp-exporter.nixdeleted−127

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/unifi-exporter.nixdeleted−105

This diff is too big to show here.

nixos/modules/services/monitoring/prometheus/varnish-exporter.nixdeleted−61

This diff is too big to show here.

nixos/modules/services/monitoring/riemann-dash.nix+2−2

This diff is too big to show here.

nixos/modules/services/monitoring/riemann-tools.nix+2−2

This diff is too big to show here.

nixos/modules/services/monitoring/riemann.nix+20−6

This diff is too big to show here.

nixos/modules/services/monitoring/scollector.nix+2−2

This diff is too big to show here.

nixos/modules/services/monitoring/smartd.nix+2−2

This diff is too big to show here.

nixos/modules/services/monitoring/statsd.nix+1−1

This diff is too big to show here.

nixos/modules/services/monitoring/telegraf.nix+1−1

This diff is too big to show here.

nixos/modules/services/monitoring/ups.nix+2−2

This diff is too big to show here.

nixos/modules/services/monitoring/uptime.nix+1−1

This diff is too big to show here.

nixos/modules/services/monitoring/vnstat.nix+1−1

This diff is too big to show here.

nixos/modules/services/monitoring/zabbix-agent.nix+15−3

This diff is too big to show here.

nixos/modules/services/monitoring/zabbix-server.nix+3−3

This diff is too big to show here.

nixos/modules/services/network-filesystems/beegfs.nix+13−2

This diff is too big to show here.

nixos/modules/services/network-filesystems/ceph.nixnew file+371

This diff is too big to show here.

nixos/modules/services/network-filesystems/davfs2.nix+2−2

This diff is too big to show here.

nixos/modules/services/network-filesystems/glusterfs.nix+4−3

This diff is too big to show here.

nixos/modules/services/network-filesystems/ipfs.nix+17−3

This diff is too big to show here.

nixos/modules/services/network-filesystems/openafs/client.nix+21−7

This diff is too big to show here.

nixos/modules/services/network-filesystems/openafs/lib.nix+7−2

This diff is too big to show here.

nixos/modules/services/network-filesystems/openafs/server.nix+23−14

This diff is too big to show here.

nixos/modules/services/network-filesystems/samba.nix+4−6

This diff is too big to show here.

nixos/modules/services/network-filesystems/tahoe.nix+2−2

This diff is too big to show here.

nixos/modules/services/network-filesystems/xtreemfs.nix+3−3

This diff is too big to show here.

nixos/modules/services/network-filesystems/yandex-disk.nix+3−3

This diff is too big to show here.

nixos/modules/services/networking/amuled.nix+3−3

This diff is too big to show here.

nixos/modules/services/networking/aria2.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/asterisk.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/avahi-daemon.nix+12−3

This diff is too big to show here.

nixos/modules/services/networking/bind.nix+11−1

This diff is too big to show here.

nixos/modules/services/networking/bird.nix+3−2

This diff is too big to show here.

nixos/modules/services/networking/bitlbee.nix+29−14

This diff is too big to show here.

nixos/modules/services/networking/btsync.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/charybdis.nix+3−3

This diff is too big to show here.

nixos/modules/services/networking/chrony.nix+25−37

This diff is too big to show here.

nixos/modules/services/networking/cjdns.nix+3−2

This diff is too big to show here.

nixos/modules/services/networking/cntlm.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/consul.nix+5−4

This diff is too big to show here.

nixos/modules/services/networking/coturn.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/dante.nix+7−6

This diff is too big to show here.

nixos/modules/services/networking/ddclient.nix+60−53

This diff is too big to show here.

nixos/modules/services/networking/dhcpcd.nix+3−2

This diff is too big to show here.

nixos/modules/services/networking/dhcpd.nix+2−1

This diff is too big to show here.

nixos/modules/services/networking/dnscache.nix+25−8

This diff is too big to show here.

nixos/modules/services/networking/dnschain.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/dnscrypt-proxy.nix+7

This diff is too big to show here.

nixos/modules/services/networking/dnscrypt-proxy.xml+43−46

This diff is too big to show here.

nixos/modules/services/networking/dnsdist.nixnew file+61

This diff is too big to show here.

nixos/modules/services/networking/dnsmasq.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/ejabberd.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/epmd.nixnew file+56

This diff is too big to show here.

nixos/modules/services/networking/eternal-terminal.nixnew file+89

This diff is too big to show here.

nixos/modules/services/networking/firewall.nix+235−211

This diff is too big to show here.

nixos/modules/services/networking/flashpolicyd.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/freenet.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/freeradius.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/gale.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/gateone.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/gdomap.nix−3

This diff is too big to show here.

nixos/modules/services/networking/git-daemon.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/gnunet.nix+13−5

This diff is too big to show here.

nixos/modules/services/networking/hans.nixnew file+145

This diff is too big to show here.

nixos/modules/services/networking/haproxy.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/hostapd.nix+4−9

This diff is too big to show here.

nixos/modules/services/networking/hylafax/default.nixnew file+29

This diff is too big to show here.

nixos/modules/services/networking/hylafax/faxq-default.nixnew file+12

This diff is too big to show here.

nixos/modules/services/networking/hylafax/faxq-wait.shnew file+29

This diff is too big to show here.

nixos/modules/services/networking/hylafax/hfaxd-default.nixnew file+10

This diff is too big to show here.

nixos/modules/services/networking/hylafax/modem-default.nixnew file+22

This diff is too big to show here.

nixos/modules/services/networking/hylafax/options.nixnew file+375

This diff is too big to show here.

nixos/modules/services/networking/hylafax/spool.shnew file+111

This diff is too big to show here.

nixos/modules/services/networking/hylafax/systemd.nixnew file+249

This diff is too big to show here.

nixos/modules/services/networking/i2p.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/i2pd.nix+405−207

This diff is too big to show here.

nixos/modules/services/networking/iodine.nix+19−7

This diff is too big to show here.

nixos/modules/services/networking/iperf3.nixnew file+87

This diff is too big to show here.

nixos/modules/services/networking/ircd-hybrid/default.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/iwd.nix+7−8

This diff is too big to show here.

nixos/modules/services/networking/keepalived/default.nix+60−2

This diff is too big to show here.

nixos/modules/services/networking/keepalived/vrrp-instance-options.nixnew file+135

This diff is too big to show here.

nixos/modules/services/networking/keepalived/vrrp-options.nixdeleted−121

This diff is too big to show here.

nixos/modules/services/networking/keepalived/vrrp-script-options.nixnew file+64

This diff is too big to show here.

nixos/modules/services/networking/kippo.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/kresd.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/lambdabot.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/lldpd.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/mailpile.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/matterbridge.nix+53−31

This diff is too big to show here.

nixos/modules/services/networking/minidlna.nix+31−16

This diff is too big to show here.

nixos/modules/services/networking/miniupnpd.nix+2−22

This diff is too big to show here.

nixos/modules/services/networking/mjpg-streamer.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/monero.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/morty.nixnew file+96

This diff is too big to show here.

nixos/modules/services/networking/mosquitto.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/murmur.nix+5−4

This diff is too big to show here.

nixos/modules/services/networking/namecoind.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/nat.nix+15−5

This diff is too big to show here.

nixos/modules/services/networking/ndppd.nixnew file+47

This diff is too big to show here.

nixos/modules/services/networking/networkmanager.nix+200−39

This diff is too big to show here.

nixos/modules/services/networking/nftables.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/nghttpx/nghttpx-options.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/ngircd.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/nix-serve.nix+3−1

This diff is too big to show here.

nixos/modules/services/networking/nntp-proxy.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/nsd.nix+143−10

This diff is too big to show here.

nixos/modules/services/networking/ntpd.nix+3−1

This diff is too big to show here.

nixos/modules/services/networking/nullidentdmod.nixnew file+34

This diff is too big to show here.

nixos/modules/services/networking/nylon.nix+3−3

This diff is too big to show here.

nixos/modules/services/networking/ocserv.nixnew file+99

This diff is too big to show here.

nixos/modules/services/networking/oidentd.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/openntpd.nix+7−5

This diff is too big to show here.

nixos/modules/services/networking/openvpn.nix+4−1

This diff is too big to show here.

nixos/modules/services/networking/owamp.nixnew file+47

This diff is too big to show here.

nixos/modules/services/networking/pdns-recursor.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/pdnsd.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/polipo.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/pptpd.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/prayer.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/prosody.nix+221−29

This diff is too big to show here.

nixos/modules/services/networking/quagga.nix+17−18

This diff is too big to show here.

nixos/modules/services/networking/quassel.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/radicale.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/radvd.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/rdnssd.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/redsocks.nix+2

This diff is too big to show here.

nixos/modules/services/networking/resilio.nix+3−8

This diff is too big to show here.

nixos/modules/services/networking/rpcbind.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/sabnzbd.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/searx.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/seeks.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/shadowsocks.nixnew file+112

This diff is too big to show here.

nixos/modules/services/networking/shairport-sync.nix+3−2

This diff is too big to show here.

nixos/modules/services/networking/shout.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/smokeping.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/sniproxy.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/spiped.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/ssh/sshd.nix+117−17

This diff is too big to show here.

nixos/modules/services/networking/sslh.nix+95−19

This diff is too big to show here.

nixos/modules/services/networking/strongswan-swanctl/module.nixnew file+82

This diff is too big to show here.

nixos/modules/services/networking/strongswan-swanctl/param-constructors.nixnew file+162

This diff is too big to show here.

nixos/modules/services/networking/strongswan-swanctl/param-lib.nixnew file+82

This diff is too big to show here.

nixos/modules/services/networking/strongswan-swanctl/swanctl-params.nixnew file+1254

This diff is too big to show here.

nixos/modules/services/networking/strongswan.nix+19−4

This diff is too big to show here.

nixos/modules/services/networking/stubby.nixnew file+214

This diff is too big to show here.

nixos/modules/services/networking/supplicant.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/supybot.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/syncthing.nix+36−27

This diff is too big to show here.

nixos/modules/services/networking/tcpcrypt.nix+6−6

This diff is too big to show here.

nixos/modules/services/networking/teamspeak3.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/tinc.nix+6−16

This diff is too big to show here.

nixos/modules/services/networking/tinydns.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/tox-bootstrapd.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/toxvpn.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/tvheadend.nix+3−3

This diff is too big to show here.

nixos/modules/services/networking/unbound.nix+8−3

This diff is too big to show here.

nixos/modules/services/networking/unifi.nix+33−6

This diff is too big to show here.

nixos/modules/services/networking/vsftpd.nix+3−3

This diff is too big to show here.

nixos/modules/services/networking/wireguard.nix+55−53

This diff is too big to show here.

nixos/modules/services/networking/wpa_supplicant.nix+12

This diff is too big to show here.

nixos/modules/services/networking/xl2tpd.nix+2−2

This diff is too big to show here.

nixos/modules/services/networking/xrdp.nix+9−4

This diff is too big to show here.

nixos/modules/services/networking/zerobin.nix+1−1

This diff is too big to show here.

nixos/modules/services/networking/zeronet.nixnew file+114

This diff is too big to show here.

nixos/modules/services/networking/zerotierone.nix+31−7

This diff is too big to show here.

nixos/modules/services/networking/znc.nixdeleted−421

This diff is too big to show here.

nixos/modules/services/networking/znc/default.nixnew file+306

This diff is too big to show here.

nixos/modules/services/networking/znc/options.nixnew file+270

This diff is too big to show here.

nixos/modules/services/printing/cupsd.nix+35−8

This diff is too big to show here.

nixos/modules/services/scheduling/atd.nix+2−2

This diff is too big to show here.

nixos/modules/services/scheduling/chronos.nix+1−1

This diff is too big to show here.

nixos/modules/services/scheduling/fcron.nix+2−1

This diff is too big to show here.

nixos/modules/services/scheduling/marathon.nix+1−1

This diff is too big to show here.

nixos/modules/services/search/elasticsearch-curator.nixnew file+93

This diff is too big to show here.

nixos/modules/services/search/elasticsearch.nix+47−49

This diff is too big to show here.

nixos/modules/services/search/hound.nix+2−2

This diff is too big to show here.

nixos/modules/services/search/kibana.nix+2−38

This diff is too big to show here.

nixos/modules/services/search/solr.nix+72−109

This diff is too big to show here.

nixos/modules/services/security/certmgr.nixnew file+194

This diff is too big to show here.

nixos/modules/services/security/cfssl.nixnew file+209

This diff is too big to show here.

nixos/modules/services/security/clamav.nix+6−5

This diff is too big to show here.

nixos/modules/services/security/fprot.nix+2−2

This diff is too big to show here.

nixos/modules/services/security/hologram-server.nix+33−5

This diff is too big to show here.

nixos/modules/services/security/munge.nix+14−2

This diff is too big to show here.

nixos/modules/services/security/oauth2_proxy.nix+108−61

This diff is too big to show here.

nixos/modules/services/security/oauth2_proxy_nginx.nixnew file+64

This diff is too big to show here.

nixos/modules/services/security/sks.nix+67−33

This diff is too big to show here.

nixos/modules/services/security/sshguard.nix+1

This diff is too big to show here.

nixos/modules/services/security/tor.nix+58−25

This diff is too big to show here.

nixos/modules/services/security/torify.nix+1−1

This diff is too big to show here.

nixos/modules/services/security/torsocks.nix+1−1

This diff is too big to show here.

nixos/modules/services/security/usbguard.nix+5−2

This diff is too big to show here.

nixos/modules/services/security/vault.nix+20−6

This diff is too big to show here.

nixos/modules/services/system/cloud-init.nix+33−9

This diff is too big to show here.

nixos/modules/services/system/dbus.nix+3−2

This diff is too big to show here.

nixos/modules/services/system/kerberos.nix+5−5

This diff is too big to show here.

nixos/modules/services/system/localtime.nix+2−8

This diff is too big to show here.

nixos/modules/services/system/nscd.nix+1−3

This diff is too big to show here.

nixos/modules/services/system/saslauthd.nix+1−2

This diff is too big to show here.

nixos/modules/services/system/uptimed.nix+1−1

This diff is too big to show here.

nixos/modules/services/torrent/deluge.nix+4−14

This diff is too big to show here.

nixos/modules/services/torrent/flexget.nix+1−1

This diff is too big to show here.

nixos/modules/services/torrent/peerflix.nix+1−1

This diff is too big to show here.

nixos/modules/services/torrent/transmission.nix+20−13

This diff is too big to show here.

nixos/modules/services/ttys/kmscon.nix+13−2

This diff is too big to show here.

nixos/modules/services/web-apps/atlassian/confluence.nix+2−2

This diff is too big to show here.

nixos/modules/services/web-apps/atlassian/crowd.nix+5−4

This diff is too big to show here.

nixos/modules/services/web-apps/atlassian/jira.nix+3−3

This diff is too big to show here.

nixos/modules/services/web-apps/codimd.nixnew file+920

This diff is too big to show here.

nixos/modules/services/web-apps/frab.nix+2−3

This diff is too big to show here.

nixos/modules/services/web-apps/matomo-doc.xmlnew file+90

This diff is too big to show here.

nixos/modules/services/web-apps/matomo.nixnew file+253

This diff is too big to show here.

nixos/modules/services/web-apps/mattermost.nix+6−6

This diff is too big to show here.

nixos/modules/services/web-apps/nextcloud.nixnew file+487

This diff is too big to show here.

nixos/modules/services/web-apps/nexus.nix+44−10

This diff is too big to show here.

nixos/modules/services/web-apps/nixbot.nixdeleted−149

This diff is too big to show here.

nixos/modules/services/web-apps/piwik-doc.xmldeleted−95

This diff is too big to show here.

nixos/modules/services/web-apps/piwik.nixdeleted−227

This diff is too big to show here.

nixos/modules/services/web-apps/pump.io-configure.jsdeleted−23

This diff is too big to show here.

nixos/modules/services/web-apps/pump.io.nixdeleted−438

This diff is too big to show here.

nixos/modules/services/web-apps/restya-board.nix+2−2

This diff is too big to show here.

nixos/modules/services/web-apps/selfoss.nix+2−2

This diff is too big to show here.

nixos/modules/services/web-apps/tt-rss.nix+50−6

This diff is too big to show here.

nixos/modules/services/web-apps/virtlyst.nixnew file+72

This diff is too big to show here.

nixos/modules/services/web-apps/youtrack.nixnew file+177

This diff is too big to show here.

nixos/modules/services/web-servers/apache-httpd/default.nix+3−8

This diff is too big to show here.

nixos/modules/services/web-servers/apache-httpd/limesurvey.nix+1−1

This diff is too big to show here.

nixos/modules/services/web-servers/apache-httpd/mercurial.nix+1−1

This diff is too big to show here.

nixos/modules/services/web-servers/apache-httpd/owncloud.nix+1−12

This diff is too big to show here.

nixos/modules/services/web-servers/apache-httpd/per-server-options.nix+1−1

This diff is too big to show here.

nixos/modules/services/web-servers/apache-httpd/trac.nix−2

This diff is too big to show here.

nixos/modules/services/web-servers/apache-httpd/wordpress.nix+1−1

This diff is too big to show here.

nixos/modules/services/web-servers/caddy.nix+4−4

This diff is too big to show here.

nixos/modules/services/web-servers/hitch/default.nixnew file+108

This diff is too big to show here.

nixos/modules/services/web-servers/hydron.nixnew file+167

This diff is too big to show here.

nixos/modules/services/web-servers/lighttpd/cgit.nix+22−6

This diff is too big to show here.

nixos/modules/services/web-servers/lighttpd/default.nix+2−2

This diff is too big to show here.

nixos/modules/services/web-servers/lighttpd/gitweb.nix+8−27

This diff is too big to show here.

nixos/modules/services/web-servers/lighttpd/inginious.nixdeleted−261

This diff is too big to show here.

nixos/modules/services/web-servers/meguca.nixnew file+158

This diff is too big to show here.

nixos/modules/services/web-servers/mighttpd2.nix+2−2

This diff is too big to show here.

nixos/modules/services/web-servers/minio.nix+3−3

This diff is too big to show here.

nixos/modules/services/web-servers/nginx/default.nix+76−16

This diff is too big to show here.

nixos/modules/services/web-servers/nginx/gitweb.nixnew file+61

This diff is too big to show here.

nixos/modules/services/web-servers/nginx/location-options.nix+10

This diff is too big to show here.

nixos/modules/services/web-servers/nginx/vhost-options.nix+17−1

This diff is too big to show here.

nixos/modules/services/web-servers/tomcat.nix+251−194

This diff is too big to show here.

nixos/modules/services/web-servers/traefik.nix+2−2

This diff is too big to show here.

nixos/modules/services/web-servers/uwsgi.nix+5−11

This diff is too big to show here.

nixos/modules/services/web-servers/varnish/default.nix+16−7

This diff is too big to show here.

nixos/modules/services/web-servers/zope2.nix+2−2

This diff is too big to show here.

nixos/modules/services/x11/compton.nix+6

This diff is too big to show here.

nixos/modules/services/x11/desktop-managers/default.nix+9−9

This diff is too big to show here.

nixos/modules/services/x11/desktop-managers/enlightenment.nix+8−3

This diff is too big to show here.

nixos/modules/services/x11/desktop-managers/gnome3.nix+36−42

This diff is too big to show here.

nixos/modules/services/x11/desktop-managers/lumina.nix+1−2

This diff is too big to show here.

nixos/modules/services/x11/desktop-managers/lxqt.nix+14−5

This diff is too big to show here.

nixos/modules/services/x11/desktop-managers/mate.nix+3−1

This diff is too big to show here.

nixos/modules/services/x11/desktop-managers/plasma5.nix+12−8

This diff is too big to show here.

nixos/modules/services/x11/desktop-managers/xfce.nix+5−15

This diff is too big to show here.

nixos/modules/services/x11/desktop-managers/xterm.nix+1

This diff is too big to show here.

nixos/modules/services/x11/display-managers/auto.nix+20−4

This diff is too big to show here.

nixos/modules/services/x11/display-managers/default.nix+71−56

This diff is too big to show here.

nixos/modules/services/x11/display-managers/gdm.nix+30−10

This diff is too big to show here.

nixos/modules/services/x11/display-managers/lightdm-greeters/enso-os.nixnew file+159

This diff is too big to show here.

nixos/modules/services/x11/display-managers/lightdm-greeters/gtk.nix+5−5

This diff is too big to show here.

nixos/modules/services/x11/display-managers/lightdm-greeters/mini.nixnew file+100

This diff is too big to show here.

nixos/modules/services/x11/display-managers/lightdm.nix+53−28

This diff is too big to show here.

nixos/modules/services/x11/display-managers/sddm.nix+40−20

This diff is too big to show here.

nixos/modules/services/x11/display-managers/slim.nix+3−3

This diff is too big to show here.

nixos/modules/services/x11/display-managers/startx.nixnew file+44

This diff is too big to show here.

nixos/modules/services/x11/display-managers/xpra.nix+20−24

This diff is too big to show here.

nixos/modules/services/x11/gdk-pixbuf.nixnew file+45

This diff is too big to show here.

nixos/modules/services/x11/hardware/libinput.nix+2−2

This diff is too big to show here.

nixos/modules/services/x11/redshift.nix+3

This diff is too big to show here.

nixos/modules/services/x11/terminal-server.nix+1−1

This diff is too big to show here.

nixos/modules/services/x11/window-managers/awesome.nix+6−1

This diff is too big to show here.

nixos/modules/services/x11/window-managers/bspwm.nix+1−1

This diff is too big to show here.

nixos/modules/services/x11/window-managers/default.nix+3−4

This diff is too big to show here.

nixos/modules/services/x11/window-managers/metacity.nix+3−9

This diff is too big to show here.

nixos/modules/services/x11/window-managers/openbox.nix−1

This diff is too big to show here.

nixos/modules/services/x11/window-managers/stumpwm.nix+2−2

This diff is too big to show here.

nixos/modules/services/x11/window-managers/wmii.nix+1−2

This diff is too big to show here.

nixos/modules/services/x11/xserver.nix+42−24

This diff is too big to show here.

nixos/modules/system/activation/activation-script.nix+64−19

This diff is too big to show here.

nixos/modules/system/activation/switch-to-configuration.pl+40−10

This diff is too big to show here.

nixos/modules/system/activation/top-level.nix+49−36

This diff is too big to show here.

nixos/modules/system/boot/coredump.nix+5−2

This diff is too big to show here.

nixos/modules/system/boot/grow-partition.nix+10−3

This diff is too big to show here.

nixos/modules/system/boot/initrd-network.nix+35−5

This diff is too big to show here.

nixos/modules/system/boot/initrd-ssh.nix+2−2

This diff is too big to show here.

nixos/modules/system/boot/kernel.nix+2−2

This diff is too big to show here.

nixos/modules/system/boot/kexec.nix+19−18

This diff is too big to show here.

nixos/modules/system/boot/loader/generations-dir/generations-dir.nix+1−1

This diff is too big to show here.

nixos/modules/system/boot/loader/grub/grub.nix+64−16

This diff is too big to show here.

nixos/modules/system/boot/loader/grub/install-grub.pl+34−21

This diff is too big to show here.

nixos/modules/system/boot/loader/loader.nix+1−1

This diff is too big to show here.

nixos/modules/system/boot/loader/raspberrypi/builder.shdeleted−122

This diff is too big to show here.

nixos/modules/system/boot/loader/raspberrypi/raspberrypi-builder.nixnew file+10

This diff is too big to show here.

nixos/modules/system/boot/loader/raspberrypi/raspberrypi-builder.shnew file+132

This diff is too big to show here.

nixos/modules/system/boot/loader/raspberrypi/raspberrypi.nix+85−25

This diff is too big to show here.

nixos/modules/system/boot/loader/raspberrypi/uboot-builder.nixnew file+35

This diff is too big to show here.

nixos/modules/system/boot/loader/raspberrypi/uboot-builder.shnew file+38

This diff is too big to show here.

nixos/modules/system/boot/loader/systemd-boot/systemd-boot-builder.py+2−1

This diff is too big to show here.

nixos/modules/system/boot/loader/systemd-boot/systemd-boot.nix+34

This diff is too big to show here.

nixos/modules/system/boot/luksroot.nix+246−123

This diff is too big to show here.

nixos/modules/system/boot/modprobe.nix+1−1

This diff is too big to show here.

nixos/modules/system/boot/networkd.nix+172−32

This diff is too big to show here.

nixos/modules/system/boot/plymouth.nix+2−1

This diff is too big to show here.

nixos/modules/system/boot/resolved.nix+3−1

This diff is too big to show here.

nixos/modules/system/boot/stage-1-init.sh+36−36

This diff is too big to show here.

nixos/modules/system/boot/stage-1.nix+65−8

This diff is too big to show here.

nixos/modules/system/boot/stage-2-init.sh+13−6

This diff is too big to show here.

nixos/modules/system/boot/stage-2.nix+2−3

This diff is too big to show here.

nixos/modules/system/boot/systemd-lib.nix+31−10

This diff is too big to show here.

nixos/modules/system/boot/systemd-nspawn.nix+2−7

This diff is too big to show here.

nixos/modules/system/boot/systemd-unit-options.nix+2−2

This diff is too big to show here.

nixos/modules/system/boot/systemd.nix+61−45

This diff is too big to show here.

nixos/modules/system/boot/timesyncd.nix+4−4

This diff is too big to show here.

nixos/modules/tasks/bcache.nix+1−1

This diff is too big to show here.

nixos/modules/tasks/encrypted-devices.nix−1

This diff is too big to show here.

nixos/modules/tasks/filesystems.nix+5−3

This diff is too big to show here.

nixos/modules/tasks/filesystems/bcachefs.nix+50−11

This diff is too big to show here.

nixos/modules/tasks/filesystems/exfat.nix+1−1

This diff is too big to show here.

nixos/modules/tasks/filesystems/ext.nix+1−1

This diff is too big to show here.

nixos/modules/tasks/filesystems/zfs.nix+102−52

This diff is too big to show here.

nixos/modules/tasks/kbd.nix+1−1

This diff is too big to show here.

nixos/modules/tasks/network-interfaces-scripted.nix+23−8

This diff is too big to show here.

nixos/modules/tasks/network-interfaces-systemd.nix+1−1

This diff is too big to show here.

nixos/modules/tasks/network-interfaces.nix+9−54

This diff is too big to show here.

nixos/modules/tasks/scsi-link-power-management.nix+25−3

This diff is too big to show here.

nixos/modules/tasks/swraid.nix+2−2

This diff is too big to show here.

nixos/modules/tasks/trackpoint.nix+13−4

This diff is too big to show here.

nixos/modules/testing/service-runner.nix+1−1

This diff is too big to show here.

nixos/modules/testing/test-instrumentation.nix+14−7

This diff is too big to show here.

nixos/modules/virtualisation/amazon-image.nix+6−9

This diff is too big to show here.

nixos/modules/virtualisation/amazon-init.nix+1−1

This diff is too big to show here.

nixos/modules/virtualisation/amazon-options.nix+1−1

This diff is too big to show here.

nixos/modules/virtualisation/azure-agent.nix+8−4

This diff is too big to show here.

nixos/modules/virtualisation/azure-common.nix+1−1

This diff is too big to show here.

nixos/modules/virtualisation/azure-config-user.nix+1−1

This diff is too big to show here.

nixos/modules/virtualisation/azure-config.nix+1−1

This diff is too big to show here.

nixos/modules/virtualisation/azure-image.nix+2−2

This diff is too big to show here.

nixos/modules/virtualisation/azure-qemu-220-no-etc-install.patchdeleted−14

This diff is too big to show here.

nixos/modules/virtualisation/brightbox-config.nix+1−1

This diff is too big to show here.

nixos/modules/virtualisation/brightbox-image.nix+1−1

This diff is too big to show here.

nixos/modules/virtualisation/container-config.nix+7

This diff is too big to show here.

nixos/modules/virtualisation/containers.nix+28−10

This diff is too big to show here.

nixos/modules/virtualisation/docker-image.nix+1−1

This diff is too big to show here.

nixos/modules/virtualisation/docker-preloader.nixnew file+135

This diff is too big to show here.

nixos/modules/virtualisation/docker.nix+1−1

This diff is too big to show here.

nixos/modules/virtualisation/ec2-amis.nix+35−1

This diff is too big to show here.

nixos/modules/virtualisation/gce-images.nix+2−1

This diff is too big to show here.

nixos/modules/virtualisation/google-compute-config.nix+1−1

This diff is too big to show here.

nixos/modules/virtualisation/google-compute-image.nix+38−32

This diff is too big to show here.

nixos/modules/virtualisation/hyperv-guest.nix+31−4

This diff is too big to show here.

nixos/modules/virtualisation/kvmgt.nixnew file+70

This diff is too big to show here.

nixos/modules/virtualisation/libvirtd.nix+31−13

This diff is too big to show here.

nixos/modules/virtualisation/lxc-container.nix+2−2

This diff is too big to show here.

nixos/modules/virtualisation/lxc.nix+4−1

This diff is too big to show here.

nixos/modules/virtualisation/lxd.nix+35−29

This diff is too big to show here.

nixos/modules/virtualisation/nova-config.nix+1−1

This diff is too big to show here.

nixos/modules/virtualisation/openvswitch.nix+1−4

This diff is too big to show here.

nixos/modules/virtualisation/parallels-guest.nix+24−6

This diff is too big to show here.

nixos/modules/virtualisation/qemu-guest-agent.nixnew file+36

This diff is too big to show here.

nixos/modules/virtualisation/qemu-vm.nix+69−25

This diff is too big to show here.

nixos/modules/virtualisation/rkt.nix+1−1

This diff is too big to show here.

nixos/modules/virtualisation/virtualbox-guest.nix+2−2

This diff is too big to show here.

nixos/modules/virtualisation/virtualbox-host.nix+24−5

This diff is too big to show here.

nixos/modules/virtualisation/virtualbox-image.nix+39−11

This diff is too big to show here.

nixos/modules/virtualisation/vmware-guest.nix+1−1

This diff is too big to show here.

nixos/modules/virtualisation/xe-guest-utilities.nix+1−1

This diff is too big to show here.

nixos/modules/virtualisation/xen-dom0.nix+10−4

This diff is too big to show here.

nixos/modules/virtualisation/xen-domU.nix+1−1

This diff is too big to show here.

nixos/release-combined.nix+22−13

This diff is too big to show here.

nixos/release-small.nix+4

This diff is too big to show here.

nixos/release.nix+75−201

This diff is too big to show here.

nixos/tests/acme.nix+5−28

This diff is too big to show here.

nixos/tests/all-tests.nixnew file+214

This diff is too big to show here.

nixos/tests/ammonite.nix+1−1

This diff is too big to show here.

nixos/tests/atd.nix+4−9

This diff is too big to show here.

nixos/tests/avahi.nix+1−1

This diff is too big to show here.

nixos/tests/bcachefs.nixnew file+38

This diff is too big to show here.

nixos/tests/beegfs.nix+3−3

This diff is too big to show here.

nixos/tests/bind.nixnew file+27

This diff is too big to show here.

nixos/tests/bittorrent.nix+70−37

This diff is too big to show here.

nixos/tests/boot.nix+11−2

This diff is too big to show here.

nixos/tests/borgbackup.nix+152−11

This diff is too big to show here.

nixos/tests/buildbot.nix+114−105

This diff is too big to show here.

nixos/tests/cadvisor.nix+2−2

This diff is too big to show here.

nixos/tests/cassandra.nix+46−43

This diff is too big to show here.

nixos/tests/ceph.nixnew file+139

This diff is too big to show here.

nixos/tests/certmgr.nixnew file+151

This diff is too big to show here.

nixos/tests/cfssl.nixnew file+67

This diff is too big to show here.

nixos/tests/chromium.nix+35−7

This diff is too big to show here.

nixos/tests/cjdns.nix+6−15

This diff is too big to show here.

nixos/tests/cloud-init.nix+6−3

This diff is too big to show here.

nixos/tests/codimd.nixnew file+54

This diff is too big to show here.

nixos/tests/common/letsencrypt.nixdeleted−446

This diff is too big to show here.

nixos/tests/common/letsencrypt/common.nixnew file+27

This diff is too big to show here.

nixos/tests/common/letsencrypt/default.nixnew file+445

This diff is too big to show here.

nixos/tests/common/letsencrypt/mkcerts.nixnew file+69

This diff is too big to show here.

nixos/tests/common/letsencrypt/mkcerts.shnew file+6

This diff is too big to show here.

nixos/tests/common/letsencrypt/snakeoil-certs.nixnew file+253

This diff is too big to show here.

nixos/tests/common/resolver.nix+1−1

This diff is too big to show here.

nixos/tests/common/user-account.nix+3−3

This diff is too big to show here.

nixos/tests/containers-bridge.nix+1−2

This diff is too big to show here.

nixos/tests/containers-extra_veth.nix+1−2

This diff is too big to show here.

nixos/tests/containers-hosts.nix+1−1

This diff is too big to show here.

nixos/tests/containers-imperative.nix+19−4

This diff is too big to show here.

nixos/tests/containers-ipv4.nix+2−2

This diff is too big to show here.

nixos/tests/containers-ipv6.nix+1−2

This diff is too big to show here.

nixos/tests/containers-macvlans.nix+2−2

This diff is too big to show here.

nixos/tests/containers-physical_interfaces.nix+6−6

This diff is too big to show here.

nixos/tests/containers-portforward.nix+1−2

This diff is too big to show here.

nixos/tests/containers-reloadable.nix+3−4

This diff is too big to show here.

nixos/tests/containers-restart_networking.nix+4−5

This diff is too big to show here.

nixos/tests/containers-tmpfs.nix+2−2

This diff is too big to show here.

nixos/tests/couchdb.nix+2−2

This diff is too big to show here.

nixos/tests/deluge.nixnew file+29

This diff is too big to show here.

nixos/tests/dhparams.nixnew file+144

This diff is too big to show here.

nixos/tests/dnscrypt-proxy.nix+3−2

This diff is too big to show here.

nixos/tests/docker-edge.nix+1−1

This diff is too big to show here.

nixos/tests/docker-preloader.nixnew file+27

This diff is too big to show here.

nixos/tests/docker-registry.nix+24−4

This diff is too big to show here.

nixos/tests/docker-tools-overlay.nixnew file+32

This diff is too big to show here.

nixos/tests/docker-tools.nix+33−6

This diff is too big to show here.

nixos/tests/docker.nix+1−1

This diff is too big to show here.

nixos/tests/dovecot.nix+16−3

This diff is too big to show here.

nixos/tests/ec2.nix+8−3

This diff is too big to show here.

nixos/tests/ecryptfs.nix+2−2

This diff is too big to show here.

nixos/tests/elk.nix+53−8

This diff is too big to show here.

nixos/tests/emacs-daemon.nix+1−1

This diff is too big to show here.

nixos/tests/env.nix+1−1

This diff is too big to show here.

nixos/tests/etcd-cluster.nix+3−3

This diff is too big to show here.

nixos/tests/etcd.nix+1−1

This diff is too big to show here.

nixos/tests/ferm.nix+5−3

This diff is too big to show here.

nixos/tests/firefox.nix+1−1

This diff is too big to show here.

nixos/tests/firewall.nix+3−3

This diff is too big to show here.

nixos/tests/flannel.nix+3−3

This diff is too big to show here.

nixos/tests/flatpak.nixnew file+26

This diff is too big to show here.

nixos/tests/fleet.nixdeleted−76

This diff is too big to show here.

nixos/tests/fsck.nixnew file+29

This diff is too big to show here.

nixos/tests/fwupd.nix+1−1

This diff is too big to show here.

nixos/tests/gdk-pixbuf.nixnew file+21

This diff is too big to show here.

nixos/tests/gitea.nixnew file+77

This diff is too big to show here.

nixos/tests/gitlab.nix+15−6

This diff is too big to show here.

nixos/tests/gitolite.nix+4−4

This diff is too big to show here.

nixos/tests/gnome3-gdm.nix+11−5

This diff is too big to show here.

nixos/tests/gnome3.nix+9−4

This diff is too big to show here.

nixos/tests/gocd-agent.nix+1−1

This diff is too big to show here.

nixos/tests/gocd-server.nix+1−1

This diff is too big to show here.

nixos/tests/grafana.nix+2−2

This diff is too big to show here.

nixos/tests/graphite.nix+18−9

This diff is too big to show here.

nixos/tests/hadoop/hdfs.nixnew file+54

This diff is too big to show here.

nixos/tests/hadoop/yarn.nixnew file+46

This diff is too big to show here.

nixos/tests/haka.nix+1−1

This diff is too big to show here.

nixos/tests/handbrake.nixnew file+25

This diff is too big to show here.

nixos/tests/haproxy.nixnew file+41

This diff is too big to show here.

nixos/tests/hardened.nix+6−4

This diff is too big to show here.

nixos/tests/hibernate.nix+3−3

This diff is too big to show here.

nixos/tests/hitch/default.nixnew file+33

This diff is too big to show here.

nixos/tests/hitch/example.pemnew file+53

This diff is too big to show here.

nixos/tests/hitch/example/index.txtnew file+1

This diff is too big to show here.

nixos/tests/hocker-fetchdocker/default.nixnew file+15

This diff is too big to show here.

nixos/tests/hocker-fetchdocker/hello-world-container.nixnew file+19

This diff is too big to show here.

nixos/tests/hocker-fetchdocker/machine.nixnew file+26

This diff is too big to show here.

nixos/tests/home-assistant.nix+13−10

This diff is too big to show here.

nixos/tests/hound.nix+2−2

This diff is too big to show here.

nixos/tests/hydra.nixdeleted−32

This diff is too big to show here.

nixos/tests/hydra/create-trivial-project.shnew file+57

This diff is too big to show here.

nixos/tests/hydra/default.nixnew file+77

This diff is too big to show here.

nixos/tests/i3wm.nix+8−6

This diff is too big to show here.

nixos/tests/iftop.nixnew file+34

This diff is too big to show here.

nixos/tests/incron.nixnew file+52

This diff is too big to show here.

nixos/tests/influxdb.nix+1−1

This diff is too big to show here.

nixos/tests/initrd-network-ssh/default.nix+3−3

This diff is too big to show here.

nixos/tests/initrd-network.nix+1−1

This diff is too big to show here.

nixos/tests/installer.nix+81−60

This diff is too big to show here.

nixos/tests/ipfs.nix+2−2

This diff is too big to show here.

nixos/tests/ipv6.nix+3−3

This diff is too big to show here.

nixos/tests/jenkins.nix+4−4

This diff is too big to show here.

nixos/tests/kafka.nixnew file+73

This diff is too big to show here.

nixos/tests/kafka_0_10.nixdeleted−48

This diff is too big to show here.

nixos/tests/kafka_0_11.nixdeleted−48

This diff is too big to show here.

nixos/tests/kafka_0_9.nixdeleted−48

This diff is too big to show here.

nixos/tests/kafka_1_0.nixdeleted−48

This diff is too big to show here.

nixos/tests/kernel-copperhead.nixdeleted−19

This diff is too big to show here.

nixos/tests/kernel-latest.nix+1−1

This diff is too big to show here.

nixos/tests/kernel-lts.nix+1−1

This diff is too big to show here.

nixos/tests/kexec.nix+1−1

This diff is too big to show here.

nixos/tests/keymap.nix+50−86

This diff is too big to show here.

nixos/tests/krb5/deprecated-config.nix+1−1

This diff is too big to show here.

nixos/tests/krb5/example-config.nix+1−1

This diff is too big to show here.

nixos/tests/kubernetes/base.nix+6−3

This diff is too big to show here.

nixos/tests/kubernetes/certs.nix+54−21

This diff is too big to show here.

nixos/tests/kubernetes/dns.nix+3−3

This diff is too big to show here.

nixos/tests/kubernetes/e2e.nix+1−1

This diff is too big to show here.

nixos/tests/kubernetes/kubernetes-common.nix−1

This diff is too big to show here.

nixos/tests/kubernetes/rbac.nix+2−2

This diff is too big to show here.

nixos/tests/ldap.nix+2−2

This diff is too big to show here.

nixos/tests/lightdm.nix+2−2

This diff is too big to show here.

nixos/tests/login.nix+1−1

This diff is too big to show here.

nixos/tests/make-test.nix+6−2

This diff is too big to show here.

nixos/tests/mathics.nix+1−1

This diff is too big to show here.

nixos/tests/matrix-synapse.nix+9−8

This diff is too big to show here.

nixos/tests/memcached.nixnew file+28

This diff is too big to show here.

nixos/tests/mesos.nix+6−3

This diff is too big to show here.

nixos/tests/minio.nix+1−1

This diff is too big to show here.

nixos/tests/misc.nix+15−4

This diff is too big to show here.

nixos/tests/mongodb.nix+1−1

This diff is too big to show here.

nixos/tests/morty.nixnew file+32

This diff is too big to show here.

nixos/tests/mpd.nixnew file+119

This diff is too big to show here.

nixos/tests/mumble.nix+2−2

This diff is too big to show here.

nixos/tests/munin.nix+17−7

This diff is too big to show here.

nixos/tests/mutable-users.nix+2−2

This diff is too big to show here.

nixos/tests/mysql-backup.nix+13−5

This diff is too big to show here.

nixos/tests/mysql-replication.nix+12−5

This diff is too big to show here.

nixos/tests/mysql.nix+1−2

This diff is too big to show here.

nixos/tests/nat.nix+4−6

This diff is too big to show here.

nixos/tests/netdata.nix+10−3

This diff is too big to show here.

nixos/tests/networking-proxy.nix+4−4

This diff is too big to show here.

nixos/tests/networking.nix+46−38

This diff is too big to show here.

nixos/tests/nextcloud/basic.nixnew file+56

This diff is too big to show here.

nixos/tests/nextcloud/default.nixnew file+9

This diff is too big to show here.

nixos/tests/nextcloud/with-mysql-and-memcached.nixnew file+97

This diff is too big to show here.

nixos/tests/nextcloud/with-postgresql-and-redis.nixnew file+130

This diff is too big to show here.

nixos/tests/nexus.nix+9−11

This diff is too big to show here.

nixos/tests/nfs.nix+4−3

This diff is too big to show here.

nixos/tests/nginx.nix+1−1

This diff is too big to show here.

nixos/tests/nix-ssh-serve.nixnew file+39

This diff is too big to show here.

nixos/tests/novacomd.nix+8−2

This diff is too big to show here.

nixos/tests/nsd.nix+9

This diff is too big to show here.

nixos/tests/openldap.nixnew file+35

This diff is too big to show here.

nixos/tests/opensmtpd.nixnew file+125

This diff is too big to show here.

nixos/tests/openssh.nix+7−20

This diff is too big to show here.

nixos/tests/osquery.nixnew file+28

This diff is too big to show here.

nixos/tests/ostree.nixnew file+21

This diff is too big to show here.

nixos/tests/owncloud.nix+2−2

This diff is too big to show here.

nixos/tests/pam-oath-login.nix+3−5

This diff is too big to show here.

nixos/tests/panamax.nixdeleted−21

This diff is too big to show here.

nixos/tests/partition.nix+1−1

This diff is too big to show here.

nixos/tests/peerflix.nix+1−1

This diff is too big to show here.

nixos/tests/pgjwt.nix+1−1

This diff is too big to show here.

nixos/tests/phabricator.nix+3−3

This diff is too big to show here.

nixos/tests/php-pcre.nix+3−3

This diff is too big to show here.

nixos/tests/plasma5.nix+22−19

This diff is too big to show here.

nixos/tests/plotinus.nix+6−6

This diff is too big to show here.

nixos/tests/postgis.nix+2−2

This diff is too big to show here.

nixos/tests/postgresql.nix+16−3

This diff is too big to show here.

nixos/tests/powerdns.nix+1−1

This diff is too big to show here.

nixos/tests/predictable-interface-names.nix+24−24

This diff is too big to show here.

nixos/tests/printing.nix+5−3

This diff is too big to show here.

nixos/tests/prometheus-exporters.nixnew file+316

This diff is too big to show here.

nixos/tests/prometheus.nix+1−1

This diff is too big to show here.

nixos/tests/prosody.nixnew file+78

This diff is too big to show here.

nixos/tests/proxy.nix+3−3

This diff is too big to show here.

nixos/tests/pump.io.nixdeleted−89

This diff is too big to show here.

nixos/tests/quagga.nix+5−6

This diff is too big to show here.

nixos/tests/quake3.nix+2−2

This diff is too big to show here.

nixos/tests/rabbitmq.nix+1−1

This diff is too big to show here.

nixos/tests/radicale.nix+1−1

This diff is too big to show here.

nixos/tests/redmine.nixnew file+40

This diff is too big to show here.

nixos/tests/riak.nix+1−1

This diff is too big to show here.

nixos/tests/rspamd.nix+160−46

This diff is too big to show here.

nixos/tests/rsyslogd.nixnew file+42

This diff is too big to show here.

nixos/tests/run-in-machine.nix+6−3

This diff is too big to show here.

nixos/tests/rxe.nix+2−2

This diff is too big to show here.

nixos/tests/samba.nix+2−2

This diff is too big to show here.

nixos/tests/sddm.nix+9−6

This diff is too big to show here.

nixos/tests/simple.nix+1−1

This diff is too big to show here.

nixos/tests/slim.nix+2−2

This diff is too big to show here.

nixos/tests/slurm.nix+70−18

This diff is too big to show here.

nixos/tests/smokeping.nix+1−1

This diff is too big to show here.

nixos/tests/solr.nixnew file+47

This diff is too big to show here.

nixos/tests/ssh-keys.nixnew file+15

This diff is too big to show here.

nixos/tests/statsd.nixdeleted−40

This diff is too big to show here.

nixos/tests/strongswan-swanctl.nixnew file+148

This diff is too big to show here.

nixos/tests/subversion.nix+2−2

This diff is too big to show here.

nixos/tests/sudo.nix+2−2

This diff is too big to show here.

nixos/tests/switch-test.nix+2−2

This diff is too big to show here.

nixos/tests/systemd.nixnew file+68

This diff is too big to show here.

nixos/tests/taskserver.nix+4−3

This diff is too big to show here.

nixos/tests/tomcat.nix+1−1

This diff is too big to show here.

nixos/tests/tor.nixnew file+28

This diff is too big to show here.

nixos/tests/trac.nix+4−4

This diff is too big to show here.

nixos/tests/transmission.nixnew file+21

This diff is too big to show here.

nixos/tests/udisks2.nix+4−3

This diff is too big to show here.

nixos/tests/upnp.nixnew file+94

This diff is too big to show here.

nixos/tests/vault.nix+3−3

This diff is too big to show here.

nixos/tests/virtualbox.nix+49−10

This diff is too big to show here.

nixos/tests/wordpress.nix+3−6

This diff is too big to show here.

nixos/tests/xautolock.nixnew file+24

This diff is too big to show here.

nixos/tests/xdg-desktop-portal.nixnew file+17

This diff is too big to show here.

nixos/tests/xfce.nix+1−1

This diff is too big to show here.

nixos/tests/xmonad.nix+1−1

This diff is too big to show here.

nixos/tests/xrdp.nix+3−3

This diff is too big to show here.

nixos/tests/xss-lock.nixnew file+25

This diff is too big to show here.

nixos/tests/yabar.nix+13−5

This diff is too big to show here.

nixos/tests/zfs.nix+6−3

This diff is too big to show here.

nixos/tests/zookeeper.nix+1−1

This diff is too big to show here.

pkgs/applications/altcoins/aeon/default.nix+19−11

This diff is too big to show here.

pkgs/applications/altcoins/bitcoin-abc.nix+7−4

This diff is too big to show here.

pkgs/applications/altcoins/bitcoin-classic.nix+5−2

This diff is too big to show here.

pkgs/applications/altcoins/bitcoin-unlimited-const-comparators.patchnew file+38

This diff is too big to show here.

pkgs/applications/altcoins/bitcoin-unlimited.nix+14−6

This diff is too big to show here.

pkgs/applications/altcoins/bitcoin-xt.nix+10−5

This diff is too big to show here.

pkgs/applications/altcoins/bitcoin.nix+21−6

This diff is too big to show here.

pkgs/applications/altcoins/btc1.nix+11−10

This diff is too big to show here.

pkgs/applications/altcoins/clightning.nixnew file+47

This diff is too big to show here.

pkgs/applications/altcoins/dapp.nixdeleted−33

This diff is too big to show here.

pkgs/applications/altcoins/dashpay.nix+6−6

This diff is too big to show here.

pkgs/applications/altcoins/dcrd.nixnew file+34

This diff is too big to show here.

pkgs/applications/altcoins/dcrwallet.nixnew file+43

This diff is too big to show here.

pkgs/applications/altcoins/default.nix+58−30

This diff is too big to show here.

pkgs/applications/altcoins/dero.nix+3−3

This diff is too big to show here.

pkgs/applications/altcoins/dogecoin.nix+1−1

This diff is too big to show here.

pkgs/applications/altcoins/ethabi.nix+7−6

This diff is too big to show here.

pkgs/applications/altcoins/ethrun.nixdeleted−25

This diff is too big to show here.

pkgs/applications/altcoins/ethsign/default.nixdeleted−59

This diff is too big to show here.

pkgs/applications/altcoins/freicoin.nix+2−2

This diff is too big to show here.

pkgs/applications/altcoins/go-ethereum-classic/default.nix+1−1

This diff is too big to show here.

pkgs/applications/altcoins/go-ethereum.nix+3−14

This diff is too big to show here.

pkgs/applications/altcoins/hevm.nixdeleted−61

This diff is too big to show here.

pkgs/applications/altcoins/litecoin.nix+11−4

This diff is too big to show here.

pkgs/applications/altcoins/masari.nixnew file+27

This diff is too big to show here.

pkgs/applications/altcoins/memorycoin.nix+1−1

This diff is too big to show here.

pkgs/applications/altcoins/mist.nixnew file+72

This diff is too big to show here.

pkgs/applications/altcoins/monero-gui/default.nix+10−7

This diff is too big to show here.

pkgs/applications/altcoins/monero-gui/move-log-file.patch+22−37

This diff is too big to show here.

pkgs/applications/altcoins/monero-gui/move-translations-dir.patch+7−8

This diff is too big to show here.

pkgs/applications/altcoins/monero/build-wallet-rpc.patchdeleted−78

This diff is too big to show here.

pkgs/applications/altcoins/monero/default.nix+24−25

This diff is too big to show here.

pkgs/applications/altcoins/namecoin.nix+6−3

This diff is too big to show here.

pkgs/applications/altcoins/nano-wallet/CMakeLists.txt.patchnew file+13

This diff is too big to show here.

pkgs/applications/altcoins/nano-wallet/default.nixnew file+57

This diff is too big to show here.

pkgs/applications/altcoins/parity-ui/default.nixnew file+50

This diff is too big to show here.

pkgs/applications/altcoins/parity-ui/env.nixnew file+19

This diff is too big to show here.

pkgs/applications/altcoins/parity/beta.nixnew file+9

This diff is too big to show here.

pkgs/applications/altcoins/parity/default.nixnew file+7

This diff is too big to show here.

pkgs/applications/altcoins/parity/parity.nixnew file+43

This diff is too big to show here.

pkgs/applications/altcoins/parity/patches/vendored-sources-2.0.patchnew file+98

This diff is too big to show here.

pkgs/applications/altcoins/parity/patches/vendored-sources-2.1.patchnew file+83

This diff is too big to show here.

pkgs/applications/altcoins/particl/particl-core.nixnew file+53

This diff is too big to show here.

pkgs/applications/altcoins/primecoin.nixdeleted−58

This diff is too big to show here.

pkgs/applications/altcoins/seth.nixdeleted−33

This diff is too big to show here.

pkgs/applications/altcoins/stellar-core.nix+1−1

This diff is too big to show here.

pkgs/applications/altcoins/wownero.nixnew file+51

This diff is too big to show here.

pkgs/applications/audio/FIL-plugins/default.nixnew file+37

This diff is too big to show here.

pkgs/applications/audio/MMA/default.nix+4−4

This diff is too big to show here.

pkgs/applications/audio/a2jmidid/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/aacgain/default.nix+21−7

This diff is too big to show here.

pkgs/applications/audio/abcde/abcde.patchdeleted−30

This diff is too big to show here.

pkgs/applications/audio/abcde/default.nix+20−22

This diff is too big to show here.

pkgs/applications/audio/aeolus/default.nix+3−3

This diff is too big to show here.

pkgs/applications/audio/airwave/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/aj-snapshot/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/amarok/default.nixnew file+42

This diff is too big to show here.

pkgs/applications/audio/amarok/kf5.nixdeleted−38

This diff is too big to show here.

pkgs/applications/audio/ams-lv2/default.nix+5−5

This diff is too big to show here.

pkgs/applications/audio/ario/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/asunder/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/audacious/default.nix+6−6

This diff is too big to show here.

pkgs/applications/audio/audacious/qt-5.nix+3−3

This diff is too big to show here.

pkgs/applications/audio/audacity/default.nix+4−4

This diff is too big to show here.

pkgs/applications/audio/audio-recorder/default.nix+15−27

This diff is too big to show here.

pkgs/applications/audio/avldrums-lv2/default.nixnew file+30

This diff is too big to show here.

pkgs/applications/audio/axoloti/default.nix+14−14

This diff is too big to show here.

pkgs/applications/audio/axoloti/dfu-util.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/axoloti/libusb1.nix+3−3

This diff is too big to show here.

pkgs/applications/audio/banshee/default.nixdeleted−55

This diff is too big to show here.

pkgs/applications/audio/baudline/default.nix+3−3

This diff is too big to show here.

pkgs/applications/audio/beast/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/bitmeter/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/bitwig-studio/bitwig-studio2.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/bs1770gain/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/cadence/default.nixnew file+65

This diff is too big to show here.

pkgs/applications/audio/calf/default.nix+11−2

This diff is too big to show here.

pkgs/applications/audio/cantata/default.nix+2−11

This diff is too big to show here.

pkgs/applications/audio/caps/default.nix+2−9

This diff is too big to show here.

pkgs/applications/audio/cava/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/cdparanoia/default.nix+6−4

This diff is too big to show here.

pkgs/applications/audio/cdparanoia/fix_private_keyword.patchnew file+468

This diff is too big to show here.

pkgs/applications/audio/chuck/clang.patchnew file+58

This diff is too big to show here.

pkgs/applications/audio/chuck/default.nix+19−14

This diff is too big to show here.

pkgs/applications/audio/clementine/default.nix+30−40

This diff is too big to show here.

pkgs/applications/audio/cmus/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/cmusfm/default.nixnew file+36

This diff is too big to show here.

pkgs/applications/audio/cozy-audiobooks/default.nixnew file+85

This diff is too big to show here.

pkgs/applications/audio/crip/default.nixnew file+68

This diff is too big to show here.

pkgs/applications/audio/csa/default.nixnew file+28

This diff is too big to show here.

pkgs/applications/audio/csound/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/deadbeef/default.nix+5−5

This diff is too big to show here.

pkgs/applications/audio/deadbeef/plugins/headerbar-gtk3.nixnew file+30

This diff is too big to show here.

pkgs/applications/audio/deadbeef/plugins/infobar.nixnew file+33

This diff is too big to show here.

pkgs/applications/audio/deadbeef/plugins/mpris2.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/deadbeef/plugins/opus.nixnew file+31

This diff is too big to show here.

pkgs/applications/audio/deadbeef/wrapper.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/denemo/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/distrho/default.nix+7−5

This diff is too big to show here.

pkgs/applications/audio/dr14_tmeter/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/dragonfly-reverb/default.nixnew file+35

This diff is too big to show here.

pkgs/applications/audio/drumgizmo/default.nix+3−3

This diff is too big to show here.

pkgs/applications/audio/drumkv1/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/easytag/default.nix+21−17

This diff is too big to show here.

pkgs/applications/audio/ecasound/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/eflite/buf-overflow.patchdeleted−22

This diff is too big to show here.

pkgs/applications/audio/eflite/cvs-update.patchdeleted−98

This diff is too big to show here.

pkgs/applications/audio/eflite/default.nix+25−6

This diff is too big to show here.

pkgs/applications/audio/eflite/link.patchdeleted−11

This diff is too big to show here.

pkgs/applications/audio/elisa/default.nixnew file+35

This diff is too big to show here.

pkgs/applications/audio/eq10q/default.nix+10−1

This diff is too big to show here.

pkgs/applications/audio/espeak-ng/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/eteroj.lv2/default.nixnew file+24

This diff is too big to show here.

pkgs/applications/audio/faust/faust1.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/faust/faust2.nix+11−4

This diff is too big to show here.

pkgs/applications/audio/faust/faustlive.nixnew file+35

This diff is too big to show here.

pkgs/applications/audio/flac/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/flacon/default.nix+4−4

This diff is too big to show here.

pkgs/applications/audio/fldigi/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/fluidsynth/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/fmit/default.nix+3−3

This diff is too big to show here.

pkgs/applications/audio/fomp/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/freewheeling/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/gigedit/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/gjay/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/gmpc/default.nix+3−3

This diff is too big to show here.

pkgs/applications/audio/google-musicmanager/default.nix+47−29

This diff is too big to show here.

pkgs/applications/audio/google-play-music-desktop-player/default.nix+4−3

This diff is too big to show here.

pkgs/applications/audio/gpodder/default.nix+3−4

This diff is too big to show here.

pkgs/applications/audio/gradio/default.nix+9−10

This diff is too big to show here.

pkgs/applications/audio/gtklick/default.nix+2−3

This diff is too big to show here.

pkgs/applications/audio/gtkpod/default.nix+9−16

This diff is too big to show here.

pkgs/applications/audio/guitarix/default.nix+8−8

This diff is too big to show here.

pkgs/applications/audio/gxplugins-lv2/default.nixnew file+29

This diff is too big to show here.

pkgs/applications/audio/helm/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/hybridreverb2/default.nixnew file+49

This diff is too big to show here.

pkgs/applications/audio/infamousPlugins/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/ir.lv2/default.nix+3−3

This diff is too big to show here.

pkgs/applications/audio/jaaa/default.nix+4−4

This diff is too big to show here.

pkgs/applications/audio/jack-capture/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/jack-oscrolloscope/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/jalv/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/jamin/default.nix+4−6

This diff is too big to show here.

pkgs/applications/audio/japa/default.nix+3−3

This diff is too big to show here.

pkgs/applications/audio/kid3/default.nix+11−12

This diff is too big to show here.

pkgs/applications/audio/ladspa-sdk/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/ladspa-sdk/ladspah.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/lastfmsubmitd/default.nix+5−5

This diff is too big to show here.

pkgs/applications/audio/lastwatch/default.nix+1−2

This diff is too big to show here.

pkgs/applications/audio/lingot/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/linuxsampler/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/lmms/default.nix+5−3

This diff is too big to show here.

pkgs/applications/audio/lollypop/default.nixnew file+70

This diff is too big to show here.

pkgs/applications/audio/lsp-plugins/default.nixnew file+160

This diff is too big to show here.

pkgs/applications/audio/ltc-tools/default.nixnew file+25

This diff is too big to show here.

pkgs/applications/audio/magnetophonDSP/VoiceOfFaust/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/mda-lv2/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/meterbridge/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/meters_lv2/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/mhwaveedit/default.nix+12−11

This diff is too big to show here.

pkgs/applications/audio/mi2ly/default.nix+1

This diff is too big to show here.

pkgs/applications/audio/midas/generic.nixnew file+43

This diff is too big to show here.

pkgs/applications/audio/midas/m32edit.nixnew file+9

This diff is too big to show here.

pkgs/applications/audio/midas/x32edit.nixnew file+9

This diff is too big to show here.

pkgs/applications/audio/midisheetmusic/default.nixnew file+60

This diff is too big to show here.

pkgs/applications/audio/mikmod/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/milkytracker/decompressor_gzip.patchdeleted−20

This diff is too big to show here.

pkgs/applications/audio/milkytracker/default.nix+12−15

This diff is too big to show here.

pkgs/applications/audio/mimic/default.nixnew file+35

This diff is too big to show here.

pkgs/applications/audio/mimms/default.nix+26−26

This diff is too big to show here.

pkgs/applications/audio/mixxx/default.nix+21−21

This diff is too big to show here.

pkgs/applications/audio/monkeys-audio/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/mopidy-gmusic/default.nixdeleted−28

This diff is too big to show here.

pkgs/applications/audio/mopidy-iris/default.nixdeleted−28

This diff is too big to show here.

pkgs/applications/audio/mopidy-local-images/default.nixdeleted−33

This diff is too big to show here.

pkgs/applications/audio/mopidy-local-sqlite/default.nixdeleted−26

This diff is too big to show here.

pkgs/applications/audio/mopidy-moped/default.nixdeleted−25

This diff is too big to show here.

pkgs/applications/audio/mopidy-mopify/default.nixdeleted−23

This diff is too big to show here.

pkgs/applications/audio/mopidy-musicbox-webclient/default.nixdeleted−24

This diff is too big to show here.

pkgs/applications/audio/mopidy-soundcloud/default.nixdeleted−24

This diff is too big to show here.

pkgs/applications/audio/mopidy-spotify-tunigo/default.nixdeleted−24

This diff is too big to show here.

pkgs/applications/audio/mopidy-spotify/default.nixdeleted−23

This diff is too big to show here.

pkgs/applications/audio/mopidy-youtube/default.nixdeleted−24

This diff is too big to show here.

pkgs/applications/audio/mopidy/default.nix+5−6

This diff is too big to show here.

pkgs/applications/audio/mopidy/gmusic.nixnew file+28

This diff is too big to show here.

pkgs/applications/audio/mopidy/iris.nixnew file+34

This diff is too big to show here.

pkgs/applications/audio/mopidy/local-images.nixnew file+32

This diff is too big to show here.

pkgs/applications/audio/mopidy/local-sqlite.nixnew file+25

This diff is too big to show here.

pkgs/applications/audio/mopidy/moped.nixnew file+26

This diff is too big to show here.

pkgs/applications/audio/mopidy/mopify.nixnew file+23

This diff is too big to show here.

pkgs/applications/audio/mopidy/musicbox-webclient.nixnew file+23

This diff is too big to show here.

pkgs/applications/audio/mopidy/soundcloud.nixnew file+23

This diff is too big to show here.

pkgs/applications/audio/mopidy/spotify-tunigo.nixnew file+23

This diff is too big to show here.

pkgs/applications/audio/mopidy/spotify.nixnew file+23

This diff is too big to show here.

pkgs/applications/audio/mopidy/youtube.nixnew file+23

This diff is too big to show here.

pkgs/applications/audio/morituri/default.nixdeleted−55

This diff is too big to show here.

pkgs/applications/audio/morituri/paths.patchdeleted−87

This diff is too big to show here.

pkgs/applications/audio/mp3blaster/default.nix+5−2

This diff is too big to show here.

pkgs/applications/audio/mpc123/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/mpg123/default.nix+5−5

This diff is too big to show here.

pkgs/applications/audio/mpg321/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/muse/default.nixnew file+76

This diff is too big to show here.

pkgs/applications/audio/musescore/default.nix+12−34

This diff is too big to show here.

pkgs/applications/audio/ncmpc/default.nix+2−4

This diff is too big to show here.

pkgs/applications/audio/ncmpcpp/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/nova-filters/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/opusfile/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/padthv1/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/pamix/default.nix+8−4

This diff is too big to show here.

pkgs/applications/audio/pamixer/default.nix+13−6

This diff is too big to show here.

pkgs/applications/audio/paprefs/default.nix+6−11

This diff is too big to show here.

pkgs/applications/audio/patchage/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/pavucontrol/default.nix+4−3

This diff is too big to show here.

pkgs/applications/audio/pd-plugins/helmholtz/default.nix+4−1

This diff is too big to show here.

pkgs/applications/audio/pd-plugins/puremapping/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/pd-plugins/zexy/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/pianobar/default.nix+4−5

This diff is too big to show here.

pkgs/applications/audio/pianobooster/default.nix+3−3

This diff is too big to show here.

pkgs/applications/audio/picard/default.nix+13−8

This diff is too big to show here.

pkgs/applications/audio/pithos/default.nix−1

This diff is too big to show here.

pkgs/applications/audio/praat/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/puddletag/default.nix+2−13

This diff is too big to show here.

pkgs/applications/audio/pulseaudio-ctl/default.nixnew file+41

This diff is too big to show here.

pkgs/applications/audio/pulseaudio-modules-bt/default.nixnew file+82

This diff is too big to show here.

pkgs/applications/audio/pulseaudio-modules-bt/fix-install-path.patchnew file+20

This diff is too big to show here.

pkgs/applications/audio/pulseeffects/default.nixnew file+109

This diff is too big to show here.

pkgs/applications/audio/puredata/default.nix+9−12

This diff is too big to show here.

pkgs/applications/audio/puredata/wrapper.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/qjackctl/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/qmidinet/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/qmidiroute/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/qmmp/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/qsampler/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/qsynth/default.nix+3−3

This diff is too big to show here.

pkgs/applications/audio/quodlibet/default.nix+29−14

This diff is too big to show here.

pkgs/applications/audio/radiotray-ng/default.nix+13−11

This diff is too big to show here.

pkgs/applications/audio/reaper/default.nixnew file+81

This diff is too big to show here.

pkgs/applications/audio/redoflacs/default.nixnew file+39

This diff is too big to show here.

pkgs/applications/audio/renoise/default.nix+19−11

This diff is too big to show here.

pkgs/applications/audio/rhvoice/default.nixnew file+48

This diff is too big to show here.

pkgs/applications/audio/rhvoice/honor_nix_environment.patchnew file+14

This diff is too big to show here.

pkgs/applications/audio/rhythmbox/default.nix+30−17

This diff is too big to show here.

pkgs/applications/audio/rkrlv2/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/rosegarden/default.nix+3−3

This diff is too big to show here.

pkgs/applications/audio/samplv1/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/sayonara/default.nix+3−3

This diff is too big to show here.

pkgs/applications/audio/schismtracker/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/setbfree/default.nix+4−4

This diff is too big to show here.

pkgs/applications/audio/sfxr-qt/default.nixnew file+36

This diff is too big to show here.

pkgs/applications/audio/sidplayfp/default.nixnew file+22

This diff is too big to show here.

pkgs/applications/audio/sisco.lv2/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/snapcast/default.nixnew file+66

This diff is too big to show here.

pkgs/applications/audio/snd/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/sonata/default.nix+5−7

This diff is too big to show here.

pkgs/applications/audio/sonic-pi/default.nix+5−5

This diff is too big to show here.

pkgs/applications/audio/sonic-visualiser/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/sound-juicer/default.nix+23−29

This diff is too big to show here.

pkgs/applications/audio/soundscape-renderer/default.nix+4−2

This diff is too big to show here.

pkgs/applications/audio/spectmorph/default.nixnew file+22

This diff is too big to show here.

pkgs/applications/audio/spectrojack/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/split2flac/default.nixnew file+62

This diff is too big to show here.

pkgs/applications/audio/spotify/default.nix+48−16

This diff is too big to show here.

pkgs/applications/audio/spotify/update.shnew file+96

This diff is too big to show here.

pkgs/applications/audio/spotifywm/default.nixnew file+31

This diff is too big to show here.

pkgs/applications/audio/squishyball/default.nix+2

This diff is too big to show here.

pkgs/applications/audio/streamripper/default.nix+2−3

This diff is too big to show here.

pkgs/applications/audio/sunvox/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/swh-lv2/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/synthv1/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/tambura/default.nixnew file+34

This diff is too big to show here.

pkgs/applications/audio/tetraproc/default.nix+3−3

This diff is too big to show here.

pkgs/applications/audio/tomahawk/default.nix+4−3

This diff is too big to show here.

pkgs/applications/audio/transcode/default.nix+5−3

This diff is too big to show here.

pkgs/applications/audio/transcribe/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/uade123/default.nix+5−2

This diff is too big to show here.

pkgs/applications/audio/vcv-rack/default.nixnew file+79

This diff is too big to show here.

pkgs/applications/audio/vimpc/default.nix+1−3

This diff is too big to show here.

pkgs/applications/audio/vocal/default.nixnew file+53

This diff is too big to show here.

pkgs/applications/audio/vorbis-tools/default.nix+1−1

This diff is too big to show here.

pkgs/applications/audio/whipper/default.nixnew file+48

This diff is too big to show here.

pkgs/applications/audio/whipper/paths.patchnew file+105

This diff is too big to show here.

pkgs/applications/audio/wolf-shaper/default.nixnew file+47

This diff is too big to show here.

pkgs/applications/audio/x42-plugins/default.nix+5−5

This diff is too big to show here.

pkgs/applications/audio/ympd/default.nix+3−2

This diff is too big to show here.

pkgs/applications/audio/yoshimi/default.nix+4−4

This diff is too big to show here.

pkgs/applications/audio/zam-plugins/default.nix+2−2

This diff is too big to show here.

pkgs/applications/audio/zita-njbridge/default.nixnew file+32

This diff is too big to show here.

pkgs/applications/backup/crashplan/crashplan-small-business.nix+10−10

This diff is too big to show here.

pkgs/applications/backup/crashplan/default.nix+1−1

This diff is too big to show here.

pkgs/applications/backup/deja-dup/default.nix+18−22

This diff is too big to show here.

pkgs/applications/backup/deja-dup/fix-paths.patch+10−11

This diff is too big to show here.

pkgs/applications/backup/deja-dup/hardcode-gsettings.patchnew file+38

This diff is too big to show here.

pkgs/applications/display-managers/lightdm-enso-os-greeter/default.nixnew file+71

This diff is too big to show here.

pkgs/applications/display-managers/lightdm-gtk-greeter/default.nixdeleted−49

This diff is too big to show here.

pkgs/applications/display-managers/lightdm-mini-greeter/default.nixnew file+32

This diff is too big to show here.

pkgs/applications/display-managers/lightdm/default.nix+53−19

This diff is too big to show here.

pkgs/applications/display-managers/lightdm/gtk-greeter.nixnew file+51

This diff is too big to show here.

pkgs/applications/display-managers/lightdm/run-dir.patchnew file+13

This diff is too big to show here.

pkgs/applications/display-managers/ly/default.nixnew file+29

This diff is too big to show here.

pkgs/applications/display-managers/sddm/default.nix+10−7

This diff is too big to show here.

pkgs/applications/display-managers/slim/default.nix+8−4

This diff is too big to show here.

pkgs/applications/editors/android-studio/common.nix+60−14

This diff is too big to show here.

pkgs/applications/editors/android-studio/default.nix+38−29

This diff is too big to show here.

pkgs/applications/editors/aseprite/default.nix+18−6

This diff is too big to show here.

pkgs/applications/editors/atom/beta.nixdeleted−52

This diff is too big to show here.

pkgs/applications/editors/atom/default.nix+82−46

This diff is too big to show here.

pkgs/applications/editors/atom/env.nix+3−3

This diff is too big to show here.

pkgs/applications/editors/bonzomatic/default.nixnew file+30

This diff is too big to show here.

pkgs/applications/editors/brackets/default.nix+2−2

This diff is too big to show here.

pkgs/applications/editors/codeblocks/default.nix+4−8

This diff is too big to show here.

pkgs/applications/editors/dit/default.nixnew file+30

This diff is too big to show here.

pkgs/applications/editors/eclipse/build-eclipse.nix+5−5

This diff is too big to show here.

pkgs/applications/editors/eclipse/default.nix+94−43

This diff is too big to show here.

pkgs/applications/editors/eclipse/plugins.nix+65−23

This diff is too big to show here.

pkgs/applications/editors/ed/default.nix+1−2

This diff is too big to show here.

pkgs/applications/editors/edbrowse/default.nix+8−10

This diff is too big to show here.

pkgs/applications/editors/elvis/default.nix+1−1

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/bbdb/default.nix+1−1

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/calfw/default.nix+1−1

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/cask/default.nix+2−2

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/cedille/default.nixnew file+30

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/elpa-generated.nix+830−292

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/elpa-packages.nix+1−1

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/emacs-clang-complete-async/default.nix+1−1

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/emacs-libvterm/default.nixnew file+41

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/filesets-plus/default.nix+2−2

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/font-lock-plus/default.nix+2−2

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/haskell/default.nix+3

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/header2/default.nix+2−2

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/hexrgb/default.nix+2−2

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/icicles/default.nix+14−14

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/jdee/default.nix+1−1

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/lib-requires/default.nix+2−2

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/maude/default.nix+1−1

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/melpa-generated.nix+46035−20457

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/melpa-packages.nix+93−62

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/melpa-stable-generated.nix+22836−9509

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/melpa-stable-packages.nix+40−7

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/ocaml/default.nix+1−1

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/org-generated.nix+14−9

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/org-packages.nix+1−7

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/org/default.nix+1−1

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/scala-mode/v1.nix+1−1

This diff is too big to show here.

pkgs/applications/editors/emacs-modes/thingatpt-plus/default.nix+2−2

This diff is too big to show here.

pkgs/applications/editors/emacs/25.nix+139

This diff is too big to show here.

pkgs/applications/editors/emacs/builder.sh−40

This diff is too big to show here.

pkgs/applications/editors/emacs/clean-env.patch+2−2

This diff is too big to show here.

pkgs/applications/editors/emacs/default.nix+36−30

This diff is too big to show here.

pkgs/applications/editors/emacs/macport.nix+16−16

This diff is too big to show here.

pkgs/applications/editors/featherpad/default.nix+23

This diff is too big to show here.

pkgs/applications/editors/flpsed/default.nix+3−3

This diff is too big to show here.

pkgs/applications/editors/focuswriter/default.nix+3−3

This diff is too big to show here.

pkgs/applications/editors/geany/default.nix+7−13

This diff is too big to show here.

pkgs/applications/editors/geany/with-vte.nix+1−1

This diff is too big to show here.

pkgs/applications/editors/ghostwriter/default.nix+2−2

This diff is too big to show here.

pkgs/applications/editors/gnome-builder/default.nix+158

This diff is too big to show here.

pkgs/applications/editors/gnome-latex/default.nix+47

This diff is too big to show here.

pkgs/applications/editors/gobby/default.nix+12−16

This diff is too big to show here.

pkgs/applications/editors/hexcurse/default.nix+13−1

This diff is too big to show here.

pkgs/applications/editors/howl/default.nix+40

This diff is too big to show here.

pkgs/applications/editors/ht/default.nix+2

This diff is too big to show here.

pkgs/applications/editors/ht/gcc7.patch+11

This diff is too big to show here.

pkgs/applications/editors/jetbrains/common.nix+8−6

This diff is too big to show here.

pkgs/applications/editors/jetbrains/default.nix+80−64

This diff is too big to show here.

pkgs/applications/editors/jetbrains/update.pl+1−1

This diff is too big to show here.

pkgs/applications/editors/jucipp/default.nix+4−4

This diff is too big to show here.

pkgs/applications/editors/jupp/default.nix+1−1

This diff is too big to show here.

pkgs/applications/editors/jupyter/default.nix+18

This diff is too big to show here.

pkgs/applications/editors/jupyter/kernel.nix+74

This diff is too big to show here.

pkgs/applications/editors/kakoune/default.nix+5−4

This diff is too big to show here.

pkgs/applications/editors/kdevelop5/kdevelop.nix+13−11

This diff is too big to show here.

pkgs/applications/editors/kdevelop5/kdevplatform.nix−44

This diff is too big to show here.

pkgs/applications/editors/kile/default.nix+5−7

This diff is too big to show here.

pkgs/applications/editors/kodestudio/default.nix+11−11

This diff is too big to show here.

pkgs/applications/editors/leo-editor/default.nix+4−13

This diff is too big to show here.

pkgs/applications/editors/lighttable/default.nix+4−4

This diff is too big to show here.

pkgs/applications/editors/manuskript/default.nix+5−5

This diff is too big to show here.

pkgs/applications/editors/mg/default.nix+2−2

This diff is too big to show here.

pkgs/applications/editors/micro/default.nix+2−2

This diff is too big to show here.

pkgs/applications/editors/moe/default.nix+1−1

This diff is too big to show here.

pkgs/applications/editors/monodevelop/default.nix+5−4

This diff is too big to show here.

pkgs/applications/editors/music/tuxguitar/default.nix+2−2

This diff is too big to show here.

pkgs/applications/editors/nano/default.nix+10−10

This diff is too big to show here.

pkgs/applications/editors/nano/nanorc/default.nix+29

This diff is too big to show here.

pkgs/applications/editors/ne/default.nix+2−2

This diff is too big to show here.

pkgs/applications/editors/nedit/default.nix+1

This diff is too big to show here.

pkgs/applications/editors/neovim/default.nix+11−37

This diff is too big to show here.

pkgs/applications/editors/neovim/neovim-remote.nix+4−4

This diff is too big to show here.

pkgs/applications/editors/neovim/qt.nix+14−9

This diff is too big to show here.

pkgs/applications/editors/neovim/ruby_provider/Gemfile.lock+2−2

This diff is too big to show here.

pkgs/applications/editors/neovim/ruby_provider/gemset.nix+4−4

This diff is too big to show here.

pkgs/applications/editors/neovim/wrapper.nix+36−29

This diff is too big to show here.

pkgs/applications/editors/netbeans/default.nix+1−1

This diff is too big to show here.

pkgs/applications/editors/notepadqq/default.nix+10−7

This diff is too big to show here.

pkgs/applications/editors/nvpy/default.nix+2−2

This diff is too big to show here.

pkgs/applications/editors/okteta/default.nix+34

This diff is too big to show here.

pkgs/applications/editors/quilter/default.nix+52

This diff is too big to show here.

pkgs/applications/editors/rednotebook/default.nix+6−4

This diff is too big to show here.

pkgs/applications/editors/rstudio/clang-location.patch+25

This diff is too big to show here.

pkgs/applications/editors/rstudio/default.nix+2−2

This diff is too big to show here.

pkgs/applications/editors/rstudio/fix-cmake.patch+15

This diff is too big to show here.

pkgs/applications/editors/rstudio/preview.nix+119

This diff is too big to show here.

pkgs/applications/editors/scite/default.nix+4−4

This diff is too big to show here.

pkgs/applications/editors/sigil/default.nix+2−2

This diff is too big to show here.

pkgs/applications/editors/standardnotes/default.nix+48

This diff is too big to show here.

pkgs/applications/editors/sublime/2/default.nix+59

This diff is too big to show here.

pkgs/applications/editors/sublime/3/common.nix+118

This diff is too big to show here.

pkgs/applications/editors/sublime/3/packages.nix+18

This diff is too big to show here.

pkgs/applications/editors/sublime/default.nix−59

This diff is too big to show here.

pkgs/applications/editors/sublime3/default.nix−113

This diff is too big to show here.

pkgs/applications/editors/texmacs/common.nix+68

This diff is too big to show here.

pkgs/applications/editors/texmacs/darwin.nix+59

This diff is too big to show here.

pkgs/applications/editors/texmacs/darwin.patch+29

This diff is too big to show here.

pkgs/applications/editors/texmacs/default.nix+18−73

This diff is too big to show here.

pkgs/applications/editors/texmaker/default.nix+9−6

This diff is too big to show here.

pkgs/applications/editors/texstudio/default.nix+8−7

This diff is too big to show here.

pkgs/applications/editors/textadept/default.nix−1

This diff is too big to show here.

pkgs/applications/editors/thonny/default.nix+51

This diff is too big to show here.

pkgs/applications/editors/tiled/default.nix+4−4

This diff is too big to show here.

pkgs/applications/editors/tweak/default.nix+1−1

This diff is too big to show here.

pkgs/applications/editors/typora/default.nix+19−10

This diff is too big to show here.

pkgs/applications/editors/vanubi/default.nix−29

This diff is too big to show here.

pkgs/applications/editors/vim/common.nix+2−2

This diff is too big to show here.

pkgs/applications/editors/vim/configurable.nix+132−129

This diff is too big to show here.

pkgs/applications/editors/vim/default.nix+7−4

This diff is too big to show here.

pkgs/applications/editors/vim/ft-nix-support.patch+1−70

This diff is too big to show here.

pkgs/applications/editors/vim/macvim.nix+1−1

This diff is too big to show here.

pkgs/applications/editors/vim/qvim.nix+82−98

This diff is too big to show here.

pkgs/applications/editors/vis/default.nix+6−2

This diff is too big to show here.

pkgs/applications/editors/vscode-with-extensions/default.nix−82

This diff is too big to show here.

pkgs/applications/editors/vscode/default.nix+21−15

This diff is too big to show here.

pkgs/applications/editors/vscode/with-extensions.nix+87

This diff is too big to show here.

pkgs/applications/editors/wxhexeditor/default.nix+19−9

This diff is too big to show here.

pkgs/applications/editors/yi/wrapper.nix+2−2

This diff is too big to show here.

pkgs/applications/editors/zed/default.nix−82

This diff is too big to show here.

pkgs/applications/editors/zed/deps.json−6

This diff is too big to show here.

pkgs/applications/editors/zed/node-packages.nix−877

This diff is too big to show here.

pkgs/applications/editors/zed/node.nix−16

This diff is too big to show here.

pkgs/applications/gis/grass/default.nix+14−3

This diff is too big to show here.

pkgs/applications/gis/grass/no_symbolic_links.patch+37

This diff is too big to show here.

pkgs/applications/gis/openorienteering-mapper/default.nix+68

This diff is too big to show here.

pkgs/applications/gis/qgis/default.nix+61−15

This diff is too big to show here.

pkgs/applications/gis/saga/clang_patch.patch+19

This diff is too big to show here.

pkgs/applications/gis/saga/default.nix+19−9

This diff is too big to show here.

pkgs/applications/gis/saga/finite-6.3.0.patch+55

This diff is too big to show here.

pkgs/applications/gis/saga/finite.patch+13

This diff is too big to show here.

pkgs/applications/gis/saga/lts.nix+36

This diff is too big to show here.

pkgs/applications/gis/whitebox-tools/default.nix+24

This diff is too big to show here.

pkgs/applications/graphics/ImageMagick/7.0.nix+13−13

This diff is too big to show here.

pkgs/applications/graphics/ImageMagick/default.nix+15−13

This diff is too big to show here.

pkgs/applications/graphics/PythonMagick/default.nix+12−4

This diff is too big to show here.

pkgs/applications/graphics/ahoviewer/default.nix+24−17

This diff is too big to show here.

pkgs/applications/graphics/animbar/default.nix+40

This diff is too big to show here.

pkgs/applications/graphics/antimony/default.nix+17−11

This diff is too big to show here.

pkgs/applications/graphics/ao/default.nix+3−2

This diff is too big to show here.

pkgs/applications/graphics/avocode/default.nix+104

This diff is too big to show here.

pkgs/applications/graphics/awesomebump/default.nix+1−1

This diff is too big to show here.

pkgs/applications/graphics/batik/default.nix+11−2

This diff is too big to show here.

pkgs/applications/graphics/c3d/default.nix+4−3

This diff is too big to show here.

pkgs/applications/graphics/cinepaint/default.nix+6−6

This diff is too big to show here.

pkgs/applications/graphics/darktable/default.nix+22−13

This diff is too big to show here.

pkgs/applications/graphics/dia/default.nix+15−19

This diff is too big to show here.

pkgs/applications/graphics/digikam/default.nix+8−7

This diff is too big to show here.

pkgs/applications/graphics/displaycal/default.nix+6−4

This diff is too big to show here.

pkgs/applications/graphics/dosage/default.nix+28

This diff is too big to show here.

pkgs/applications/graphics/draftsight/default.nix+25−14

This diff is too big to show here.

pkgs/applications/graphics/drawpile/default.nix+44

This diff is too big to show here.

pkgs/applications/graphics/epeg/default.nix+34

This diff is too big to show here.

pkgs/applications/graphics/exrdisplay/default.nix+7−9

This diff is too big to show here.

pkgs/applications/graphics/exrtools/default.nix+2−2

This diff is too big to show here.

pkgs/applications/graphics/fbida/default.nix+12−9

This diff is too big to show here.

pkgs/applications/graphics/feh/default.nix+9−9

This diff is too big to show here.

pkgs/applications/graphics/fig2dev/default.nix+25

This diff is too big to show here.

pkgs/applications/graphics/freecad/default.nix+19−6

This diff is too big to show here.

pkgs/applications/graphics/freepv/default.nix+2−2

This diff is too big to show here.

pkgs/applications/graphics/fstl/default.nix+35

This diff is too big to show here.

pkgs/applications/graphics/gcolor2/default.nix+5−4

This diff is too big to show here.

pkgs/applications/graphics/gcolor3/default.nix+17−16

This diff is too big to show here.

pkgs/applications/graphics/geeqie/default.nix+13−10

This diff is too big to show here.

pkgs/applications/graphics/geeqie/geeqie-no-changelog.patch+14

This diff is too big to show here.

pkgs/applications/graphics/gimp/2.8.nix−58

This diff is too big to show here.

pkgs/applications/graphics/gimp/default.nix+83

This diff is too big to show here.

pkgs/applications/graphics/gimp/plugins/default.nix+14−58

This diff is too big to show here.

pkgs/applications/graphics/gimp/remove-cc-reference.patch+13

This diff is too big to show here.

pkgs/applications/graphics/gimp/wrapper.nix+4−3

This diff is too big to show here.

pkgs/applications/graphics/giv/default.nix+3−3

This diff is too big to show here.

pkgs/applications/graphics/glabels/default.nix+6−7

This diff is too big to show here.

pkgs/applications/graphics/gnuclad/default.nix+22

This diff is too big to show here.

pkgs/applications/graphics/gocr/default.nix+3−3

This diff is too big to show here.

pkgs/applications/graphics/goxel/default.nix+6−4

This diff is too big to show here.

pkgs/applications/graphics/goxel/disable-imgui_ini.patch+13

This diff is too big to show here.

pkgs/applications/graphics/gqview/default.nix+3−2

This diff is too big to show here.

pkgs/applications/graphics/grafx2/default.nix+1−1

This diff is too big to show here.

pkgs/applications/graphics/graphicsmagick/compat.nix+37

This diff is too big to show here.

pkgs/applications/graphics/graphicsmagick/default.nix+4−5

This diff is too big to show here.

pkgs/applications/graphics/gthumb/default.nix+29−14

This diff is too big to show here.

pkgs/applications/graphics/hugin/default.nix+5−5

This diff is too big to show here.

pkgs/applications/graphics/imagej/default.nix+1−1

This diff is too big to show here.

pkgs/applications/graphics/imgcat/default.nix+33

This diff is too big to show here.

pkgs/applications/graphics/imlibsetroot/default.nix+1−1

This diff is too big to show here.

pkgs/applications/graphics/imv/default.nix+16−9

This diff is too big to show here.

pkgs/applications/graphics/inkscape/default.nix+20−12

This diff is too big to show here.

pkgs/applications/graphics/jbrout/default.nix+1

This diff is too big to show here.

pkgs/applications/graphics/jpegoptim/default.nix+3−3

This diff is too big to show here.

pkgs/applications/graphics/k3d/default.nix+15−15

This diff is too big to show here.

pkgs/applications/graphics/kgraphviewer/default.nix+3−3

This diff is too big to show here.

pkgs/applications/graphics/kipi-plugins/default.nix+3−3

This diff is too big to show here.

pkgs/applications/graphics/krita/default.nix+11−9

This diff is too big to show here.

pkgs/applications/graphics/krop/default.nix+40

This diff is too big to show here.

pkgs/applications/graphics/ktikz/default.nix+2−3

This diff is too big to show here.

pkgs/applications/graphics/leocad/default.nix+3−3

This diff is too big to show here.

pkgs/applications/graphics/meshlab/default.nix+13−9

This diff is too big to show here.

pkgs/applications/graphics/meshlab/fix-2016.02.patch−88

This diff is too big to show here.

pkgs/applications/graphics/meshlab/fix-20180627-beta.patch+25

This diff is too big to show here.

pkgs/applications/graphics/mozjpeg/default.nix+8−10

This diff is too big to show here.

pkgs/applications/graphics/mypaint/default.nix+9−4

This diff is too big to show here.

pkgs/applications/graphics/nomacs/default.nix+4−7

This diff is too big to show here.

pkgs/applications/graphics/nomacs/fix-appdata-install.patch−13

This diff is too big to show here.

pkgs/applications/graphics/ocrad/default.nix+1−1

This diff is too big to show here.

pkgs/applications/graphics/openimageio/default.nix+4−4

This diff is too big to show here.

pkgs/applications/graphics/openscad/default.nix+19−9

This diff is too big to show here.

pkgs/applications/graphics/panotools/default.nix+1−1

This diff is too big to show here.

pkgs/applications/graphics/paraview/default.nix+25−12

This diff is too big to show here.

pkgs/applications/graphics/pbrt/default.nix+8−3

This diff is too big to show here.

pkgs/applications/graphics/pbrt/openexr-cmake-3.12.patch+26

This diff is too big to show here.

pkgs/applications/graphics/pencil/default.nix+15−15

This diff is too big to show here.

pkgs/applications/graphics/photivo/default.nix+2−2

This diff is too big to show here.

pkgs/applications/graphics/photoflow/default.nix+56

This diff is too big to show here.

pkgs/applications/graphics/photoqt/default.nix−1

This diff is too big to show here.

pkgs/applications/graphics/phototonic/default.nix+3−5

This diff is too big to show here.

pkgs/applications/graphics/pinta/default.nix+1−1

This diff is too big to show here.

pkgs/applications/graphics/pqiv/default.nix+2−2

This diff is too big to show here.

pkgs/applications/graphics/processing/default.nix−39

This diff is too big to show here.

pkgs/applications/graphics/processing/use-nixpkgs-jre.patch−88

This diff is too big to show here.

pkgs/applications/graphics/processing3/default.nix+63

This diff is too big to show here.

pkgs/applications/graphics/qcomicbook/default.nix+43

This diff is too big to show here.

pkgs/applications/graphics/qiv/default.nix+4−3

This diff is too big to show here.

pkgs/applications/graphics/qscreenshot/default.nix+3−2

This diff is too big to show here.

pkgs/applications/graphics/qtpfsgui/default.nix+1−1

This diff is too big to show here.

pkgs/applications/graphics/rapcad/default.nix+3−2

This diff is too big to show here.

pkgs/applications/graphics/rapid-photo-downloader/default.nix+71

This diff is too big to show here.

pkgs/applications/graphics/rawtherapee/default.nix+5−5

This diff is too big to show here.

pkgs/applications/graphics/renderdoc/custom_swig.patch−32

This diff is too big to show here.

pkgs/applications/graphics/renderdoc/default.nix+25−37

This diff is too big to show here.

pkgs/applications/graphics/sane/backends/brscan4/default.nix+4−4

This diff is too big to show here.

pkgs/applications/graphics/sane/backends/generic.nix+1−1

This diff is too big to show here.

pkgs/applications/graphics/sane/xsane.nix+4−4

This diff is too big to show here.

pkgs/applications/graphics/scantailor/advanced.nix+26

This diff is too big to show here.

pkgs/applications/graphics/scantailor/default.nix+1−1

This diff is too big to show here.

pkgs/applications/graphics/screencloud/default.nix+1−1

This diff is too big to show here.

pkgs/applications/graphics/seg3d/default.nix+3−3

This diff is too big to show here.

pkgs/applications/graphics/shotwell/default.nix+21−14

This diff is too big to show here.

pkgs/applications/graphics/shutter/default.nix+14−9

This diff is too big to show here.

pkgs/applications/graphics/smartdeblur/default.nix+1−1

This diff is too big to show here.

pkgs/applications/graphics/solvespace/default.nix+6−6

This diff is too big to show here.

pkgs/applications/graphics/sxiv/default.nix+4−4

This diff is too big to show here.

pkgs/applications/graphics/synfigstudio/default.nix+2−2

This diff is too big to show here.

pkgs/applications/graphics/tesseract/default.nix+34−30

This diff is too big to show here.

pkgs/applications/graphics/ufraw/default.nix+21−5

This diff is too big to show here.

pkgs/applications/graphics/unigine-valley/default.nix+3−3

This diff is too big to show here.

pkgs/applications/graphics/viewnior/default.nix+3−3

This diff is too big to show here.

pkgs/applications/graphics/vimiv/default.nix+2−2

This diff is too big to show here.

pkgs/applications/graphics/write_stylus/default.nix+65

This diff is too big to show here.

pkgs/applications/graphics/xara/default.nix+1−1

This diff is too big to show here.

pkgs/applications/graphics/xfig/builder.sh−28

This diff is too big to show here.

pkgs/applications/graphics/xfig/default.nix+27−32

This diff is too big to show here.

pkgs/applications/graphics/yacreader/default.nix+25

This diff is too big to show here.

pkgs/applications/graphics/yed/default.nix+3−3

This diff is too big to show here.

pkgs/applications/graphics/zgv/default.nix+1−1

This diff is too big to show here.

pkgs/applications/inferno/default.nix+1−1

This diff is too big to show here.

pkgs/applications/kde/akonadi-import-wizard.nix+20

This diff is too big to show here.

pkgs/applications/kde/akonadi-mime.nix+2−2

This diff is too big to show here.

pkgs/applications/kde/akonadi/akonadi-paths.patch+60−61

This diff is too big to show here.

pkgs/applications/kde/akonadi/default.nix+2−2

This diff is too big to show here.

pkgs/applications/kde/ark/default.nix+1−1

This diff is too big to show here.

pkgs/applications/kde/default.nix+16−4

This diff is too big to show here.

pkgs/applications/kde/dolphin.nix+6−2

This diff is too big to show here.

pkgs/applications/kde/dragon.nix+25

This diff is too big to show here.

pkgs/applications/kde/eventviews.nix+4−2

This diff is too big to show here.

pkgs/applications/kde/fetch.sh+1−1

This diff is too big to show here.

pkgs/applications/kde/grantleetheme/default.nix+3−3

This diff is too big to show here.

pkgs/applications/kde/grantleetheme/grantlee-merge-theme-dirs.patch+83−81

This diff is too big to show here.

pkgs/applications/kde/k3b.nix+14−8

This diff is too big to show here.

pkgs/applications/kde/kalarm.nix+37

This diff is too big to show here.

pkgs/applications/kde/kalarmcal.nix+2−2

This diff is too big to show here.

pkgs/applications/kde/kcalutils.nix+2−2

This diff is too big to show here.

pkgs/applications/kde/kdebugsettings.nix+20

This diff is too big to show here.

pkgs/applications/kde/kdenlive-cmake-concurrent-module.patch−12

This diff is too big to show here.

pkgs/applications/kde/kdenlive.nix+2−10

This diff is too big to show here.

pkgs/applications/kde/kdepim-addons.nix+25

This diff is too big to show here.

pkgs/applications/kde/kdepim-runtime.nix+2−2

This diff is too big to show here.

pkgs/applications/kde/kio-extras.nix+2−2

This diff is too big to show here.

pkgs/applications/kde/kitinerary.nix+19

This diff is too big to show here.

pkgs/applications/kde/kleopatra.nix+2−2

This diff is too big to show here.

pkgs/applications/kde/kmail-account-wizard.nix+2−2

This diff is too big to show here.

pkgs/applications/kde/kmailtransport.nix+4−2

This diff is too big to show here.

pkgs/applications/kde/konqueror.nix+20

This diff is too big to show here.

pkgs/applications/kde/konquest.nix+18

This diff is too big to show here.

pkgs/applications/kde/konsole.nix+2−2

This diff is too big to show here.

pkgs/applications/kde/kpimtextedit.nix+2−2

This diff is too big to show here.

pkgs/applications/kde/kpkpass.nix+15

This diff is too big to show here.

pkgs/applications/kde/krfb.nix+2−2

This diff is too big to show here.

pkgs/applications/kde/ksystemlog.nix+17

This diff is too big to show here.

pkgs/applications/kde/libkdegames.nix+26

This diff is too big to show here.

pkgs/applications/kde/libkgapi.nix+3−2

This diff is too big to show here.

pkgs/applications/kde/libkomparediff2.nix+1−1

This diff is too big to show here.

pkgs/applications/kde/marble.nix+6−2

This diff is too big to show here.

pkgs/applications/kde/mbox-importer.nix−3

This diff is too big to show here.

pkgs/applications/kde/messagelib.nix+2−2

This diff is too big to show here.

pkgs/applications/kde/okteta.nix−21

This diff is too big to show here.

pkgs/applications/kde/okular.nix+16−14

This diff is too big to show here.

pkgs/applications/kde/pim-data-exporter.nix+1−1

This diff is too big to show here.

pkgs/applications/kde/pimcommon.nix+1−1

This diff is too big to show here.

pkgs/applications/kde/spectacle.nix+2−1

This diff is too big to show here.

pkgs/applications/kde/srcs.nix+876−852

This diff is too big to show here.

pkgs/applications/misc/1password/default.nix+44

This diff is too big to show here.

pkgs/applications/misc/acbuild/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/adobe-reader/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/airspy/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/airtame/default.nix+22−42

This diff is too big to show here.

pkgs/applications/misc/alacritty/default.nix+59−17

This diff is too big to show here.

pkgs/applications/misc/albert/default.nix+7−4

This diff is too big to show here.

pkgs/applications/misc/antfs-cli/default.nix+5−4

This diff is too big to show here.

pkgs/applications/misc/ape/apeclex.nix+8

This diff is too big to show here.

pkgs/applications/misc/ape/clex.nix+25

This diff is too big to show here.

pkgs/applications/misc/ape/default.nix+45

This diff is too big to show here.

pkgs/applications/misc/apvlv/default.nix+9−1

This diff is too big to show here.

pkgs/applications/misc/archiver/default.nix+28

This diff is too big to show here.

pkgs/applications/misc/archiver/deps.nix+56

This diff is too big to show here.

pkgs/applications/misc/artha/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/audio/soxr/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/audio/wavesurfer/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/avrdudess/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/barrier/default.nix+42

This diff is too big to show here.

pkgs/applications/misc/bashSnippets/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/bb/default.nix+7−3

This diff is too big to show here.

pkgs/applications/misc/bitcoinarmory/default.nix−1

This diff is too big to show here.

pkgs/applications/misc/bleachbit/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/blender/default.nix+15−5

This diff is too big to show here.

pkgs/applications/misc/buku/default.nix+16−8

This diff is too big to show here.

pkgs/applications/misc/calcurse/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/calibre/default.nix+20−19

This diff is too big to show here.

pkgs/applications/misc/calibre/disable_plugins.patch+17

This diff is too big to show here.

pkgs/applications/misc/calibre/no_updates_dialog.patch+15

This diff is too big to show here.

pkgs/applications/misc/cataract/build.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/cataract/default.nix+1−10

This diff is too big to show here.

pkgs/applications/misc/cataract/unstable.nix+1−10

This diff is too big to show here.

pkgs/applications/misc/cbatticon/default.nix+6−2

This diff is too big to show here.

pkgs/applications/misc/cgminer/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/cheat/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/cherrytree/default.nix+4−4

This diff is too big to show here.

pkgs/applications/misc/chirp/default.nix+5−5

This diff is too big to show here.

pkgs/applications/misc/cli-visualizer/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/clipit/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/clipmenu/default.nix+33

This diff is too big to show here.

pkgs/applications/misc/cointop/default.nix+31

This diff is too big to show here.

pkgs/applications/misc/cointop/deps.nix+3

This diff is too big to show here.

pkgs/applications/misc/confclerk/default.nix+4−4

This diff is too big to show here.

pkgs/applications/misc/cool-retro-term/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/copyq/default.nix+5−4

This diff is too big to show here.

pkgs/applications/misc/coursera-dl/default.nix+41

This diff is too big to show here.

pkgs/applications/misc/cpp-ethereum/default.nix+5−4

This diff is too big to show here.

pkgs/applications/misc/ctodo/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/cura/default.nix+21−6

This diff is too big to show here.

pkgs/applications/misc/cura/lulzbot.nix+5−5

This diff is too big to show here.

pkgs/applications/misc/curabydagoma/default.nix+76

This diff is too big to show here.

pkgs/applications/misc/curaengine/default.nix+14−6

This diff is too big to show here.

pkgs/applications/misc/dbeaver/default.nix+4−4

This diff is too big to show here.

pkgs/applications/misc/dbvisualizer/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/deco/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/deepin-terminal/default.nix−46

This diff is too big to show here.

pkgs/applications/misc/devilspie2/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/dfilemanager/default.nix+1−2

This diff is too big to show here.

pkgs/applications/misc/diffpdf/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/digitalbitbox/default.nix+145

This diff is too big to show here.

pkgs/applications/misc/djvulibre/default.nix+2−4

This diff is too big to show here.

pkgs/applications/misc/dmenu/default.nix+5−5

This diff is too big to show here.

pkgs/applications/misc/dmrconfig/default.nix+39

This diff is too big to show here.

pkgs/applications/misc/doing/Gemfile+2

This diff is too big to show here.

pkgs/applications/misc/doing/Gemfile.lock+25

This diff is too big to show here.

pkgs/applications/misc/doing/default.nix+25

This diff is too big to show here.

pkgs/applications/misc/doing/gemset.nix+60

This diff is too big to show here.

pkgs/applications/misc/doomseeker/default.nix+13−10

This diff is too big to show here.

pkgs/applications/misc/doomseeker/fix_paths.patch+40

This diff is too big to show here.

pkgs/applications/misc/doomseeker/qt_build_fix.patch+47

This diff is too big to show here.

pkgs/applications/misc/dozenal/default.nix+61

This diff is too big to show here.

pkgs/applications/misc/dozenal/lua-header.patch+16

This diff is too big to show here.

pkgs/applications/misc/dunst/default.nix+14−5

This diff is too big to show here.

pkgs/applications/misc/eaglemode/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/electron-cash/default.nix+14−9

This diff is too big to show here.

pkgs/applications/misc/electrum-ltc/default.nix−55

This diff is too big to show here.

pkgs/applications/misc/electrum/dash.nix

This diff is too big to show here.

pkgs/applications/misc/electrum/default.nix+22−17

This diff is too big to show here.

pkgs/applications/misc/electrum/ltc.nix+55

This diff is too big to show here.

pkgs/applications/misc/ephemeralpg/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/et/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/eureka-editor/default.nix+39

This diff is too big to show here.

pkgs/applications/misc/evilvte/default.nix+3

This diff is too big to show here.

pkgs/applications/misc/evtest/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/exercism/default.nix+5−4

This diff is too big to show here.

pkgs/applications/misc/exercism/deps.nix+201

This diff is too big to show here.

pkgs/applications/misc/extract_url/default.nix+42

This diff is too big to show here.

pkgs/applications/misc/far2l/add-nix-syntax-highlighting.patch−158

This diff is too big to show here.

pkgs/applications/misc/far2l/default.nix+15−7

This diff is too big to show here.

pkgs/applications/misc/fbreader/default.nix+50−20

This diff is too big to show here.

pkgs/applications/misc/fbreader/typecheck.patch+11

This diff is too big to show here.

pkgs/applications/misc/fetchmail/default.nix+2−1

This diff is too big to show here.

pkgs/applications/misc/finalterm/default.nix−65

This diff is too big to show here.

pkgs/applications/misc/fllog/default.nix+34

This diff is too big to show here.

pkgs/applications/misc/flmsg/default.nix+34

This diff is too big to show here.

pkgs/applications/misc/flrig/default.nix+34

This diff is too big to show here.

pkgs/applications/misc/flwrap/default.nix+34

This diff is too big to show here.

pkgs/applications/misc/font-manager/default.nix+15−14

This diff is too big to show here.

pkgs/applications/misc/gImageReader/default.nix+71

This diff is too big to show here.

pkgs/applications/misc/gammu/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/gcal/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/gcalcli/default.nix+17−22

This diff is too big to show here.

pkgs/applications/misc/get_iplayer/default.nix+4−4

This diff is too big to show here.

pkgs/applications/misc/girara/default.nix+7−24

This diff is too big to show here.

pkgs/applications/misc/gkrellm/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/gksu/default.nix+5−5

This diff is too big to show here.

pkgs/applications/misc/glava/default.nix+81

This diff is too big to show here.

pkgs/applications/misc/gmtp/default.nix+8−4

This diff is too big to show here.

pkgs/applications/misc/gnome-usage/default.nix+37

This diff is too big to show here.

pkgs/applications/misc/gnss-sdr/default.nix+2−1

This diff is too big to show here.

pkgs/applications/misc/gnuradio-nacl/default.nix−39

This diff is too big to show here.

pkgs/applications/misc/gnuradio-rds/default.nix−38

This diff is too big to show here.

pkgs/applications/misc/gnuradio/ais.nix

This diff is too big to show here.

pkgs/applications/misc/gnuradio/default.nix+7−5

This diff is too big to show here.

pkgs/applications/misc/gnuradio/gsm.nix

This diff is too big to show here.

pkgs/applications/misc/gnuradio/limesdr.nix+38

This diff is too big to show here.

pkgs/applications/misc/gnuradio/nacl.nix+39

This diff is too big to show here.

pkgs/applications/misc/gnuradio/osmosdr.nix

This diff is too big to show here.

pkgs/applications/misc/gnuradio/rds.nix+38

This diff is too big to show here.

pkgs/applications/misc/go-jira/default.nix+22

This diff is too big to show here.

pkgs/applications/misc/golden-cheetah/default.nix+19−5

This diff is too big to show here.

pkgs/applications/misc/goldendict/default.nix+11−9

This diff is too big to show here.

pkgs/applications/misc/gollum/Gemfile.lock+27−19

This diff is too big to show here.

pkgs/applications/misc/gollum/default.nix+1

This diff is too big to show here.

pkgs/applications/misc/gollum/gemset.nix+64−29

This diff is too big to show here.

pkgs/applications/misc/googleearth/default.nix+36−18

This diff is too big to show here.

pkgs/applications/misc/googler/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/gosmore/default.nix+3

This diff is too big to show here.

pkgs/applications/misc/gosmore/pointer_int_comparison.patch+11

This diff is too big to show here.

pkgs/applications/misc/gpa/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/gphoto2/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/gphoto2/gphotofs.nix+5−5

This diff is too big to show here.

pkgs/applications/misc/gpsprune/default.nix+8−13

This diff is too big to show here.

pkgs/applications/misc/gpx-viewer/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/gpx/default.nix+23

This diff is too big to show here.

pkgs/applications/misc/gpxsee/default.nix+12−7

This diff is too big to show here.

pkgs/applications/misc/gqrx/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/gramps/default.nix+17−18

This diff is too big to show here.

pkgs/applications/misc/gremlin-console/default.nix+29

This diff is too big to show here.

pkgs/applications/misc/guake/default.nix+25−57

This diff is too big to show here.

pkgs/applications/misc/gummi/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/gutenberg/default.nix+35

This diff is too big to show here.

pkgs/applications/misc/gv/default.nix+14−3

This diff is too big to show here.

pkgs/applications/misc/gxmessage/default.nix+3−2

This diff is too big to show here.

pkgs/applications/misc/gxneur/default.nix+11−15

This diff is too big to show here.

pkgs/applications/misc/hamster-time-tracker/default.nix+4−4

This diff is too big to show here.

pkgs/applications/misc/haxor-news/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/hdate/default.nix+16

This diff is too big to show here.

pkgs/applications/misc/hello-unfree/default.nix+23

This diff is too big to show here.

pkgs/applications/misc/hello/default.nix+6−5

This diff is too big to show here.

pkgs/applications/misc/houdini/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/houdini/runtime.nix+7−7

This diff is too big to show here.

pkgs/applications/misc/hovercraft/default.nix+35

This diff is too big to show here.

pkgs/applications/misc/hr/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/hstr/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/hubstaff/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/hugo/default.nix+8−2

This diff is too big to show here.

pkgs/applications/misc/hugo/deps.nix+382−95

This diff is too big to show here.

pkgs/applications/misc/hyper/default.nix+6−7

This diff is too big to show here.

pkgs/applications/misc/icesl/default.nix+4−4

This diff is too big to show here.

pkgs/applications/misc/img2pdf/default.nix+27

This diff is too big to show here.

pkgs/applications/misc/ipmicfg/default.nix+6−5

This diff is too big to show here.

pkgs/applications/misc/ipmiview/default.nix+4−6

This diff is too big to show here.

pkgs/applications/misc/jekyll/basic/Gemfile.lock+19−21

This diff is too big to show here.

pkgs/applications/misc/jekyll/basic/gemset.nix+38−38

This diff is too big to show here.

pkgs/applications/misc/jekyll/default.nix+2

This diff is too big to show here.

pkgs/applications/misc/jekyll/full/Gemfile+1−1

This diff is too big to show here.

pkgs/applications/misc/jekyll/full/Gemfile.lock+27−32

This diff is too big to show here.

pkgs/applications/misc/jekyll/full/gemset.nix+54−63

This diff is too big to show here.

pkgs/applications/misc/jekyll/update.sh+15

This diff is too big to show here.

pkgs/applications/misc/jgmenu/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/jigdo/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/josm/default.nix+5−5

This diff is too big to show here.

pkgs/applications/misc/jrnl/default.nix+3−5

This diff is too big to show here.

pkgs/applications/misc/k2pdfopt/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/kdbplus/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/kdeconnect/default.nix+5−4

This diff is too big to show here.

pkgs/applications/misc/keepass-plugins/keeagent/default.nix+4−4

This diff is too big to show here.

pkgs/applications/misc/keepass-plugins/keepassrpc/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/keepass/default.nix+25−8

This diff is too big to show here.

pkgs/applications/misc/keepass/keepass-plugins-load.patch+1

This diff is too big to show here.

pkgs/applications/misc/keepass/keepass-plugins.patch+13

This diff is too big to show here.

pkgs/applications/misc/keepassx/cmake.patch−18

This diff is too big to show here.

pkgs/applications/misc/keepassx/community.nix+62−7

This diff is too big to show here.

pkgs/applications/misc/keepassx/darwin.patch+14−14

This diff is too big to show here.

pkgs/applications/misc/keepassx/qt511.patch+15

This diff is too big to show here.

pkgs/applications/misc/khal/default.nix+15−10

This diff is too big to show here.

pkgs/applications/misc/khard/default.nix+24−4

This diff is too big to show here.

pkgs/applications/misc/kitty/default.nix+31−10

This diff is too big to show here.

pkgs/applications/misc/kitty/fix-paths.patch+27

This diff is too big to show here.

pkgs/applications/misc/kiwix/default.nix+6−3

This diff is too big to show here.

pkgs/applications/misc/krename/default.nix+7−7

This diff is too big to show here.

pkgs/applications/misc/krusader/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/kupfer/default.nix+2−4

This diff is too big to show here.

pkgs/applications/misc/latte-dock/default.nix+16−13

This diff is too big to show here.

pkgs/applications/misc/librecad/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/lilyterm/default.nix+8−9

This diff is too big to show here.

pkgs/applications/misc/limesuite/default.nix+51

This diff is too big to show here.

pkgs/applications/misc/llpp/default.nix+5−7

This diff is too big to show here.

pkgs/applications/misc/lxterminal/default.nix+8−7

This diff is too big to show here.

pkgs/applications/misc/lyx/default.nix+11−4

This diff is too big to show here.

pkgs/applications/misc/madonctl/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/makeself/Use-rm-from-PATH.patch+43

This diff is too big to show here.

pkgs/applications/misc/makeself/default.nix+6−3

This diff is too big to show here.

pkgs/applications/misc/mako/default.nix+25

This diff is too big to show here.

pkgs/applications/misc/masterpdfeditor/default.nix+53−52

This diff is too big to show here.

pkgs/applications/misc/mdp/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/mediainfo-gui/default.nix+4−4

This diff is too big to show here.

pkgs/applications/misc/mediainfo/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/memo/default.nix+22−8

This diff is too big to show here.

pkgs/applications/misc/menumaker/default.nix+21

This diff is too big to show here.

pkgs/applications/misc/merkaartor/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/minergate-cli/default.nix+36

This diff is too big to show here.

pkgs/applications/misc/minergate/default.nix+36

This diff is too big to show here.

pkgs/applications/misc/mlterm/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/moonlight-embedded/default.nix+10−9

This diff is too big to show here.

pkgs/applications/misc/mop/default.nix+4−3

This diff is too big to show here.

pkgs/applications/misc/mucommander/default.nix+84

This diff is too big to show here.

pkgs/applications/misc/multibootusb/default.nix+59

This diff is too big to show here.

pkgs/applications/misc/multimon-ng/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/mupdf/darwin.patch+27−32

This diff is too big to show here.

pkgs/applications/misc/mupdf/default.nix+14−23

This diff is too big to show here.

pkgs/applications/misc/mupdf/default.upstream+1−1

This diff is too big to show here.

pkgs/applications/misc/mupdf/mupdf-1.12-shared_libs-1.patch−41

This diff is too big to show here.

pkgs/applications/misc/mupdf/mupdf-1.14-shared_libs.patch+39

This diff is too big to show here.

pkgs/applications/misc/mwic/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/mysql-workbench/default.nix+68−91

This diff is too big to show here.

pkgs/applications/misc/mysql-workbench/fix-gdal-includes.patch+47

This diff is too big to show here.

pkgs/applications/misc/mysql-workbench/hardcode-paths.patch+187

This diff is too big to show here.

pkgs/applications/misc/navipowm/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/navit/CMakeLists.txt.patch+13

This diff is too big to show here.

pkgs/applications/misc/navit/default.nix+77−17

This diff is too big to show here.

pkgs/applications/misc/neap/default.nix+44

This diff is too big to show here.

pkgs/applications/misc/netsurf/buildsystem/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/netsurf/libcss/default.nix+2

This diff is too big to show here.

pkgs/applications/misc/nix-tour/default.nix+4−5

This diff is too big to show here.

pkgs/applications/misc/nixnote2/default.nix+9−2

This diff is too big to show here.

pkgs/applications/misc/nnn/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/notejot/default.nix+48

This diff is too big to show here.

pkgs/applications/misc/notify-osd-customizable/default.nix+47

This diff is too big to show here.

pkgs/applications/misc/notify-osd/default.nix+4−4

This diff is too big to show here.

pkgs/applications/misc/nrsc5/default.nix+5−3

This diff is too big to show here.

pkgs/applications/misc/nut/default.nix+4−3

This diff is too big to show here.

pkgs/applications/misc/ocropus/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/octoprint/default.nix+42−17

This diff is too big to show here.

pkgs/applications/misc/octoprint/plugins.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/ola/default.nix+6−3

This diff is too big to show here.

pkgs/applications/misc/omegat.nix+40

This diff is too big to show here.

pkgs/applications/misc/onboard/default.nix+9−8

This diff is too big to show here.

pkgs/applications/misc/oneko/default.nix+4−5

This diff is too big to show here.

pkgs/applications/misc/open-pdf-presenter/default.nix−22

This diff is too big to show here.

pkgs/applications/misc/openbrf/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/opencpn/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/opentx/default.nix+61

This diff is too big to show here.

pkgs/applications/misc/orca/default.nix+21−15

This diff is too big to show here.

pkgs/applications/misc/orpie/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/osmctools/default.nix+1

This diff is too big to show here.

pkgs/applications/misc/osmium-tool/default.nix+23

This diff is too big to show here.

pkgs/applications/misc/overmind/default.nix+27

This diff is too big to show here.

pkgs/applications/misc/pbpst/default.nix+49

This diff is too big to show here.

pkgs/applications/misc/pcmanfm/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/pcmanx-gtk2/default.nix+13−7

This diff is too big to show here.

pkgs/applications/misc/pdf-quench/default.nix+37

This diff is too big to show here.

pkgs/applications/misc/pdfdiff/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/pdfmod/default.nix+5−4

This diff is too big to show here.

pkgs/applications/misc/pdfpc/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/pdfshuffler/default.nix+5−4

This diff is too big to show here.

pkgs/applications/misc/perkeep/default.nix+13−53

This diff is too big to show here.

pkgs/applications/misc/pgadmin/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/pgmanage/default.nix+15−6

This diff is too big to show here.

pkgs/applications/misc/pinfo/default.nix−1

This diff is too big to show here.

pkgs/applications/misc/plank/default.nix+48

This diff is too big to show here.

pkgs/applications/misc/plasma-applet-volumewin7mixer/cmake.patch+20

This diff is too big to show here.

pkgs/applications/misc/plasma-applet-volumewin7mixer/default.nix+26

This diff is too big to show here.

pkgs/applications/misc/playonlinux/default.nix+5−7

This diff is too big to show here.

pkgs/applications/misc/plover/default.nix+40−19

This diff is too big to show here.

pkgs/applications/misc/polar-bookshelf/default.nix+87

This diff is too big to show here.

pkgs/applications/misc/polybar/default.nix+29−9

This diff is too big to show here.

pkgs/applications/misc/posterazor/default.nix+4−3

This diff is too big to show here.

pkgs/applications/misc/projectlibre/default.nix+44

This diff is too big to show here.

pkgs/applications/misc/pstree/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/pt/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/ptask/default.nix+3−2

This diff is too big to show here.

pkgs/applications/misc/ptask/json_c_is_error.patch+13

This diff is too big to show here.

pkgs/applications/misc/pwsafe/default.nix+23−41

This diff is too big to show here.

pkgs/applications/misc/pytrainer/default.nix+17−8

This diff is too big to show here.

pkgs/applications/misc/pytrainer/fix-test-tz.patch+24−12

This diff is too big to show here.

pkgs/applications/misc/qlcplus/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/qmapshack/default.nix+4−4

This diff is too big to show here.

pkgs/applications/misc/qpdfview/default.nix+14−10

This diff is too big to show here.

pkgs/applications/misc/qradiolink/default.nix+59

This diff is too big to show here.

pkgs/applications/misc/qsstv/default.nix+54

This diff is too big to show here.

pkgs/applications/misc/qsyncthingtray/default.nix+2−3

This diff is too big to show here.

pkgs/applications/misc/qtbitcointrader/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/ranger/default.nix+14−9

This diff is too big to show here.

pkgs/applications/misc/redis-desktop-manager/default.nix+8−12

This diff is too big to show here.

pkgs/applications/misc/redshift/default.nix+37−13

This diff is too big to show here.

pkgs/applications/misc/regextester/default.nix+58

This diff is too big to show here.

pkgs/applications/misc/rescuetime/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/robo3t/default.nix+4−3

This diff is too big to show here.

pkgs/applications/misc/rofi/config.patch+54

This diff is too big to show here.

pkgs/applications/misc/rofi/default.nix+15−7

This diff is too big to show here.

pkgs/applications/misc/rofi/wrapper.nix+22

This diff is too big to show here.

pkgs/applications/misc/roxterm/default.nix+9−9

This diff is too big to show here.

pkgs/applications/misc/rsibreak/default.nix+28

This diff is too big to show here.

pkgs/applications/misc/rtl-sdr/default.nix+11−5

This diff is too big to show here.

pkgs/applications/misc/rtl_433/default.nix+26

This diff is too big to show here.

pkgs/applications/misc/rtv/default.nix+7−14

This diff is too big to show here.

pkgs/applications/misc/rxvt_unicode/default.nix+1

This diff is too big to show here.

pkgs/applications/misc/rxvt_unicode/wrapper.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/safeeyes/default.nix+71

This diff is too big to show here.

pkgs/applications/misc/sakura/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/sbagen/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/sc-im/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/sdcv/default.nix+1−2

This diff is too big to show here.

pkgs/applications/misc/sent/default.nix+6−2

This diff is too big to show here.

pkgs/applications/misc/sequeler/default.nix+45

This diff is too big to show here.

pkgs/applications/misc/sigal/default.nix+6−4

This diff is too big to show here.

pkgs/applications/misc/simplenote/default.nix+9−8

This diff is too big to show here.

pkgs/applications/misc/slade/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/slade/git.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/sleepyhead/default.nix+42

This diff is too big to show here.

pkgs/applications/misc/slic3r-prusa3d/default.nix−98

This diff is too big to show here.

pkgs/applications/misc/slic3r/default.nix+1

This diff is too big to show here.

pkgs/applications/misc/slic3r/prusa3d.nix+128

This diff is too big to show here.

pkgs/applications/misc/slstatus/default.nix+30

This diff is too big to show here.

pkgs/applications/misc/soapyairspy/default.nix+30

This diff is too big to show here.

pkgs/applications/misc/soapybladerf/default.nix+31

This diff is too big to show here.

pkgs/applications/misc/soapyhackrf/default.nix+30

This diff is too big to show here.

pkgs/applications/misc/soapyremote/default.nix+28

This diff is too big to show here.

pkgs/applications/misc/soapysdr/default.nix+50

This diff is too big to show here.

pkgs/applications/misc/soapyuhd/default.nix+34

This diff is too big to show here.

pkgs/applications/misc/solaar/default.nix+11−9

This diff is too big to show here.

pkgs/applications/misc/spacefm/default.nix+12−8

This diff is too big to show here.

pkgs/applications/misc/ssocr/default.nix+24

This diff is too big to show here.

pkgs/applications/misc/st/default.nix+10−11

This diff is too big to show here.

pkgs/applications/misc/st/st-fix-deletekey.patch−15

This diff is too big to show here.

pkgs/applications/misc/stag/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/stog/default.nix+9−8

This diff is too big to show here.

pkgs/applications/misc/stupidterm/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/subsurface/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/sweethome3d/default.nix+4−4

This diff is too big to show here.

pkgs/applications/misc/sweethome3d/editors.nix+5−5

This diff is too big to show here.

pkgs/applications/misc/synapse/default.nix+5−5

This diff is too big to show here.

pkgs/applications/misc/synergy/default.nix+32−14

This diff is too big to show here.

pkgs/applications/misc/synergy/respect_macos_arch.patch+61

This diff is too big to show here.

pkgs/applications/misc/synergy/update_gtest_gmock.patch+158

This diff is too big to show here.

pkgs/applications/misc/tabula/default.nix+39

This diff is too big to show here.

pkgs/applications/misc/taskell/default.nix+59

This diff is too big to show here.

pkgs/applications/misc/taskjuggler/2.x/default.nix+6−6

This diff is too big to show here.

pkgs/applications/misc/taskjuggler/Gemfile.lock+7−7

This diff is too big to show here.

pkgs/applications/misc/taskjuggler/default.nix+9−4

This diff is too big to show here.

pkgs/applications/misc/taskjuggler/gemset.nix+34−26

This diff is too big to show here.

pkgs/applications/misc/tasknc/default.nix+4−3

This diff is too big to show here.

pkgs/applications/misc/tasksh/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/taskwarrior/default.nix+4−4

This diff is too big to show here.

pkgs/applications/misc/termdown/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/terminal-notifier/default.nix+3−1

This diff is too big to show here.

pkgs/applications/misc/terminator/default.nix+6−10

This diff is too big to show here.

pkgs/applications/misc/terminus/default.nix+43

This diff is too big to show here.

pkgs/applications/misc/termite/add_errno_header.patch+24

This diff is too big to show here.

pkgs/applications/misc/termite/default.nix+32−44

This diff is too big to show here.

pkgs/applications/misc/termite/remove_ldflags_macos.patch+25

This diff is too big to show here.

pkgs/applications/misc/termite/wrapper.nix+15

This diff is too big to show here.

pkgs/applications/misc/teseq/default.nix+22

This diff is too big to show here.

pkgs/applications/misc/tilda/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/tilix/default.nix+12−6

This diff is too big to show here.

pkgs/applications/misc/timewarrior/default.nix+4−4

This diff is too big to show here.

pkgs/applications/misc/tint2/default.nix+9−11

This diff is too big to show here.

pkgs/applications/misc/tnef/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/todiff/default.nix+25

This diff is too big to show here.

pkgs/applications/misc/todolist/default.nix+22

This diff is too big to show here.

pkgs/applications/misc/toggldesktop/TogglDesktop.pro+19

This diff is too big to show here.

pkgs/applications/misc/toggldesktop/default.nix+148

This diff is too big to show here.

pkgs/applications/misc/toggldesktop/libtoggl.pro+20

This diff is too big to show here.

pkgs/applications/misc/toot/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/tootle/default.nix+38

This diff is too big to show here.

pkgs/applications/misc/tqsl/default.nix+1−8

This diff is too big to show here.

pkgs/applications/misc/translate-shell/default.nix+18−81

This diff is too big to show here.

pkgs/applications/misc/truecrypt/default.nix−98

This diff is too big to show here.

pkgs/applications/misc/truecrypt/gcc6.patch−61

This diff is too big to show here.

pkgs/applications/misc/tvbrowser/bin.nix+56

This diff is too big to show here.

pkgs/applications/misc/twmn/default.nix+2−1

This diff is too big to show here.

pkgs/applications/misc/tzupdate/default.nix+2−3

This diff is too big to show here.

pkgs/applications/misc/udiskie/default.nix+5−6

This diff is too big to show here.

pkgs/applications/misc/unixcw/default.nix+37

This diff is too big to show here.

pkgs/applications/misc/unixcw/remove-use-of-dlopen.patch+677

This diff is too big to show here.

pkgs/applications/misc/urh/default.nix+5−4

This diff is too big to show here.

pkgs/applications/misc/urlscan/default.nix+7−4

This diff is too big to show here.

pkgs/applications/misc/valauncher/default.nix−28

This diff is too big to show here.

pkgs/applications/misc/valentina/default.nix+67

This diff is too big to show here.

pkgs/applications/misc/vcal/default.nix+37

This diff is too big to show here.

pkgs/applications/misc/veracrypt/default.nix+23−28

This diff is too big to show here.

pkgs/applications/misc/verbiste/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/viking/default.nix+4−4

This diff is too big to show here.

pkgs/applications/misc/visidata/default.nix+29

This diff is too big to show here.

pkgs/applications/misc/vit/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/volnoti/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/vym/default.nix+6−6

This diff is too big to show here.

pkgs/applications/misc/weather/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/wego/default.nix+5−1

This diff is too big to show here.

pkgs/applications/misc/welle-io/default.nix+8−8

This diff is too big to show here.

pkgs/applications/misc/wikicurses/default.nix+8−15

This diff is too big to show here.

pkgs/applications/misc/wmname/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/wordnet/default.nix+9−4

This diff is too big to show here.

pkgs/applications/misc/worker/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/workrave/default.nix+10−19

This diff is too big to show here.

pkgs/applications/misc/wsjtx/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/xautoclick/default.nix+5−2

This diff is too big to show here.

pkgs/applications/misc/xca/default.nix+16−11

This diff is too big to show here.

pkgs/applications/misc/xchm/default.nix+3−2

This diff is too big to show here.

pkgs/applications/misc/xdgmenumaker/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/xfe/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/xfontsel/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/xiphos/default.nix+4−4

This diff is too big to show here.

pkgs/applications/misc/xkbd/default.nix+30

This diff is too big to show here.

pkgs/applications/misc/xlog/default.nix+29

This diff is too big to show here.

pkgs/applications/misc/xmind/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/xmove/default.nix+1

This diff is too big to show here.

pkgs/applications/misc/xmr-stak/default.nix+12−7

This diff is too big to show here.

pkgs/applications/misc/xmrig/default.nix+34

This diff is too big to show here.

pkgs/applications/misc/xmrig/proxy.nix+34

This diff is too big to show here.

pkgs/applications/misc/xneur/0.8.nix−29

This diff is too big to show here.

pkgs/applications/misc/xneur/default.nix+23−32

This diff is too big to show here.

pkgs/applications/misc/xneur/src-for-default.nix−9

This diff is too big to show here.

pkgs/applications/misc/xneur/src-info-for-default.nix−5

This diff is too big to show here.

pkgs/applications/misc/xpad/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/xpdf/cmake_version.patch+15

This diff is too big to show here.

pkgs/applications/misc/xpdf/default.nix+18−8

This diff is too big to show here.

pkgs/applications/misc/xrandr-invert-colors/default.nix+2−2

This diff is too big to show here.

pkgs/applications/misc/xscope/default.nix+24

This diff is too big to show here.

pkgs/applications/misc/xterm/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/xtermcontrol/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/yaft/default.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/yakuake/default.nix+3−2

This diff is too big to show here.

pkgs/applications/misc/yarssr/default.nix+68

This diff is too big to show here.

pkgs/applications/misc/yate/default.nix+5−4

This diff is too big to show here.

pkgs/applications/misc/yubioath-desktop/default.nix+3−3

This diff is too big to show here.

pkgs/applications/misc/zathura/core/default.nix+17−34

This diff is too big to show here.

pkgs/applications/misc/zathura/core/icon.xpm−120

This diff is too big to show here.

pkgs/applications/misc/zathura/djvu/default.nix+7−16

This diff is too big to show here.

pkgs/applications/misc/zathura/djvu/gtkflags.patch−23

This diff is too big to show here.

pkgs/applications/misc/zathura/pdf-mupdf/default.nix+17−18

This diff is too big to show here.

pkgs/applications/misc/zathura/pdf-poppler/default.nix+7−14

This diff is too big to show here.

pkgs/applications/misc/zathura/ps/default.nix+8−17

This diff is too big to show here.

pkgs/applications/misc/zathura/ps/gtkflags.patch−23

This diff is too big to show here.

pkgs/applications/misc/zathura/wrapper.nix+1−1

This diff is too big to show here.

pkgs/applications/misc/zscroll/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/apache-directory-studio/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/bittorrentsync/generic.nix+4−4

This diff is too big to show here.

pkgs/applications/networking/browsers/brave/default.nix+144

This diff is too big to show here.

pkgs/applications/networking/browsers/browsh/default.nix+60

This diff is too big to show here.

pkgs/applications/networking/browsers/browsh/deps.nix+272

This diff is too big to show here.

pkgs/applications/networking/browsers/chromium/browser.nix+1

This diff is too big to show here.

pkgs/applications/networking/browsers/chromium/common.nix+65−59

This diff is too big to show here.

pkgs/applications/networking/browsers/chromium/default.nix+8−8

This diff is too big to show here.

pkgs/applications/networking/browsers/chromium/patches/chromium-gcc5-r4.patch−98

This diff is too big to show here.

pkgs/applications/networking/browsers/chromium/patches/constexpr-fix.patch−98

This diff is too big to show here.

pkgs/applications/networking/browsers/chromium/patches/fix_network_api_crash.patch−77

This diff is too big to show here.

pkgs/applications/networking/browsers/chromium/patches/include-math-for-round.patch−34

This diff is too big to show here.

pkgs/applications/networking/browsers/chromium/patches/nix_plugin_paths_52.patch−70

This diff is too big to show here.

pkgs/applications/networking/browsers/chromium/patches/nix_plugin_paths_68.patch+61

This diff is too big to show here.

pkgs/applications/networking/browsers/chromium/patches/remove-webp-include-69.patch+11

This diff is too big to show here.

pkgs/applications/networking/browsers/chromium/plugins.nix+10−7

This diff is too big to show here.

pkgs/applications/networking/browsers/chromium/update.sh+1−1

This diff is too big to show here.

pkgs/applications/networking/browsers/chromium/upstream-info.nix+9−9

This diff is too big to show here.

pkgs/applications/networking/browsers/conkeror/default.nix+4−4

This diff is too big to show here.

pkgs/applications/networking/browsers/dillo/default.nix+3−2

This diff is too big to show here.

pkgs/applications/networking/browsers/dwb/default.nix−35

This diff is too big to show here.

pkgs/applications/networking/browsers/eolie/0001-Extend-the-python-path-rather-than-replacing-it.patch−35

This diff is too big to show here.

pkgs/applications/networking/browsers/eolie/0001-Remove-post-install-script-handle-in-nix-config-inst.patch−23

This diff is too big to show here.

pkgs/applications/networking/browsers/eolie/default.nix+35−42

This diff is too big to show here.

pkgs/applications/networking/browsers/falkon/default.nix+11−10

This diff is too big to show here.

pkgs/applications/networking/browsers/firefox-bin/beta_sources.nix+409−389

This diff is too big to show here.

pkgs/applications/networking/browsers/firefox-bin/default.nix+37−21

This diff is too big to show here.

pkgs/applications/networking/browsers/firefox-bin/devedition_sources.nix+409−389

This diff is too big to show here.

pkgs/applications/networking/browsers/firefox-bin/release_sources.nix+415−385

This diff is too big to show here.

pkgs/applications/networking/browsers/firefox-bin/update.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/browsers/firefox/common.nix+110−57

This diff is too big to show here.

pkgs/applications/networking/browsers/firefox/fix-pa-context-connect-retval.patch+26

This diff is too big to show here.

pkgs/applications/networking/browsers/firefox/no-buildconfig.patch+3−3

This diff is too big to show here.

pkgs/applications/networking/browsers/firefox/packages.nix+103−68

This diff is too big to show here.

pkgs/applications/networking/browsers/firefox/update.nix+2−4

This diff is too big to show here.

pkgs/applications/networking/browsers/firefox/wrapper.nix+43−35

This diff is too big to show here.

pkgs/applications/networking/browsers/google-chrome/default.nix+12−16

This diff is too big to show here.

pkgs/applications/networking/browsers/jumanji/default.nix−31

This diff is too big to show here.

pkgs/applications/networking/browsers/links2/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/browsers/luakit/default.nix+61

This diff is too big to show here.

pkgs/applications/networking/browsers/lynx/default.nix+7−5

This diff is too big to show here.

pkgs/applications/networking/browsers/midori/default.nix+5−5

This diff is too big to show here.

pkgs/applications/networking/browsers/mozilla-plugins/flashplayer/default.nix+12−11

This diff is too big to show here.

pkgs/applications/networking/browsers/mozilla-plugins/flashplayer/standalone.nix+8−13

This diff is too big to show here.

pkgs/applications/networking/browsers/mozilla-plugins/google-talk-plugin/default.nix+6−6

This diff is too big to show here.

pkgs/applications/networking/browsers/mozilla-plugins/trezor/default.nix−47

This diff is too big to show here.

pkgs/applications/networking/browsers/opera/default.nix+6−3

This diff is too big to show here.

pkgs/applications/networking/browsers/otter/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/browsers/palemoon/default.nix+10−8

This diff is too big to show here.

pkgs/applications/networking/browsers/qtchan/default.nix+44

This diff is too big to show here.

pkgs/applications/networking/browsers/qutebrowser/default.nix+30−18

This diff is too big to show here.

pkgs/applications/networking/browsers/surf/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/browsers/tor-browser-bundle-bin/default.nix+33−26

This diff is too big to show here.

pkgs/applications/networking/browsers/tor-browser-bundle/default.nix+29−6

This diff is too big to show here.

pkgs/applications/networking/browsers/uzbl/default.nix+7−6

This diff is too big to show here.

pkgs/applications/networking/browsers/vimb/default.nix+4−4

This diff is too big to show here.

pkgs/applications/networking/browsers/vimprobable2/default.nix+4−4

This diff is too big to show here.

pkgs/applications/networking/browsers/vivaldi/chromium-gcc-r1.patch−14

This diff is too big to show here.

pkgs/applications/networking/browsers/vivaldi/chromium-gcc5-r1.patch−66

This diff is too big to show here.

pkgs/applications/networking/browsers/vivaldi/chromium-gn-bootstrap-r14.patch−27

This diff is too big to show here.

pkgs/applications/networking/browsers/vivaldi/default.nix+8−8

This diff is too big to show here.

pkgs/applications/networking/browsers/vivaldi/ffmpeg-codecs.nix+9−14

This diff is too big to show here.

pkgs/applications/networking/browsers/vivaldi/update.sh+2−1

This diff is too big to show here.

pkgs/applications/networking/browsers/w3m/default.nix+1

This diff is too big to show here.

pkgs/applications/networking/c14/default.nix+4−5

This diff is too big to show here.

pkgs/applications/networking/charles/default.nix+48

This diff is too big to show here.

pkgs/applications/networking/cloudflared/default.nix+25

This diff is too big to show here.

pkgs/applications/networking/cloudflared/deps.nix+444

This diff is too big to show here.

pkgs/applications/networking/cluster/click/default.nix+29

This diff is too big to show here.

pkgs/applications/networking/cluster/click/fix_cargo_lock_version.patch+13

This diff is too big to show here.

pkgs/applications/networking/cluster/cni/default.nix+3−6

This diff is too big to show here.

pkgs/applications/networking/cluster/cni/plugins.nix+33

This diff is too big to show here.

pkgs/applications/networking/cluster/docker-machine/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/cluster/docker-machine/kvm.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/cluster/docker-machine/kvm2.nix+31

This diff is too big to show here.

pkgs/applications/networking/cluster/flink/default.nix+8−12

This diff is too big to show here.

pkgs/applications/networking/cluster/habitat/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/cluster/hadoop/default.nix+148−44

This diff is too big to show here.

pkgs/applications/networking/cluster/helm/default.nix+33−34

This diff is too big to show here.

pkgs/applications/networking/cluster/helm/deps.nix+840

This diff is too big to show here.

pkgs/applications/networking/cluster/helmfile/default.nix+37

This diff is too big to show here.

pkgs/applications/networking/cluster/heptio-ark/default.nix+25

This diff is too big to show here.

pkgs/applications/networking/cluster/hetzner-kube/default.nix+24

This diff is too big to show here.

pkgs/applications/networking/cluster/kanif/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/cluster/kompose/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/cluster/kontemplate/default.nix+25−16

This diff is too big to show here.

pkgs/applications/networking/cluster/kontemplate/deps.nix+48−57

This diff is too big to show here.

pkgs/applications/networking/cluster/kops/default.nix+5−5

This diff is too big to show here.

pkgs/applications/networking/cluster/ksonnet/default.nix+23

This diff is too big to show here.

pkgs/applications/networking/cluster/kubernetes/default.nix+14−11

This diff is too big to show here.

pkgs/applications/networking/cluster/kubetail/default.nix+30

This diff is too big to show here.

pkgs/applications/networking/cluster/kubeval/default.nix+48

This diff is too big to show here.

pkgs/applications/networking/cluster/kubeval/deps.nix+174

This diff is too big to show here.

pkgs/applications/networking/cluster/luigi/default.nix+32

This diff is too big to show here.

pkgs/applications/networking/cluster/mesos/default.nix+20−14

This diff is too big to show here.

pkgs/applications/networking/cluster/minikube/default.nix+27−36

This diff is too big to show here.

pkgs/applications/networking/cluster/minikube/localkube.patch−20

This diff is too big to show here.

pkgs/applications/networking/cluster/minishift/default.nix+67

This diff is too big to show here.

pkgs/applications/networking/cluster/nomad/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/cluster/openshift/default.nix+49−18

This diff is too big to show here.

pkgs/applications/networking/cluster/panamax/api/Gemfile−23

This diff is too big to show here.

pkgs/applications/networking/cluster/panamax/api/Gemfile.lock−164

This diff is too big to show here.

pkgs/applications/networking/cluster/panamax/api/default.nix−74

This diff is too big to show here.

pkgs/applications/networking/cluster/panamax/api/gemset.nix−568

This diff is too big to show here.

pkgs/applications/networking/cluster/panamax/ui/Gemfile−31

This diff is too big to show here.

pkgs/applications/networking/cluster/panamax/ui/Gemfile.lock−226

This diff is too big to show here.

pkgs/applications/networking/cluster/panamax/ui/default.nix−72

This diff is too big to show here.

pkgs/applications/networking/cluster/panamax/ui/gemset.nix−789

This diff is too big to show here.

pkgs/applications/networking/cluster/pig/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/cluster/spark/default.nix+11−13

This diff is too big to show here.

pkgs/applications/networking/cluster/stern/default.nix+25

This diff is too big to show here.

pkgs/applications/networking/cluster/stern/deps.nix+336

This diff is too big to show here.

pkgs/applications/networking/cluster/taktuk/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/cluster/terraform-landscape/Gemfile.lock+5−5

This diff is too big to show here.

pkgs/applications/networking/cluster/terraform-landscape/default.nix+8−9

This diff is too big to show here.

pkgs/applications/networking/cluster/terraform-landscape/gemset.nix+8−8

This diff is too big to show here.

pkgs/applications/networking/cluster/terraform-providers/data.nix+654

This diff is too big to show here.

pkgs/applications/networking/cluster/terraform-providers/default.nix+28

This diff is too big to show here.

pkgs/applications/networking/cluster/terraform-providers/gandi/default.nix+26

This diff is too big to show here.

pkgs/applications/networking/cluster/terraform-providers/gandi/deps.nix+21

This diff is too big to show here.

pkgs/applications/networking/cluster/terraform-providers/ibm/default.nix+38

This diff is too big to show here.

pkgs/applications/networking/cluster/terraform-providers/libvirt/default.nix+51

This diff is too big to show here.

pkgs/applications/networking/cluster/terraform-providers/providers.txt+16

This diff is too big to show here.

pkgs/applications/networking/cluster/terraform-providers/update-all+143

This diff is too big to show here.

pkgs/applications/networking/cluster/terraform/default.nix+43−9

This diff is too big to show here.

pkgs/applications/networking/cluster/terraform/providers/data.nix−507

This diff is too big to show here.

pkgs/applications/networking/cluster/terraform/providers/default.nix−25

This diff is too big to show here.

pkgs/applications/networking/cluster/terraform/providers/update-all−100

This diff is too big to show here.

pkgs/applications/networking/cluster/terragrunt/default.nix+5−5

This diff is too big to show here.

pkgs/applications/networking/cluster/terragrunt/deps.nix+16−16

This diff is too big to show here.

pkgs/applications/networking/compactor/default.nix+52

This diff is too big to show here.

pkgs/applications/networking/corebird/default.nix+17−13

This diff is too big to show here.

pkgs/applications/networking/davmail/default.nix+8−6

This diff is too big to show here.

pkgs/applications/networking/drive/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/dropbox/cli.nix

This diff is too big to show here.

pkgs/applications/networking/dropbox/default.nix+4−4

This diff is too big to show here.

pkgs/applications/networking/enhanced-ctorrent/default.nix+14−1

This diff is too big to show here.

pkgs/applications/networking/errbot/default.nix+5−3

This diff is too big to show here.

pkgs/applications/networking/esniper/default.nix+6−8

This diff is too big to show here.

pkgs/applications/networking/feedreaders/canto-curses/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/feedreaders/canto-daemon/default.nix+4−5

This diff is too big to show here.

pkgs/applications/networking/feedreaders/feedreader/default.nix+50

This diff is too big to show here.

pkgs/applications/networking/feedreaders/newsbeuter/default.nix−61

This diff is too big to show here.

pkgs/applications/networking/feedreaders/newsboat/default.nix+6−4

This diff is too big to show here.

pkgs/applications/networking/feedreaders/rssguard/default.nix+2−8

This diff is too big to show here.

pkgs/applications/networking/feedreaders/rsstail/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/firehol/default.nix+34−5

This diff is too big to show here.

pkgs/applications/networking/flent/default.nix+30

This diff is too big to show here.

pkgs/applications/networking/flent/http-getter.nix+23

This diff is too big to show here.

pkgs/applications/networking/flexget/default.nix+63−62

This diff is too big to show here.

pkgs/applications/networking/ftp/filezilla/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/ftp/taxi/default.nix+47

This diff is too big to show here.

pkgs/applications/networking/gmailieer/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/gns3/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/gns3/server.nix+13

This diff is too big to show here.

pkgs/applications/networking/google-drive-ocamlfuse/default.nix+6−7

This diff is too big to show here.

pkgs/applications/networking/gopher/gopherclient/default.nix+1

This diff is too big to show here.

pkgs/applications/networking/ids/bro/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/ids/daq/default.nix+8−4

This diff is too big to show here.

pkgs/applications/networking/ids/snort/default.nix+9−4

This diff is too big to show here.

pkgs/applications/networking/ike/default.nix−2

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/SkypeExport/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/amsn/default.nix+6−1

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/baresip/default.nix+7−9

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/bitlbee-discord/default.nix+4−3

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/bitlbee-facebook/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/bitlbee-steam/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/bitlbee/default.nix+16−13

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/blink/default.nix+7−6

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/bluejeans/default.nix+49

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/coyim/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/dino/default.nix+7−7

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/discord/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/ekiga/default.nix+8−6

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/franz/default.nix+13−19

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/gajim/default.nix+38−97

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/gitter/default.nix+71

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/gomuks/default.nix+23

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/hipchat/default.nix+8−18

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/jackline/default.nix+4−6

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/jackline/tls-0.9.0.patch−29

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/jitsi/default.nix+3−7

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/linphone/default.nix+8−1

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/matrique/default.nix+55

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/mattermost-desktop/default.nix+81

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/mcabber/default.nix+6−2

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/messenger-for-desktop/default.nix−104

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/mikutter/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/nheko/default.nix+75

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/pidgin-plugins/pidgin-opensteamworks/default.nix+10−11

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/pidgin-plugins/pidgin-skypeweb/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/pidgin-plugins/pidgin-xmpp-receipts/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/pidgin-plugins/purple-discord/default.nix+31

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/pidgin-plugins/purple-facebook/default.nix+7−7

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/pidgin-plugins/purple-hangouts/default.nix+5−5

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/pidgin-plugins/purple-lurch/default.nix+31

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/pidgin-plugins/purple-matrix/default.nix+15−13

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/pidgin-plugins/purple-xmpp-http-upload/default.nix+25

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/pidgin-plugins/sipe/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/pidgin-plugins/skype4pidgin/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/pidgin-plugins/telegram-purple/default.nix+4−4

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/pidgin-plugins/tox-prpl/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/pidgin/default.nix+8−9

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/pidgin/wrapper.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/poezio/default.nix+28

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/pond/default.nix+4−5

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/profanity/default.nix+27−8

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/profanity/patches/packages-osx.patch+11

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/profanity/patches/undefined-macros.patch+40

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/psi-plus/default.nix+7−6

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/psi/default.nix+4−3

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/pybitmessage/default.nix+7−7

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/qtox/default.nix+20−15

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/quaternion/default.nix+18−9

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/rambox/bare.nix+7−8

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/rambox/default.nix+21−7

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/rambox/disable-tooltips.patch−19

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/rambox/hide-check-for-updates.patch−35

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/rambox/sencha/bare.nix+4−4

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/ratox/default.nix+10−8

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/ratox/ldlibs.patch−5

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/ricochet/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/ring-daemon/default.nix+4−5

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/riot/riot-web.nix+5−3

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/salut-a-toi/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/signal-desktop/beta.nix−87

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/signal-desktop/default.nix+70−49

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/silc-client/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/skype-call-recorder/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/skypeforlinux/default.nix+19−15

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/slack-term/default.nix+23

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/slack/default.nix+20−12

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/spectral/default.nix+33

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/stride/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/swift-im/default.nix+50

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/swift-im/qt-5.11.patch+10

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/swift-im/scons.patch+53

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/teamspeak/client.nix+5−4

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/teamspeak/server.nix+4−4

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/telegram/tdesktop/default.nix+18−124

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/telegram/tdesktop/fix-internal-compiler-error.patch+68

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/telegram/tdesktop/generic.nix+151

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/telepathy/gabble/default.nix+9−8

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/telepathy/haze/default.nix+4−4

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/telepathy/idle/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/telepathy/logger/default.nix+8−8

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/telepathy/mission-control/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/telepathy/salut/default.nix+6−6

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/torchat/default.nix−1

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/toxic/default.nix+4−4

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/utox/default.nix+17−10

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/vacuum/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/viber/default.nix+4−6

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/vk-messenger/default.nix+53

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/wavebox/default.nix+66

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/weechat-matrix-bridge/default.nix−44

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/weechat-xmpp/default.nix−35

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/weechat-xmpp/libpath.patch−16

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/wire-desktop/default.nix+109

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/zoom-us/default.nix+82−80

This diff is too big to show here.

pkgs/applications/networking/instant-messengers/zoom-us/update.sh+7

This diff is too big to show here.

pkgs/applications/networking/insync/default.nix+4−4

This diff is too big to show here.

pkgs/applications/networking/ipfs-cluster/default.nix+41

This diff is too big to show here.

pkgs/applications/networking/ipfs-migrator/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/ipfs-migrator/deps.nix+4−13

This diff is too big to show here.

pkgs/applications/networking/ipfs/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/irc/bip/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/irc/chatzilla/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/irc/communi/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/irc/hexchat/default.nix+4−4

This diff is too big to show here.

pkgs/applications/networking/irc/ii/default.nix+4−4

This diff is too big to show here.

pkgs/applications/networking/irc/irssi/default.nix+4−3

This diff is too big to show here.

pkgs/applications/networking/irc/irssi/otr/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/irc/konversation/default.nix+3−2

This diff is too big to show here.

pkgs/applications/networking/irc/quassel/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/irc/quassel/qt5_11.patch+72

This diff is too big to show here.

pkgs/applications/networking/irc/quassel/source.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/irc/sic/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/irc/weechat/default.nix+68−35

This diff is too big to show here.

pkgs/applications/networking/irc/weechat/scripts/default.nix+15

This diff is too big to show here.

pkgs/applications/networking/irc/weechat/scripts/wee-slack/default.nix+39

This diff is too big to show here.

pkgs/applications/networking/irc/weechat/scripts/wee-slack/libpath.patch+13

This diff is too big to show here.

pkgs/applications/networking/irc/weechat/scripts/weechat-matrix-bridge/default.nix+46

This diff is too big to show here.

pkgs/applications/networking/irc/weechat/scripts/weechat-matrix-bridge/library-path.patch

This diff is too big to show here.

pkgs/applications/networking/irc/weechat/scripts/weechat-xmpp/default.nix+36

This diff is too big to show here.

pkgs/applications/networking/irc/weechat/scripts/weechat-xmpp/libpath.patch+16

This diff is too big to show here.

pkgs/applications/networking/jmeter/default.nix+40−12

This diff is too big to show here.

pkgs/applications/networking/linssid/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/mailreaders/afew/default.nix+11−1

This diff is too big to show here.

pkgs/applications/networking/mailreaders/alpine/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/mailreaders/astroid/default.nix+24−9

This diff is too big to show here.

pkgs/applications/networking/mailreaders/balsa/default.nix+61

This diff is too big to show here.

pkgs/applications/networking/mailreaders/claws-mail/default.nix+26−17

This diff is too big to show here.

pkgs/applications/networking/mailreaders/imapfilter.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/mailreaders/inboxer/default.nix+10−7

This diff is too big to show here.

pkgs/applications/networking/mailreaders/lumail/default.nix+42−10

This diff is too big to show here.

pkgs/applications/networking/mailreaders/mailnag/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/mailreaders/mailpile/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/mailreaders/mblaze/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/mailreaders/msgviewer/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/mailreaders/mutt/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/mailreaders/neomutt/default.nix+18−5

This diff is too big to show here.

pkgs/applications/networking/mailreaders/notmuch-bower/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/mailreaders/notmuch/default.nix+32−45

This diff is too big to show here.

pkgs/applications/networking/mailreaders/nylas-mail-bin/default.nix+8−11

This diff is too big to show here.

pkgs/applications/networking/mailreaders/realpine/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/mailreaders/sup/default.nix+2−3

This diff is too big to show here.

pkgs/applications/networking/mailreaders/sylpheed/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/mailreaders/thunderbird-bin/default.nix+12−14

This diff is too big to show here.

pkgs/applications/networking/mailreaders/thunderbird-bin/release_sources.nix+245−255

This diff is too big to show here.

pkgs/applications/networking/mailreaders/thunderbird/default.nix+38−24

This diff is too big to show here.

pkgs/applications/networking/modem-manager-gui/default.nix+50

This diff is too big to show here.

pkgs/applications/networking/msmtp/default.nix+13−5

This diff is too big to show here.

pkgs/applications/networking/mumble/default.nix+25−13

This diff is too big to show here.

pkgs/applications/networking/ndppd/default.nix+17−2

This diff is too big to show here.

pkgs/applications/networking/netperf/default.nix+13−5

This diff is too big to show here.

pkgs/applications/networking/newsreaders/liferea/default.nix+8−9

This diff is too big to show here.

pkgs/applications/networking/newsreaders/pan/default.nix+23−8

This diff is too big to show here.

pkgs/applications/networking/newsreaders/quiterss/default.nix+11−4

This diff is too big to show here.

pkgs/applications/networking/newsreaders/slrn/default.nix+4−1

This diff is too big to show here.

pkgs/applications/networking/nextcloud-client/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/nload/default.nix+14−1

This diff is too big to show here.

pkgs/applications/networking/offrss/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/ostinato/default.nix+4−4

This diff is too big to show here.

pkgs/applications/networking/owamp/default.nix+28

This diff is too big to show here.

pkgs/applications/networking/owncloud-client/default.nix+4−3

This diff is too big to show here.

pkgs/applications/networking/owncloud-client/find-sql.patch+12

This diff is too big to show here.

pkgs/applications/networking/p2p/deluge/default.nix+13−3

This diff is too big to show here.

pkgs/applications/networking/p2p/eiskaltdcpp/default.nix+5−4

This diff is too big to show here.

pkgs/applications/networking/p2p/frostwire/default.nix+76−13

This diff is too big to show here.

pkgs/applications/networking/p2p/frostwire/frostwire-bin.nix+31

This diff is too big to show here.

pkgs/applications/networking/p2p/gnunet/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/p2p/gnunet/git.nix+92

This diff is too big to show here.

pkgs/applications/networking/p2p/gnunet/svn.nix−93

This diff is too big to show here.

pkgs/applications/networking/p2p/ktorrent/default.nix+20−2

This diff is too big to show here.

pkgs/applications/networking/p2p/ncdc/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/p2p/opentracker/default.nix+7−7

This diff is too big to show here.

pkgs/applications/networking/p2p/qbittorrent/default.nix+18−15

This diff is too big to show here.

pkgs/applications/networking/p2p/retroshare/default.nix+3−2

This diff is too big to show here.

pkgs/applications/networking/p2p/soulseekqt/default.nix+73

This diff is too big to show here.

pkgs/applications/networking/p2p/synapse-bt/default.nix+27

This diff is too big to show here.

pkgs/applications/networking/p2p/tixati/default.nix+4−4

This diff is too big to show here.

pkgs/applications/networking/p2p/transmission-remote-gtk/default.nix+16−13

This diff is too big to show here.

pkgs/applications/networking/p2p/transmission/default.nix+7−23

This diff is too big to show here.

pkgs/applications/networking/p2p/tribler/default.nix+9−7

This diff is too big to show here.

pkgs/applications/networking/p2p/twister/default.nix+4−2

This diff is too big to show here.

pkgs/applications/networking/p2p/zeronet/default.nix+35

This diff is too big to show here.

pkgs/applications/networking/pjsip/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/protocol/default.nix+20

This diff is too big to show here.

pkgs/applications/networking/protonmail-bridge/default.nix+85

This diff is too big to show here.

pkgs/applications/networking/pyload/default.nix+1−2

This diff is too big to show here.

pkgs/applications/networking/remote/anydesk/default.nix+32−12

This diff is too big to show here.

pkgs/applications/networking/remote/citrix-receiver/default.nix+57−52

This diff is too big to show here.

pkgs/applications/networking/remote/citrix-receiver/wrapper.nix+19

This diff is too big to show here.

pkgs/applications/networking/remote/freerdp/default.nix+7−7

This diff is too big to show here.

pkgs/applications/networking/remote/freerdp/legacy.nix+1−2

This diff is too big to show here.

pkgs/applications/networking/remote/putty/default.nix+20−6

This diff is too big to show here.

pkgs/applications/networking/remote/remmina/default.nix+26−39

This diff is too big to show here.

pkgs/applications/networking/remote/ssvnc/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/remote/teamviewer/default.nix+16−45

This diff is too big to show here.

pkgs/applications/networking/remote/x2goclient/default.nix+14−9

This diff is too big to show here.

pkgs/applications/networking/remote/x2goclient/qt511.patch+15

This diff is too big to show here.

pkgs/applications/networking/remote/xrdp/default.nix+5−5

This diff is too big to show here.

pkgs/applications/networking/resilio-sync/default.nix+5−5

This diff is too big to show here.

pkgs/applications/networking/seafile-client/default.nix+8−6

This diff is too big to show here.

pkgs/applications/networking/sieve-connect/default.nix+48

This diff is too big to show here.

pkgs/applications/networking/sipcmd/default.nix+1

This diff is too big to show here.

pkgs/applications/networking/siproxd/default.nix+1

This diff is too big to show here.

pkgs/applications/networking/sniffers/etherape/default.nix+9−11

This diff is too big to show here.

pkgs/applications/networking/sniffers/kismet/default.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/sniffers/wireshark/default.nix+55−12

This diff is too big to show here.

pkgs/applications/networking/soapui/default.nix+51

This diff is too big to show here.

pkgs/applications/networking/spideroak/default.nix+13−13

This diff is too big to show here.

pkgs/applications/networking/ssb/patchwork-classic/default.nix+106

This diff is too big to show here.

pkgs/applications/networking/super-productivity/default.nix+105

This diff is too big to show here.

pkgs/applications/networking/sync/backintime/common.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/sync/backintime/qt4.nix+5−2

This diff is too big to show here.

pkgs/applications/networking/sync/casync/default.nix+52

This diff is too big to show here.

pkgs/applications/networking/sync/desync/default.nix+27

This diff is too big to show here.

pkgs/applications/networking/sync/desync/deps.nix+129

This diff is too big to show here.

pkgs/applications/networking/sync/lsyncd/default.nix+14−6

This diff is too big to show here.

pkgs/applications/networking/sync/rclone/browser.nix+25

This diff is too big to show here.

pkgs/applications/networking/sync/rclone/default.nix+3−3

This diff is too big to show here.

pkgs/applications/networking/sync/rsync/base.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/sync/rsync/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/sync/rsync/rrsync.nix+1−1

This diff is too big to show here.

pkgs/applications/networking/syncplay/default.nix+8−13

This diff is too big to show here.

pkgs/applications/networking/syncthing-gtk/default.nix+18−10

This diff is too big to show here.

pkgs/applications/networking/syncthing-gtk/disable-syncthing-binary-configuration.patch−77

This diff is too big to show here.

pkgs/applications/networking/syncthing/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/syncthing/inotify-deps.nix−21

This diff is too big to show here.

pkgs/applications/networking/syncthing/inotify.nix−37

This diff is too big to show here.

pkgs/applications/networking/tcpkali/default.nix+2−2

This diff is too big to show here.

pkgs/applications/networking/testssl/default.nix+22−17

This diff is too big to show here.

pkgs/applications/networking/testssl/testssl.patch−10

This diff is too big to show here.

pkgs/applications/networking/transporter/default.nix+73

This diff is too big to show here.

pkgs/applications/networking/tsung/default.nix+50

This diff is too big to show here.

pkgs/applications/networking/vnstat/default.nix+4−4

This diff is too big to show here.

pkgs/applications/networking/weather/meteo/default.nix+54

This diff is too big to show here.

pkgs/applications/networking/znc/default.nix+20−10

This diff is too big to show here.

pkgs/applications/networking/znc/modules.nix+3−1

This diff is too big to show here.

pkgs/applications/office/abiword/default.nix+9−12

This diff is too big to show here.

pkgs/applications/office/aesop/default.nix+50

This diff is too big to show here.

pkgs/applications/office/atlassian-cli/default.nix+49

This diff is too big to show here.

pkgs/applications/office/atlassian-cli/wrapper.sh+20

This diff is too big to show here.

pkgs/applications/office/autokey/default.nix+38

This diff is too big to show here.

pkgs/applications/office/autokey/remove-requires-dbus-python.patch+11

This diff is too big to show here.

pkgs/applications/office/beancount/bean-add.nix+1−1

This diff is too big to show here.

pkgs/applications/office/beancount/default.nix−44

This diff is too big to show here.

pkgs/applications/office/bookworm/default.nix+77

This diff is too big to show here.

pkgs/applications/office/calligra/default.nix+7−13

This diff is too big to show here.

pkgs/applications/office/calligra/qt5_11.patch+98

This diff is too big to show here.

pkgs/applications/office/cb2bib/default.nix+3−3

This diff is too big to show here.

pkgs/applications/office/fava/default.nix+3−5

This diff is too big to show here.

pkgs/applications/office/gnucash/2.4.nix+90

This diff is too big to show here.

pkgs/applications/office/gnucash/2.6.nix+5−7

This diff is too big to show here.

pkgs/applications/office/gnucash/default.nix+63−43

This diff is too big to show here.

pkgs/applications/office/gnumeric/default.nix+9−9

This diff is too big to show here.

pkgs/applications/office/grisbi/default.nix+4−4

This diff is too big to show here.

pkgs/applications/office/homebank/default.nix+5−5

This diff is too big to show here.

pkgs/applications/office/ib/tws/default.nix+1−1

This diff is too big to show here.

pkgs/applications/office/impressive/default.nix+3−3

This diff is too big to show here.

pkgs/applications/office/jabref/default.nix+2−2

This diff is too big to show here.

pkgs/applications/office/jameica/default.nix+75

This diff is too big to show here.

pkgs/applications/office/keepnote/default.nix+1−1

This diff is too big to show here.

pkgs/applications/office/kexi/default.nix+10−3

This diff is too big to show here.

pkgs/applications/office/kmymoney/default.nix+78

This diff is too big to show here.

pkgs/applications/office/ledger-web/Gemfile.lock+3−3

This diff is too big to show here.

pkgs/applications/office/ledger-web/gemset.nix+10−2

This diff is too big to show here.

pkgs/applications/office/ledger/2.6.3.nix+5−1

This diff is too big to show here.

pkgs/applications/office/ledger/default.nix+6−3

This diff is too big to show here.

pkgs/applications/office/libreoffice/default-primary-src.nix+6−6

This diff is too big to show here.

pkgs/applications/office/libreoffice/default.nix+112−93

This diff is too big to show here.

pkgs/applications/office/libreoffice/generate-libreoffice-srcs.py+8−1

This diff is too big to show here.

pkgs/applications/office/libreoffice/libreoffice-srcs-still.nix+352−296

This diff is too big to show here.

pkgs/applications/office/libreoffice/libreoffice-srcs.nix+298−235

This diff is too big to show here.

pkgs/applications/office/libreoffice/still-primary-src.nix+5−5

This diff is too big to show here.

pkgs/applications/office/libreoffice/still.nix+121−95

This diff is too big to show here.

pkgs/applications/office/libreoffice/wrapper.nix+19

This diff is too big to show here.

pkgs/applications/office/libreoffice/wrapper.sh+18

This diff is too big to show here.

pkgs/applications/office/marp/default.nix+2−2

This diff is too big to show here.

pkgs/applications/office/mendeley/default.nix+9−13

This diff is too big to show here.

pkgs/applications/office/mendeley/update.nix+2−2

This diff is too big to show here.

pkgs/applications/office/moneyplex/default.nix+6−6

This diff is too big to show here.

pkgs/applications/office/mytetra/default.nix+9−4

This diff is too big to show here.

pkgs/applications/office/osmo/default.nix+2−2

This diff is too big to show here.

pkgs/applications/office/paperwork/backend.nix+14−6

This diff is too big to show here.

pkgs/applications/office/paperwork/default.nix+11−11

This diff is too big to show here.

pkgs/applications/office/pinpoint/default.nix+2−2

This diff is too big to show here.

pkgs/applications/office/planner/default.nix+3−3

This diff is too big to show here.

pkgs/applications/office/scribus/default.nix+3−3

This diff is too big to show here.

pkgs/applications/office/scribus/unstable.nix+39

This diff is too big to show here.

pkgs/applications/office/skrooge/default.nix+14−6

This diff is too big to show here.

pkgs/applications/office/spice-up/default.nix+15−15

This diff is too big to show here.

pkgs/applications/office/timetrap/default.nix+1−1

This diff is too big to show here.

pkgs/applications/office/todo.txt-cli/default.nix+2−2

This diff is too big to show here.

pkgs/applications/office/todoman/default.nix+65

This diff is too big to show here.

pkgs/applications/office/treesheets/default.nix+4−4

This diff is too big to show here.

pkgs/applications/office/tryton/default.nix+30−7

This diff is too big to show here.

pkgs/applications/office/trytond/default.nix+10−7

This diff is too big to show here.

pkgs/applications/office/tudu/default.nix+2−2

This diff is too big to show here.

pkgs/applications/office/wordgrinder/default.nix+1−1

This diff is too big to show here.

pkgs/applications/office/wpsoffice/default.nix+2−2

This diff is too big to show here.

pkgs/applications/office/zim/default.nix+3−3

This diff is too big to show here.

pkgs/applications/office/zotero/default.nix+7−6

This diff is too big to show here.

pkgs/applications/science/astronomy/astrolabe-generator/default.nix+31

This diff is too big to show here.

pkgs/applications/science/astronomy/celestia/default.nix+7−10

This diff is too big to show here.

pkgs/applications/science/astronomy/gildas/aarch64.patch+12

This diff is too big to show here.

pkgs/applications/science/astronomy/gildas/clang.patch+22

This diff is too big to show here.

pkgs/applications/science/astronomy/gildas/default.nix+69

This diff is too big to show here.

pkgs/applications/science/astronomy/gildas/wrapper.patch+19

This diff is too big to show here.

pkgs/applications/science/astronomy/gpredict/default.nix+11−11

This diff is too big to show here.

pkgs/applications/science/astronomy/gravit/default.nix+5−4

This diff is too big to show here.

pkgs/applications/science/astronomy/openspace/assets.patch+100

This diff is too big to show here.

pkgs/applications/science/astronomy/openspace/config.patch+49

This diff is too big to show here.

pkgs/applications/science/astronomy/openspace/constexpr.patch+91

This diff is too big to show here.

pkgs/applications/science/astronomy/openspace/default.nix+89

This diff is too big to show here.

pkgs/applications/science/astronomy/openspace/vrpn.patch+13

This diff is too big to show here.

pkgs/applications/science/astronomy/stellarium/default.nix+16−9

This diff is too big to show here.

pkgs/applications/science/astronomy/xearth/default.nix+32

This diff is too big to show here.

pkgs/applications/science/biology/EZminc/default.nix+32

This diff is too big to show here.

pkgs/applications/science/biology/N3/default.nix+38

This diff is too big to show here.

pkgs/applications/science/biology/bcftools/default.nix+4−6

This diff is too big to show here.

pkgs/applications/science/biology/bowtie2/default.nix+3−2

This diff is too big to show here.

pkgs/applications/science/biology/conglomerate/default.nix+34

This diff is too big to show here.

pkgs/applications/science/biology/diamond/default.nix+1−1

This diff is too big to show here.

pkgs/applications/science/biology/freebayes/default.nix+1−1

This diff is too big to show here.

pkgs/applications/science/biology/hisat2/default.nix+49

This diff is too big to show here.

pkgs/applications/science/biology/hmmer/default.nix+25

This diff is too big to show here.

pkgs/applications/science/biology/igv/default.nix+3−3

This diff is too big to show here.

pkgs/applications/science/biology/inormalize/default.nix+39

This diff is too big to show here.

pkgs/applications/science/biology/inormalize/lgmask-interp.patch+10

This diff is too big to show here.

pkgs/applications/science/biology/inormalize/nu_correct_norm-interp.patch+10

This diff is too big to show here.

pkgs/applications/science/biology/iv/default.nix+1−1

This diff is too big to show here.

pkgs/applications/science/biology/minc-tools/default.nix+17−10

This diff is too big to show here.

pkgs/applications/science/biology/minc-widgets/default.nix+34

This diff is too big to show here.

pkgs/applications/science/biology/minimap2/default.nix+31

This diff is too big to show here.

pkgs/applications/science/biology/mni_autoreg/default.nix+36

This diff is too big to show here.

pkgs/applications/science/biology/mosdepth/default.nix+45

This diff is too big to show here.

pkgs/applications/science/biology/ncbi-tools/default.nix+6−1

This diff is too big to show here.

pkgs/applications/science/biology/neuron/default.nix+1−1

This diff is too big to show here.

pkgs/applications/science/biology/paml/default.nix+2−2

This diff is too big to show here.

pkgs/applications/science/biology/picard-tools/default.nix+2−2

This diff is too big to show here.

pkgs/applications/science/biology/platypus/default.nix+3−3

This diff is too big to show here.

pkgs/applications/science/biology/raxml/default.nix+2−3

This diff is too big to show here.

pkgs/applications/science/biology/samtools/default.nix+2−2

This diff is too big to show here.

pkgs/applications/science/biology/seaview/default.nix+41

This diff is too big to show here.

pkgs/applications/science/biology/snpeff/default.nix+3−3

This diff is too big to show here.

pkgs/applications/science/biology/somatic-sniper/default.nix+28

This diff is too big to show here.

pkgs/applications/science/biology/somatic-sniper/somatic-sniper.patch+26

This diff is too big to show here.

pkgs/applications/science/biology/star/default.nix+2−2

This diff is too big to show here.

pkgs/applications/science/biology/strelka/default.nix+37

This diff is too big to show here.

pkgs/applications/science/biology/vcftools/default.nix+3−3

This diff is too big to show here.

pkgs/applications/science/chemistry/avogadro/default.nix+3−3

This diff is too big to show here.

pkgs/applications/science/chemistry/gwyddion/default.nix+3−3

This diff is too big to show here.

pkgs/applications/science/chemistry/jmol/default.nix+54

This diff is too big to show here.

pkgs/applications/science/chemistry/molden/default.nix+6−4

This diff is too big to show here.

pkgs/applications/science/chemistry/molden/dont_register_file_types.patch+29

This diff is too big to show here.

pkgs/applications/science/chemistry/octopus/default.nix+15−13

This diff is too big to show here.

pkgs/applications/science/chemistry/openmolcas/default.nix+72

This diff is too big to show here.

pkgs/applications/science/chemistry/pymol/default.nix+6−6

This diff is too big to show here.

pkgs/applications/science/chemistry/quantum-espresso/default.nix+49

This diff is too big to show here.

pkgs/applications/science/chemistry/siesta/default.nix+69

This diff is too big to show here.

pkgs/applications/science/electronics/adms/default.nix+1−1

This diff is too big to show here.

pkgs/applications/science/electronics/bitscope/common.nix−6

This diff is too big to show here.

pkgs/applications/science/electronics/bitscope/packages.nix+1−8

This diff is too big to show here.

pkgs/applications/science/electronics/eagle/default.nix−97

This diff is too big to show here.

pkgs/applications/science/electronics/eagle/eagle.nix+83

This diff is too big to show here.

pkgs/applications/science/electronics/eagle/eagle7.nix+97

This diff is too big to show here.

pkgs/applications/science/electronics/eagle/eagle7_fixer.c

This diff is too big to show here.

pkgs/applications/science/electronics/geda/default.nix+3−1

This diff is too big to show here.

pkgs/applications/science/electronics/gtkwave/default.nix+3−3

This diff is too big to show here.

pkgs/applications/science/electronics/kicad/default.nix+53−53

This diff is too big to show here.

pkgs/applications/science/electronics/kicad/unstable.nix+13−11

This diff is too big to show here.

pkgs/applications/science/electronics/librepcb/default.nix+9−7

This diff is too big to show here.

pkgs/applications/science/electronics/librepcb/fix-2017-12.patch−29

This diff is too big to show here.

pkgs/applications/science/electronics/ngspice/default.nix+9−7

This diff is too big to show here.

pkgs/applications/science/electronics/pcb/default.nix+9−2

This diff is too big to show here.

pkgs/applications/science/electronics/pulseview/default.nix+2−2

This diff is too big to show here.

pkgs/applications/science/electronics/verilator/default.nix+4−4

This diff is too big to show here.

pkgs/applications/science/electronics/xcircuit/default.nix+35

This diff is too big to show here.

pkgs/applications/science/geometry/drgeo/default.nix+4−2

This diff is too big to show here.

pkgs/applications/science/logic/abc/default.nix+11−10

This diff is too big to show here.

pkgs/applications/science/logic/abella/default.nix+2−2

This diff is too big to show here.

pkgs/applications/science/logic/acgtk/default.nix+10−41

This diff is too big to show here.

pkgs/applications/science/logic/acgtk/install-emacs-to-site-lisp.patch−23

This diff is too big to show here.

pkgs/applications/science/logic/acgtk/use-nix-ocaml-byteflags.patch−11

This diff is too big to show here.

pkgs/applications/science/logic/aiger/default.nix+6−4

This diff is too big to show here.

pkgs/applications/science/logic/alt-ergo/default.nix+4−4

This diff is too big to show here.

pkgs/applications/science/logic/aspino/default.nix+19−7

This diff is too big to show here.

pkgs/applications/science/logic/beluga/default.nix+34

This diff is too big to show here.

pkgs/applications/science/logic/boolector/default.nix+38−29

This diff is too big to show here.

pkgs/applications/science/logic/btor2tools/default.nix+33

This diff is too big to show here.

pkgs/applications/science/logic/cedille/default.nix+50

This diff is too big to show here.

pkgs/applications/science/logic/celf/default.nix+36

This diff is too big to show here.

pkgs/applications/science/logic/coq/8.3.nix−82

This diff is too big to show here.

pkgs/applications/science/logic/coq/8.4.nix−97

This diff is too big to show here.

pkgs/applications/science/logic/coq/configure.8.3.patch−1112

This diff is too big to show here.

pkgs/applications/science/logic/coq/configure.patch−11

This diff is too big to show here.

pkgs/applications/science/logic/coq/default.nix+12−7

This diff is too big to show here.

pkgs/applications/science/logic/coq/no-codesign.patch−19

This diff is too big to show here.

pkgs/applications/science/logic/coq2html/default.nix+2−2

This diff is too big to show here.

pkgs/applications/science/logic/cryptoverif/default.nix+2−2

This diff is too big to show here.

pkgs/applications/science/logic/cvc4/default.nix+7−7

This diff is too big to show here.

pkgs/applications/science/logic/elan/default.nix+44

This diff is too big to show here.

pkgs/applications/science/logic/eprover/default.nix+7−8

This diff is too big to show here.

pkgs/applications/science/logic/hol/default.nix+1−1

This diff is too big to show here.

pkgs/applications/science/logic/hol_light/default.nix+22−17

This diff is too big to show here.

pkgs/applications/science/logic/isabelle/default.nix+2−2

This diff is too big to show here.

pkgs/applications/science/logic/jonprl/default.nix+1−1

This diff is too big to show here.

pkgs/applications/science/logic/lean/default.nix+2−2

This diff is too big to show here.

pkgs/applications/science/logic/lean2/default.nix+1−1

This diff is too big to show here.

pkgs/applications/science/logic/leo2/default.nix+1−1

This diff is too big to show here.

pkgs/applications/science/logic/lingeling/default.nix+49

This diff is too big to show here.

pkgs/applications/science/logic/ltl2ba/default.nix+2−2

This diff is too big to show here.

pkgs/applications/science/logic/matita/130312.nix−65

This diff is too big to show here.

pkgs/applications/science/logic/matita/Makefile.patch−11

This diff is too big to show here.

pkgs/applications/science/logic/matita/configure.patch−36

This diff is too big to show here.

pkgs/applications/science/logic/matita/configure_130312.patch−35

This diff is too big to show here.

pkgs/applications/science/logic/matita/default.nix−52

This diff is too big to show here.

pkgs/applications/science/logic/mcrl2/default.nix+4−5

This diff is too big to show here.

pkgs/applications/science/logic/monosat/default.nix+67

This diff is too big to show here.

pkgs/applications/science/logic/ott/default.nix+2−2

This diff is too big to show here.

pkgs/applications/science/logic/picosat/default.nix+3

This diff is too big to show here.

pkgs/applications/science/logic/poly/default.nix+13−10

This diff is too big to show here.

pkgs/applications/science/logic/potassco/clingo.nix+9−6

This diff is too big to show here.

pkgs/applications/science/logic/prooftree/default.nix+12−10

This diff is too big to show here.

pkgs/applications/science/logic/prover9/default.nix+1−1

This diff is too big to show here.

pkgs/applications/science/logic/proverif/default.nix+4−4

This diff is too big to show here.

pkgs/applications/science/logic/sad/default.nix+7−2

This diff is too big to show here.

pkgs/applications/science/logic/sad/monoid.patch+51

This diff is too big to show here.

pkgs/applications/science/logic/satallax/default.nix+1−1

This diff is too big to show here.

pkgs/applications/science/logic/saw-tools/default.nix+2−2

This diff is too big to show here.

pkgs/applications/science/logic/symbiyosys/default.nix+5−5

This diff is too big to show here.

pkgs/applications/science/logic/tamarin-prover/default.nix+24−9

This diff is too big to show here.

pkgs/applications/science/logic/tamarin-prover/ghc-8.4-support-term.patch+109

This diff is too big to show here.

pkgs/applications/science/logic/tamarin-prover/ghc-8.4-support-theory.patch+130

This diff is too big to show here.

pkgs/applications/science/logic/tamarin-prover/ghc-8.4-support-utils.patch+140

This diff is too big to show here.

pkgs/applications/science/logic/tlaplus/default.nix+40

This diff is too big to show here.

pkgs/applications/science/logic/tlaplus/tlaps.nix+54

This diff is too big to show here.

pkgs/applications/science/logic/tlaplus/toolbox.nix+77

This diff is too big to show here.

pkgs/applications/science/logic/tptp/default.nix+5−4

This diff is too big to show here.

pkgs/applications/science/logic/vampire/default.nix+59

This diff is too big to show here.

pkgs/applications/science/logic/verifast/default.nix+15−10

This diff is too big to show here.

pkgs/applications/science/logic/why3/default.nix+4−4

This diff is too big to show here.

pkgs/applications/science/logic/workcraft/default.nix+33

This diff is too big to show here.

pkgs/applications/science/logic/yices/default.nix+6−4

This diff is too big to show here.

pkgs/applications/science/logic/z3/4.5.0.nix−31

This diff is too big to show here.

pkgs/applications/science/logic/z3/default.nix+16−4

This diff is too big to show here.

pkgs/applications/science/machine-learning/labelimg/default.nix+23

This diff is too big to show here.

pkgs/applications/science/machine-learning/shogun/default.nix+19−11

This diff is too big to show here.

pkgs/applications/science/machine-learning/torch/torch-distro.nix+8−4

This diff is too big to show here.

pkgs/applications/science/math/R/default.nix+9−7

This diff is too big to show here.

pkgs/applications/science/math/almonds/default.nix+4−7

This diff is too big to show here.

pkgs/applications/science/math/bcal/default.nix+6−5

This diff is too big to show here.

pkgs/applications/science/math/bliss/default.nix+37

This diff is too big to show here.

pkgs/applications/science/math/caffe/darwin.patch+47

This diff is too big to show here.

pkgs/applications/science/math/caffe/default.nix+54−14

This diff is too big to show here.

pkgs/applications/science/math/calc/default.nix+34−32

This diff is too big to show here.

pkgs/applications/science/math/cbc/default.nix+4−4

This diff is too big to show here.

pkgs/applications/science/math/clp/default.nix+15−17

This diff is too big to show here.

pkgs/applications/science/math/cntk/default.nix+11−19

This diff is too big to show here.

pkgs/applications/science/math/cntk/fix_std_bind.patch+11

This diff is too big to show here.

pkgs/applications/science/math/colpack/default.nix+2−1

This diff is too big to show here.

pkgs/applications/science/math/cplex/default.nix+82

This diff is too big to show here.

pkgs/applications/science/math/csdp/default.nix+1−1

This diff is too big to show here.

pkgs/applications/science/math/ecm/default.nix+3−3

This diff is too big to show here.

pkgs/applications/science/math/form/default.nix+22

This diff is too big to show here.

pkgs/applications/science/math/fricas/default.nix+2−2

This diff is too big to show here.

pkgs/applications/science/math/gap/default.nix+70−15

This diff is too big to show here.

pkgs/applications/science/math/geogebra/default.nix+4−8

This diff is too big to show here.

pkgs/applications/science/math/gfan/default.nix+10−5

This diff is too big to show here.

pkgs/applications/science/math/giac/default.nix+37−11

This diff is too big to show here.

pkgs/applications/science/math/ginac/default.nix+4−3

This diff is too big to show here.

pkgs/applications/science/math/glsurf/default.nix+4−3

This diff is too big to show here.

pkgs/applications/science/math/gmsh/CMakeLists.txt.patch−37

This diff is too big to show here.

pkgs/applications/science/math/gmsh/default.nix+9−11

This diff is too big to show here.

pkgs/applications/science/math/gurobi/default.nix+54

This diff is too big to show here.

pkgs/applications/science/math/hmetis/default.nix+42

This diff is too big to show here.

pkgs/applications/science/math/jags/default.nix+7−7

This diff is too big to show here.

pkgs/applications/science/math/lp_solve/default.nix+2−2

This diff is too big to show here.

pkgs/applications/science/math/lrcalc/default.nix+41

This diff is too big to show here.

pkgs/applications/science/math/mathematica/10.nix+2−4

This diff is too big to show here.

pkgs/applications/science/math/mathematica/9.nix+2−4

This diff is too big to show here.

pkgs/applications/science/math/mathematica/default.nix+13−21

This diff is too big to show here.

pkgs/applications/science/math/mathematica/l10ns.nix+33

This diff is too big to show here.

pkgs/applications/science/math/maxima/default.nix+44−10

This diff is too big to show here.

pkgs/applications/science/math/maxima/known-ecl-failures.patch+21

This diff is too big to show here.

pkgs/applications/science/math/mxnet/default.nix+29−17

This diff is too big to show here.

pkgs/applications/science/math/nasc/default.nix+62

This diff is too big to show here.

pkgs/applications/science/math/nauty/default.nix+2−2

This diff is too big to show here.

pkgs/applications/science/math/palp/default.nix+86

This diff is too big to show here.

pkgs/applications/science/math/pari/default.nix+21−9

This diff is too big to show here.

pkgs/applications/science/math/pari/gp2c.nix+3−3

This diff is too big to show here.

pkgs/applications/science/math/pari/unstable.nix−31

This diff is too big to show here.

pkgs/applications/science/math/pspp/default.nix+13−2

This diff is too big to show here.

pkgs/applications/science/math/pynac/default.nix+48

This diff is too big to show here.

pkgs/applications/science/math/qalculate-gtk/default.nix+7−5

This diff is too big to show here.

pkgs/applications/science/math/ratpoints/default.nix+21−5

This diff is too big to show here.

pkgs/applications/science/math/ries/default.nix+21

This diff is too big to show here.

pkgs/applications/science/math/ripser/default.nix+4−3

This diff is too big to show here.

pkgs/applications/science/math/sage/README.md+117

This diff is too big to show here.

pkgs/applications/science/math/sage/default.nix+135−210

This diff is too big to show here.

pkgs/applications/science/math/sage/env-locations.nix+46

This diff is too big to show here.

pkgs/applications/science/math/sage/env.patch−22

This diff is too big to show here.

pkgs/applications/science/math/sage/fetch-mirrors.sh−11

This diff is too big to show here.