Re: Managing stream (arbitrary) branch and module lifecycles

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

 



On Thu, Sep 20, 2018 at 09:11:57AM -0400, Matthew Miller wrote:
> On Tue, Sep 18, 2018 at 10:48:46AM +0200, Adam Samalik wrote:
> > There is another concept in Modularity we can use here: defaults. You could
> > have both streams 1.7 and 1.8 built for all active (non-EOL) Fedora
> > releases, but have different default for each. So in your case, F27 could
> > have 1.7 as a default and F28+ could have 1.8 as a default.
> > 
> > Independently of this, you could also retire 1.7 with the end of F27 if
> > there was no need to have it in the future releases.
> 
> Is there a way for users to say "keep me on whatever module is the default"
> when upgrading?

If they enable the module explicitly, they will keep that stream,
regardless of what the current defaults are.

Explicit enablement can happen in two ways:

1. By running `dnf module enable name:stream`, or
2. by installing any package from that module.

P

Attachment: signature.asc
Description: PGP signature

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
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