Hi Leo,
On Wed Feb 5, 2025 at 11:31 AM CET, Leo Famulari wrote: > On Wed, Feb 5, 2025, at 03:05, Tanguy LE CARROUR wrote: >> but I also had to update one of its dependency: >> `go-git-sr-ht-rjarry-go-opt`. >> It’s a major update to `2.0.1` so I created a new >> `go-git-sr-ht-rjarry-go-opt-v2` >> inheriting from `go-git-sr-ht-rjarry-go-opt`… but realized that >> `go-git-sr-ht-rjarry-go-opt` was only used by `aerc`. >> >> Is it any use to create a new package? Should I just update the existing one? >> Should I rename it? Create a new one? … so many questions!! 😱 > > You should update the existing package. No need to rename it. > > Treat it like any other library package. It would be more complicated if it > had more than one user. That makes total sense to me! Thanks! But… > Any other questions? :) Yes! 😁 But Oleg made a comment that also make total sense: > 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? -- Tanguy
