Re: Failing to use gnulib bootstrap in libtool

[Gary V. Vaughan]

Hi Jim,

Thanks for the feedback.

On 3 Sep 2010, at 13:05, Jim Meyering wrote:
> Gary V. Vaughan wrote:
>> 14. Updating
>> ============
>> 
>> There's no obvious way for bootstrap to update itself.  Since we got to some 
>> lengths to install the `gnulib' subproject that it comes from, it should at 
>> least be able to warn that it is out of date even if a self-update is not 
>> possible - is it even possible (let alone portable) for a script to copy 
>> something over itself while running, and then re-exec to pick up the changes?
> 
> Detection would be easy.  Something like this:
> 
>    cmp $0 $gnulib_path/$build_aux/bootstrap

Well, $build_aux is the path from AC_CONFIG_AUX_DIR, and at least in Libtool's 
case is not the same as gnulib's build-aux path.

> A warning would be good, but I would avoid an auto-update.

How about:

   cmp $0 $gnulib_path/build-aux/bootstrap >/dev/null 2>&1 \
       func_warning "$gnulib_path/build-aux/bootstrap differs from $0"

Cheers,
-- 
Gary V. Vaughan (address@hidden)

PGP.sig
Description: This is a digitally signed message part