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 -- cb@df7cb.de | http://www.df7cb.de/
Attachment:
signature.asc
Description: Digital signature