Re: RHEL 9 and modularity

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 <johnmh@xxxxxxxxxxxxx>
> wrote:
> >
> >
> > 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 don't natively
> > > 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.

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux