On Fri, 2022-06-24 at 11:15 +0200, Eric Schirra wrote:
What always amazes me. They want to introduce things like ALP (that's the docker story, isn't it?),
Docker? Not likely, the current thinking of the Local Container Management WG is that Podman will be the default container runtime for local workloads - with containerd/whatever-is-wanted-by-kubernetes being the non-local, clustered container runtime of choice.
among other things with the justification of the immense effort if you create the packages yourself, as has been the case until now. In contrast, you always ride a dead horse and have to pay for all problems, including security gaps, yourself. Not to mention the additional work that results. This does not fit together. And, sorry, that can come after my experience only from BWLer. Only they come up with such ideas.
Well the obvious bit you seem to be neglecting is, unlike this community-initiated effort by Axel, which will succeed or fail entirely on the backs of volunteers, ALP is initiated by SUSE who are doing so to address very real business needs they seek to address. So, any additional work within the scopes of ALP that SUSE cares about will obviously be something SUSE is willing to invest into. Whether or not that leads to additional work/additional volunteers needed in scopes of ALP that SUSE doesn't care about is another matter..but, by definition, these are areas which SUSE doesnt' care about. Just as you can't force a random contributor-off-the-street to take care of things they dont want to, same should apply to SUSE and ALP. A more nuanced point of course would be to realise that, if ALP delivers on even a minority of it's stated goals, with everything containerised the problems Axel is finding with Leap would no longer apply, because people should be able to mix and match containers from various codestreams.. a new python container atop an old base OS? No problem for the user, and potentially less problem for the maintainers to build and maintain because they can focus on just what they need to get that new python working, not worry about the impact across a huge 15,000+ package codebase. Regards, Richard