Re: Martin Pitt 2014-03-17 <20140317073216.gb3...@piware.de>
> > hsql-postgresql started to fail to build on Debian because the header
> > file postgres.h was removed from libpq-dev. According to
> > https://bugs.debian.org/314427, this is a file that should only be used
> > for server-side programming and hence was removed from libpq-dev;
> > clients should only use these header files, it seems:

Hi,

I've had a look at the haskell-hsql-postgresql source - the place
where it reads postgres.h and catalog/pg_type.h is where it defines
the mapping from haskell datatype -> PostgreSQL datatype. As the
package isn't just a client, but an interface driver (apparently using
the "binary" wire protocol), it's ok to make it depend on the server
headers.

Unfortunately there's not really a good place where else to pull this
information from. Maybe http://libpqtypes.esilo.com/ would help, but
this isn't packaged yet, and would require rewriting hsql-pg.

> If there are legitimate reason why this client-side application needs
> a server-side header, the package could grow a build dependency on
> postgresql-server-dev-9.3 to at least make this fact explicit and fix
> the FTBFS in the short term.

The OIDs of the exposed datatypes won't ever change, so B-D on
postgresql-server-dev-all is safe even if -9.3 will be replaced by
-9.4 or later in the future.

What worries me, though, is this:

Build-Conflicts:
 postgresql-server-dev-8.3,
 postgresql-server-dev-8.4

haskell-hsql-postgresql (1.7.3-2) unstable; urgency=low

  * Make postgresql-server-dev-8.[34] a Build-Conflicts (Closes: 559583)
    If this package is present at build-time, the resulting ghc-pkg info will
    reference a directory from it in Includes, causing the installation to
    fail (see #471786). But if it is not, everything goes well and we have one
    dependency less.

 -- Joachim Breitner <nome...@debian.org>  Sat, 05 Dec 2009 17:10:34 +0100

I cannot reproduce the problem here with postgresql-server-dev-9.3
installed - the deps of the resulting .debs are the same, but I didn't
look into the package for file references in there.

B-C on packages that change name with every release seems fragile
anyway, so it would best be avoided.

Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/

Attachment: signature.asc
Description: Digital signature

Reply via email to