[pkg-go] automatic rebuild of binaries

[Michael Stapelberg]

Hi Ximin,

Ximin Luo <infinity0 at pwned.gg> writes:
> When shared libraries are updated, binaries that use this library are
> also automatically updated. That is one of the main advantages of
> dynamic linking, and the excellent dependency-handling of APT allows
> us to do this without much headache, unlike e.g. on Windows.
>
> Go does not currently have shared libraries, so a golang binary that
> is compiled in Debian, is *not* automatically updated when its library
> dependencies are updated (since currently[1] we only package libraries
> as source code).
>
> This is counter-intuitive, and IMO a problem. Do people agree, and if
> so, how shall we try to solve it? One option is to set up other
> infrastructure to poke the maintainer of a binary to do a re-build
> when the shared libraries update. This is likely to happen quite often
> though, and creates a lot of manual work that is fundamentally
> unnecessary. Does Debian support anything like automatic rebuilding?
I was thinking about some automation to do this, i.e. rebuild all
reverse-dependencies whenever a package changes. I talked to nomeata@
about it nearly a year ago, and they have the same situation with
Haskell.

I suppose it’d be a good idea to write down a few structured thoughts on
what I imagined. Hopefully I’ll get around to it this weekend.

-- 
Best regards,
Michael