[Autoconf-patches] Re: autoscan repair

[Akim Demaille]

| [Quoting Akim Demaille, on September 4 2000, 16:55, in "Re: autoscan repair"]
| > 
| > | The Getopt::Long change in autoscan (2000-08-01) is broken. Use the
| > | attached patch to repair it. I have Redhat 5.2's stock Perl 5.004_04,
| > | btw., which should be fairly average.
| 
| Actually, 5.004 is very old and the Getopt::Long that comes with it
| does not (yet) support the Configure subroutine.
| 
| > Arg, I actually trusted the documentation, thanks!
| > 
| > CONFIGURATION OPTIONS
| >        GetOptions can be configured by calling subroutine
| > ===>   Getopt::Long::Configure. This subroutine takes a list of
| 
| The documentation is right. Please consider upgrading your Perl and/or
| Getopt::Long packages. If that is not possible, use subroutine
| "config" instead.

Well, then I'd say the doc is still confusing: there are several
references to `config' too:

       GetOptions can be configured by calling subroutine
       Getopt::Long::Configure. This subroutine takes a list of
       quoted strings, each specifying a configuration option to
       be set, e.g.  ignore_case. Options can be reset by
       prefixing with no_, e.g.  no_ignore_case. Case does not
===>   matter. Multiple calls to config are possible.

       Previous versions of Getopt::Long used variables for the
       purpose of configuring. Although manipulating these
       variables still work, it is strongly encouraged to use the
===>   new config routine. Besides, it is much easier.



The question is: will you keep backward compatibility with `config'
for a while?

Autoscan is a maintainer tool, so we shouldn't be afraid to ask the
maintainers to update their tools.  OTOH, if current distros such as
RH still ship an ``old'' Perl, then it's definitely too early for us
to require a more modern version.