yeah looks keep it in config.layout for change by distributors is
better.
apache take libexecdir: ${exec_prefix}/modules in the default layout
to install modules, in my gentoo, it changed
to /usr/lib64/apache2/modules.
I'd prefer to set /usr/lib64/trafficserver/plugins for our plugins, at
least, I got my ebuild file for gentoo, and rpm spec file for Fedora,
ready to ship.
thanks
在 2011-02-28一的 09:52 -0500，Theo Schlossnagle写道：
> libexecdir. 'tis where they belong. We sometimes pull a
> --libexecdir=/some/path/to/modules, but that's on us.
>
> On Mon, Feb 28, 2011 at 9:49 AM, Leif Hedstrom <zw...@apache.org> wrote:
> > On 02/28/2011 02:25 AM, ming....@gmail.com wrote:
> >>
> >> hi, all:
> >> We have now install plugins into libexecdir, which is recommend for
> >> used for executable files in most distributions, such as fedora:
> >> lib/ contains object files and libraries that are not designed to be
> >> directly utilized by users or shell scripts. The libexec/ directory
> >> contains small helper programs called by other programs
> >>
> >> I'd like to change the default plugin dir to libdir, that is:
> >> 1, remove 'Makefile.am:pkglibdir = ${pkglibexecdir}' line from plugins
> >> and example Makefile.am.
> >> 2, change proxy.config.plugin.plugin_dir to pkglibdir.
> >>
> >> any comments?
> >>
> >
> > To me that doesn't make a whole lot of sense, but that's just IMHO :). To
> > me, /lib should be libraries that other application links with, and clearly
> > our plugins (.so's) do not fall into this category. I'm open to suggestions
> > other than libexec though if there is some better / more standard place for
> > this (e.g. httpd puts them in $prefix/modules it seems).
> >
> > -- leif
> >
> >
>
>
>
