| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Extensions User Design |
| Date: | 2009-06-25 08:24:40 |
| Message-ID: | 937d27e10906250124r99c2036rf4fe602998c2689@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 24, 2009 at 9:43 PM, Josh Berkus<josh(at)agliodbs(dot)com> wrote:
>> == OS Filesystem Interaction
>>
>> PostgreSQL already provides standard paths where to install extensions by
>> means of PGXS, and distribution packagers have been able to adapt those.
>> We
>> should just stick with this, meaning the problem is solved.
>
> I think that the user should be able to put the extension file download
> anywhere in their filesystem, and on install PostgreSQL should copy the
> files to the appropriate place. That is, they shouldn't have to first copy
> the files to /pg_source_dir/contrib/. Maybe you had that covered, but I
> didn't see it explicitly.
>
> Also, this means that we'll want to make sure that PGXS is included in all
> existing packages of PostgresQL. Is it?
Apologies if I missed further discussion on this - I'm somewhat
distracted with release preparations at the moment...
PGXS is essentially useless on Windows unless you're compiling your
own code using Mingw/msys, which will be a miniscule percentage of
users. Our installers for 8.3 and above are all built using VC++.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2009-06-25 08:58:16 | Re: Extensions User Design |
| Previous Message | Dimitri Fontaine | 2009-06-25 07:58:25 | Re: Extensions User Design |