Braden == Braden McDaniel [EMAIL PROTECTED] writes:
[...]
Braden Right... But aclocal pulls them from a standard location on the
Braden system. While this means the distribution may be colored by
Braden characteristics of the system where it's built, it does mean that in
Braden general
On Thu, 2004-01-29 at 03:26, Alexandre Duret-Lutz wrote:
Anyway, the point is that you should not fear this. Installing
third-party macros in /usr/share/aclocal will continue to work.
Ah, good. Thank you for clarifying this.
--
Braden McDaniel e-mail: [EMAIL
On Thu, Jan 29, 2004 at 09:26:50AM +0100, Alexandre Duret-Lutz wrote:
..
Anyway, the point is that you should not fear this. Installing
third-party macros in /usr/share/aclocal will continue to work.
I think the problem arises when packages assume that libtool.m4 lives
in /usr/share/aclocal
On Wed, 2004-01-28 at 20:29, Braden McDaniel wrote:
Why are the libtool macros being installed to $(pkgdatadir) rather than
$(datadir)/aclocal?
Because aclocal is slowly being deprecated, and will eventually vanish
entirely. Managing Autoconf macros really isn't a job for Automake.
The new
On Wed, Jan 28, 2004 at 10:13:21PM +, Scott James Remnant wrote:
On Wed, 2004-01-28 at 20:29, Braden McDaniel wrote:
Why are the libtool macros being installed to $(pkgdatadir) rather than
$(datadir)/aclocal?
Because aclocal is slowly being deprecated, and will eventually vanish
On Wed, 2004-01-28 at 22:26, Albert Chin wrote:
On Wed, Jan 28, 2004 at 10:13:21PM +, Scott James Remnant wrote:
One day a version of Autoconf will use these, but for now when you run
aclocal it'll add an m4_include line to aclocal.m4 for each of these
files (rather than including them
Scott James Remnant wrote:
On Wed, 2004-01-28 at 22:26, Albert Chin wrote:
On Wed, Jan 28, 2004 at 10:13:21PM +, Scott James Remnant wrote:
One day a version of Autoconf will use these, but for now when you run
aclocal it'll add an m4_include line to aclocal.m4 for each of these
files
