Viktor Dukhovni:
> On Thu, May 08, 2014 at 08:13:00PM -0400, Wietse Venema wrote:
>
> > postfix-files can be shared because it references files that are
> > shared.
> >
> > dynamicmaps.cf can be shared provided as you ALSO share the
> > dynamicmaps.cf plugins by ALSO putting them into $daemon_directory.
>
> Yes, that'll work I guess. And the Debian backwards compatibility
> is not that compelling in this case?
If Debian could live with a backwards-compatibility symlink, then
I think that we have an opportunity to improve on what exists without
breaking compatibility,
The idea is that:
- dynamicmaps.cf and its plugins should be updated together,
- they should be updated together with the programs that use those
plugins,
- they should be shared among Postfix instances that use the same
programs.
That means we should install dynamicmaps.cf and plugins in a "shared"
location rather than a per-instance location.
While it would be OK to install libpostfix-*.so.* under /usr/lib
or /usr/local/lib, I do not think that would not be an appropriate
location for dynamicmaps.cf or plugins. I chose $daemon_directory
because postfix-files and other non-program files are already
installed there. We could instead introduce a "plugin" directory
for dynamicmaps.cf (and its plugins).
dynamicmaps.cf could permit relative pathnames that would automatically
be prepended with the value of $daemon_directory (or $plugin_directory).
That would make dynamicmaps.cf content location-independent, and
simplify a few things. However, I see no reason to break support
for Debian-style absolute pathnames.
Wietse
