(and from Hydra). It is still possible to install any of those packages by
referring to them by attribute:
| $ nix-env -iA haskellPackages_ghc6104.hopenssl --dry-run
| (dry run; not doing anything)
| installing `haskell-hopenssl-ghc6.10.4-1.6.1'
| these paths will be fetched (50.61 MiB download, 450.34 MiB unpacked):
| /nix/store/rjsgga1fdqin47n2rkfn9l7v9ncsfh9l-haskell-hopenssl-ghc6.10.4-1.6.1
| /nix/store/y567qhqbjxbkldg3kq2clzn52a56cmdn-haskell-mtl-ghc6.10.4-1.1.0.2
| /nix/store/zbn24z1443fbrx6ch1nn2vnss9bdw1g0-ghc-6.10.4
It's no longer possible to install those by name anymore, though:
| $ nix-env -i haskell-hopenssl-ghc6.10.4
| error: selector `haskell-hopenssl-ghc6.10.4' matches no derivations
That style works only for active GHC versions 7.4.2 and 7.6.2:
| $ nix-env -qaP \* | grep haskell-hopenssl
| haskellPackages.hopenssl haskell-hopenssl-ghc7.4.2-1.6.1
| haskellPackages_ghc742_no_profiling.hopenssl haskell-hopenssl-ghc7.4.2-1.6.1
| haskellPackages_ghc742_profiling.hopenssl haskell-hopenssl-ghc7.4.2-1.6.1-profiling
| haskellPackages_ghc762.hopenssl haskell-hopenssl-ghc7.6.2-1.6.1
These changes intend to ease the load on Hydra. If you desperately need
pre-build binaries of any of those old versions, please post a short note
on the nix-dev mailing list.
Now in x-updates as well.
Conflicts (auto-solved):
pkgs/top-level/all-packages.nix
The use case is to do a deep replacement of a dependency without rebuilding the entire tree.
For example, suppose a security hole is found in glibc and a patch released. Ideally, you'd
just rebuild everything, but that takes time, space, and CPU that you might not have, so in
the mean time you could build a safe version of, say, firefox with:
firefox-safe = replace-dependency { drv = firefox; old-dependency = glibc; new-dependency = patched-glibc; };
Building firefox-safe will rebuild glibc, but only do a simple copy/string replacement on all other dependencies
of firefox. On my system (MBP 13" mid-2012), after a new glibc had been build building firefox took around 11 seconds.
See the comments in the file for more details.
