When building `reflex-dom` for GHCJS, the following dependencies are not
needed and will fail to build: glib, gtk3, webkitgtk3,
webkitgtk3-javascriptcore. Now we explicitely need the dependencies
needed for building for GHCJS.
This also:
1 Builds Setup.hs with ghcjs, which (among other things) defines
__GHCJS__ and ghcjs_HOST_OS during pre-processing.
2 Fixes ghc-paths to point at ghcjs and use NIX_GHCJS_* env-vars.
3 Boots ghcjs into $prefix/lib/$compiler.
wpa_supplicant 2.4 appears to have a serious bug that makes impossible
to use wifi for some number of people.
(See https://bbs.archlinux.org/viewtopic.php?id=196584 for an example)
It was resolved in a patch for the to-be-released 2.5 which it seemed
worth it to cherry-pick here.
In c0d5cd0ff90cac2e04f6b436991baa4c4471150f, the binaries for poppler
were carved off into a separate package, and calibre has had broken pdf
support since. This changes all dependencies on poppler to
poppler_utils, which fixes this support, much as was done for
cups_filter in 394562655ff09ef490eca8b14fe02c393e9ac70e.
This reverts commit d170c98d13a7b622c57c9b9f727a6bfec95a9181.
niksnut argues that we need smaller system closures, not bigger.
So users facing the trouble of getting gcc rebuilds after nix-collect-garbage
for any minimal nixos configuration change should use other means of
not losing the stdenv output.
One way is to keep one somewhere: nix-build -A stdenv -o stdenv '<nixpkgs>'.
Another may be to use nix.conf options like gc-keep-outputs, gc-keep-derivations
or env-keep-derivations.
This will help a lot on ARM, where nix-collect-garbage erases gcc; then, any
change to a small system config file requires rebuilding gcc again.
I don't know why it does not happen on x86. Maybe it just pulls the gcc from
hydra, if garbage is collected.
It boots, but some things still don't work:
1) Installation of DTBs
2) Boot of initrd
Booting still needs a proper config.txt in /boot, which could probably be
managed by NixOS.
