minimum version selection in golang

[Akash Kumar]

why minimum version selection has "minimum" as max versions are chosen for each module path ? 

[t hepudds]

Hi Akash,

My understanding is there were at least two reasons Minimal Version Selection was called "minimal".

First, it is "minimal" in the sense of being simpler and easier to predict, especially compared to traditional SAT-based approaches for version selection.

The second reason is described for example in the original Minimal Version Selection post (https://research.swtch.com/vgo-mvs):
  "Minimal version selection always selects the minimal (oldest) module version that satisfies the overall requirements of a build."

In other words, given 'require foo v1.0.0' and 'require foo v1.2.3', the minimal version that is sensible is the largest of those two versions —  v1.2.3 satisfies both 'require' directives, whereas v1.0.0 does not satisfy 'require foo v1.2.3'. Also, by default it does not select the most recently published version, which is common behavior for some other package managers in many cases.

That said, this mailing list is for discussing the development of Go itself. Questions like this are better posed to the golang-nuts mailing list or other places such as those listed here:
  https://go.dev/wiki/Questions
 
Regards,
--thepudds