Packaging Kubernetes for Debian
Packaging Kubernetes for Debian
Posted Nov 2, 2020 15:05 UTC (Mon) by LtWorf (subscriber, #124958)In reply to: Packaging Kubernetes for Debian by cyphar
Parent article: Packaging Kubernetes for Debian
It is a language developed at google to run on their own internal systems. When they made it they just wanted a binary blob so that whatever distributions they might use internally that month, it would just work.
It was never the idea to make go programs for others.
Posted Nov 2, 2020 16:58 UTC (Mon)
by Cyberax (✭ supporter ✭, #52523)
[Link] (3 responses)
The static compilation has always been a welcome feature. I remember that I was introduced to Go by HPC (High Performance Computation) folks who really LOVED that they could compile a binary locally and run it on a cluster, without caring for mismatching glibc versions.
Posted Nov 2, 2020 20:14 UTC (Mon)
by smurf (subscriber, #17840)
[Link] (1 responses)
"It's a general purpose language" and "it's not designed for distribution" is not a contradiction.
Go binaries can be distributed like hell. Go sources? not so much, esp. if by "distributed" one means "included in a distribution". You basically need network access, github (and whatever else the code in question and/or any of its its dependencies want) needs to be up and reachable, and so on.
If you plan to work on a Go program offline, you basically need to start the compiler once, before disconnecting from the net, so it can cache all that stuff.
And that's the polar opposite of what a distribution is trying to accomplish.
Posted Nov 3, 2020 0:43 UTC (Tue)
by Cyberax (✭ supporter ✭, #52523)
[Link]
But even module-based Go doesn't need Github access, it needs a way to resolve packages and you can use one of the many repo managers for that (like Artifactory).
Posted Nov 13, 2020 3:19 UTC (Fri)
by nivedita76 (subscriber, #121790)
[Link]
Packaging Kubernetes for Debian
Packaging Kubernetes for Debian
Packaging Kubernetes for Debian
Packaging Kubernetes for Debian