This issue seems to be getting a little muddled, Rick was pointing to issues that would affect relying on newer packages of Node.js for existing code bases that target 0.6.x; however as Node Package Manager (NPM) modules continue to evolve, in particular, and target the newer versions of node certain aspects become difficult to maintain for a 0.6.x author.
These issues involve: 1. Lack of support for some problems when using the WAF build system (and the purpose of moving to gyp covered in detail on node.js' mailing lists) 2. Misleading module support, due to default engine version. (see: `npm help json`'s engines field) 3. Documentation issues, missing direct links to docs on the nodejs.orgwebsite due to 0.8.x being the recommended stable release (use google to find em instead, and even then pick the right one?). 4. Various bug fixes that are not back ported. These do not break any existing code for node@0.6.x, however, they could introduce problems with maintenance, bug fixes, support, security, etc. Removing 0.6.x would be a problematic situation since there are breaking API changes, but it appears the original goal of this conversation was to include a 0.8.x package more than to remove the 0.6.x package entirely. I personally do not use the packages, but wished to clarify this since it seems to be terse conversation that leads to confusion on both ends. Jonas and Paul, can you clarify why those reasons are not encouraging, and/or a way to rephrase the original intent of the issue in a manner that is appropriate? It seems if a fork of 0.6.x was maintained and kept up to date with all the bug fixes this would be appropriate, but as documentation fixes and code fixes are not being back ported to 0.6.x it would be encouraging to know the route to take this issue. We have little wish to change your existing code, but would like to take the proper steps to update the package to a new version for both current and future reference. Thans for your patience, Bradley Meck
_______________________________________________ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel