Hi! Did we consider using a monorepo like the Rust team is doing for their packages? You would store only the debian/ for each project in the monorepo, not the entire upstream source code. Compare:
https://salsa.debian.org/rust-team/debcargo-conf/-/tree/master/src?ref_type=heads Documentation here: https://rust-team.pages.debian.net/book/packaging-tools.html Probably very little from that monorepo can be re-used for Go, but I find the general idea interesting -- especially considering recent experience with how tedious it is to manually update a bunch of Go team packages with all the different conventions... I suppose an alternative would be to better enforce consistency between all the Salsa go team packages, to allow operations that work on multiple projects, but we need tooling for that. I feel uncomfortable making consistency changes in some packages that appear more "owned" by someone that uses a different style from the Go Team policy and it is hard to tell what is intentional and what is just lack of time to update it. Thoughts? /Simon
signature.asc
Description: PGP signature
