On Wed, Feb 18, 2015 at 11:16:19AM +0100, Andreas wrote:
> > This is something the distribution maintainers will have to figure
> > out. If you are a distribution maintainer, please DO NOT apply
> > the above patch unless it is first adopted upstream.
>
> Since, as you said, some distributions lack /usr/libexec, wouldn't it be
> a better idea to leave it up to the package/distribution maintainers to
> separate shared objects from shared executables?
As Redhat and others have discovered, on multi-arch systems multiple
executables of various ABIs can be deployed in a single directory,
but object libraries need to be segregated by ABI.
This extends to "off-path" executabes that are only executed by
other programs, but are not intended to be used directly by users.
This is what /usr/libexec is for, and it is starting to be used
in Linux systems.
The upstream Postfix release defaults to
daemon_directory = /usr/libexec/postfix
on all but one system type (GNU0 Debian whatever that is),
and even that one should probably be changed to /usr/libexec.
With 3.0.0 Linux distributions should start using the upstream
default. This does mean that users should remove explicit legacy
default settings of daemon_directory from their main.cf files.
Distribution package upgrades will need to update or drop obsolete
daemon_directory settings from all installed Postfix instances.
--
Viktor.
