Hey! I've been working on modernising some Go packages to use the new module-aware dh-go build system. but I've noticed that these packages cannot currently be backported to trixie-backports without reverting to the legacy dh-golang build system, carrying those patches in a backports branch seems kind of silly to me :-)
At least for those packages I am maintaining in backports I would not want to adopt dh-go due to the additional maintenance needed... Would it make sense to backport dh-go to trixie-backports to allow packages to use the new build system across both suites? I'm happy to try to handle the backport if others think it would be useful. Are there any known issues or other reasons not to do this? I had a look in the mailing list archive and wiki pages but saw no mention of it... Cheers! Chris
