Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!sbphy.ai.mit.edu!bfox
From: bfox@sbphy.ai.mit.edu (Brian Fox)
Newsgroups: gnu.bash.bug
Subject: Minor glitch in Bash 1.04 Makefile
Message-ID: <8912191643.AA05565@sbphy.Ucsb.EDU>
Date: 19 Dec 89 16:43:29 GMT
References: <8912191612.AA13443@orion>
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 37


   Date: Tue, 19 Dec 89 11:12:59 EST
   From: bet@orion.mc.duke.edu (Bennett Todd)
   X-Zippy: Well, I'm INVISIBLE AGAIN..  I might as well pay a visit to the
    LADIES ROOM...

   First, a minor nit. Most of the other gnu distributions seem to be
   following the convention of installing in /usr/local/{bin,man,...}
   which makes me very happy, since that's the convention I'm following:-).
   Are more folks using that or using /usr/gnu/bin as destdir (which the
   Bash makefile comes with)?

Everywhere I go, I need a full tree.  It just seemed reasonable and easy
to place the GNU stuff in:

	/usr/gnu
		info	-- contains the info files.
		src	-- contains the source.
		  lib	-- contains library source.
		bin	-- binary executables.
		etc	-- things that might go in /usr/etc. in.cfingerd.
		lib	-- libraries.

This means that I can install all of the software that I want without
giving unsuspecting people strange behaviours.  For example, if I
install the GNU version of ls, only the people who have /usr/gnu/bin in
their paths will get it.

Typically, there are links for emacs, bash, and gcc to the appropriate
places in the gnu tree.

   Now for the actual buglet, the DOCUMENTATION define refers to
   $(LIBRARY_DOCS) where it appears it should be $(LIBRARY_DOC).

Thanks.

Brian