On Thu, 2019-10-17 at 08:08 -0400, Stephen Gallagher wrote: > One of the (often un- or misinformed) major arguments people keep > using against Modularity is "it makes packaging harder!". One thing I've found to be a problem with modularity is that it's easy to be un- or misinformed. I spent a lot of time reading the docs (and I'm glad there are docs, I'm not criticizing the docs) and I still found it difficult to modularize my rpick package. My experiences as a packager for the other distributions I've worked with that offer parallel installability (which necessarily means parallel availability) was that I didn't need to know very much to do it. It was generally obvious what to do to make my package use slots, for example. I think the problem is that modularity is complicated enough that it's hard to know it well without investment. Could we think of a solution that is simple so that packagers can more easily understand how it works? Or better, can we employ a solution that another distribution has developed?
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ 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
