[RFC] Superseding aclocal? (was: Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal)

[Adding Automake list in CC:] Reference: On 10/17/2012 10:25 AM, Gary V. Vaughan wrote: > > [SNIP] > > I remember many years ago that Tom Tromey (IIRC) stated that aclocal > was just a stop-gap measure until autoconf coul

Re: [RFC] Superseding aclocal? (was: Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal)

Hi Stefano, Thanks for the fast response! On 17 Oct 2012, at 15:52, Stefano Lattarini wrote: > [Adding Automake list in CC:] > > Reference: > > > On 10/17/2012 10:25 AM, Gary V. Vaughan wrote: >> >> [SNIP] >> >> I r

[RFC] Moving ltmain.sh and libtool.m4 into Automake

Autotoolers, For quite some time now I've been thinking about simplifying Libtool, but I'm interested in feedback and more particularly buy-in from Automake maintainers before I start the work, so that I have a better idea of what direction I'm heading in... Libtool is just (a complicated) compil

Re: [RFC] Superseding aclocal?

On 10/17/2012 11:24 AM, Gary V. Vaughan wrote: > Hi Stefano, > > Thanks for the fast response! > > On 17 Oct 2012, at 15:52, Stefano Lattarini > wrote: > >> [Adding Automake list in CC:] >> >> Reference: >> >> >> On 10

Re: [RFC] Moving ltmain.sh and libtool.m4 into Automake

On 10/17/2012 11:41 AM, Gary V. Vaughan wrote: > Autotoolers, > > For quite some time now I've been thinking about simplifying Libtool, > but I'm interested in feedback and more particularly buy-in from > Automake maintainers before I start the work, so that I have a better > idea of what directio

Re: [RFC] Moving ltmain.sh and libtool.m4 into Automake

On Wed, 17 Oct 2012, Gary V. Vaughan wrote: Libtool is just (a complicated) compiler wrapper, to make building and linking against libraries easy to specify... be that on the command line with a direct libtool invocation, or from Makefile.am specifications. I'm considering splitting the current

Re: [RFC] Superseding aclocal?

Hi Stefano, On 17 Oct 2012, at 16:45, Stefano Lattarini wrote: > On 10/17/2012 11:24 AM, Gary V. Vaughan wrote: >> On 17 Oct 2012, at 15:52, Stefano Lattarini >> wrote: >>> On 10/17/2012 10:25 AM, Gary V. Vaughan wrote: I remember many years ago that Tom Tromey (IIRC) stated that aclocal >

Re: [RFC] Moving ltmain.sh and libtool.m4 into Automake

Thanks to everyone for your feedback. Much appreciated. It seems that merging libtool into Automake would be an unpopular move all around, with significant downsides for users, so I no longer plan to do that... unless there is a still strong technical argument supporting it that I've yet to hear.

Re: [RFC] Moving ltmain.sh and libtool.m4 into Automake

On 17/10/2012 08:27, Gary V. Vaughan wrote: >> > Creading a stand-alone libltdl package is a very good idea. > The separation will also make both packages much smaller and more manageable, > especially without all the contortions of trying to support all the different > ways of copying everything i

Re: [RFC] Moving ltmain.sh and libtool.m4 into Automake

On 17/10/12 05:41, Gary V. Vaughan wrote: > Another consideration is that rolling Libtool into Automake would make > using Libtool as a standalone script rather more difficult. Having > said that, my impression is that Libtool is rarely used that way in > any case, and further simplification may b

Re: [RFC] Moving ltmain.sh and libtool.m4 into Automake

On Wed, 2012-10-17 at 16:41 +0700, Gary V. Vaughan wrote: > Another consideration is that rolling Libtool into Automake would make > using Libtool as a standalone script rather more difficult. Having > said that, my impression is that Libtool is rarely used that way in > any case, and further simp

Re: [RFC] Superseding aclocal?

On 10/17/2012 05:17 PM, Gary V. Vaughan wrote: > Hi Stefano, > > On 17 Oct 2012, at 16:45, Stefano Lattarini > wrote: >> On 10/17/2012 11:24 AM, Gary V. Vaughan wrote: >> >>> I think there is no need for such a cumbersome transition. Instead, I would >>> do it like this: >>> >>> 1. Fold macro