@JerrySievert

I wanted to check with you about the possibility of adding support for static builds of PL/v8 to future releases. At @xtuple, we were discussing how nice the EnterpriseDB PostgreSQL installers are. They're an easy way for end users to get a PostgreSQL server up and running. The installer also includes a lot of the basic extensions someone might need. We reached out to @dpage at @EnterpriseDB about why they don't include PL/v8 in their installer. He mentioned that the build process for PL/v8 had been difficult in the past.

I think one way to get over the hurdle of the build process is to include static build of PL/v8 with each release. This is similar to how Node.js ships with a static libv8 build. By including a static build with each release, we could remove the need for libv8 to be present on the machine. You are aware of the old libv8 version on the debain OSs and how that has forced you to maintain the 1.4.x branch of PL/v8.

We're already maintaining a set of static PL/v8 builds at xTuple. You can find them here:

• http://updates.xtuple.com/updates/plv8/linux32/xtuple_plv8.tgz
• http://updates.xtuple.com/updates/plv8/linux64/xtuple_plv8.tgz
• http://updates.xtuple.com/updates/plv8/mac/xtuple_plv8.tgz
• http://updates.xtuple.com/updates/plv8/win/xtuple_plv8.zip

They currently are built with PL/v8 version 1.4.4, but just last week we started the process of moving them to 2.0.3. The builds are created by a script that does a PL/v8 static build for PGVERSIONS="9.1.2 9.2.10 9.3.2 9.4.4 9.5.0". We'll be adding 9.6.x soon.

Instead of maintaining these scripts at xTuple, I'd like to work with you on contributing them to the PL/v8 repo and start to use them to publish static builds with each release. I believe the package repository maintainers could then pick them up as official releases and remove the need for a dynamic libv8 build.

Thoughts?