Re: Defining the future of the packager workflow in Fedora

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

 



On Tue, Oct 08, 2019 at 02:06:06AM +0200, Kevin Kofler wrote:
> Sure, I fully understand the theoretical benefits to be had from Modularity 
> (though I still think that this is much more useful for LTS distributions 
> such as RHEL or CentOS than for Fedora). The issue is that it all breaks 
> down when modules depend on each other (and they already do), because of the 
> unavoidable versioning conflicts (Module A requires Module C version 1, 
> Module B requires Module C version 2, and only one version of Module C can 
> be installed) that bring us Module Hell, a.k.a., RPM Hell 2.0. And this 
> follows directly from the specification of the Modularity feature. And it 
> has already happened in practice (see the libgit2 chaos).

Yeah, I agree that there's a problem with non-parallel-installable modules
that aren't effectively leaves.

-- 
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
_______________________________________________
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