Subject: Re: texinfo files
To: NetBSD-current Discussion List <>
From: Michael C. Richardson <>
List: current-users
Date: 09/26/1998 11:45:28

  As the guy who started the thread when I realized that wasn't
installed anywhere...

>>>>> "Greg" == Greg A Woods <> writes:

    Greg> I wouldn't really know, actually.  The only Linux distribution I have
    Greg> any experience with at all is the Red Hat one, and of course it did come
    Greg> with ready-to-run packages for everything on the CD-ROM.  I didn't have
    Greg> room on my Multia's disk for all the packages, of course, so I

  More to the point: getting a redhat box to rebuild the world under the
current redhat frequently fails.

  Even editing a file in the kernel build tree, and typing "make" often
fails to do what you expect (i.e. rebuild only part of the tree). It
might as well be a shell script, since you have to "make clean; make" to
get a new kernel built.

  So, let's not discuss whether redhat or other linux comes with texinfo.
It does. It also ships with Emacs, TeX, and every single window manager
ever invented. I also have no idea how to do things like install some
packages on the file server and have them functional on clients (Our /usr/pkg
works very well for that, btw).
  We should include makeinfo in the same place we include nroff, for the
same reasons.
  We should include 'info' in the smae place we include "man" for the same
reasons. We currently have no documentation on UUCP, yet it is part of
base. We *do* need to ship the info files. 
  TeX is not required for any of this.

  And now, back to libc: what exactly is being done to it? Is there a 
libc for i386 that I get from someone that has vasprintf so that I can
build gdb from our tree?

   :!mcr!:            |  Network and security consulting/contract programming
   Michael Richardson |         Firewalls, TCP/IP and Unix administration
	ON HUMILITY: To err is human, to moo bovine.

Version: 2.6.3ia
Charset: latin1
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface