nixpkgs/pkgs/development/libraries/haskell/deepseq/1.3.0.1.nix

{ cabal }:

cabal.mkDerivation (self: {
  pname = "deepseq";
  version = "1.3.0.1";
  sha256 = "068zka6rwprbzpx7yisi1ajsxdly23zaf2vjklx1wp66yypx54lp";
  meta = {
    description = "Deep evaluation of data structures";
    license = self.stdenv.lib.licenses.bsd3;
    platforms = self.ghc.meta.platforms;
    maintainers = [ self.stdenv.lib.maintainers.andres ];
  };
})
Re-generated Haskell package descriptions with the latest version of cabal2nix. svn path=/nixpkgs/trunk/; revision=32327 2012-02-16 15:05:41 +01:00			`{ cabal }:`
haskell-deepseq: added version 1.3.0.0 svn path=/nixpkgs/trunk/; revision=32005 2012-02-03 20:06:38 +01:00
			`cabal.mkDerivation (self: {`
			`pname = "deepseq";`
haskell-deepseq: update to version 1.3.0.1 2012-09-10 14:21:42 +02:00			`version = "1.3.0.1";`
			`sha256 = "068zka6rwprbzpx7yisi1ajsxdly23zaf2vjklx1wp66yypx54lp";`
haskell-deepseq: added version 1.3.0.0 svn path=/nixpkgs/trunk/; revision=32005 2012-02-03 20:06:38 +01:00			`meta = {`
			`description = "Deep evaluation of data structures";`
			`license = self.stdenv.lib.licenses.bsd3;`
			`platforms = self.ghc.meta.platforms;`
Removed myself as a maintainer from Haskell packages that I don't personally use. 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 2012-03-24 11:21:28 +01:00			`maintainers = [ self.stdenv.lib.maintainers.andres ];`
haskell-deepseq: added version 1.3.0.0 svn path=/nixpkgs/trunk/; revision=32005 2012-02-03 20:06:38 +01:00			`};`
			`})`