[Pkg-postgresql-public] pg_bulkload package sponsorship

[Alexander]

On Thu, May 31, 2012 at 4:39 PM, Christoph Berg <*@debian.org> wrote:
[...]
>> The problem is not libpq per se, but PG_VERSION_NUM in
>> /usr/include/postgresql/pg_config.h
>
> Ah, that's a problem then, sure.
>
>> Which implies in-the-tree build in different environment for every
>> version of PostgreSQL. Long live OpenVZ.
>
> Is PG_VERSION_NUM the only thing taken from that file? If you are

It is included indirectly through some "postgres.h", thus no clean
hack is visible. It is pity, but seems to be no way - the target
PostgreSQL development version should be the only one in the system.


Ok, finally I have it for v8.4 and 9.0, 9.1 will be soon (should make
the installer branch for extensions).

1. pg_buildext is not possible, the version is a set in a `rules' variable
2. there is an explicit rule for regression tests, should be run as
`postgres' user only
3. server side package has `configure' and `postinst' with debconf
interface. The admin can pick the databases,
    where to install the extension. `template1' is default. Is it a
good idea to have this input `high' priority?
4. postrm cleanly removes the function from the databases, priorly
selected with debconf

Thanks to Ivan Shmakov for combing control.in wording.


Could anybody of Debian developers to have a look at
http://acca.it.cx/~assa/pgbulkload/ with a word of advise?


-- 
Sincerely yours, Alexander Kuznetsov