Re: A simpler way to configure the source code?

From: teg(at)redhat(dot)com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=)
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: A simpler way to configure the source code?
Date: 2002-01-30 15:50:05
Message-ID: xuywuxzx2he.fsf@halden.devel.redhat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:

> The other day, I did a test build of "everything", which involved
> specifying 17 command-line arguments to configure. This is probably the
> reason why some fringe features are not tested very often: the list of
> options is pretty overwhelming.
>
> I remembered that in the old days PHP had an interactive setup script,
> that asked you mainly yes/no questions about each feature you wanted, and
> would run "configure" based on the answers it got. This sort of thing
> might help our situation, because instead of having to specify all the
> options, users can just keep pressing Y all the time. Of course it could
> also be considered as a general improvement in user-friendliness.

I hated that (same for perl).

--
Trond Eivind Glomsrød
Red Hat, Inc.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleg Bartunov 2002-01-30 17:21:00 postgresql under Windows is slow
Previous Message Tom Lane 2002-01-30 15:46:25 Re: Syscaches should store negative entries, too