On Mon, Sep 24, 2018 at 3:39 PM, Mikolaj Izdebski <mizdebsk@xxxxxxxxxx> wrote: > On 09/24/2018 08:52 PM, Miro Hrončok wrote: >> On 24.9.2018 19:09, Mikolaj Izdebski wrote: >>> I'm in the process of transitioning maintenance of all software to >>> modules only. The reason is that module maintenance is much easier >>> compared to maintenance of non-modular, "ursine" packages. >>> >>> Ideally these packages should be retired instead of orphaning them, but >>> these packages are build-required by a lot of other things. >> This is an interesting situation. If more maintainers will decide to do >> this, we can easily break everything and only have modules, except we >> will no longer have any system to have those modules run on. >> >> (I'm not saying you shouldn't do this; I'm just really concerned if >> modularity is actually helping Fedora as a whole or if it will >> eventually break it entirely.) > > I was hoping for a solution like "ursa-major" described in [1], that > would allow modules to be used as build-dependencies for non-modular > packages. This would allow properly retiring non-modular packages and > maintaining only modules, which would be also used as build dependencies > for non-modular packages. But it seems that currently no one is > interested in implementing such solution. > > Java SIG is dying slowly, this package set recently lost another > co-maintainer and I don't have time to maintain all these packages by > myself. Switching to module-only content is probably the best move to > keep high-quality software delivered to our users and reduce maintenance > work at the same time. > > [1] > https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx/message/JZMPGE2VMBHDO4D6SC4YTRSYNQYZOT63/ This is something that worried me also when I read this message. Are modules only intended for leaf packages at the moment? I admit that I have not really been keeping up to date with modularity. Or is the intended workflow that (eventually) everything's a module, and so if something needs to depend on a module, it too must be inside a module for this to work? This seems like it could become a problem, because I imagine that there are lots of leaf packages out there that aren't in modules, or don't necessarily need to be in modules-- unless parts of the distribution start becoming module-only. (Maybe this discussion belongs in a new thread, but I think it's important). Ben Rosser _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
