Subject: Re: [htdig3-dev] GNU configure
From: Tom Metro (firstname.lastname@example.org)
Date: Sat Dec 04 1999 - 08:15:47 PST
Geoff Hutchison <email@example.com> writes:
> >I'm sure this can be accomplished with GNU configure, but I'm not
> >familiar enough with it to know how.
> The best solution is to write a small shell script that passes the
> appropriate options to configure for you.
I thought of that, but then it solves the problem for me while not
improving the situation for other Ht://Dig users.
I'd suggest creating a Perl script (I can't stand Bourne shell
programming, and see little need for it these days) that acts as an
outer wrapper, which could either read defaults from a user-edited
template file, or interactively prompt the user, then proceed to run
'configure' or 'make install' if it's a binary distribution. But it
seems redundant to have a script wrapped around configure. Again, I'm
not very familiar with configure, but isn't it designed for this type
of thing? Couldn't the interactive questions and the optional
read-from-a-file capability be incorporated into it? (Perl uses both
in it's build environment, though I don't recall if it uses GNU
configure or something custom.)
> Why did we do away with the CONFIG file?
I wasn't aware it was gone. When I built 3.1.3 I ran configure and
then ended up editing CONFIG to set the defaults as I liked them. This
was easy, once I figured out which file held the post-configure
> It's not as powerful as configure options.
I think command line options are more suited for people already
familiar with the defaults that the developers have set and already
know what they need to customize for their build. With command line
options, the presumption is that if you don't supply any options, the
right thing will happen in most cases. On the other hand an
interactive Q&A or file that the user is directed to by the
installation documentation tends to more explicitly say to the user,
"look these settings over carefully as many probably will need to be
changed for your environment."
For example, everybody's document root is different. There isn't
really a meaningful default. So running configure without specifying a
document root is more like an error condition.
-- Tom Metro Venture Logic firstname.lastname@example.org Newton, MA, USA
------------------------------------ To unsubscribe from the htdig3-dev mailing list, send a message to email@example.com You will receive a message to confirm this.
This archive was generated by hypermail 2b28 : Sat Dec 04 1999 - 09:28:58 PST