Re: Ben Caradoc-Davies 2013-09-17 <20130917035657.9266.82928.report...@torroth-kf.arrc.csiro.au> > => create extension pgtap; > ERROR: could not open extension control file > "/usr/share/postgresql/9.3/extension/pgtap.control": No such file or directory > > I also note that pgtap 0.90.0-1 declares no dependencies on postgresql. > Perhaps > a naming convention like that used by postgis (e.g. > postgresql-9.3-postgis-2.1) > would help ease upgrades and allow explicit dependencies to be included?
That's what the other extension packages do, though these also contain compiled .so files. For SQL-only extension, a single package might also be enough, possibly with a "Provides: postgresql-9.3-pgtap". (postgis has an extra -2.1 which is due to its complexity, that shouldn't be necessary for simple packages.) Generally, it would be nice if the package would grow full pg_buildext support, that is, it should produce binaries (or content) for all PostgreSQL server versions that "pg_buildext supported-versions" outputs. That's only one version on sid, but for apt.postgresql.org we support everything from 8.4 up. > I also also note that pgtap is affected by this postgresql-9.3 extension > change, and installation from source requires manual intervention: > http://postgresql.1045698.n5.nabble.com/PostgreSQL-9-3-beta-breaks-some- > extensions-quot-make-install-quot-td5755344.html > > I ended up having to manually "/usr/bin/install -c -m 644" several files that > were missed by "make install" from pgtap-0.93.0/sql to the > /usr/share/postgresql/9.3/extension . Might need to patch the makefile. I've opened a separate bug #729559 for this. Christoph -- c...@df7cb.de | http://www.df7cb.de/
signature.asc
Description: Digital signature
