From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
Cc: | <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Library names on Unix |
Date: | 2006-01-04 14:29:57 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4E7ED7C@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----Original Message-----
> From: Peter Eisentraut [mailto:peter_e(at)gmx(dot)net]
> Sent: 04 January 2006 14:12
> To: Dave Page
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] Library names on Unix
>
> As far as consistency goes, this behavior is consistent with other
> PostgreSQL-using packages (that I have had a hand in), e.g.,
> libpqxx.
And inconsistent with other PostgreSQL-using packages that I have a hand
in, e.g., pgAdmin :-)
> While
> the dichotomy between options and variables is certainly not
> comprehensible
> to the casual user, I'd hesitate to make up new stuff for the
> purpose of
> spelling things differently. As long as it's documented, it
> should be OK.
It seems to me it's not just a case of spelling things differently -
it's doing things the way users expect. I've *never* come across a
configure script that required me to set options via the environment
rather than a --with-foo= style option.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | noreply | 2006-01-04 22:36:30 | [ psqlodbc-Bugs-1000518 ] "Requested conversion is not supported" when trying to query information_schema.tables on SQL |
Previous Message | Peter Eisentraut | 2006-01-04 14:12:04 | Re: Library names on Unix |