Hi Thorsten, On Tue, Nov 3, 2026 at 5:14 PM Thorsten Alteholz <[email protected]> wrote: > On 03.11.26 15:43, Andrew Lee wrote: > > 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. > > I am afraid this is not something that the go-team can decide. According > to Debian policy 4.13 embedded code copies should be avoided.
Thank you for the clarification. However, my question was not about embedded or vendored code, but rather about individual submodules within a Go monorepo. Monorepos with multiple Go modules are very common in the Go ecosystem. For example, in the repository https://github.com/moby/moby, there is a main module at the root with its own go.mod file, alongside several submodules located in subdirectories such as api/go.mod, client/go.mod, and man/go.mod. Could someone explain how we should handle packaging the main repository as a single source package in Debian when its individual submodules have already been packaged as separate source packages? How to track the separate individual submodules source package update all at once with a new upstream releases? Best regards, -- -Andrew
