Hi Team, I am writing to start a discussion regarding how we package Go main repo vs individual submodules separately in Debian.
Recently, I noticed Simon Quigley sponsor uploaded packages for individual submodules belonging to one Go project, such as individual `github.com/moby/moby/api` and `github.com/moby/moby/client` from main project `github.com/moby/moby`. Splitting submodules can sometimes help for a dependency satisfication, but also often creates maintenance overhead and version synchronization challenges. When upstream repositories manage all submodules under a single release lifecycle, separating them into independent Debian source packages can lead to package fragmentation and make tracking upstream updates much harder. I think we should have a general guideline or preference for packaging the main repo of a Go project as a whole, rather than splitting out individual submodules, unless there is a strong reason to do so. Keeping the unified source tree together usually preserves the intended upstream structure and simplifies dependency management, especially when working with `dh-go` module-aware buildsystem. I would love to hear your thoughts on this approach and understand which way that the team prefers for packaging Go packages. Best regards, -- -Andrew
