Hi Simon and Arthur, On Tue, Sep 1, 2026 at 8:34 AM Simon Josefsson <[email protected]> wrote: > introduce -v6 packages just because. Sometimes upgrading a v4 to v6 > goes painlessly and there is just one or two reverse dependencies that > can easily be fixed. But when it doesn't, we are often stuck, and then
Yes, option 2 the best recommended practice to going forward. The major versioning as /v4, /v6 is just like soname versioning. We sometimes should keep both versions available in the Go Ecosystem in Debian if upstream are still keep maintaining both and applications are still using both. The status of both versions can be verify easily on https://pkg.go.dev. As we have been working on module-aware builds, we better to name the source/binary package name in a consisten way to avoid confusions and also make it work in both legacy GOPATH mode and Go Workspace mode in this stage. Best regards, -- -Andrew
