[Pkg-postgresql-public] [pgsql-pkg-debian] Debian packaging of the q3c and pgsphere extensions

Christoph Berg myon at debian.org
Thu Aug 3 09:25:45 UTC 2017


Re: Ole Streicher 2017-07-31 <d478ece1-f884-0576-91f3-910820d54669 at debian.org>
> I am posting to both lists since I am unsure where the best place is. I
> am however not subscribed to any of them, so please keep in Cc for the
> moment:

Hi Ole,

both lists are fine.

> As a dependency of the Virtual Observatory "DACHS" package [1], which I
> am planning to package, I need to have the "q3c" [2] and "pgsphere" [3]
> packages in Debian. All packages already exist in a separate repository
> [4]; the initial packaging was done by Florian Rothmaier.

Florian was talking to me about these some years back, iirc we were
close to getting the packages polished up, but then communication got
stuck at some point. Thanks for taking this up again!

I'd also like to include the packages on apt.postgresql.org.

> However, I am very new to Postgresql extension packaging, and therefore
> I would ask to get some useful hints here. Especially: Is there a Debian
> policy for postgresql extensions that documents the preferred way for
> packaging?

pg_buildext(1) and dh_make_pgxs(1) (both from postgresql-server-dev-all)
should provide a working skeleton at least for the case of extension-only
packages.

> A preferred git repository? Or is the Debian Science git
> repository OK?

Any git repo works.

> Are extensions dependent on the postgresql version, and
> if yes, how should I create the package to enable smooth transitions?

The server major version is encoded in the .so files built and the
path names, so they are dependent, yes.

> What are the preferred names for the packages?

postgresql-9.6-q3c etc.

> I would be glad to get some initial startup here (maybe a simple
> template or so)?

See pg_buildext(1) and dh_make_pgxs(1).

The existing

https://anonscm.debian.org/cgit/debian-science/packages/q3c.git/
https://anonscm.debian.org/cgit/debian-science/packages/pgsphere.git/

repositories seem mostly fine even by today's packaging standards
(maybe some of the extra clutter in debian/rules could be removed), so
you should probably go from there.

Fwiw, I'd strongly recommend to add a debian/tests/ testsuite (see
also pg_buildext(1)), even if it's just a "create extension q3c;", so
we have some test coverage.

Thanks,
Christoph
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/attachments/20170803/bd47e30e/attachment.sig>


More information about the Pkg-postgresql-public mailing list