| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| 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 00:44:11 |
| Message-ID: | 19697.1012351451@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | 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.
"--with-everything"? Or more usefully, "--with-everything --without-perl"
if, say, you don't have Perl installed.
Or you could just reverse the defaults on all the options, but that'd
likely provoke a revolt.
> I remembered that in the old days PHP had an interactive setup script,
Perl's got one of those too, and I hate it ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mitch Vincent | 2002-01-30 01:33:22 | Re: A simpler way to configure the source code? |
| Previous Message | Don Baccus | 2002-01-30 00:43:01 | Re: A simpler way to configure the source code? |