Alternatives only work when the set are alternatives of a similar function.
Here the original name conflict concerned programs with completely different
concerns,
and it's been established that "node" is too generic a name - a name conflict
happened once
and will likely happen again when the Next
I think it's very unrealistic to mark this bug as invalid. Node.js is
used FAR more than the current 'node' package, and using update-
alternatives or similar would allow both of them to coexist. Not having
the 'node' executable present upon package installation is a source of
headache for nodejs a
** Changed in: nodejs (Ubuntu)
Status: Confirmed => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/nodejs/+question/244936
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nodejs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265045
Title:
Mak
Isn't nodejs-legacy available in ubuntu ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265045
Title:
Make /usr/bin/node available so shebang works
To manage notifications about this bug go to:
ht
