🚀 go-pugleaf

Ideally, the only program which should ever need to be specially
`configure'd is GNU make.  make is powerful enough, in and of itself,
to be able to completely replace *both* configuration schemes, given
standardization of the inner workings of the GNUmakefiles.

For example, I should be able to have a source tree with a GNUmakefile
in it saying:

+------------------------------
|SUBDIRS=prog1 prog2 prog3 ...
|include source-tree.mk
+------------------------------

To build all the programs in this tree, I should be able to do
something like this:

make check	# make sure everything is configured correctly
make all
make tests
make install

All the configuration stuff that both Cygnus configure and autoconf
put in Makefiles should be stored in at most two configuration files,
$(target).mk and $(host).mk; the `make check' step would, among other
things, make sure that these exist and define all the necessary
information (and if not, telling you).  All the benefits of (bleah)
imake, at a fraction of the pain...

(Conceivably, a user wanting to use a GNU program would then need to
download at least two other packages: GNU make, and a set of
configuration files appropriate for their environment.)

-GAWollman


-- 
   Garrett A. Wollman   = wollman@uvm.edu = UVM is welcome to my opinions
                        = uvm-gen!wollman =
   That's what being alive is all about.  No deity, no higher goal
   exists, than to bring joy to another person.    - Elf Sternberg