On Thu, Feb 06, 2025 at 09:35:49AM +0100, tan...@bioneland.org wrote: > > Yes it has V2 in import path > > https://git.sr.ht/~rjarry/go-opt/tree/main/item/go.mod#L1 > > > > So the common logic is to inherit and create new package variant. > > gnu packages golang-* contains a lot of examples of that, feel free > > to take look. > > […] > > The package variable name should follow go.mod import path, > > the first line of that file. > > And the module is definitively name `git.sr.ht/~rjarry/go-opt/v2`. > > So now I would, update and rename. > > WDYT?
Right. In Go, the versioned URLs constitute an API break. Effectively a new package. Basically, Go uses URLs as canonical package names throughout the entire ecosystem, from fetching from the internet, building, and referring to as libraries. So if the URL changes, it's no longer the same package from the perspective of the authors. Does that make sense?
