Mathijs Kwik 0dd3996ab4 node-packages: upgrade coffee-script to 1.4.0 ... I'm not sure yet how to handle these upgrades. Should we keep the old version around? Should we only keep it around if other pkgs in nixpkgs depend on it? Probably people develop their own projects (that are not in nixpkgs) on top of these and we don't want to break these. For now, I think it's best just to keep old versions around, but update the (unversioned) link to the latest. External projects should then depend on explicit version numbers if they don't want stuff to break. If a certain package has +5 versions in nixpkgs, we can clear out the unuseful ones.		2012-10-31 08:39:05 +01:00
..
all-packages.nix	updated spring from 88 to 91 and downgraded the boost library which spring uses from default to 1.49 as the	2012-10-28 13:43:15 +00:00
guile-2-test.nix
haskell-defaults.nix	Add haskell-platform-2012.4.0.0 release candidate.	2012-10-03 21:12:46 +02:00
haskell-packages.nix	Add cabal-dev.	2012-10-30 09:03:53 +01:00
make-tarball.nix	* Include the Git shortrev in the version number.	2012-06-04 04:12:17 +00:00
mingw.nix
node-packages.nix	node-packages: upgrade coffee-script to 1.4.0	2012-10-31 08:39:05 +01:00
perl-packages.nix	perlPackages.NetSMTPTLS	2012-10-25 10:33:23 -04:00
platforms.nix	sheevaplug platform: Add hardware watchdog support	2012-10-04 13:11:13 +02:00
python-packages.nix	update boto to 2.6.0	2012-10-25 10:55:22 +02:00
release-cross.nix	Fixing mingw-w64 builds. I can build simple C++ programs with gccCrossStageFinal.	2012-05-24 22:07:23 +00:00
release-lib.nix
release-small.nix	automake: remove versions 1.7 and 1.9	2012-07-07 11:27:29 +02:00
release.nix	Make Firefox 16 the default	2012-10-23 15:35:48 +02:00