Re: Extensions, patch v18 (merge against master, bitrot-only-fixes)

From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, PostgreSQL-Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Extensions, patch v18 (merge against master, bitrot-only-fixes)
Date: 2010-12-16 20:05:37
Message-ID: m2r5dho54e.fsf@2ndQuadrant.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> I thought the suggestion of having "version = 9.1devel" line in each
> contrib's module extension file was a joke. It is certainly not going
> to be sustainable in the long run -- I don't think we want to be
> modifying all control files each release. We need to find a better way
> to fix this.

Consider also the use case where we only update contrib module minor
version when they do receive an update in the tree. If we get to do
that, maybe it's good enough with plain .control files.

Of course having some Makefile or other support doesn't prevent anything
here, it just allows some more flexibility. That was considered some
more complexity not solving any real world use-case on-list, though.

FWIW, it seems very likely that should we ship without the Make support
I'll have to add it to every extension I maintain, separately.

Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-12-16 20:10:10 Re: Extensions, patch v18 (merge against master, bitrot-only-fixes)
Previous Message Dimitri Fontaine 2010-12-16 19:51:59 Re: Extensions, patch v18 (merge against master, bitrot-only-fixes)