project3

Exploring Haskell packages

This section covers how to tweak Haskell packages that Nix builds (typically to fix failing builds).

Begin by running the following command to build the morte package:

$ nix-build '<nixpkgs>' --attr haskellPackages.morte
...
/nix/store/z8rf74cylf9dqj63yb8p3j37sn8n49zf-morte-1.6.2

nix-build creates a result symlink pointing to the built package. We can use tree to study the directory layout of the built package:

$ tree result
result
├── bin
│   └── morte
├── lib
│   └── ghc-8.0.1
│       ├── morte-1.6.2
│       │   ├── libHSmorte-1.6.2-9FIpoXNPAFhL3LxBszO4VO.a
│       │   ├── libHSmorte-1.6.2-9FIpoXNPAFhL3LxBszO4VO-ghc8.0.1.so
│       │   └── Morte
│       │       ├── Context.dyn_hi
│       │       ├── Context.hi
│       │       ├── Core.dyn_hi
│       │       ├── Core.hi
│       │       ├── Import.dyn_hi
│       │       ├── Import.hi
│       │       ├── Lexer.dyn_hi
│       │       ├── Lexer.hi
│       │       ├── Parser.dyn_hi
│       │       ├── Parser.hi
│       │       ├── Tutorial.dyn_hi
│       │       └── Tutorial.hi
│       └── package.conf.d
│           └── morte-1.6.2-9FIpoXNPAFhL3LxBszO4VO.conf
├── nix-support
│   └── propagated-native-build-inputs
└── share
    ├── doc
    │   └── x86_64-linux-ghc-8.0.1
    │       └── morte-1.6.2
    │           ├── html
    │           │   ├── doc-index.html
    │           │   ├── frames.html
    │           │   ├── haddock-util.js
    │           │   ├── hslogo-16.png
    │           │   ├── index-frames.html
    │           │   ├── index.html
    │           │   ├── mini_Morte-Context.html
    │           │   ├── mini_Morte-Core.html
    │           │   ├── mini_Morte-Import.html
    │           │   ├── mini_Morte-Lexer.html
    │           │   ├── mini_Morte-Parser.html
    │           │   ├── mini_Morte-Tutorial.html
    │           │   ├── minus.gif
    │           │   ├── Morte-Context.html
    │           │   ├── Morte-Core.html
    │           │   ├── morte.haddock
    │           │   ├── Morte-Import.html
    │           │   ├── Morte-Lexer.html
    │           │   ├── Morte-Parser.html
    │           │   ├── Morte-Tutorial.html
    │           │   ├── morte.txt
    │           │   ├── ocean.css
    │           │   ├── plus.gif
    │           │   ├── src
    │           │   │   ├── hscolour.css
    │           │   │   ├── Morte-Context.html
    │           │   │   ├── Morte-Core.html
    │           │   │   ├── Morte-Import.html
    │           │   │   ├── Morte-Lexer.html
    │           │   │   ├── Morte-Parser.html
    │           │   │   └── Morte-Tutorial.html
    │           │   └── synopsis.png
    │           └── LICENSE
    └── x86_64-linux-ghc-8.0.1
        └── morte-1.6.2
            ├── bench
            │   └── src
            │       ├── concat.mt
            │       ├── factorial.mt
            │       └── recursive.mt
            └── test
                └── src
                    ├── example0.mt
                    ├── example10.mt
                    ├── example11.mt
                    ├── example12.mt
                    ├── example13.mt
                    ├── example14.mt
                    ├── example15.mt
                    ├── example1.mt
                    ├── example2.mt
                    ├── example3.mt
                    ├── example4.mt
                    ├── example5.mt
                    ├── example6.mt
                    ├── example7.mt
                    ├── example8.mt
                    └── example9.mt

19 directories, 68 files

This package has a significantly more complex layout:

bin/

This directory stores any executable programs that the Haskell package produces. Nix does not require that derivations deposit executables in this directory, but Nix does specially integrate with packages that do use this directory for their executables. For example, if you use NixOS and you add a package to environment.systemPackages then the bin/ directory for the package is added to the system $PATH. Similarly, if you add a package as a buildInput to a Nix derivation, then any executables underneath bin/ are added to the $PATH of the derivation's build script.
lib/ghc-8.0.1/morte-1.6.2/

This contains all object code and interface files built by the Haskell library. By default, Nix generates both a static library (i.e. libHSmorte-1.6.2-9FIpoXNPAFhL3LxBszO4VO.a) and a dynamic library (i.e. libHSmorte-1.6.2-9FIpoXNPAFhL3LxBszO4VO-ghc8.0.1.so) for any Haskell package that provides a library section in the *.cabal file

