Re: Extensions, patch v16 - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Extensions, patch v16
Date
Msg-id 8F791603-F3F8-42DF-B6DF-66B339A81B43@kineticode.com
Whole thread Raw
In response to Re: Extensions, patch v16  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Responses Re: Extensions, patch v16
List pgsql-hackers
On Dec 10, 2010, at 11:28 AM, Dimitri Fontaine wrote:

> Well the Makefile support is just a facility to fill in the control file
> automatically for you, on the grounds that you're probably already
> maintaining your version number in the Makefile. Or that it's easy to
> get it there, as in:
>
> EXTVERSION = $(shell dpkg-parsechangelog | awk -F '[:-]' '/^Version:/ { print substr($$2, 2) }')
>
> That comes from a real world example that's yet to be adapted to being
> an extension in 9.1, but still:
>
>  https://github.com/dimitri/pgfincore/blob/debian/Makefile

I use that in pgTAP, too (line 23):
  https://github.com/theory/pgtap/blob/master/Makefile

But I don't need core to support that. Frankly, if we're not going to generate the control file from Makefile
variables,then I'd rather not have any control file Makefile variables at all. 

> Upgrade are left for a future patch, did we decide. Still, it seems to
> me that we will support some upgrade scripts so that author can decide
> what to do knowing current and next version, and yes, knowing that the
> module has already been taken care of by the OS-level packaging.

Yeah, this will be needed ASAP.

Best,

David



pgsql-hackers by date:

Previous
From: "BRUSSER Michael"
Date:
Subject: Re: initdb failure with Postgres 8.4.4
Next
From: Tom Lane
Date:
Subject: Re: Extensions, patch v16