On 2020-03-24 19:08:23 +0000 (+0000), Janos LENART wrote: > I know Dimitry was fighting an uphill battle with kubernetes > between 2016 and 2018 and he experienced first hand the problems > posed by vendored code. > > We see more and more software making excessive use of vendored > code. Pretty much everything that is written in Go. Some of these > are crucially important, like Docker or Kubernetes. So I > understand the concern everyone has about how this fits with the > Debian Policy. [snip rationale for packaging Kubernetes while giving up on policy] If this represents the actual state of building Kubernetes, it's unclear to me why Debian would package it at all. I don't see the value to users in consuming Kubernetes from a Debian package if the result is compromising on Debian's vision and values so that they can get the exact same thing they'd have if they just used the Kubernetes community's recommended tooling to install it instead. I'm all for using the best tool for the job, and while I've been a die-hard Debian user for more than two decades I also don't install every last bit of software from its packages. Some software ecosystems have chosen to focus on tools and workflows which are incompatible with Debian's, but that doesn't mean that either one is inherently bad nor that they need to be integrated at all costs. -- Jeremy Stanley
Attachment:
signature.asc
Description: PGP signature