Re: postgres extensions and postgres multi-version support
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Christoph, hi Dimitri,
thank you very much for your help. Your both answers were exactly what
I was searching for :-)
I added the template file "control.in" to my "debian/" directory and
updated "rules". I corrected my watch file (it should work now) and now
I'm building the "q3c" package for the newest upstream version (1.4.19).
I git-pushed my changes to the remote repo at
http://anonscm.debian.org/gitweb/?p=debian-science/packages/q3c.git .
It should be mentioned that my "debian/rules" is still based on an
outdated version of "pg_buildext" from
"postgresql-server-dev-all" (129). So the next step will be to use v152
of this script which includes the "loop()" function and supports the
entry "all" in "debian/pgversions".
I'll get back to you in a couple of days after the next update of my
package.
Could you imagine to sponsor my package or would you say it should
rather be maintained by the Debian Science maintainers? From my point of
view, it's worth to have the postgres extension "q3c" packaged just for
itself but it's also true that "q3c" is a dependency of a piece of
astronomical software I seek to package in the near future.
Best regards,
Florian
Am 21.01.2014 16:05, schrieb Christoph Berg:
> Re: Florian Rothmaier 2014-01-21 <[🔎] 52DE8102.8040000@ari.uni-heidelberg.de>
>> Currently, my "debian/control" has the following structure:
>>
>> Source: q3c
>> ...
>>
>> Package: postgresql-8.4-q3c
>> ...
>>
>> Package: postgresql-9.0-q3c
>> ...
>>
>> Package: postgresql-9.1-q3c
>> ...
>>
>>
>> While looking at other postgres extensions (e.g. "ip4r", "postgis",
>> "prefix"), I noted that in all cases, the extension is built for one
>> specific postgres version only, e.g.
>>
>> "postgresql-9.1-postgis" for the "postgis" source package or
>> "postgresql-9.3-prefix" for the "prefix" source package in jessie,
>>
>> so what I'm doing does not seem to be common practice.
>>
>> Hence my question is: does it make sense to use "pg_buildext" for the
>> multi-version support of postgres, or will this do more harm than good
>> and should therefore be dropped?
>
> Hi Florian,
>
> pg_buildext makes sense indeed, but you are missing one bit here,
> debian/control is regenerated from debian/control.in at "clean" time.
> This will rewrite the control file to include the supported PostgreSQL
> versions only. Have a look at any package build-depending on
> postgresql-server-dev-all to see how it works.
>
> Let me know if you have further questions.
>
> Christoph
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJS4qy6AAoJEGXz/obPl241E7cQAIJW0Q0dVD38LdT5Yu68y9Tc
QIJPm22Ai0AwboG5kc1v/K/pn9FPVai0rQIbeA3l+0RNg4nX2TD+A+VrT61h6K1v
+cpPeeLGLau4Yotb0sV0hFS8ab5s9keggAznE6hjLA/PVpiOnh8wSn4FZpzfhgvx
MONI28GP2jKk5yAZTFsV3i2hBIf3VeHdpHrIeFRdF/vumm8T/n7GRcFWxYKAV3Jn
YSFPWXs0HYqAqYoIRa5cDzH/gh1G5/D0xBzVOOqdDR8stKKb78wfygF3h8E5VxWY
pe34PWiDAZUjK13GJHhf+N2YGBhLJw8h0mTBEw4mQi9bUP7GelosAGwxUS++MO9f
M6/EMgt1eOX9RMGB+6ZN4aGN4tij8l6YxKNa/5AIVCCwkH8U4AGEVpA2gVnegy4c
J0lZaQBJJf6zeYM8CAHsNuTCf0qD8GP8WqO8MAIEXaFLvn5a6lid8maXl09w7uoh
Yf5pM2XedkYmGnH1c5fA03TNjQxgTGs+V4D6mNAhg/n39J+0OvxN+ZMNmpxDWC/1
o0sNGDKMKXQahWTla5YHsi9CiYGEuIlZGxuOsEcYHHe7QbQ5dM8OiwufUlwaX3Qv
fTJJhVcQUx1WofouCW78PuhC5w/wic+KV0cwa/E4WneO5TeV/C4fMPhgngha4FXR
z84FPrGFmyid0Gni0Qk9
=3HGg
-----END PGP SIGNATURE-----
Reply to: