From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
---|---|
To: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Extensions User Design |
Date: | 2009-06-24 21:29:58 |
Message-ID: | 71F1218D-67A0-4FE9-97FF-BE30D10BB34F@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jun 24, 2009, at 2:12 PM, Dimitri Fontaine wrote:
>> The core team isn't appropriate for this. We'd start a new
>> committee/list somewhere instead, and it would be part of the same
>> effort which produces a "recommended" list of extensions and
>> drivers for packagers.
>
> It'd still deprecate contrib/, which could maybe become examples/?
No, it would not be distributed with core at all. They could all be
packaged up together in a single distribution of recommended modules,
however.
>> This may not be necessary if simple download-unzip-and-install is
>> simple enough.
>
> I hope it'll get simple enough, yes, as simple as current PGXS
> modules from source are:
> - cvs up or wget
> - tar xzf ... && cd ...
> - make install
> - psql -f ... mydb
Then it could also be easily scripted, too.
> PGXS has it covered, and we're not yet there, but I'm thinking PGXS
> should be a pre requisite of the extension facility as far as
> extensions authors are concerned. Then packagers will make it so
> that users won't typically face those details.
+1.
Best,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2009-06-24 21:41:03 | Re: Extensions User Design |
Previous Message | David E. Wheeler | 2009-06-24 21:27:25 | Re: Extensions User Design |