Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-11-09 Thread Adrian Bunk
On Sat, Nov 03, 2012 at 01:31:39AM +0100, Stefano Lattarini wrote: Oops, I should have answered to this before writing my last reply ... On 11/02/2012 09:46 PM, Eric Blake wrote: On 10/17/2012 04:15 AM, Stefano Lattarini wrote: Similar to AC_CONFIG_MACRO_DIR, but accepts more than one

Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-11-09 Thread Nick Bowler
On 2012-11-09 18:00 +0200, Adrian Bunk wrote: On Sat, Nov 03, 2012 at 01:31:39AM +0100, Stefano Lattarini wrote: On 11/02/2012 09:46 PM, Eric Blake wrote: On 10/17/2012 04:15 AM, Stefano Lattarini wrote: [...] Hmm, I'm wondering if we should do something fancier, and have both

aclocal: stop handling AC_CONFIG_MACRO_DIR; handle just AC_CONFIG_MACRO_DIRS (was: Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-11-09 Thread Stefano Lattarini
[+cc bug-automake] On 11/09/2012 05:33 PM, Nick Bowler wrote: On 2012-11-09 18:00 +0200, Adrian Bunk wrote: On Sat, Nov 03, 2012 at 01:31:39AM +0100, Stefano Lattarini wrote: On 11/02/2012 09:46 PM, Eric Blake wrote: On 10/17/2012 04:15 AM, Stefano Lattarini wrote: [...] Hmm, I'm wondering

Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-11-02 Thread Eric Blake
On 11/02/2012 02:46 PM, Eric Blake wrote: +++ b/lib/autoconf/general.m4 @@ -1727,13 +1727,21 @@ AC_PROVIDE([AC_CONFIG_AUX_DIR_DEFAULT])dnl ## ## +# AC_CONFIG_MACRO_DIRS(DIR-1 [DIR-2 ... DIR-n]) +# +# Declare

Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-11-02 Thread Eric Blake
On 11/02/2012 03:19 PM, Eric Blake wrote: I wrote these off the cuff while composing the email, so they are relatively untested. And while re-reading, I see I botched the self-redefinition, as well as failed to call AC_CONFIG_MACRO_DIR if the first use was AC_CONFIG_MACRO_DIRS. Here's

Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-11-02 Thread Stefano Lattarini
Oops, I should have answered to this before writing my last reply ... On 11/02/2012 09:46 PM, Eric Blake wrote: On 10/17/2012 04:15 AM, Stefano Lattarini wrote: Similar to AC_CONFIG_MACRO_DIR, but accepts more than one argument. This will allow projects to use several m4 macro local dirs.

Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-10-21 Thread Russ Allbery
Andrew W. Nosenko andrew.w.nose...@gmail.com writes: On Wed, Oct 17, 2012 at 1:14 AM, Eric Blake ebl...@redhat.com wrote: Wrong. For better or worse, Libtool has a goal of specifically being usable even without autoconf or automake. Yes, but this goal is missed. And missed very far and

Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-10-18 Thread Stefano Lattarini
On 10/17/2012 10:05 PM, Nick Bowler wrote: On 2012-10-17 09:25 +0200, Stefano Lattarini wrote: On 10/16/2012 10:46 PM, Nick Bowler wrote: I think it's important to have, for testing, a version of aclocal that actually makes use of this feature. The reason I wrote this patch is because I want

Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-10-17 Thread Stefano Lattarini
Hi Nick, thanks for the feedback. On 10/16/2012 10:46 PM, Nick Bowler wrote: It's a little bit hard to review documentation in unified diff format, but I have some comments: On 2012-10-16 21:30 +0200, Stefano Lattarini wrote: Similar to AC_CONFIG_MACRO_DIRS, but accepts more than one

Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-10-17 Thread Gary V. Vaughan
Hi Nick, On Oct 17, 2012, at 3:46 AM, Nick Bowler nbow...@elliptictech.com wrote: Tools like libtoolize will (again, hopefully) be using this information to decide where to copy libtool macros. Probably aclocal --install will need to do this as well. If multiple macro directories are

Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-10-17 Thread Gary V. Vaughan
Hi Eric, On Oct 17, 2012, at 4:45 AM, Eric Blake ebl...@redhat.com wrote: On 10/16/2012 03:38 PM, Andrew W. Nosenko wrote: Excuse, may be it's too late to party, but... What is the reason to to invent yet another macro name? Anyway in the most packages there will be one and the only one

Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-10-17 Thread Gary V. Vaughan
Hi Stefano, On Oct 17, 2012, at 2:25 PM, Stefano Lattarini stefano.lattar...@gmail.com wrote: based solely on this documentation, that deal with these macro directories. It would be very bad if we ended up with two tools that, for example, interpreted the directory ordering differently. ...

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

2012-10-17 Thread Stefano Lattarini
[Adding Automake list in CC:] Reference: https://lists.gnu.org/archive/html/autoconf-patches/2012-10/msg00018.html 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 could find

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

2012-10-17 Thread Gary V. Vaughan
Hi Stefano, Thanks for the fast response! On 17 Oct 2012, at 15:52, Stefano Lattarini stefano.lattar...@gmail.com wrote: [Adding Automake list in CC:] Reference: https://lists.gnu.org/archive/html/autoconf-patches/2012-10/msg00018.html On 10/17/2012 10:25 AM, Gary V. Vaughan wrote:

Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-10-17 Thread Adrian Bunk
On Wed, Oct 17, 2012 at 02:50:20AM +0300, Andrew W. Nosenko wrote: ... and noone uses libtool without automake (the reverse is not true again). Wrong. For better or worse, Libtool has a goal of specifically being usable even without autoconf or automake. Yes, but this goal is missed.

[PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-10-16 Thread Stefano Lattarini
Similar to AC_CONFIG_MACRO_DIRS, but accepts more than one argument. This will allow projects to use several m4 macro local dirs. This is especially important for projects that are used as nested subpackages of larger projects. See also:

Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-10-16 Thread Nick Bowler
It's a little bit hard to review documentation in unified diff format, but I have some comments: On 2012-10-16 21:30 +0200, Stefano Lattarini wrote: Similar to AC_CONFIG_MACRO_DIRS, but accepts more than one argument. I assume this was meant to say

Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-10-16 Thread Andrew W. Nosenko
Excuse, may be it's too late to party, but... What is the reason to to invent yet another macro name? Anyway in the most packages there will be one and the only one line: AC_CONFIG_MACRO_DIR([m4]) And even when the many dirs are need, they will be written one by one in the theirs own macro

Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-10-16 Thread Eric Blake
On 10/16/2012 03:38 PM, Andrew W. Nosenko wrote: Excuse, may be it's too late to party, but... What is the reason to to invent yet another macro name? Anyway in the most packages there will be one and the only one line: AC_CONFIG_MACRO_DIR([m4]) And even when the many dirs are need,

Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-10-16 Thread Andrew W. Nosenko
On Wed, Oct 17, 2012 at 12:45 AM, Eric Blake ebl...@redhat.com wrote: On 10/16/2012 03:38 PM, Andrew W. Nosenko wrote: Excuse, may be it's too late to party, but... What is the reason to to invent yet another macro name? Anyway in the most packages there will be one and the only one line:

Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-10-16 Thread Eric Blake
On 10/16/2012 04:08 PM, Andrew W. Nosenko wrote: The problem is that existing tools (here's looking at you libtool) are inconsistent if you HAPPEN to use AC_CONFIG_MACRO_DIR - some use the first directory, others use the last, and some crash altogether. Back-compat requires that we have a new

Re: [PATCH 1/2] AC_CONFIG_MACRO_DIRS: new macro, mostly for aclocal

2012-10-16 Thread Andrew W. Nosenko
The answer is two fold. Lyrics and pragmatics. Pragmatic part is very simple: If you feel from your experience that the path with introducing the new macro is better -- then let it be. After all, you know about this triplet (autconf+automake+libtool) far more than me. Lyrics is below, feel free