alioth/nixpkgs
3
0
Fork 0
forked from mirrors/nixpkgs
Code Releases Activity

node-packages: upgrade coffee-script to 1.4.0

Browse source 
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.
This commit is contained in:
Mathijs Kwik 2012-10-30 10:17:52 +01:00
parent 4b3d29003e
commit 0dd3996ab4
1 changed files with 13 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
pkgs/top-level/node-packages.nix
View file

@ -178,8 +178,8 @@ let self = {
];
};
"coffee-script" = self."coffee-script-1.3.3";
"coffee-script-~1" = self."coffee-script-1.3.3";
"coffee-script" = self."coffee-script-1.4.0";
"coffee-script-~1" = self."coffee-script-1.4.0";
"coffee-script-~1.1.2" = self.buildNodePackage rec {
name = "coffee-script-1.1.3";
@ -203,6 +203,17 @@ let self = {
];
};
"coffee-script-1.4.0" = self.buildNodePackage rec {
name = "coffee-script-1.4.0";
src = fetchurl {
url = "http://registry.npmjs.org/coffee-script/-/${name}.tgz";
sha256 = "146e8985d89210b63dae83378fd851ccf54d38d7d11cadcdca01520d50882613";
};
deps = [
];
};
"commander" = self."commander-~0.6.1";
"commander-~0.6.1" = self.buildNodePackage rec {