From: | "Mickael Deloison" <mdeloison(at)gmail(dot)com> |
---|---|
To: | "Dave Page" <dpage(at)pgadmin(dot)org> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: pgScript patch based on pgScript-1.0-beta-3 |
Date: | 2008-08-14 13:26:45 |
Message-ID: | 1f8f052b0808140626l47721ae5g6f09d244d60f154c@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
2008/8/14 Dave Page <dpage(at)pgadmin(dot)org>:
> Well a lot of the argument around separating it was based on the idea
> that you would continue to work on it without being bound by the
> pgAdmin release cycle. I think that makes you one of major the
> decision makers - so what do you think we should do?
>
> FWIW, I don't have any major objection to any of the integration
> methods, though having it as a completely separate executable is
> probably my least favourite option.
>
I'm not sure to understand all the possibilities.
By DLL, what do you mean? Do you say that pgScript code would be on
pgFoundry (like it is right now) or would be on pgAdmin SVN. If on
pgAdmin SVN, would it be compiled and included in pgAdmin when you
compile pgAdmin? And with a DLL, isn't there a problem if you want to
distribute pgAdmin binary with the PostgreSQL Windows distribution?
Because the DLL should be distributed as well...
Mickael
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2008-08-14 13:38:24 | Re: pgScript patch based on pgScript-1.0-beta-3 |
Previous Message | Dave Page | 2008-08-14 07:24:31 | Re: pgScript patch based on pgScript-1.0-beta-3 |