Autogenerate the extension unpackaged script

[robe]

Right now before release, we generate the unpackaged scripts used to

CREATE EXTENSION postgis FROM unpackaged;

by installing postgis with CREATE EXTENSION and then running a query to see what is in the package. strk is working on script to generate the unpackaged script by sourcing the .sql files we generate. This will simplify our packaging logic and also ensure the unpackaged is always in synch at all times.

For testing the quality of it I propose as part of installcheck (postcheck) #2358

1. Count number of objects before PostGIS install

2. Install PostGIS using non-extension scripts

3. Run the generated CREATE EXTENSION postgis FROM unpackaged;

4. Run DROP EXTENSION postgis;

5. The number of objects in data install should be the same as 1

[strk]

The script creating the "from unpackaged" thing is in progress, and promising. And exposing few bugs here and there. A couple already fixed and pushed (duplicated signatures in postgis.sql), another in raster which I'll open a ticket for.

[strk]

Filed ticket #2532 for the raster commutators

[strk]

And #2533 is for the duplicated signatures

[strk]

See how you like r12104 — it only does "postgis" extension but it could easily also do topology and geocoder and what not.

[strk]

r12105 implements it for "postgis_topology". "postgis_tiger_geocoder" is still left out from the fun.

[strk]

I'll consider this done. The tiger geocoder I don't usually build so no idea if it can be automated in the same way. If you think so (and that it should) please file a new ticket.