FreeTDS Development Group

[James Cameron <cameron AT stl.dec.com>]

Mihai Ibanescu wrote:
> On Tue, 12 Jan 1999, Craig Spannring wrote:
> > The 'configure' file needs to be auto-generated for each machine.
> This is wrong. GNU packages should install even on systems without
> autoconf.

I agree with Mihai.  All the other packages that I master and use with
autoconf ship the configure file and do not require autoconf to be
installed.  The whole point of autoconf is to have it write a script
that configures the package for compilation and installation on any
target machine.

The file "configure" would normally be included within CVS, and would
only be changed if;

        1)  a new version of autoconf was made available, or;

        2)  some new feature is required of the platforms that
            mandates a configuration phase check for it.

The package I master (Netrek Vanilla Server) would not decide to do step
one unless step two caused it as well, or if someone complained that the
configuration phase failed on their platform and that the new version of
autoconf fixes it.

-- 
James Cameron                                      (cameron AT stl.dec.com)

OpenVMS, Linux, Firewalls, Software Engineering, CGI, HTTP, X, C, FORTH,
COBOL, BASIC, DCL, csh, bash, ksh, sh, Electronics, Microcontrollers,
Disability Engineering, Netrek, Bicycles, Pedant, Farming, Home Control,
Remote Area Power, Greek Scholar, Tenor Vocalist, Church Sound, Husband.

"Specialisation is for insects." -- Robert Heinlein.