On 11/11/26 13:37, Simon Josefsson wrote:
There is a middle-ground: just break off some packages, but not all.
yes, "and"...
migrate all consumers of golang-google-cloud kms/ to also add the new
golang-google-cloud-kms-dev package
that sounds like a lot of work from a generic point of view, and becomes
a hassle when you have to undo it and merge it back once it's not
feasible anymore because the two diverged too much.
this multiplies with each submodule you're breaking out.
personally, I'd rather spend the time do breaking them off completely
and be done with it. ymmv.
As a temporary solution until we establish some consensus, I would still
consider that vendoring the newer kms/ files may be the simplest fix.
I'd consider vendoring to be even worse than the "middle-ground",
updating and tracking individual copies, even if it's only temporary
time intended (even disregarding that most of the time it later becomes
more permant for $reasons), is horrible and always results in much more
work, stuff that gets forgotten, etc. that (often) other people have to
cleanup years later.
Regards,
Daniel