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
..
applications	Update/fix PuTTY	2012-10-30 12:49:43 +04:00
build-support	Remove deprecated option --ephemeral from fetchdarcs	2012-10-22 15:02:33 +02:00
data	xkeyboard-config; Update to 2.7	2012-09-26 15:51:57 -04:00
desktops	Fix waf env python to ${python}/bin/python	2012-10-23 19:40:46 +02:00
development	smatch: add dependency on Perl	2012-10-30 17:15:26 +01:00
games	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
lib	Make Firefox 16 the default	2012-10-23 15:35:48 +02:00
misc	jackaudio: Add extra download URL. Main site seems down.	2012-10-18 14:17:21 +02:00
os-specific	Update Bluez/Obex	2012-10-29 23:56:26 +04:00
servers	zabbix: Update to 1.8.15	2012-10-26 16:23:30 +02:00
shells	bash-completion: remove NixOS-specific patch	2012-10-16 18:26:02 +02:00
stdenv	The loongson2f bootstrap files were already at nixos.org.	2012-10-25 23:22:41 +02:00
test
tools	Update Bluez/Obex	2012-10-29 23:56:26 +04:00
top-level	node-packages: upgrade coffee-script to 1.4.0	2012-10-31 08:39:05 +01:00