Am 23.01.2021 um 11:02 schrieb Arjen de Korte:
Citeren Ralf Lang <lang@b1-systems.de>:
Hi, I think this is only partly right. Packages should not have hard preference on a specific web server unless they are server modules.
Or provide configurations specifically for that webserver, preferably in a way that bundles these settings in a subpackage like https://en.opensuse.org/openSUSE:Packaging_PHP#Supporting_different_web_serv..., but that's also what you mention below, so I guess we can agree on that. Still, many packages currently requirering mod_php_any are indeed apache2 only and they should definitly have a hard dependency on that.
I agree, if it's mod_php_any then it's inherently apache as the only provider of mod_php runtime. However, I am not sure if there is so much software that really needs mod_php for technical reasons.
Production php should not be mod_php anyway but rather fcgi/fpm which works with different webservers just the same.
+1
as for web server config snippets or whole vhost configs, they should be offerings only and i do not even like them to be automatically live/active.
+1
Providing software to the right parts of fs, compatible to a distribution, and assuming how the user will run it are two different businesses.
+1, but yet I also understand that people want to provide something that works out-of-the box.
I understand that. It's revolving around what a distribution should do and should not do. And if I may open an entirely different can of worms, I am currently dropping pear support for "my" 100+ packages groupware blob, moving to composer and I have no real idea how I can deliver an rpm-based, distribution friendly product out of it. There's little guidance on how to package that. I am really puzzled how the role of classic OS packaging is supposed to evolve wrt these trees of right-for-this app version requirements. But that's just backstory, I think it is perfectly valid to just say "this app wants a web server of any sort installed". Unless in the case of roundcube, it's even possible the PHP backend would run nicely with an apache/nginx on a DIFFERENT server. Which is a perfectly valid scaleout scenario, I believe. Regards Ralf
-- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537