On 5/9/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
Am Freitag, 5. Mai 2006 20:07 schrieb Martijn van Oosterhout:
> 1. Provide an escape option they can add
> 2. Package systems can usually apply patches prior to compiling, they can
> always remove the offending line if they like.
> 3. Try and get feedback from them now rather than wait
My feedback is this: You are going to enter a world of pain.
Seems that way. Especially if the non-PGAC options won't be
handled automatically.
Some projects have solved the problem different way - by printing
out the summary of most important options at the end of configure:
PostgreSQL version X.X.X
OpenSSL: no
Integer datatime: yes
Python: yes
Perl: yes
So at the end of configure the user can visually confirm
his expectations without needing to parse the noise
from full configure output. Maybe this would be better
solution.
--
marko
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
