bug#9026: [PATCH] aclocal: handle ACLOCAL_PATH environment variable

2011-09-20 Thread Stefano Lattarini
On Monday 19 September 2011, Paolo Bonzini wrote: On Mon, Sep 19, 2011 at 18:39, Stefano Lattarini stefano.lattar...@gmail.com wrote: Just to be sure, you are not including http://lists.gnu.org/archive/html/automake-patches/2010-11/msg00091.html are you? No, not yet at least.

bug#9026: [PATCH] aclocal: handle ACLOCAL_PATH environment variable

2011-09-20 Thread Stefano Lattarini
On Tuesday 20 September 2011, Paolo Bonzini wrote: On 09/20/2011 12:51 PM, Stefano Lattarini wrote: Yes (and that's on purpose: ACLOCAL_PATH is typically used by a user which has newer versions of libraries installed, so they need their directories to override everything). Yes,

bug#9026: [PATCH] aclocal: handle ACLOCAL_PATH environment variable

2011-09-20 Thread Paolo Bonzini
On 09/20/2011 02:09 PM, Stefano Lattarini wrote: Yeah, I think the problem is that in the normal search path (from `aclocal -I /foo -I /bar'): 1. `/foo' 2. `/bar' 3. ACDIR-APIVERSION 4. ACDIR The directories from dirlist and ACLOCAL_PATH should go after (3), rather than

bug#9026: [PATCH] aclocal: handle ACLOCAL_PATH environment variable

2011-09-20 Thread Stefano Lattarini
On Tuesday 20 September 2011, Paolo Bonzini wrote: On 09/20/2011 02:09 PM, Stefano Lattarini wrote: Yeah, I think the problem is that in the normal search path (from `aclocal -I /foo -I /bar'): 1. `/foo' 2. `/bar' 3. ACDIR-APIVERSION 4. ACDIR The

bug#9026: [PATCH] aclocal: handle ACLOCAL_PATH environment variable

2011-09-20 Thread Stefano Lattarini
On Tuesday 20 September 2011, Stefano Lattarini wrote: We definitely want to clean this all up in 1.12 -- code, documentation and testsuite as well. For the moment, I'd like to push this follow-up patch to maint as well, to smooth out the transition a bit. I will push this patch and the