I agree completely. I think the new vhost/multiple-config-file support architecture is bad. I recently upgraded from a year-old version of the webalizer package to the current one and tried to adapt my homegrown vhost infrastructure (which is similar to Jacob's) to the new one in order to reduce the deviation from the "official" way of doing things, but it's just awful. See below for the rationale.
I cannot even retain my own way of doing things because the webalizer package's configure script insists on moving /etc/webalizer.conf to /etc/webalizer/webalizer.conf on each and every configuration of the package. I considered filing a bug about this with serious severity, but then I figured that the entire "official" infrastructure should rather be improved instead. I think users of webalizer (like Jacob and me) have long been accustomed to using webalizer.conf as a default config file and use smaller config files on top of that with specific configuration directives for specific vhosts. Having this default config file (webalizer.conf) in the same directory as all the vhost config files is a mess. Either move webalizer.conf back to /etc/ (preferred, since it's upstream's way), or create a sub-directory in /etc/webalizer/ for the vhost config files. Please consider changing the package's config file architecture to that end.
pgpOl0BGWfmW4.pgp
Description: PGP signature
