Re: [Pkg-grass-general] [Fwd: PostgreSQL transition ahead]
On Tue, Jun 07, 2005 at 11:15:45AM -0400, Steve Halasz wrote:
> Forwarding this since it affects qgis, grass and postgis(?). -Steve
>
> > (1) postgresql-dev was split into libpq-dev (for client apps like
> > postfix or pygresql) and postgresql-server-dev-<version> for server
> > extensions (like postgresql-plruby and postgresql-ocaml).
> >
> > (2) PostgreSQL 8.0 brought a new SONAME for libpq (libpq4), which
> > removed a few symbols which were only intended for internal use,
> > but were used nevertheless by some client apps (like "psql").
> > libpq4 can talk to all PostgreSQL servers back to 7.3 (same like
> > libpq3).
> >
> > (1) makes all packages FTBFS that build-depend on postgresql-dev (I
> > CC'ed all affected packages). These need to be changed to depend on
> > libpq-dev, and make buildable again. This will automatically care for
> > (2) since libpq-dev makes the package depend on libpq4 then.
> >
I would suggest to depend on both libpq-dev | postgresql-dev for
clients. That would retain sarge compatibility in backports for free.
> > * Sid will be broken for a fair amount of time anyway since there are
> > more transitions ahead of us (g++ 4.0, dbus, etc.)
> >
Yay, I missed those daily instabilities :)
--
Francesco P. Lovergine
Reply to: