Re: Modularity and the system-upgrade path

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

 



On Wed, Oct 16, 2019 at 12:15 AM Neal Gompa <ngompa13@xxxxxxxxx> wrote:
>
> On Wed, Oct 16, 2019 at 12:11 AM John M. Harris Jr <johnmh@xxxxxxxxxxxxx> wrote:
> >
> > On Tuesday, October 15, 2019 9:07:51 PM MST Neal Gompa wrote:
> > > On Wed, Oct 16, 2019 at 12:05 AM John M. Harris Jr <johnmh@xxxxxxxxxxxxx>
> > > wrote:
> > > >
> > > >
> > > > On Tuesday, October 15, 2019 6:26:31 PM MST Stephen Gallagher wrote:
> > > >
> > > > > given that we're talking about the need to migrate defaults
> > > >
> > > >
> > > >
> > > > To clarify, that has not been decided, and a prominent option mentioned
> > > > in
> > > > this thread is the option to simply require that there is a non-modular
> > > > package.
> > > >
> > > >
> > >
> > >
> > > I think we can pretty much guarantee that's not going to happen.
> > > Unfortunately, modularization is a one-way road, given how modularity
> > > is implemented in DNF and how our distribution policies are currently
> > > structured.
> > >
> > > It just means that people need to *really* think of the consequences
> > > of modularizing content, because there's basically no going back after
> > > that. We have no escape hatches or transition mechanisms to go from
> > > modular to non-modular variants of the same RPMs.
> >
> > That's not what the proposal is. The proposal is to require a non-modular
> > version, an "ursine package", for modular packages, instead of default
> > modules.
>
> We cannot remove already existing default modules without further
> breaking things. Moreover, DNF will refuse to expose non-modular RPMs
> if it's aware of modular ones that have existed at some point. The
> best we can do is stop people from making more.
>

This is currently accurate.

> We have no process for de-modularization and I fully expect us to not
> have one ever, as the end goal of the modularity project is to enable
> a fully modularized distribution. Even RHEL 8 isn't a full realization
> of that vision.

This is not true. It should be *possible* to have a fully modularized
distribution, but that isn't a specific goal for Fedora or RHEL.

Also, we *are* investigating ways that we could move RPMs out of
modules, because this may be important for many reasons (such as
moving a common dependency out of a module and back to the non-modular
repo to be shared). We haven't figured this one out yet, but it's on
the queue.
_______________________________________________
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