Daniel Baumann <[email protected]> writes: > Hi Simon, > > On 11/11/26 11:46, Simon Josefsson wrote: >> Another solution is to do a separate package for interesting >> sub-directories with faster release cadence. But we already discussed >> this, and I agree the general preference is to not do that. > > in general: I consider "breaking" up multi-repos into individual > source packages to be always superiour - it gets rid of any complexity > and gaining update flexibility, with the only drawback of having more > individual (source-)packages to take care of, but that is something > that scales much better and is easy to automate. > > for g-g-cloud specifically: personally, if I would want to update it, > I'd still break it up, but I think to (vagely, I can be totally wrong > and I didn't double-check) to remember that Andrew mentioned some > components inside it do reference each other in a nested way, which > then results in a bunch of circular build-depends. I wouldn't expect > this to be a continous problem if the package(s) were actively > maintained and updated in timely to keep the pace with upstream. Since > they are not, I'd still consider it a one-time-effort only to resolv > them on the path of having it actively maintained. > > just my opinion, I'm not going to do the work as the current version > in Debian is new enough for the stuff I care about (and others are > not, so, working on those atm).
Thanks for thoughts. There is a middle-ground: just break off some packages, but not all. For example, add a golang-google-cloud-kms package that contains the kms/ sub-directory (tracking the kms/vX.Y.Z git tag), migrate all consumers of golang-google-cloud kms/ to also add the new golang-google-cloud-kms-dev package, and drop the kms/ sub-directory from the golang-google-cloud package. Possibly golang-google-cloud-dev package could be modified to say Depends:golang-google-cloud-kms-dev to avoid touching dependencies. This would allow us to get the more modern kms/ stuff packaged, which is currently blocking several crypto packages from being able to upgrade. As a temporary solution until we establish some consensus, I would still consider that vendoring the newer kms/ files may be the simplest fix. /Simon
signature.asc
Description: PGP signature
