RE: RFC: ./configure or ./config.status --clean

[Robert Collins]

I think there are valid points to both the 'tools don't clean up after
themselves' and the 'autoconf and automake shouldn't be in lockstep'
arguments.

IMO autoconf will make life easier for both automake and non-automake
users by providing a clean capability of it's own. That in itself should
make the self-cleaning approach useful. 

As for the reductio argument on tools cleaning up point, well any tool
that generates files as a sideeffect, should be responsible for cleaning
them up.

rm, cp, ln don't generate files as sideeffects. Compilers sometime do -
ie when generating dependencies files as a sideeffect of compilation.

libtool certainly does - and IIRC it provides it's own clean capability
(for the .libs directory).

As a secondary point, as a user, I'd love to see one of two things:
* looser coupling between automake and autoconf, or
* a single product.

The current tight coupling presents some challenges in getting projects
upgraded. 

Anyway, just my 2c.

Rob