Thread: DBD::Pg PPM?

Hello ActiveStaters,

I see that the DBD::Pg build always fails:
 http://code.activestate.com/ppm/DBD-Pg/

I'm sure this is because PostgreSQL is not installed on any of the PPM build boxes (smokers?). DBD::mysql, on the other
hand,builds fine (most of the time): 
 http://code.activestate.com/ppm/DBD-mysql/

Would it be possible to adapt whatever was done for DBD::mysql to allow DBD::Pg to be built? I assume it means that
PostgreSQLneeds to be installed, or at least its include files and libraries. 

I've Cc'd pgsql-hackers, as its denizens can provide feedback on what might be needed. There might also be something
worthpoaching from the abandoned "DBD-Pg PPM Binaries" project. 
 http://pgfoundry.org/projects/dbdpgppm/

Thanks,

David

On Feb 26, 2013, at 3:07 PM, Jan Dubois <jand@activestate.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

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.

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.

So if I had any extra time to spare (hah!), I would probably try to get DBD::mysql to build on OS X first, because currently we don't cover this at all.

Cheers,
-Jan