Matt Sergeant wrote:
On 22 Aug 2005, at 03:57, Peter J. Holzer wrote:
Note this is why I implemented $Include.
Maybe my cold is addling my brain, but I don't see how $Include can be
used to load plugins from different locations.
In my RPM, qpsmtpd and qpsmtpd-forkserver are in /usr/bin (they probably
should be in /usr/sbin instead). By default, qpsmtpd would now look in
/usr/bin/plugins for the plugins, but they are in
/usr/share/qpsmtpd/plugins instead. So a config option is needed to tell
qpsmtpd where they are. In addition, a sysadmin might want to install
his own plugins into /usr/local/qpsmtpd/plugins - this is what Devin's
patch allows.
Ah I see. Yes ignore me.
$Include is there so that a "plugin" RPM/DEB/Whatever can just drop a
plugin in the plugins dir and a config file in a plugin.d directory
and qpsmtpd will automatically pick it up.
In short: $Include is there so that an RPM doesn't have to modify
config/plugins.
Matt.
Could plugins be in plugins/subdir if their config file was
plugin.d/subdir/configfile?
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.
-Bob
