On Fri, Jun 29, 2012 at 12:46 PM, Isaac Schlueter <[email protected]> wrote:
> > Why is trying to go back in history to find a version that matches so > > important? > > It's important because there is a much more common case than the one > you're describing: You write version 1.0 with node 0.6 in mind. Make > changes, updates, yadda yadda. Then 0.8 comes out, and you add > support for that. You release 2.0 with the engines setting on it. > > For a while, you may even be releasing updates to both the 1.0 and the > 2.0 versions! So, you'd prefer to have 0.6.x users get the 1.0.latest > and 0.8.x users get the 2.0.latest. > And this is why dependencies can specify "matts-module": "1.x". Sure, under this scheme they have to go and add that to their package.json, but at least they wouldn't get a broken version installed with a warning they are likely to ignore in the meantime. They would actually get npm erroring out and telling them about the problem. It seems to me that there's no perfect solution to this problem, but backtracking through versions is creating more problems than it solves. Are there *any* other packaging systems that do that? I can't think of one. Matt. -- 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
