Re: config.status --recheck != configure

[Akim Demaille]

>>>>> "Bob" == Bob Friesenhahn <address@hidden> writes:

Bob> I have learned the hard way that 'config.status --recheck'
Bob> produces incomplete results as compared to the original
Bob> 'configure' that created config.status.  I assume that this is
Bob> because config.status runs configure with the extra options
Bob> '--no-create --no-recursion'.

Bob> Is this shortcoming by design or accident?

Both: by accident what you propose is having ./config.status kill
itself by running configure which creates it.  So by design, it is
avoided.

Bob> It is much more convenient to simply execute 'config.status
Bob> --recheck' rather than 'config.status --version' and then pasting
Bob> in what it prints.

Agreed :(