Re: autoreconf --help

2006-05-18 Thread Paul Eggert
Ralf Wildenhues [EMAIL PROTECTED] writes:

 OK to apply?

Yes, and thanks.

 Do you think we need to announce this change in NEWS?

Not really.


___
http://lists.gnu.org/mailman/listinfo/libtool


Re: autoreconf --help

2006-05-18 Thread Ralf Wildenhues
Hi Paul,

* Paul Eggert wrote on Thu, May 18, 2006 at 08:45:37AM CEST:
 Ralf Wildenhues [EMAIL PROTECTED] writes:
 
  OK to apply?
 
 Yes, and thanks.

Done, thanks!

Cheers,
Ralf


___
http://lists.gnu.org/mailman/listinfo/libtool


Re: autoreconf --help (was: Libtool release plan)

2006-05-17 Thread Olly Betts
On Wed, May 17, 2006 at 07:19:57PM +0200, Ralf Wildenhues wrote:
 At the same time let's get rid of the
 CONFIGURE-AC argument we're suggesting there but which didn't work right
 anyway.  But let's not actually change the functionality, so that what
 works continues to.  (A bit fragile, I know; I think the long term goal
 should be to implement that functionality properly, in all autotools;
 but I don't want to do that now.)

Another approach would be to change autoreconf to just remove any
filename part - that's easy to explain to the user (the top-level
directory or any file in it) and also easy to implement (simply
s,[^/\\]*$,, on that argument.)

Cheers,
Olly


___
http://lists.gnu.org/mailman/listinfo/libtool


Re: autoreconf --help

2006-05-17 Thread Ralf Wildenhues
Hi Olly,

* Olly Betts wrote on Wed, May 17, 2006 at 08:56:28PM CEST:
 On Wed, May 17, 2006 at 07:19:57PM +0200, Ralf Wildenhues wrote:
  At the same time let's get rid of the
  CONFIGURE-AC argument we're suggesting there but which didn't work right
  anyway.  But let's not actually change the functionality, so that what
  works continues to.  (A bit fragile, I know; I think the long term goal
  should be to implement that functionality properly, in all autotools;
  but I don't want to do that now.)
 
 Another approach would be to change autoreconf to just remove any
 filename part - that's easy to explain to the user (the top-level
 directory or any file in it) and also easy to implement (simply
 s,[^/\\]*$,, on that argument.)

Well, the point is that
  autoreconf subdir/foobar.ac

simply won't cause the called tools to use foobar.ac, but the first that
exists in the list
  subdir/configure.ac
  subdir/configure.in

The file name you pass currently is stripped off as you suggest, but
since it won't be used, I think that it is confusing to document this
unless it is actually used.

Cheers,
Ralf


___
http://lists.gnu.org/mailman/listinfo/libtool


Re: autoreconf --help

2006-05-17 Thread Olly Betts
On 2006-05-17, Ralf Wildenhues [EMAIL PROTECTED] wrote:
 Well, the point is that
   autoreconf subdir/foobar.ac

 simply won't cause the called tools to use foobar.ac, but the first that
 exists in the list
   subdir/configure.ac
   subdir/configure.in

Yeah, I know.

My thought was that it is sometimes convenient to be able to do
something like:

for f in `find . -name configure.ac -print` ; do autoreconf $f ; done

But it's not a big deal - it's not hard for the user to chop the leaf
themselves in the case above, and as you say it's a bit odd to accept a
filename to indicate just a directory.

Cheers,
Olly



___
http://lists.gnu.org/mailman/listinfo/libtool