Le 14/06/2019 à 20:03, Josh Boyer a écrit : > On Fri, Jun 14, 2019 at 3:50 AM Remi Collet <Fedora@xxxxxxxxxxxxxxxxx> wrote: >> >> >>> IMHO, having library in modules is an error, this can only raise issues >> >> Some examples, taken from RHEL-8 >> >> libJudy is part of the mariadb module ... (without -devel) >> libssh2 is part of the virt module... (without -devel) >> libzip is part of the php module... >> etc >> >> How are we going to manage this in EPEL ? > > Can you elaborate further? How are you going to build package requiring libssh2 in EPEL ? Dependency on "virt" seems terribly strange and we don't have the "devel" package, and are not allowed per Guidelines to replace things which are part of RHEL. So probably we have to add libssh2 in EPEL, but what will happen if soname change ? making installation if "virt" module impossible ? As "libssh2" is only used by "virt", and is not part of the provided contract of the module, we can imagine - virt version x with libssh2 version 1 - virt version y (major update = new stream) with libssh2 version 2 - virt version y (minor update, same stream) with libssh2 version 3 - etc Next problem, I need libssh2 and libjudy (and some others) in the PHP module, so ? - add a module dependency on mariadb and virt ? => this can't work and don't make sense - add the judy and libssh2 and other lib in the php module ? => at some point, we are going to generate conflicts between modules IMHO, such libraries have to be in the base distribution. Another funny thing, I have some PHP extensions which use nodejs, how to mange this in a modular world ? - make PHP module depends on NODEJS module ? - create another module only for these extensions ? For memory, PHP is not available as module in Fedora, because of such issues (and PHP stack is hundreds of packages, with tons of library bindings). But I really want to see more PHP stuff in EPEL, as for previous version, and this have to be managed as module. Remi _______________________________________________ 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
