3 ms·
For Go modules, does this order matter? Or another way, for MVS, does the order matter? What happens when p comes before o? What are the differences between m
by verdverm 5y ago
For Go modules, does this order matter?
Or another way, for MVS, does the order matter?
What happens when p comes before o? What are the differences between major and minor version updates?
- scrubs 5y agoIs there a command that elicits or demonstrates MVS. This page is good explaining what MVS is: https://research.swtch.com/vgo-mvs https://research.swtch.com/vgo-mvs Same with less detail (see bottom of page): https://encore.dev/guide/go.mod https://encore.dev/guide/go.mod
- verdverm 5y agoI suspect that it does not matter, because eventually you end up with the full list to decide MVS from. No proof on hand though I've implemented a generic (language independent) here https://github.com/hofstadter-io/hof/blob/_dev/lib/mod/modder/modder_vendor.go https://github.com/hofstadter-io/hof/blob/_dev/lib/mod/modde...
- scrubs 5y agoIn part to answer my own questions from https://golang.org/doc/modules/gomod-ref https://golang.org/doc/modules/gomod-ref We read: * ... * ... * A list of minimum versions of other modules required by the current module. * ... Meaning after running `go mod tidy` go.mod has that MVS build dependency list.