I am just curious as to why the default location for the configuration files of logwatch is changed in the ebuild from /etc/log.d to /usr/share/logwatch ? I think /etc/ makes more sense, because I for example need to tweak the default configuration files a LOT (I use metalog), and don't want to lose the changes on an upgrade. That wouldn't've hurt a whole lot, if the default location that logwatch.pl looks for its configuration files was not changed from /etc/log.d to /usr/share/logwatch . What is the point in creating a symlink from /etc/logwatch to /usr/share/logwatch if logwatch doesn't even try to read the files from /etc?
mainly because AFAIK /etc/log.d is a RedHat extension and, if I remember it right, in some other distros/progs /etc/log.d is used by other applications (do not remember which one). So, when I originally wrote the ebuild I found more correct to use the directory where the program resides and to symlink it on /etc with a unique name (logwatch) instead of log.d . It seemed to be a reasonable alternative, btw I might be wrong... PS: you can't make the perl script use /etc directly since the config file path is hardwired in the script itself (in must be in scripdir/conf). I created the symlink on /etc as an helper for the users, so they can easily find the config instead having to search it in /usr. This seemed reasonable to me too; btw, again, I might be wrong... bye, Alessandro
Agreed. New ebuild conforms as suggested. sys-apps/logwatch-4.3.2
