Alexandre Oliva writes:
> The problem of adding configure options is that, in a multi-package
> build (think of the so-called Cygnus top-level configure), all
> configure scripts must accept the same set of options, even if they
> ignore some, otherwise you can't use these options for any of the
> packages.
This has always been the argument against these kinds of changes, but it's
not really valid. For those people who don't use nested configures
there's a 100% win. Those people who do use nested configures cannot use
these new options (until they upgrade all their packages over time), but
this is no change from the situation they currently face.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