By default, these libraries are compiled with GHC's -fsplit-objs flag to enable split object files, which reduces the library size but increases the compile time. This is another reason why I recommend building the root project using cabal during development because by default cabal won't compile with split objects and will therefore build faster. However, -fsplit-objs is a good default when Nix builds the project, so you don't need to change this setting.

Nix also stores a "singleton" GHC package database holding just one package such as package.conf.d/morte-1.6.2-9FIpoXNPAFhL3LxBszO4VO.conf. This is one difference between Nix and stack: stack uses up to three package databases (i.e. the global, snapshot, and project databases) whereas Nix uses a package database per package. In practice this difference usually doesn't matter, but for more exotic build scenarios (such as compiling different sets of packages with different flags) this gives Nix greater flexibility than stack.

nix-support/propagated-native-build-inputs

Anything which depends on the morte library must also depend on packages listed in nix-support/propagated-native-build-inputs. This is how Nix ensures that you are not missing any libraries when linking packages. For example, this is what the file looks like for morte:

cat result/nix-support/propagated-native-build-inputs 
     /nix/store/ifgkzb0df0d6378399hny3ry8x530wim-Earley-0.11.0.1 /nix/store/3q914v2ijfj26fv5w9hd07a6lcnr4d89-http-client-0.4.31.1 /nix/store/xp55z3bpf92yaswyd6s9ajzr44w5m1r7-http-client-tls-0.2.4.1 /nix/store/39a8f70x5j09jnixj6cwv9l0n6jdncwb-microlens-0.4.7.0 /nix/store/rqd01fgj53wyc627wvns94j68a5iza07-microlens-mtl-0.1.10.0 /nix/store/x0g5n6k09f6zga000w9y0z1hx4i9ryyx-pipes-4.1.9 /nix/store/gkg8jgn8f8if6j83jhz3v6i5nnqwg8vc-system-fileio-0.3.16.3 /nix/store/x8chw4wp9r4dapsjmbgsbs3blgnmsxy5-system-filepath-0.4.13.4 /nix/store/zx0yg2d5jxwpdig83qica8hq4mv5l0hx-text-1.2.2.1 /nix/store/l4w7l07k9hr1qrmj9772zk60scw5xa4n-text-format-0.3.1.1   /nix/store/0crlsp45jgs2bs50bv68klpdz1b1jpk9-optparse-applicative-0.12.1.0 /nix/store/zx0yg2d5jxwpdig83qica8hq4mv5l0hx-text-1.2.2.1

All of those paths are packages that morte depends on, each of which provides object code which must be linked into any executable that depends on morte

share/doc/x86_64-linux-ghc-8.0.1/morte-1.6.2/html

These are the generated haddocks for the project. You can open share/doc/x86_64-linux-ghc-8.0.1/morte-1.6.2/html/index.html in your browser to view morte's documentation
share/doc/x86_64-linux-ghc-8.0.1/morte-1.6.2/LICENSE

This is the project license
x86_64-linux-ghc-8.0.1/morte-1.6.2

These are extra data files bundled with the project for running tests and benchmarks. cabal includes these files because morte has the following line in the morte.cabal file:
```
Data-Files: bench/src/*.mt test/src/*.mt
```

Tweaking Haskell projects

You can customize what Nix includes in a built Haskell package using the pkg.haskell.lib suite of utilities. For example, release0.nix contains an example of disabling haddocks for the morte package:

let
  config = {
    packageOverrides = pkgs: rec {
      haskellPackages = pkgs.haskellPackages.override {
        overrides = haskellPackagesNew: haskellPackagesOld: rec {
          morte = pkgs.haskell.lib.dontHaddock haskellPackagesOld.morte;
        };
      };
    };
  };

  pkgs = import <nixpkgs> { inherit config; };

in
  { morte = pkgs.haskellPackages.morte;
  }

You can find the full list of pkgs.haskell.lib utilities in this file:

Utilities for tweaking Haskell packages

Some really convenient utilities include:

pkgs.haskell.lib.dontCheck - Disable tests (applies derivation option doCheck = false;)
pkgs.haskell.lib.appendPatch - Patch a Haskell package
pkgs.haskell.lib.overrideCabal - General tool for post-processing the output of cabal2nix

For example, this project is almost identical to the previous project except that instead of using Nix to test the executable we now add a test suite to our Haskell package that tests our TAR code in Test.hs:

