This reverts commit ec8b816154. The change told
the Cabal build system to use the hash-part of $out as the internal identifier
for the library it's building (rather than generating such an ID itself). While
a good idea in theory, this choice had an unfortunate side-effect: When Cabal
links libraries X, Y, and Z into an executable, then the generated binary
contains their respective IDs. Now, Nix finds those strings and treats them as
an indication that there is a *run-time dependency* on the corresponding store
paths. This means that the generated executable will always depend on the store
paths of all the Haskell libraries that went into it, even when linked
statically.
This commit removes all references to emacs24 with the exception of
emacs24-macports. The two folders in `pkgs/applications/editors` named
`emacs-24` and `emacs-24` are consolidated to a new `emacs` folder.
Various parts in nixpkgs also referenced `emacs24Packages` (pinned to
`emacs24`) explicitly where `emacsPackages` (non-pinned) is more
appropriate. These references get fixed by this commit too.
This update was generated by hackage2nix v2.0.1-9-g9d0fb31 using the following inputs:
- Hackage: d68983aeb2
- LTS Haskell: 36c0f4fa5e
- Stackage Nightly: 8b258a761d
The switch to LTS 7.x has made many older versions obsolete and so they
are no longer included in our package set by default:
- aeson-pretty 0.7.x
- hoogle 4.x
- persistent 2.2
- persistent-sqlite 2.2
- persistent-template 2.1
This update was generated by hackage2nix v2.0.1-8-g914b77b using the following inputs:
- Hackage: 3a577eda9a
- LTS Haskell: 36c0f4fa5e
- Stackage Nightly: 8b258a761d
It's my understanding that Emacs runs the "structured-haskell-mode" binary
virtually every time you press a key in an Haskell buffer, and since
dynamically linked Haskell binaries take *much* longer to start up, switching
this particular package to statically linked libraries ought to result in a
performance boost.
This update was generated by hackage2nix v2.0.1-8-g914b77b using the following inputs:
- Hackage: aa7348b0fd
- LTS Haskell: 56135ef31a
- Stackage Nightly: 8b7d8b236d
Configuring haste-compiler-0.5.5.0...
Setup: At least the following dependencies are missing:
HTTP -any,
bzlib -any,
either -any,
ghc-simple -any,
system-fileio -any,
tar -any
This update was generated by hackage2nix v2.0.1-7-g2231107 using the following inputs:
- Hackage: 3d791385a6
- LTS Haskell: 56135ef31a
- Stackage Nightly: a8a4229c98
This update was generated by hackage2nix v2.0.1-3-g27b56fd using the following inputs:
- Hackage: 535780cef6
- LTS Haskell: d7ece2dc93
- Stackage Nightly: 15c64f722e
This update was generated by hackage2nix v2.0.1 using the following inputs:
- Hackage: 0752bfd4f0
- LTS Haskell: e602b68df3
- Stackage Nightly: f7407f2e81
This update was generated by hackage2nix v2.0-23-ga0c4861 using the following inputs:
- Hackage: cfc500652f
- LTS Haskell: 8678a3c7f3
- Stackage Nightly: a0f3555d1f
This update was generated by hackage2nix v2.0-22-ga83e456 using the following inputs:
- Hackage: 729f27336e
- LTS Haskell: a23e74ee23
- Stackage Nightly: 4a0b9e146a
https://github.com/NixOS/nixpkgs/pull/17555 added an override that pins the
version of haskellPackages.hans to a specific Git revision. This means that any
version updates in the Haskell packages set will have no effect and that our
users will be stuck at that (arbitrary) version until the override is removed
again. Furthermore, it's bad practice to distribute a package dubbed as version
X when it's really version Y! The proper way to fix this issue IMHO is to
convince upstream to released a fixed version to Hackage.
This update was generated by hackage2nix v2.0-22-ga83e456 using the following inputs:
- Hackage: 352d6a176e
- LTS Haskell: a23e74ee23
- Stackage Nightly: 4a0b9e146a
This update was generated by hackage2nix v2.0-22-ga83e456 using the following inputs:
- Hackage: 07ee4666b6
- LTS Haskell: dfe21a3b8d
- Stackage Nightly: 7c2bfd83db
This update was generated by hackage2nix v2.0-18-g8001337 using the following inputs:
- Hackage: 0be8ef7fab
- LTS Haskell: d085132b77
- Stackage Nightly: 84fc6fbee7
This makes it easier to ensure that the list of stage 1 packages accurately matches the given version of ghcjs, and makes it possible for this list to be overridden
This update was generated by hackage2nix v2.0-18-g8001337 using the following inputs:
- Hackage: 690eda62e2
- LTS Haskell: d085132b77
- Stackage Nightly: 494d6bf80b
Previously, the stage2 information was stored in haskell-modules, and imported directly from there. However, the correct stage2 information is determined by the version of ghcjs-boot repository. This commit makes the stage2 information part of the ghcjs derivation, which improves organization and makes it possible to override stage2 when overriding ghcjs.
This update was generated by hackage2nix v2.0-18-g8001337 using the following inputs:
- Hackage: de00016925
- LTS Haskell: d085132b77
- Stackage Nightly: bf146896f3
These packages are broken in "haskellPackages" and have been for quite a while:
- disable goatee, goatee-gtk, and qtah-* (ping @khumba)
- disable persistent-mongoDB (ping @psibi)
This update was generated by hackage2nix v2.0-12-gb304101 using the following inputs:
- Hackage: b135e7a1de
- LTS Haskell: a5a99cf176
- Stackage Nightly: bf146896f3
This commit fixes a problem that occurs with externally linked haskell
libraries on Darwin. It does this by adding the libraries to the
--extra-lib-dirs flag and the DYLD_LIBRARY_PATH environment variable.
This update was generated by hackage2nix v2.0-11-gcec8f95 using the following inputs:
- Hackage: 19ec8f3a6d
- LTS Haskell: a5a99cf176
- Stackage Nightly: bf146896f3
This update was generated by hackage2nix v2.0-4-gb156b94 using the following inputs:
- Hackage: 5bb0a1b20f
- LTS Haskell: a5a99cf176
- Stackage Nightly: 3664752ea8
This update was generated by hackage2nix v2.0-2-g0bc3d6d using the following inputs:
- Hackage: d6d8323227
- LTS Haskell: 52eeaf4edc
- Stackage Nightly: 64dfa6aa2e
I've realized that publishing updates to Hackage is far easier than
publishing updates in Nixpkgs, and since all Hackage updates show up in
Nix automatically I've decided to go back to publishing cabal2nix on
Hackage again.
Unfortunately, this means that I'll have to change the version numbering
scheme to comply with the expectations of the Haskell PVP (which is used
by Stackage), so the new version 2.0 looks like a downgrade to Nix,
which used to have version 20160406. :-(
If in doubt, run "nix-env -u --always" to force the update. I am sorry
about the inconvenience.
This update was generated by hackage2nix v2.0-2-g0bc3d6d using the following inputs:
- Hackage: fcabbcc70b
- LTS Haskell: 52eeaf4edc
- Stackage Nightly: ff50bc1a46
This update was generated by hackage2nix v20160613-12-g1145e86 using the following inputs:
- Hackage: 8b1e5923b5
- LTS Haskell: 1c63caa7b8
- Stackage Nightly: 39da79aced
This update was generated by hackage2nix v20160613-12-g1145e86 using the following inputs:
- Hackage: 53b696d106
- LTS Haskell: 1c63caa7b8
- Stackage Nightly: affdd756e9
This update was generated by hackage2nix v20160613-11-g57dddc7 using the following inputs:
- Hackage: 6d525b6502
- LTS Haskell: 1c63caa7b8
- Stackage Nightly: b1d16f45de
The docs were split at #16167 and broke google support. @peti fixed
build, however hoogle still didn't see packages shipped with GHC. This
patch fixes location of the libraries shipped with GHC.
This update was generated by hackage2nix v20160613-7-g3089457 using the following inputs:
- Hackage: 08c95c9ddf
- LTS Haskell: 2a2cddb443
- Stackage Nightly: 5f88469291
ghcWithHoogle builds with this patch applied, but it's probably still broken in
the sense that links might point nowhere or that the generated databases and/or
documentation might be incomplete.
In line with the Nixpkgs manual.
A mechanical change, done with this command:
find pkgs -name "*.nix" | \
while read f; do \
sed -e 's/description\s*=\s*"\([a-z]\)/description = "\u\1/' -i "$f"; \
done
I manually skipped some:
* Descriptions starting with an abbreviation, a user name or package name
* Frequently generated expressions (haskell-packages.nix)
generic-stack-builder was not setting STACK_PLATFORM_VARIANT="nix".
This is required by stack when handling its haskell packages database
snapshot. Stack must keep separated packages built with its own GHC
and those built with GHC from Nixpkgs.
This update was generated by hackage2nix v20160613 using the following inputs:
- Hackage: b9e58743e7
- LTS Haskell: 2a2cddb443
- Stackage Nightly: 4b8c8abac5
Without this patch, attempts to install at least some of the packages
that start to use setupHaskellDepends (mostly gtk-related packages)
results in collisions:
building path(s) ‘/nix/store/63k5smns43f5r2ad8wcc242x0gwd70m3-ghc-8.0.1’
collision between `/nix/store/k18i1nm5hgnb82y9w2g9hmlwhk3szjld-ghc-8.0.1/lib/ghc-8.0.1/Cabal-1.24.0.0/Distribution/Compat/Binary.dyn_hi' and `/nix/store/0rwhbwsg9kmywgbrib2bs29p2hmi80za-Cabal-1.24.0.0/lib/ghc-8.0.1/Cabal-1.24.0.0/Distribution/Compat/Binary.dyn_hi'
builder for ‘/nix/store/vrjkfpm8sb96m9i5k74h8vn0rwddgy4v-ghc-8.0.1.drv’ failed with exit code 25
This would appear to me to be a consequence of setupHaskellDepends
entries being added to propagateBuildInputs. It is sufficient in the
cases I'm familiar with (taffyBar), and I think correct, to simply add
it to the otherBuildInputs.
Previously, the user could only compile using the default version of
GHC in Nixpkgs. Now this can be changed by setting the `ghc` attribute
appropriately.
The function "callHackage <name> <version>" generates build instructions for
the requested library version on-the-fly. All of Hackage is available. Note:
this code is brand-new, experimental, and it might change in the future. Don't
base production code on this feature yet.
Example usage:
$ nix-shell -p 'haskellPackages.callHackage "cpphs" "1.19.3" {}' --run "cpphs --version"
cpphs 1.19.3
$ nix-shell -p 'haskellPackages.ghcWithPackages (self: [(self.callHackage "hsdns" "1.6.1" {})])' --run "ghc-pkg list hsdns"
/nix/store/p6r81k2vb2pzy4wcvri6z9m492i0hg63-ghc-8.0.1/lib/ghc-8.0.1/package.conf.d
hsdns-1.6.1
This update was generated by hackage2nix v20160611 using the following inputs:
- Hackage: 8f99b2654a
- LTS Haskell: 1a80e0660e
- Stackage Nightly: 504ee2b3bb
This update was generated by hackage2nix v20160406-38-g2269395 using the following inputs:
- Hackage: 65d1dbe8dd
- LTS Haskell: 1a80e0660e
- Stackage Nightly: 5863aeaee3
Now we're releasing incomplete Hackage tarballs on purpose:
http://git-annex.branchable.com/bugs/bash_completion_file_is_missing_in_the_6.20160527_tarball_on_hackage/
You know, I'll fix this shit one last time, but on the next occasion
upstream breaks the build for no apparent reason, I'm going to abandon
this project and leave it to someone else to package, because these kind
of wacko engineering decisions cast a bad light on the soundness of
git-annex as a whole, IMHO.
This update was generated by hackage2nix v20160406-35-g2a2d30b using the following inputs:
- Hackage: 7a03eee484
- LTS Haskell: 1a80e0660e
- Stackage Nightly: 7e90e5529b
These overrides didn't work, because they created a mixture of different
versions of 'persistent' in the build tree. Furthermore, we cannot pin
specific versions like that in configuration-common.nix because this
breaks builds in other package sets, i.e. the LTS variants.
This update was generated by hackage2nix v20160406-31-gd9dda87 using the following inputs:
- Hackage: 4c643345f3
- LTS Haskell: 1a80e0660e
- Stackage Nightly: 3ba38d9d9e
This update was generated by hackage2nix v20160406-30-g704cd27 using the following inputs:
- Hackage: 5f6653ffd9
- LTS Haskell: 042ef2187b
- Stackage Nightly: a2b989788f
This update was generated by hackage2nix v20160406-28-g35f7635 using the following inputs:
- Hackage: 21e9bc8a5e
- LTS Haskell: 042ef2187b
- Stackage Nightly: 2f54d84973
