Open Stack

On 7/21/23 19:48, Radosław Piliszek wrote:
> The point with Go is that it has no dynamic linking...

I would say: s/The point with/The main defect of/

> What you would be doing is repeating the compilation to produce the
> single static binary and package it.

All what Jeremy replied, plus:

- having a version in Debian stable that we may *really* rely on, with 
bugs reported and fixed for months before the distro is released as 
stable. Not just the latest upstream release with the latest not-yet 
discovered bugs.

- A real auditable software supply chain, not just "curl | sudo bash" 
from the internet.

> The upstream does this well - no reason to repeat unless building for
> fancy architectures.

yeah, there's that too! Having support for:
- ppc64el
- arm64
- risc-v
- ... (you name it...) ...

That's one of the nice things with Debian! :)

> This also helps with ensuring everyone is bug-bug compatible if they
> run the same version - no need to check anything else. :D

What helps is having everyone on the version from the distro, not 
everyone running the latest version from when they did their deployments 
(understand: everyone running something different).

Of course, YMMV. But these are the reasons I only deploy packaged 
software, and packaged the way we do in Debian. I understand why others 
prefer some other path, and deploy from upstream, it's not just what I 
like to do, and what I recommend against.

Cheers,

Thomas Goirand (zigo)