On Tue, Oct 08, 2019 at 02:09:24PM -0400, Przemek Klosowski via devel wrote: > Having said that, I am not sure it will solve the problem with > ecosystems requiring specific collection of component versions (*): > what is the expected number of required versions for each module in > those environments? If it is much more than 2 then fast/slow scheme > might not work. Yeah, I don't think modularity solves this well at the individual component version explosion of doom. Ideally, we'd get developers to not do that, but ... we've tried that for 25 years with less and less success over time. I mean, really, nothing we're doing really solves this. So... I think the solution there is really: automated bundling, automated detection of that bundling, and where possible, automated patching. But that's _another_ major project. -- 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
