Re: Modularity and the system-upgrade path

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

 



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)
--
Miroslav Suchy, RHCA
Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys
_______________________________________________
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