nixpkgs/pkgs/development/libraries/haskell/extensible-exceptions/0.1.1.4.nix

{ cabal }:

cabal.mkDerivation (self: {
  pname = "extensible-exceptions";
  version = "0.1.1.4";
  sha256 = "1273nqws9ij1rp1bsq5jc7k2jxpqa0svawdbim05lf302y0firbc";
  meta = {
    description = "Extensible exceptions";
    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 14:05:41 +00:00			`{ cabal }:`
haskell-extensible-exceptions: added version 0.1.1.4 svn path=/nixpkgs/trunk/; revision=32006 2012-02-03 19:06:41 +00:00
			`cabal.mkDerivation (self: {`
			`pname = "extensible-exceptions";`
			`version = "0.1.1.4";`
			`sha256 = "1273nqws9ij1rp1bsq5jc7k2jxpqa0svawdbim05lf302y0firbc";`
			`meta = {`
			`description = "Extensible exceptions";`
			`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 10:21:28 +00:00			`maintainers = [ self.stdenv.lib.maintainers.andres ];`
haskell-extensible-exceptions: added version 0.1.1.4 svn path=/nixpkgs/trunk/; revision=32006 2012-02-03 19:06:41 +00:00			`};`
			`})`