Package: libpq-dev Version: 8.0.3-12 Severity: normal Hi Martin, Oliver,
I've been taking a closer look at the new postgresql -dev package layout now that FTBFS bugs are finding themselves filed against packages, and I'm concerned that the current layout seems to more or less gratuitously break compatibility with historical sources. The package moves the headers from /usr/include/postgresql/ to /usr/include/postgresql/8.0/, which definitely breaks any sources that include the headers as <postgresql/foo.h>; and the recommended interface for detecting the include path is now pg_config --includedir. But there can only ever be one package installed at a time which provides pg_config... So if all such -dev packages must conflict, why not use the /usr/include/postgresql/ path directly? I realize this may be the result of an upstream decision, but I think this is worth considering given the number of packages that are still failing to build as a result of this change. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages libpq-dev depends on: ii libc6 2.3.5-3 GNU C Library: Shared libraries an ii libkrb53 1.3.6-4 MIT Kerberos runtime libraries ii libpam0g 0.79-1 Pluggable Authentication Modules l ii libpq4 8.0.3-12 PostgreSQL C client library ii libreadline5 5.0-10 GNU readline and history libraries ii libssl0.9.7 0.9.7g-1 SSL shared libraries ii zlib1g 1:1.2.3-3 compression library - runtime libpq-dev recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
