Comment 9 for bug 61850

On Saturday 20 January 2007 21:09, Nicola Larosa wrote:
> > By moving from universe to main, the required build
> > dependencies for PostgreSQL support became
> > unavailable, and hence Kexi builds without support
> > for PostgreSQL.
>
> Which dependencies, exactly? Why are they in universe? What can be done?

The C++ wrapper library for the PostgreSQL client library called libpqxx.

I don't know why it's in universe. Perhaps because Canonical (or whoever
decides) doesn't want to provide things like security support for those
packages? No idea.

> > Yes, I'm aware the problem still stands.
>
> What can be done to solve it?

It can be dealt with upstream, by using something like dlopen to avoid a build
time dependency on the libraries. This isn't a great solution, because then
you lose the type checking you get by having a copy of the right version of
the PostgreSQL development headers around when compiling. It also means that
determining which drivers are available is no longer a case of simply
checking the system configuration cache (built by kbuildsycoca).

Or Kexi could be modified to use the Qt SQL API (although this may have some
drawbacks, and isn't likely to happen any time soon).

Or Kexi could be modified to use the PostgreSQL C library directly (not a bad
idea - libpqxx has caused bother for the Kexi team before).

It could also be fixed in Ubuntu, by moving PostgreSQL into main (also a good
idea).

Or it could they could fix it by creating a separate tarball containing just
the PostgreSQL driver source code, and putting that in universe.

That's all I can think of, off the top of my head.