Re: autoconf 3.0?

[Bruce Korb]

Bernd Jendrissek wrote:

> > > Paul> No, performance is by bigger problem for me, and I think for
> > > Paul> most people.  I have lots of disk space, and "configure" scripts
> > > Paul> compress well.  But my uniprocessors go only so fast,....
> > >
> > Akim> I second this :(  I'm not sure how we can fix this problem though :(
>Bruce:
> > By separating autoconf into two pieces.  One, a package by itself
> > that needs to be installed before an autoconf-ed package gets installed
> > and then the new-autoconf package that first checks that its other
> > half has already been installed.  The first half does system config
> > checks and installs hackaround libraries and other odds and ends,
> > the second half uses that information and handles project configuration
> > options.  You'd have to bump the major release number.

Bernd:
> In fact, wouldn't this pretty much describe the present config cache
> mechanism, extended to a system-wide scale?

Almost.  I suggest simplifying the code:

  . ${AC_LOCAL_STATE_DIR}/state || {
    echo you must pre-install autoconf 3.0 before installing this package.
    exit 1
  }