Hi, not having /usr/bin/node as nodejs binary path will without any doubt render nodejs package unuseful for a vast majority of users. It simply makes them use another package than the one in debian, and most of them, if not all, don't even take care of the possibility of name conflict between /sbin/node and /usr/bin/node. If the renaming is unavoidable, then nodejs package is better off debian, along with all modules and dependent software : we'll just have to maintain it in another repository. It's like renaming /usr/bin/ruby to /usr/bin/rubyrb.
That's the *main* reason why nodejs has been removed from testing, the other being it was already obsolete. Package 0.2.0-1 explained in README.Debian it was the user responsibility to symlink /usr/local/bin/node to /usr/bin/nodejs, which does not solve the conflict with /sbin/node in any way, and in my opinion leads to a worse situation; except that it complied with debian policy. Note that for now, nodejs 0.2.6-1 is in *experimental*, which means we have to solve the conflict problem, and only then it will go to unstable. In the meantime, i agree these matters deserves a proper explanation in README.Debian. Jérémy Lal -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
