> Making it more dependent on versions of other software that are
> _currently_ available on the Internet means that older copies of
> groff will no longer build when those other repositories have moved,
> are no longer available, or old versions of those libraries are not
> where expected.
How on earth do you come to that conclusion? If you check out an old
version of groff, you simply regenerate the `configure' script, and
that's it.
> We are becoming increasingly dependent on a moving target.
> ./configure had a much less problem with this. This is a big issue.
This is *not* an issue at all. I have to repeat: The end-user will
*always* see `configure', and nothing else! *Nothing* changes.
Werner
