Re: Modularity and the system-upgrade path

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

 



On Fri, 2019-10-18 at 13:05 +0200, Lukas Ruzicka wrote:



Or, even better (or worse): Sombody installs GIMP via GNOME Software,
and under the hood, dnf does its magic and installs gimp from the
module, which might depend on another, even non-default module, etc.
But then, what will happen when that module is EOL, and the user has
never even interacted with dnf, or modules? Will system upgrades break
and prompt the user to fix something they didn't even know existed,
and have never interacted with?

This has already happened. We have had complaints from people who had never
installed any module, or used the "dnf module" command and they still ended up with
modules installed with a problem to upgrade their computers to F31.
This worries me quite a bit as people often install Fedora on computers of relatives and friends
in default configuration & instruct the users to just "press the update button when it shows up".
I've done that a couple times.

This has been working quite fine so far, so it would be bad to loose this capability, as the actual
users in question are definitely not power users and will not be able to fix any of these issues
by themselves. 

Also from their point of view it's pretty much Fedora breaking if if a specific module is ta fault.
And well, they are not really wrong if a default Fedora install simply breaks upgrades at a
random point in the future...



 

Fabio

> Pierre
> _______________________________________________
> 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
_______________________________________________
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


_______________________________________________
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

_______________________________________________
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