Dear Werner, Perhaps I am confused. Let's group users into three categories:
1. users who create documents with an already built groff 2. users who build groff from source 3. users who modify or enhance groff source code - groff developers The type of user I am referring to is number 2. Are you saying that type 2 users are still supposed to use ./configure and not ./bootstrap? Thanks. Blake On Wed, Sep 24, 2014 at 11:26 AM, Werner LEMBERG <w...@gnu.org> wrote: > > > 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 >