{-# LANGUAGE OverloadedStrings #-}

module Main where

import Control.Applicative (empty)
import qualified Project3
import qualified Turtle

main :: IO ()
main = do
    Turtle.touch "example"
    Turtle.procs "bsdtar" ["cf", "example.tar", "example"] empty
    Project3.check

For whatever reason we use bsdtar instead of tar because we are gluttons for punishment.

The project3.nix file generated by cabal2nix has no idea that our test suite depends on bsdtar so if we were to build and run the Haskell project without any modifications the test suite would fail due to a missing bsdtar executable.

However, our release1.nix file shows how we can tweak our project to include bsdtar (provided by libarchive) for the test suite:

let
  config = {
    packageOverrides = pkgs: rec {
      haskellPackages = pkgs.haskellPackages.override {
        overrides = haskellPackagesNew: haskellPackgesOld: rec {
          project3 =
            pkgs.haskell.lib.overrideCabal
              ( haskellPackagesNew.callPackage ./project3.nix {
                  tar = pkgs.libtar;
                }
              )
              ( oldDerivation: {
                  testToolDepends = [ pkgs.libarchive ];
                }
              );
        };
      };
    };
  };

  pkgs = import <nixpkgs> { inherit config; };

in
  { project3 = pkgs.haskellPackages.project3;
  }

This uses the pkgs.haskell.lib.overrideCabal which is the most general utility for tweaking derivations generated by cabal2nix. You can find the full set of fields that we can use to extend the cabal2nix code at the top of this file:

Haskell generic builder

These are also the same fields that you will see in an expression generated by cabal2nix, such as executableHaskellDepends or isLibrary. overrideCabal lets you tweak any field you see in that list.

If you build and run the release1.nix project you will see that the test suite runs and passes, indicating that our code works with TAR files generated by bsdtar:

$ nix-build --attr project3 release1.nix these derivations will be built:
  /nix/store/i7i38jx93qwxzwg9xakbd8lrfv9kbpi4-project3-1.0.0.drv
building path(s) ‘/nix/store/2z661k6rnwyiimympn1anmghdybi7izc-project3-1.0.0’
...
Building project3-1.0.0...
Preprocessing library project3-1.0.0...
[1 of 1] Compiling Project3         ( Project3.hs, dist/build/Project3.o )
Preprocessing executable 'project3' for project3-1.0.0...
[1 of 2] Compiling Project3         ( Project3.hs, dist/build/project3/project3-tmp/Project3.dyn_o )
[2 of 2] Compiling Main             ( Main.hs, dist/build/project3/project3-tmp/Main.dyn_o )
Linking dist/build/project3/project3 ...
Preprocessing test suite 'test' for project3-1.0.0...
[1 of 2] Compiling Project3         ( Project3.hs, dist/build/test/test-tmp/Project3.dyn_o )
[2 of 2] Compiling Main             ( Test.hs, dist/build/test/test-tmp/Main.dyn_o )
Linking dist/build/test/test ...
running tests
Running 1 test suites...
Test suite test: RUNNING...
Test suite test: PASS
Test suite logged to: dist/test/project3-1.0.0-test.log
1 of 1 test suites (1 of 1 test cases) passed.
...
/nix/store/2z661k6rnwyiimympn1anmghdybi7izc-project3-1.0.0

Minimizing the closure

In Nix, a package "closure" is the set of all transitive dependencies for that package. Haskell packages built using Nix have a very large closure because they all depend on ghc, which is a very large package.

For example, release2.nix contains an example of building a docker container for the project3 executable before and after closure minimization:

let
  config = rec {
    packageOverrides = pkgs: rec {
      docker-container-large = pkgs.dockerTools.buildImage {
        name = "project3-container";
        config.Cmd = [ "${haskellPackages.project3}/bin/project3" ];
      };

      docker-container-small = pkgs.dockerTools.buildImage {
        name = "project3-container";
        config.Cmd = [ "${haskellPackages.project3-minimal}/bin/project3" ];
      };

      haskellPackages = pkgs.haskellPackages.override {
        overrides = haskellPackagesNew: haskellPackgesOld: rec {
          project3 =
            pkgs.haskell.lib.overrideCabal
              ( haskellPackagesNew.callPackage ./project3.nix {
                  tar = pkgs.libtar;
                }
              )
              ( oldDerivation: {
                  testToolDepends = [ pkgs.libarchive ];
                  enableSharedExecutables = false;
                }
              );

          project3-minimal =
            pkgs.haskell.lib.overrideCabal
              ( pkgs.haskell.lib.justStaticExecutables
                  ( haskellPackagesNew.callPackage ./project3.nix {
                      tar = pkgs.libtar;
                    }
                  )
              )
              ( oldDerivation: {
                  testToolDepends = [ pkgs.libarchive ];
                }
              );
        };
      };
    };
  };

  pkgs = import <nixpkgs> { inherit config; system = "x86_64-linux"; };

in
  { project3 = pkgs.haskellPackages.project3;

    project3-minimal = pkgs.haskellPackages.project3-minimal;

    docker-container-small = pkgs.docker-container-small;

    docker-container-large = pkgs.docker-container-large;
  }

If you build the docker-container-large attribute you will get a container that contains the entire closure of the project03 project, including a complete ghc installation. This is because project03 is dynamically linked and depends on several dynamic libraries that are packaged with ghc. The final container is over 250 MB compressed and 1.5 GB uncompressed.

$ nix-build --attr docker-container-large release2.nix 
...
building path(s) ‘/nix/store/ml441hr1l5gw9piq8ysnjdaazjxapsci-project3-container.tar.gz’
Adding layer
Adding meta
Cooking the image
/nix/store/ml441hr1l5gw9piq8ysnjdaazjxapsci-project3-container.tar.gz
$ du -hs $(readlink result)
251M	/nix/store/ml441hr1l5gw9piq8ysnjdaazjxapsci-project3-container.tar.gz

If you build the docker-container-small attribute you will get a much smaller container that is only 11 MB compressed and 27 MB uncompressed:

$ nix-build --attr docker-container-small release2.nix 
...
building path(s) ‘/nix/store/3mkrcqjnqv5vwid4qcaf3p1i70y87096-project3-container.tar.gz’
Adding layer
Adding meta
Cooking the image
/nix/store/3mkrcqjnqv5vwid4qcaf3p1i70y87096-project3-container.tar.gz
$ du -hs $(readlink result)
11M	/nix/store/3mkrcqjnqv5vwid4qcaf3p1i70y87096-project3-container.tar.gz
$ docker load -i result
73bcfb39a3b5: Loading layer [==================================================>]   27.8MB/27.8MB
$ docker run -it project3-container
tar_open failed

This works thanks to the justStaticExecutables utility, which statically links the built executable and removes other unnecessary directories from the built package.

The combination of these two things significantly slims down the dependency tree. We can verify this using the handy nix-store --query --requisites command which lets you view all transitive dependencies for a given Nix package.

Before the closure minimization, we get this dependency tree:

$ nix-build --attr project3 release2.nix these derivations will be built:
...
/nix/store/1nc7kaw3lp574hhi2bfxdb490q5kp2m8-project3-1.0.0

$ nix-store --query --requisites result
/nix/store/jm1n87rp8vr90j9ahcrfzr57nc2r8vgf-glibc-2.24
/nix/store/6sp63j6m6vyspqm2d7zw15ipiym70kzc-attr-2.4.47
/nix/store/03a2gwqj26hidgqsczpvk0g65p5fbhrs-attr-2.4.47-bin
/nix/store/28wl3f34vfjpw0y5809bgr6382wqdscf-bash-4.3-p48
/nix/store/24ln24075d8i5nq1sg558y667pyijx65-ghc-8.0.1-doc
/nix/store/1rhcwhq2f8kkq01wrrr4w210n31iyq10-lzo-2.09
/nix/store/81n6pgrx7lq5f7cjajv82wa422ccvbv4-openssl-1.0.2j
/nix/store/8jwqlpyxp5c2rl5g7yspdfbh58dsciwx-xz-5.2.2
/nix/store/ci7bn61pfds1y1ijkf3c85il0jdp87ar-acl-2.2.52
/nix/store/isl3g7jbrl9a1kdljiyzvjjsqnmn060r-bzip2-1.0.6.0.1
/nix/store/wz7l2zqdsa78jxnzkigv5gy2c7hxnbxh-zlib-1.2.8
/nix/store/mh7n2d60dy0bj5qhhgwhn55skbsqcnsz-libxml2-2.9.4
/nix/store/7crpicyhj61dkqa402f6m3fmb8iy23bn-libarchive-3.2.2-lib
/nix/store/p4ks7972lzhqq9rcyc837c0a9ms2qspr-acl-2.2.52-bin
/nix/store/fsxgigm2yb6xp3axxh342cx04kxrijg1-acl-2.2.52-dev
/nix/store/igwsyzqig15qzgacq35vqdxsj0v3k1ba-attr-2.4.47-dev
/nix/store/q4f9n8vv030pddpg1y2v5p38g0rkmffy-libarchive-3.2.2
/nix/store/41zm7hyzc6qs2fzw2j2fs6c1j9bw7nfm-libarchive-3.2.2-dev
/nix/store/djd2r4cnbcx4vfbj1qalg85vjbcslwxv-gcc-5.4.0-lib
/nix/store/6xiq93r3dnny4m7svvb6hvq9qwjrixk8-gmp-6.1.1
/nix/store/8rn45r9ndfq5h7mx58r35p2szky5ja6n-coreutils-8.25
/nix/store/5kkjn2h1m852q8xh5kz0kfgi5nrbc1fz-perl-5.22.2
/nix/store/321k7mdjv4fwf1rfss1r7nayni18iqaw-glibc-2.24-bin
/nix/store/ppjqx7j8w22j0pahnq4gnzhk4vmibncn-pcre-8.39
/nix/store/h9aqgpgspgjhygj63wpncfzvz5ys851n-gnugrep-2.25
/nix/store/1q6v2661bkkzjx48q4n1d3q2ahlsha9q-linux-headers-4.4.10
/nix/store/idwrh4bm5s4lnnb03d1j2b2rqg9x42h6-glibc-2.24-dev
/nix/store/nm9r5lymydnsrlxjn30ym2kix6mbyr19-binutils-2.27
/nix/store/wb8x0kjry7xvh4jqlx391lr0bffqrzhz-gcc-5.4.0
/nix/store/yn4s58frawcqxcid79npmy2aq8cxcjj1-gcc-5.4.0-man
/nix/store/dp2nf60lqzy1kbhd78ndf5nm3fb3qicd-gcc-wrapper-5.4.0
/nix/store/glhpbq9nhyrrzzbnbdg41vn9h717rrr7-gmp-6.1.1-dev
/nix/store/gz5ph3m624zivi687zvy82izi2z39aik-ncurses-6.0
/nix/store/ff3h3dl87xl0q99b963xpwxacsqaqb43-ncurses-6.0-man
/nix/store/i3hxdbjgbagyslsqnfl7zkpnn6q32hxv-ncurses-6.0-dev
/nix/store/dg7ak1hvlj66vgn4fwvddnnr4pfncd04-ghc-8.0.1
/nix/store/pb3jxhy4z54i24i9s0kyszdmxd2xajc5-libtar-1.2.20
/nix/store/1nc7kaw3lp574hhi2bfxdb490q5kp2m8-project3-1.0.0

After closure minimization we get this dependency tree:

$ nix-build --attr project3-minimal release2.nix 
...
/nix/store/i4fypk5m0rdwribpwacdd1nbzbfqcnpc-project3-minimal
$ nix-store --query --requisites result
/nix/store/jm1n87rp8vr90j9ahcrfzr57nc2r8vgf-glibc-2.24
/nix/store/djd2r4cnbcx4vfbj1qalg85vjbcslwxv-gcc-5.4.0-lib
/nix/store/6xiq93r3dnny4m7svvb6hvq9qwjrixk8-gmp-6.1.1
/nix/store/pb3jxhy4z54i24i9s0kyszdmxd2xajc5-libtar-1.2.20
/nix/store/i4fypk5m0rdwribpwacdd1nbzbfqcnpc-project3-minimal

Much smaller! Note that the executable is still not fully statically linked. Only the Haskell dependencies have been statically linked. Most of the remaining space is due to using glibc:

$ du -hs /nix/store/jm1n87rp8vr90j9ahcrfzr57nc2r8vgf-glibc-2.24/
23M	/nix/store/jm1n87rp8vr90j9ahcrfzr57nc2r8vgf-glibc-2.24/

The actual project3 executable is tiny in comparison:

$ du -hs /nix/store/i4fypk5m0rdwribpwacdd1nbzbfqcnpc-project3-minimal
788K	/nix/store/i4fypk5m0rdwribpwacdd1nbzbfqcnpc-project3-minimal

If we wanted to get the size down further we'd need to use something like musl instead of glibc.

Conclusion

This concludes the section on exploring and customizing Haskell packages. The next section covers simplified dependency management.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

README.md

Exploring Haskell packages

Tweaking Haskell projects

Minimizing the closure

Conclusion

Name		Name	Last commit message	Last commit date
parent directory ..
cbits		cbits
LICENSE		LICENSE
Main.hs		Main.hs
Project3.hs		Project3.hs
README.md		README.md
Test.hs		Test.hs
project3.cabal		project3.cabal
project3.nix		project3.nix
release0.nix		release0.nix
release1.nix		release1.nix
release2.nix		release2.nix

FilesExpand file tree

project3

Directory actions

More options

Directory actions

More options

Latest commit

History

project3

Folders and files

parent directory

README.md

Exploring Haskell packages

Tweaking Haskell projects

Minimizing the closure

Conclusion