On Saturday, June 20, 2020 2:40:48 PM MST Neal Gompa wrote:
On Sat, Jun 20, 2020 at 5:25 PM John M. Harris Jr
> On Saturday, June 20, 2020 4:42:17 AM MST Neal Gompa wrote:
> > TL;DR benefits of modularity for Fedora:
> > * Automating build chains for producing artifacts
> > * Straightforward mechanism of producing non-rpm artifacts using our
> > existing tooling (modules -> flatpaks/containers/etc.)
> Both of these have nothing to do with Modularity, and can be done with
> existing RPMs.
They have everything to do with Modularity, because that layer is
where that stuff was implemented. Modularity was the result of the
efforts involved with Factory 2.0, which gave us a lot of improvements
in our build infrastructure tooling for the first time since 2007.
Most of that rolled out in 2017, a full ten years after the last
revamp of our infrastructure.
As far as I'm aware, flatpacks can be created without any Modules. Containers
certainly can, we've been doing that for over a decade now without them.
> > * Path to provide alternative versions of stacks that
> > multiversion (Nodejs, Perl, PHP, etc.)
> Modularity doesn't support installing multiple versions of the same
> software. It's one of the key issues with the tech.
Modules can be designed to be parallel installable if the underlying
software natively supports that. For example, Python works that way
now, and thus in RHEL there are parallel versions of Python shipped as
modules. It doesn't change the nature of the software.
But it makes it easier to make multiple complete, yet conflicting,
collections of a language stack.
Where the underlying software already supports it, you don't need Modules to
do that, just regular old packages. See Python, for example. Modularity is not
a requirement for that.
John M. Harris, Jr.