-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin Pitt <[EMAIL PROTECTED]> writes:
> Roger Leigh [2005-03-31 14:42 +0100]:
>>
>> postgresql-common wraps some of the commands in
>> /usr/lib/postgresql/8.0/bin/, but this does not include pg_config.
>
> Actually I deliberately skipped pg_config since this program is only
> needed for building applications for PostgreSQL, not for using it. I
> thought that it was a good idea to explicitly specify the major
> version you are developing for rather than hide this in the cluster
> selection magic.
>
> I don't think that the particular pg_config version should be
> determined by /etc/postgresql-common/user_clusters or even
> ~/.postgresqlrc settings, this would make builds fairly indeterminate.
OK. That all makes sense.
>> It's easy enough to set the PATH for configure, but if this not
>> necessary it would mean libpqxx could build on any packaged
>> postgresql version, which would be rather more flexible than
>> hardcoding the path.
>
> For Etch all client libraries should be built against the PostgreSQL 8
> version of libpq (libpq4). libpq4 is fully compatible to libpq3 (but
> not the other way round, upstream removed some functions), so as long
> as a client app/lib builds fine with libpq4 there is no need for
> per-version client packages.
OK. If libpq4 is the default library to link with for /all/
PostgreSQL versions, why not simply put the 8.0 version of pg_config
(or a symlink) in /usr/bin for use by all clients? If it's only
useful for building and linking programs using libpq, and we only ever
link with libpq4, the 7.x pg_configs will be unused anyway??
> I really don't like the idea to link it against pg_wrapper. However, I
> am not opposed to the idea of putting a wrapper pg_config into
> /usr/bin which accepts a --version argument and calls the
> appropriate per-version pg_config. --version could default to the
> newest installed version. This would reduce the potential
> confusion/indeterminism somewhat.
>
> What do you think about this?
The added complexity, and the fact you still need to specify a
version, doesn't really make it more compelling than simply changing
$PATH. I think I would prefer to keep it as it is, unless you like
the idea in the above paragraph!
Regards,
Roger
- --
Roger Leigh
Printing on GNU/Linux? http://gimp-print.sourceforge.net/
Debian GNU/Linux http://www.debian.org/
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQFCUZcPVcFcaSW/uEgRAmlVAKD23RMEHWSiBlQOcodAN4yqIXjUbQCgly40
v0fgoz7VvsiSciMse4rZxPU=
=GzDM
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
