Quoting Rick Waldron (2013-01-14 21:09:42)
> It's strange to me this is even an issue that's being argued, I would 
> assume that a Debian package maintainer would be responsible enough to 
> keep up with the latest stable releases of whatever they have taken on 
> to maintain.
> Back in the real-world, the biggest problem is that 0.6 and 0.8 use 
> completely different build systems, replacing waf with gyp (both for 
> building node and native modules). I'm sure you can appreciate and 
> respect the depth of this problem alone.
> Please review the changes (published 6 months ago):
> [1]https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8�

If the purpose of above was to contribute to move this bugreport 
forward, then you failed: It is not at all helpful to educate on how 
irresponsible maintainers are, how much of a dreamworld they live in, or 
for how long new upstream release have been out.

If the purpose was to provoke, then you succeeded.  Happy now?

What would help is elaborate on what renders Nodejs 0.6 branch unusable.

There is currently code in Debian that will potentially be rendered 
unusable by the upgrade, so it would be nice to know what would be the 
gain compared to such potential extra burden.

 - Jonas

 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: signature

Pkg-javascript-devel mailing list

Reply via email to