4 ms·
I think this makes a lot of sense. I used to be a proponent of everything being a .deb or .rpm, but I've come to realize that certain things just can't be packa
by AdrianRossouw 14y ago
I think this makes a lot of sense. I used to be a proponent of everything being a .deb or .rpm, but I've come to realize that certain things just can't be packaged reliably on that level.
I know a whole slew of people who refuse to try out node.js because npm exists and they can't (well maybe 'really shouldnt') install those packages with apt-get.
I've yet to see a reliable up-to-date OS vendor distribution of node.js itself, much less all the packages.
- duskwuff 14y agoFrom what I understand, node.js packages are not, in most cases, intended to be installed systemwide. You can install them to a system directory (with the -g option), but by default, it assumes that you want to install to your current project, in the cwd.