[postgis-devel] extensions not building in 2.4.2?

Sandro Santilli strk at kbt.io
Fri Nov 24 00:29:28 PST 2017


On Thu, Nov 23, 2017 at 10:56:16AM +0100, Tom van Tilburg wrote:

> This part is the same in 2.4.1 and 2.4.2 and the only thing that I can see
> that changes the outcome is the removal of doc/postgis_comments.sql
> and doc/raster_comments.sql
> from the 2.4.2 distribution.
> 
> Now, since the SQL files were not supposed to be there in the first place
> (they have been put in .gitignore) it seems that all these years I have
> been building extensions illegally and free-riding on the distributed
> comments files (never ran into trouble with it). Is my assumption correct
> that the pre-2.4.2 configuration was wrong? And that I should fix my setup
> to build these comments files in order to get extensions back?

I'm not sure what the official policy is with reguard of the
distribution of those files. My guess is that whoever prepared 2.4.2
tarball did not have the required tools to build those comments
(docbook tools), so I guess an important action to take here would be
to come up with an official policy and make sure our "make_dist.sh"
script enforces it (like bail out if comments are not there for
inclusion, or make sure they are *not* included).

In any case it makes sense for you to fix your build scripts so to
*build* those comments on your side, if you want extension.

--strk;


More information about the postgis-devel mailing list