From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Wheeler <david(at)kineticode(dot)com>, josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Suggestion: Which Binary? |
Date: | 2006-04-01 15:47:39 |
Message-ID: | 442EA09B.1000602@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Jim C. Nasby wrote:
>On Fri, Mar 31, 2006 at 07:01:18PM -0500, Tom Lane wrote:
>
>
>>David Wheeler <david(at)kineticode(dot)com> writes:
>>
>>
>>>Yes, but even the environment variables get me what I want. I
>>>therefore respectfully submit the attached patch to document them in
>>>the INSTALL file.
>>>
>>>
>>It seems rather pointless to document two instances of what is in fact
>>a generic autoconf-script behavior ...
>>
>>
>
>The problem is that PostgreSQL is moving out of the realm of "hard-core
>geeks only" and more into the mainstream. I'd bet a number of our users
>have very little idea how autoconf and it's progeny work. It's probably
>not unlikely that those folks would be able to figure out where their
>perl was, but then not know how to tell it to configure.
>
>
Most such users would use a binary distribution, though - either from
the OS supplier or from our collection of binaries. If people are going
to build postgres themselves from source then I *do* expect them to be
moderately hard-core geeks.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2006-04-01 16:44:30 | Re: Postgres dies when using an intarray operator |
Previous Message | Thomas Hallgren | 2006-04-01 15:43:46 | Re: Remote PL/Java, Summary |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Drake | 2006-04-01 18:20:58 | patch to have configure check if CC is intel C compiler |
Previous Message | Peter Eisentraut | 2006-04-01 15:34:57 | Re: Suggestion: Which Binary? |