On Tue, Aug 23, 2005 at 12:17:32AM -0400, Bob Dodds wrote: > A per plugin deb or rpm could install into qpsmtpd with > minimal meddling that way. Maintaining debs rpms for > qpsmtpd installs with a given set of plugins would be > easy to maintain without scripting edits of config/plugins.
It can anyway, even without having qpsmtpd check the config path where it found the reference to the plugin. Being able to $include a directory, e.g. /etc/qpsmtpd/plugins.d/, allows supplemental plugin packages to configure themselves. Plugins installed from the package manager, moreover, are free to install themselves in /usr/share/qpsmtpd/plugins/ alongside qpsmtpd's own, a situation which doesn't even require multiple plugin dirs. Writing code to edit a system config file after an admin has been in there is a treacherous affair, and most package maintainers try strenuously to avoid it. The approach I've taken with the Debian packaging is to store all the auto-config and debconf-configured files in separate clobbered-on-install files and $include them into the main config with an explanation of their function and how to disable the automatic config. -- Devin \ aqua(at)devin.com, IRC:Requiem; http://www.devin.com Carraway \ 1024D/E9ABFCD2: 13E7 199E DD1E 65F0 8905 2E43 5395 CA0D E9AB FCD2
