After some experiments / research it looks like nethserver-modules leave their (httpd, apache) configurations files behind after removal. I checked with SOGo, Webtop, Roundcube and Statistics.
Not strange if you take in account RPM is unaware of most of those files: they are created at template expansion. Interesting exception is
webtop5-webdav.conf it is static ( non templated ) nevertherless stays behind too after removing nethserver-webtop.
It is removed if you (auto)remove webtop5* completely (that is an other story…)
From own experience with nethserver-gitea the httpd (apache) configuration files are worrying. IMO other configuration files, sometimes left behind as
.rmpsave, do not harm.
Reloading the httpd configuration of removed module(s) does compromise the stability of our systems.
In the nethserver-gitea module it is solved in the SPEC by explicit removal of this file:
%postun if [ $1 == 0 ]; then /usr/bin/rm -f /etc/httpd/conf.d/zz_gitea.conf > /dev/null 2>&1 fi
Syntax reference of [ $1 == 0 ]
Id’ like to introduce to consider removal of httpd configuration files at module removal being good practice.
What do you think?