I think the fact that the right hand side of a dep specification can be either a repo (user/repo in github, url), or a version spec satisfied from a (single) registry, but not both, is a problem. I'd particularly like a tool that allows git repos to be used as package sources, with some convention about version tags allowing version dependency specs to be applied, and npm update to work.
Not sure about your solution, but I do have a suggestion - don't fork npm. Wrap it. You should be able to write a tool that implements your solution to this, calling npm when necessary to leverage its install capabilities, but not its decision making about where packages come from. Sam -- -- 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.
