Chicken, Egg, or go.mod? Solving Go Circular Build-Dependencies in Debian
If you maintain Go related packages. You’ve seen the error: Package A needs B, but B needs A.
In the Go world, this is becoming the “normal” for core libraries as Go’s modular designs for a world of “get the latest” but Debian still lives in a world of “builds in order from source”.
This talk will deep-dive into the tools and techniques for breaking circular build-dependency in the Debian Go packaging. If you maintain Go related package in Debian. It may helps to unblocks your Debian Go packaging work while you got circular build-dependency.