Re: Modularity and the system-upgrade path

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

 



On 07. 10. 19 10:05, Miroslav Suchý wrote:
Dne 04. 10. 19 v 21:31 Miro Hrončok napsal(a):
1. (drastic for modular maintainers)

We keep miantaining the default versions of things as ursine packages. We only modularize alternate versions.

This will improve current situation. And it will resolve upgrades from F30->F31.

However, I fail to see how this generally resolve dep_enabled modules. And upgrades of modules in general. I.e,: Alice runs:
   dnf module install foo:1
Fedora N has only foo:1.
Fedora N+1 has only foo:2
Alice cannot do:
   dnf module disable foo:1
   dnf module enable foo:2
Because foo:2 is available only in Fedora N+1 and the baseurl is
https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-$releasever&arch=$basearch
And she cannot do:
   dnf module disable foo:1
   dnf system-upgrade
because of broken deps in Fedora N+1 and module foo:1 (definitelly because of depenency on module_platform(platform:fN)

The "modularity gets enabled without an explicit enablement" approach was IMHO a mistake, especially since it breaks upgrades. The original proposal in this thread is trying to invent a very complicated workaround to this feature's quirks. Instead, my proposal removes the problem, while keeping all the benefits for the users.

My proposal doesn't solve the problem for Alice in your example. Alice has run "dnf module ..." and hence she volunteered into the problem. The problems here indeed need to be fixed, but it's not something I care deeply about. If we pile workaround on workarounds in this problem, I won't care. It will only affect the users who opt in.

My proposal solves the problem problem for every other user, who has never actually run "dnf module ...", who has no idea how modules work or how to disable or reset it. That's the problem I care deeply about.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
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