On Sun, 2025-04-06 at 00:07 +0200, Simon Josefsson wrote: > Otto Kekäläinen <o...@debian.org> writes: > > > Is the goal of having the version string in all go packages? > > > > Or should golang-github-minio-minio-go be kept in the archive and just > > updated to latest?
The current packaging of golang-github-minio-minio-go is the old v6, which hasn't been touched in almost five years now. Since everything has now been moved to the -v7 package, I think it would be good to get rid of the old, unused package. (I noticed that for whatever reason dh- make-golang had set a dependency on the old v6 package rather than v7 when I packaged minio-client, which then prompted me to look for any other uses of the old version.) > I would kinda prefer to merge all the changes in > golang-github-minio-minio-go-v7-dev into > golang-github-minio-minio-go-dev and do an upload of the latter, then > migrate all packages that use golang-github-minio-minio-go-v7-dev to use > golang-github-minio-minio-go-dev, and then RM > golang-github-minio-minio-go-v7-dev instead. > > But that is also a lot of work for what appears to only be an easthetic > goal. So I'm not sure it is worth it, especially at this time since we > need to touch multiple packages... I personally prefer not to have the major version in a package name, but it is helpful when a library transition is needed, as there can be a huge list of reverse build deps that can be handled on a one-by-one basis rather than all at once. My main motivation here is simply trimming an outdated and unused leaf package prior to trixie releasing. :) Mathias
signature.asc
Description: This is a digitally signed message part
