On Tue, Jan 07, 2020 at 12:41:14PM -0500, Stephen John Smoogen wrote:
For Gregory's problem, modularity does look like a better fix for 8 BUT the person writing the module needs to know a bunch of things:
- How to make a module. [This seems to be about ~20 people.]
Probably true, but the docs are actually quite good. https://docs.fedoraproject.org/en-US/modularity/making-modules/adding-new-mo...
- What software depends on jetty which will need to be modularized
also. This isn't software dep but API deps. [That will be the packagers of java applications and such.]
Yes. But that can start small: first the jetty module, then consumers of it.
- Know how to avoid setting up a libgit2 and similar problems that
Fedora has run into. We do not want someone to install EPEL-8 modularity and find out that we smoked their production system on the first yum update or some similar thing because a module replaced something it needed but was required for some other thing (OR vice versa). From the conversations in FESCO about this.. htis is still reliant on human knowledge and detection versus a test framework.
As I understand it, this is entirely a problem with making something a *default* module, which wouldn't be the case here.