I agree with chuck. From the user POV(which is me) I would much rather
have a configure type interface. Currently I have a 2 page doc that I keep
to remind me which files and options to change for netatalk based on what
machine I'm installing on.
I much prefer the Apache or mysql method where all(almost) of the options
can be selected via command line.
s
--On Tue, May 25, 1999 1:05 PM -0700 chuck <[EMAIL PROTECTED]> wrote:
> I have to say the 'global makefile' thing rarely works - there
> are too many platforms/makes out there. As someone who uses
> odd platforms (Ultrix, OpenBSD on (MIPS|Alpha|Sun|Apple), and
> not Linux), I really hate the 1991 flashbacks of editting .h
> files and Makefiles (or Perl's Configure).
>
> Autoconf does a lot of that work for us and leaves a nice
> "config.h" that has the platform specific needs to work with.
>
> Let the user choose to disable TCP wrappers at an easily
> reproduced "./configure" line. Things like that.
>
> Recall that the common use of this is to build it and move on
> with life for 6 months, a year whatever. Then to come back and
> try to figure out how we built it before when we need to
> upgrade. Me? I keep around the ./configure lines in a build
> area with the tar.gz files (EG: netatalk-1.4b2-configure, or
> gzip-1.2.4-configure).
>
> The hard work has been done with autoconf. It's also an interface
> admins are familiar with -- and for those of us who compiled OSS in the
> late 80's and early 90's, one that we are grateful for.
<stuff deleted>
--
Scott R. Every - mailto:[EMAIL PROTECTED]
EMJ Internet - http://www.emji.net
voice : 1-888-258-8959 fax : 1-919-363-4425
