Let me see if I understand the various goals at work here:

a) Maintaining the gcc import in as close to "pristene" fastion as possible.
b) Permitting cross-compiler builds from this gcc tree on arbitrary
   host systems. [Is this the same goal as (a)? I'm not sure]
c) Not having two copies of texinfo in the source tree.
d) Permitting upgrades of texinfo independent of gcc.
e) Building documentation with the compiler.

<tv@pobox.com> (Todd Vierling) writes:

> I'd like to just point the build of src/gnu/usr.bin/texinfo to the stuff
> imported from gcc, and remove the old texinfo files in the name of disk
> space.  My assumption based on this model is that if we were to import a
> newer, incompatible texinfo, that it would be located (again) at
> src/gnu/dist/texinfo, outside the toolchain tree.

In the event of such an import (option d above), would the gcc tree
use that new texinfo, or its own? Would a different texinfo thus be
used for building gcc documentation based on whether the build
happened through our build system or through gcc's shipped
configure/build system?

        - Nathan