Re: [PATCH] more portable bootstrap procedure

[Ralf Wildenhues]

* Jim Meyering wrote on Sat, Dec 13, 2008 at 03:29:44PM CET:
> Ralf Wildenhues <address@hidden> wrote:
> >
> > Hmm, ok, I understand the point.  Well, up to you, that s/TAR/AMTAR/
> > change would be fine with me.
> 
> Since it's your change, you do need to sign off on the incremental ;-)

Yeah, right.  We can be glad that smiley wasn't trademarked after all...

> Is this what you suggest?

Yes, thanks.

Cheers,
Ralf

> --- a/bootstrap
> +++ b/bootstrap
> @@ -52,7 +52,7 @@ Options:
>  If the file $0.conf exists in the same directory as this script, its
>  contents are read as shell variables to configure the bootstrap.
> 
> -For build requisites, environment variables like \$AUTOCONF or \$TAR
> +For build requisites, environment variables like \$AUTOCONF or \$AMTAR

BTW, shouldn't that be "prerequisites"?  Isn't requisites something
entirely different (the corresponding German word denotes items that
are used for example in a stage play).

>  are honored.
> 
>  Running without arguments will suffice in most cases.
> @@ -284,6 +284,7 @@ check_versions() {
>    while read app req_ver; do
>      # Honor $APP variables ($TAR, $AUTOCONF, etc.)
>      appvar=`echo $app | tr '[a-z]' '[A-Z]'`
> +    test "$appvar" = TAR && appvar=AMTAR
>      eval "app=\${$appvar-$app}"
>      inst_ver=$(get_version $app)
>      if [ ! "$inst_ver" ]; then
> 
>