On 11/11/2013 16:41, Andrew Kelley wrote: > > > On Monday, November 11, 2013 9:46:17 AM UTC-5, Matt Sergeant wrote: > > Changing the binary name isn't required at all. > > What should be done is for applications in npm (e.g. things like Haraka), > npm should transparently fix up the path in shebang lines to whatever node is > being used to perform the installation. > > This is what Perl's CPAN does. And it resolves the issue of having > multiple node versions installed. > > And obviously Debian will have to fix any shebang lines in dpkgs it > offers of node-based apps. > > > That's a great idea! npm already adds node_modules/.bin to PATH when > executing scripts. It makes sense to also get "node" to resolve to the > correct binary at this time. If it has some directory such as ~/.npm/path/ > where it puts a softlink node -> nodejs if applicable, this would fix all the > scripts in package.json. I've created an issue in npm for this: > https://github.com/isaacs/npm/issues/4116 > > If Isaac gives his blessing I'll go ahead and make a pull request.
Note that sometimes "node" is used also in Makefile, in package.json, or shell scripts. This approach looks risky to me (and that's why i didn't do it). Jérémy. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
