Am 15.02.26 um 15:38 schrieb Simon Josefsson:
> I'm happy to follow your suggested path, or the path suggested in
> earlier discussions (which I've been following so far), but would really
> like the choice to be written down so we get consistency in the process
> across the team.

+1

> I think both approaches have reasonable arguments, and (for me) this is
> mostly an aesthetic thing with no clear technically right or wrong.

I agree.

> I have a mild preference for letting golang-*-dev track latest upstream
> version because I think that matches how non-Go versioned libraries are
> usually maintained in Debian, but I'm happy to trade that preference for
> your approach if we can get team consensus to write it down in policy.

For me, the main argument *against* tracking the latest upstream version
is that you'd always need to fix all reverse dependencies and do a
mini-transition -- whereas you can just upload the new upstream version
with a new package name and suffix without breaking anything.

Moreover, using the -vX suffix for new versions would also match Go's
definition of module versions quite nicely. This is from Go's website,
documenting Go modules (https://go.dev/ref/mod#versions):

"Starting with major version 2, module paths must have a major version
suffix like /v2 that matches the major version. For example, if a module
has the path example.com/mod at v1.0.0, it must have the path
example.com/mod/v2 at version v2.0.0."

and:

"By definition, packages in a new major version of a module are not
backwards compatible with the corresponding packages in the previous
major version. Consequently, starting with v2, packages need new import
paths. This is accomplished by adding a major version suffix to the
module path."

This implies that every new major version of a module would most
probably need all reverse dependencies patched to be usable.

I think it would also be a cleaner approach to reflect the
XS-Go-Import-Path in the package name.

Regards,
Tobias

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to