Andrew Lee <[email protected]> writes: > Hi Otto, > > On Mon, Sep 7, 2026 at 12:54 PM Otto Kekäläinen <[email protected]> wrote: >> Personally I feel it does not make sense to me to have all Go >> libraries to change the source package name on every new major >> version, so I find it hard to judge whether the implementation details >> of it make sense or not and thus I don't think I should review it. > > I understand your concern on the source package rename part. However, > this is similar to how we bump SONAME for C/C++ libraries, which also > requires going through the NEW queue for each bump.
But only for the NEW binary package. The Debian source package name does not change with C/C++ soname bumps. I agree that we should use golang-*-vX-dev consistently. I went through many different ideas that I thought were better until I arrived at this (and made several confused posts about this to list many months ago..). I'm less confident that renaming all source packages is needed or a good use of our time... I won't object if anyone else does it though, but I don't envy the task. I think renaming binary packages could be sufficient, and adopting the new source package name style could be opt-in going forward for new packages or API versions. /Simon
signature.asc
Description: PGP signature
