Old means that we have a newer version in Nixpkgs already. If there is a reason
for the old package to still exist, i.e. because some other package is still
referring to it, then Hydra will still build the package as a dependency, but
we won't want to build old packages on their own right.
By now, it happened twice that a commit broke GHC and thus all Haskell packages
we have in Nixpkgs. On such an occasion, I receive well in excess of 3000
notification e-mails from Hydra, and then I receive another 3000 e-mails after
the bug has been fixed. Under these circumstances, subscribing to these
notifications makes no sense for me.
svn path=/nixpkgs/trunk/; revision=33392
The new files ...
* conform to the coding guidelines,
* consistently specify meta.maintainers and meta.platforms,
* have proper descriptions and licenses as specified in their Cabal file, and
* take advantage of the new cabal.nix extensions, i.e. proper
distinction between buildInputs and propagatedBuildInputs.
Furthermore, the following updates were performed:
* haskell-Ranged-sets: updated to version 0.3.0
* haskell-Shellac-haskeline: updated to version 0.2.0.1
* haskell-cpphs: updated to version 1.12
* haskell-hslogger: updated to version 1.1.5
* haskell-xml: updated to version 1.3.9
* haskell-HDBC-postgresql: updated to version 2.3.2.0
* haskell-HDBC-sqlite3: updated to version 2.3.3.0
* haskell-HDBC: updated to version 2.3.1.0
* haskell-base-unicode-symbols: updated to version 0.2.2.1
* haskell-convertible: updated to version 1.0.11.0
* haskell-monad-control: updated to version 0.2.0.2
* haskell-murmur-hash: updated to version 0.1.0.4
* haskell-repa: updated to version 2.1.1.3
* haskell-statistics: updated to version 0.9.0.0
* haskell-ansi-terminal: updated to version 0.5.5
haskell-maybench was dropped, because it cannot be built with recent
versions of Cabal:
Configuring maybench-0.2.4.1...
Setup: At least the following dependencies are missing:
Cabal >=1.2 && <1.5
svn path=/nixpkgs/trunk/; revision=28446
