On Jul 4 09:10, James R. Phillips wrote:
> --- Corinna Vinschen wrote:
> > Not sure about that, but the root idea of defining libexecdir as /usr/sbin
> > (way back when) was that I disliked the idea of inetutils to have
> > libexecdir defined as ${exec_prefix}/libexec by default. This is the
> >
--- Corinna Vinschen wrote:
> Not sure about that, but the root idea of defining libexecdir as /usr/sbin
> (way back when) was that I disliked the idea of inetutils to have
> libexecdir defined as ${exec_prefix}/libexec by default. This is the
> directory in which the daemons are installed and
On Jul 2 08:40, James R. Phillips wrote:
> All,
>
> The packaging instructions at http://cygwin.com/setup.html#package_contents
> indicate
>
> [quote]
> The package is configured using (at a minimum) the following paths:
> [..snip..]
> --libexecdir=/usr/sbin
>
--- "Gerrit P. Haase" wrote:
I think this reply suffices for Igor as well. Thanks to both.
> (1) /usr/lib/package, yes. Or maybe /usr/share/package.
It is understood that the files need to install under /usr/lib/package. What
to set libexecdir to to achieve that - perhaps varies per package?
James R. Phillips wrote:
All,
The packaging instructions at http://cygwin.com/setup.html#package_contents
indicate
[quote]
The package is configured using (at a minimum) the following paths:
[..snip..]
--libexecdir=/usr/sbin
[..snip..]
[/quote]
OK, this seems wrong to me. GNU autoconf
On Sat, 2 Jul 2005, James R. Phillips wrote:
> All,
>
> The packaging instructions at
> http://cygwin.com/setup.html#package_contents indicate
>
> [quote]
> The package is configured using (at a minimum) the following paths:
> [..snip..]
> --libexecdir=/usr/sbin
>
All,
The packaging instructions at http://cygwin.com/setup.html#package_contents
indicate
[quote]
The package is configured using (at a minimum) the following paths:
[..snip..]
--libexecdir=/usr/sbin
[..snip..]
[/quote]
OK, this seems wrong to me. GNU autoconf defines libexecdir as a
