On Mon, Oct 07, 2019 at 03:20:21PM -0400, Alexander Scheel wrote: > > And where is the software for those containers coming from? Some > > container registry like Docker Hub? One of the main points of > > Modularity is to provide a trusted source of software to install into > > containers. > I never really understood this argument. Could you help me understand > it? > In what way do ursine RPMs not already do this? And more importantly, > what benefits does Modularity bring, based on an earlier thread with > Modularity use cases? I'm going to avoid the word "ursine" because I think it's more confusing then helpful. It's all the same RPMs, after all. Without modularity, RPM doesn't offer a good way to choose between different versions of the same thing. One can squash version numbers into the name, which covers some use cases, but also becomes unwieldy and loses the _idea_ that these things are different branches of the same basic software. > - Modularity doesn't bring parallel-installability. You'd have to support > it at the RPM level, which means ursine RPMs would support it to. [0] Well, the idea is: if you need parallel install, don't mess with it at the RPM level. Separate at the container level. > - Any size reduction in modular RPMs can be made to urisine RPMs. Maybe. But what if it reduces functionality? Modularity allows there to be a reduced version or a full version which can be swapped in. -- 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
