-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 3 Apr 2008 21:45:52 +0530
"Tom Dunstan" <pgsql@tomd.cc> wrote:
> > This would install all the modules but not enable them in the
> > database itself (of course). This could also be extended to the pls
> > so that we have exactly one mechanism to control those options as
> > well.
> >
> > ./configure --enable-module=pgcrypto --enable-module=plperl
>
> That's basically where I was heading, although I took it a step
> further: why not build and install all possible modules by default, if
> we think they're up to quality?
Good point.
>
> One answer is: what do you do if some required library isn't
> available?
If we build by default, then when a library isn't found the configure
output tells you:
Looking for Perl Development packages: No , disabling plperl build.
>
> --enable-module=ALL could be pretty good, though, especially if it
> build pl/perl etc that most sysadmins will want to install but do so
> in less configure args. :)
Right. I am using the Apache model here.
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
United States PostgreSQL Association: http://www.postgresql.us/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFH9QQ2ATb/zqfZUUQRAsD9AJ9b9/12ZtaJ/CpnQ3y0xH7U3a0EYACfVeUJ
FKUyEmuuw9nx3F+sk4mL2eQ=
=sA7I
-----END PGP SIGNATURE-----
