Hi, Am 16.02.2021 um 10:07 schrieb Thorsten Kukuk:
On Tue, Feb 16, Ralf Lang wrote:
Maybe I missed some memos along the way because over many years, it just worked and I did not need to learn new tricks. That's true for somebody coming from openSUSE for many years. Now think about an admin, who has to maintaine Debian, Ubuntu, Fedora and openSUSE apache configurations. Does it also just work for him on openSUSE? Or isn't openSUSE the one he always need to remember how it is done different there?
Thorsten
You are right, being compatible with either upstream defaults or other distros is good. However, last time I configured a debian (yesterday) or a rhel/centos (some months ago), they looked incompatible both to each other AND suse. And people already built their tools and docs for this situation. It's good to eliminate the need to remember details and have a smooth experience for new users but this should not break older setups unless needed. Some time ago, a tumbleweed based container broke because it used one of the older commandline tools, I think a2enmod. That tool either moved to a subpackage or it was in the subpackage all along but the subpackage was no longer installed with the same commands as before. Easy to fix, just explicitly require the subpackage. So how can we transition to debianish layouts without breaking stuff, at least for a while? 1) Create a sites-available dir on install or update 2) Either move existing vhosts.d to sites-enabled or create it from scratch. 3) Make vhosts.d a symlink to sites-available. Same should work for config snippets (conf.d) Should I build a SR? -- 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