Re: Extensions vs PGXS' MODULE_PATHNAME handling - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Extensions vs PGXS' MODULE_PATHNAME handling
Date
Msg-id F8774405-1DE7-41B9-A7A3-EBA5880AF727@kineticode.com
Whole thread Raw
In response to Re: Extensions vs PGXS' MODULE_PATHNAME handling  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Extensions vs PGXS' MODULE_PATHNAME handling  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Feb 13, 2011, at 11:34 AM, Tom Lane wrote:

> OK, so with that, attached is an example of the complete conversion diff
> for a contrib module (hstore in particular).  Although "git status"
> reports hstore--1.0.sql as being a rename of hstore.sql.in, "git diff"
> doesn't seem to be exceedingly bright about presenting it that way :-(.
> But actually the change in that script other than renaming is just
> removing the "set search_path" command and adjusting the header comment.

I sure would like it if the install script with no version in it corresponded to the latest version. Otherwise, one
mustrename the file every time one does a release. And as you're noting, you lose Git history that way. 

Best,

David



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Add support for logging the current role
Next
From: Tom Lane
Date:
Subject: Re: Extensions vs PGXS' MODULE_PATHNAME handling