🚀 go-pugleaf

In article <BASHFORD.92Feb13160404@zippy.scripps.edu>, bashford@scripps.edu (Don &) writes:
|> I think environment variable hooks should be provided whenever a
|> software system has to know about pathnames for finding include files,
|> data files, libraries, compiler passes, auxilliary programs, etc.
|> For example, the Mit X11R4 sample distribution compiled for installation
|> in "the usual places" (under /usr) can be made to work properly
|> if you put it elsewhere by means of environment variables.  If
|> you want to install things in non-standard places because of
|> disk space or access restrictions or NFS server politics, this is
|> very important.
|> 
|> Top level config files that allow for setting pathnames at compile
|> time are also essential, but not a substitute for environment variable
|> hooks.  What if you want to change the location of the installed files
|> because you have access to a new disk or a new server?  You don't want to
|> have to recompile all your software, so its nice if you can just set
|> some new environment variables

You don't need to recompile everything to change the destination of the
installed binaries, passing a define on make's command line would do it:
	make 'BINDIR=whatever' install

Given personal preferences, I concede that overiding Makefile configurations
with environment variables can be useful, but the sources should compile
correctly in the absence of these environment variables once your system
configuration stabilizes.

-Gary