Tue, 23 Mar 2004 19:04:34 -0500
Content-Type: text/plain; charset=us-ascii
* Christopher Browne (email@example.com) wrote:
> 1. /usr/lib/postgresql/lib/plr.so references libR.so
> cbbrowne@dev6:~$ ldd /usr/lib/postgresql/lib/plr.so
> libR.so =3D> /usr/lib/R/bin/libR.so (0x40020000)
> But ldconfig didn't know about this until I added "/usr/lib/R/bin" to
> /etc/ld.so.conf and ran "ldconfig -v". Is there a "standard" way for
> dpkg to cope with that?
That's an interesting problem... We don't want packages making changes
to ld.so.conf unless it's through some kind of defined interface and I'm
not aware of any at the moment. It'd be nicer if the R folks had just
used the standard library paths. :/
> 2. The /etc/init.d/postgresql script needs to have "export
> R_HOME=3D/usr/lib/R" added to it. =20
> Is there a decent 'standard' way of adding that in when pl/r is added
> in? It's only needed if postgresql-plr is installed...
The only way I can think of would be to have a directory of environment
variables under /etc/postgresql which will then be included by
/etc/init.d/postgresql. Kind of ugly, but we can't have packages
modifying the /etc/init.d/postgresql script, that way leads to disaster.
On the issue of changes to the 'main' postgresql package- I've got
something of a bigger one to request that can't really be done any other
way I don't think. To support some of the things that PostGIS can do
the PostgreSQL server needs to be linked against libstdc++, from what I
understand. Can this be done?
Many thanks for the changes to the package that I think I helped
instigate- I can now build a postgresql-postgis package by
Build-Depending on postgresql-dev. I expect to be doing an upload of
that package soon too.
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
-----END PGP SIGNATURE-----