Nix Packages collection & NixOS

hacktoberfestlinuxnixnixosnixpkgs

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
doc	Fix link	2012-10-18 10:10:49 -04:00
maintainers	svn path=/nixpkgs/trunk/; revision=32961	2012-03-09 17:53:04 +00:00
pkgs	node-packages: upgrade coffee-script to 1.4.0	2012-10-31 08:39:05 +01:00
.gitignore	Tell git to ignore .*.swp - Vim swap files	2012-10-04 11:27:57 +04:00
COPYING	* Applying an MIT-style license to Nixpkgs.	2006-04-25 16:50:34 +00:00
default.nix	* For convenience, provide a top-level Nix expression that simply	2007-04-26 14:32:57 +00:00
VERSION	* Bump version number.	2012-06-04 03:53:25 +00:00