#331 clisp's configure file does not follow GNU conventions

[Bruno Haible]

Claudio Fontana writes:
-------------------------------------------------------------------------
clisp uses a different build system
(makemake), so the different use of DESTDIR is just a
detail, in comparison with the different semantics of
the configure script and the custom procedure
involved.
Here are the INSTALL instructions:

http://cvs.sourceforge.net/viewcvs.py/\*checkout*/clisp/clisp/unix/INSTALL?rev=1.25

My offer to work on a patch towards GNU coding
standards-based installation procedure holds, as soon
as we all agree on the necessity of the change.
-------------------------------------------------------------------------

Richard M. Stallman writes:
-------------------------------------------------------------------------
The need to explicitly run makemake is also incompatible,
but that
should be trivial to fix. Just have configure itself run
makemake
at the end. It will still be possible for people to run
makemake
manually, but it will be compatible with standard usage.

Why not make these small changes to make CLISP fit the
standard?
-------------------------------------------------------------------------

Bruno Haible replies:
-------------------------------------------------------------------------

The reason for presenting some recommendations and not
running makemake directly
was that it made some guesses that often did not reflect
the user's intentions,
and the user should have an option to correct these
guesses.
It's only recently, by looking at how other packages with
many dependencies
(e.g. mono, wxWidgets) that I understood how it can be
done: let the configure
script print a summary of the most important choices, like
this:

Settings:
use readline no
use libsigsegv yes
use internationalization yes
build postgresql interface no
...
-------------------------------------------------------------------------