Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think you might have a small typo here:

> by choosing the lowest version specified in any package that depends on a given package

It picks the highest version specified in any of the requirements. (That's the minimal version that simultaneously satisfies each individual requirement, where each individual requirement is saying "I require vX.Y.Z or higher". So if A requires Foo v1.2.3 and B requires Foo v1.2.4, v1.2.4 is selected as the minimal version that satisfies both A and B, and that's true even if v1.2.5 exists).



Yep, I regrettably described the system wrong. It’s the highest version specified, and thus minimum version possible.


That's a nice & concise way to describe it.


Minimalistic Version Selection might have been a better term for it.

That did confuse me a lot. Selecting the maximum makes a lot more sense, since that gets SemVer assumptions correct.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: