On Sat, 23 Jan 2021, Arjen de Korte wrote:
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.
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.
So maybe have 'foo' and a 'foo-apache' flavor where the foo-apache package provides config files for apache and requires that? That is, separate config from the actual package. I've long wanted this for parts of our core packages where stripped down default configs would allow for a smaller installed system. Richard. -- Richard Biener <rguenther@suse.de> SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany; GF: Felix Imendörffer; HRB 36809 (AG Nuernberg)