From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
---|---|
To: | Jan Dubois <jand(at)activestate(dot)com> |
Cc: | "ppm(at)listserv(dot)ActiveState(dot)com <ppm(at)listserv(dot)ActiveState(dot)com>" <ppm(at)listserv(dot)activestate(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: DBD::Pg PPM? |
Date: | 2013-02-26 23:16:25 |
Message-ID: | 1EA88662-1086-4A28-9BC3-4619F0C93628@justatheory.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Feb 26, 2013, at 3:07 PM, Jan Dubois <jand(at)activestate(dot)com> wrote:
>> Hello ActiveStaters,
>
> The commonly used term is actually Activator. :)
Got it!
> Yes, that is one reason. We then need to apply several patches to build
> things correctly though (to statically link the client libs, deal with
> missing SIGALARM on Windows, etc).
>
> We actually have all those changes, as we include DBD::Pg in all ActivePerl
> builds; they would just need to be converted into the distroprefs format
> used by the CPAN builders. It will take some time to do it, and hasn't
> been a big priority because ActivePerl already contains whatever the latest
> version of DBD::Pg was at the time of building AP. So this is really only
> about updating DBD::Pg for older releases of AP.
Oh, I didn't realize that DBD::Pg was shipped with ActivePerl. That certainly simplifies things.
> This is different from DBD::mysql, which is not included in ActivePerl due
> to GPL-only licensing. So it was more important to spend the extra time to
> get it into PPM.
Sure, that makes sense.
Thanks for the quick response!
David
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2013-02-26 23:28:02 | Re: initdb ignoring options? |
Previous Message | Jan Dubois | 2013-02-26 23:07:50 | Re: DBD::Pg PPM? |