Opened 11 years ago

Last modified 9 years ago

#2531 closed enhancement

Autogenerate the extension unpackaged script — at Version 1

Reported by: robe Owned by: strk
Priority: medium Milestone: PostGIS 2.2.0
Component: build Version: master
Keywords: Cc:

Description (last modified by 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
  1. Install PostGIS using non-extension scripts
  1. Run the generated CREATE EXTENSION postgis FROM unpackaged;
  1. Run DROP EXTENSION postgis;
  1. The number of objects in data install should be the same as 1

Change History (1)

comment:1 by robe, 11 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.