npm permissions error

[Jeremy Lavergne]

> But we are in the business of adding portfiles for software in other package managers. We already do exactly that for perl (cpan), php (pear, pecl), etc. We don't want other package managers installing software into the MacPorts prefix, but that's exactly what "npm -g" (and cpan and pear and pecl) would do. That's why the npm port already prints a message explaining to users that the use of "npm -g" is discouraged. We already have ports for some things you can install with "npm -g", like jake and coffee-script. We should continue adding ports for other such software until nobody feels a need to run "npm -g". 

Why is MacPorts not actually controlling all these underling package managers? why can't we have MacPorts itself running 'npm -g' and tracking files from there?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 8796 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20120311/d00af963/attachment.bin>