Hi all, It's been a bit tricky to track how vgo/Go 1.11 modules have evolved since the first vgo blog series and since the official proposal was published.
To help with that, I tried to put together a list of some of the larger user-facing changes in approach that happened after the first vgo blog was published. I think there might be > 400 related GitHub issues at this point, so I'm not aiming for an exhaustive list, but rather trying to hit some of the highlights. I'm sharing that list with this group in case it is helpful, but I'm also hoping for any quick commentary from the community on other large changes that might not be listed here yet. (Also, there's a better version of this list that I put on the "Modules" wiki, where that version of this list has a bunch of hyperlinks to related discussions/CLs/issues for each bullet. The HTML version of this list is here: https://github.com/golang/go/wiki/Modules#changes-since-the-initial-vgo-proposal ). Any quick comments/corrections/additions? ---------------------------------------------------------------- Larger Changes Since Initial vgo Announcement ---------------------------------------------------------------- 1. Top-level vendor support was retained rather than vgo-based builds ignoring vendor directories entirely 2. Backported minimal module-awareness to allow older Go versions 1.9.7+ and 1.10.3+ to more easily consume modules for v2+ projects 3. Allowed consuming pre-existing packages with v2+ tags that don't yet have a go.mod (initial vgo would not use v2+ tags on a project without a go.mod) 4. Added support via command go get -u=patch to update all transitive dependencies to the latest available patch-level versions on the same minor version 5. Additional control via environmental variables (e.g., GOFLAGS in #26585) 6. Added more flexible replace directives 7. Added additional ways to interrogate modules (for human consumption, as well as for better editor / IDE integration) 8. The UX of the go CLI has continued to be refined based on experiences so far (e.g., #26581) 9. Most likely: additional support for warming caches for use cases such as CI or docker builds (#26610) 10. Most likely: better support for installing specific versions of programs to GOBIN (#24250) --thepudds -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
