Jan Wieck <[EMAIL PROTECTED]> writes:
> You know how much trouble that causes? The existance of LD_LIBRARY_PATH in your
> environment disables setuid() for security reasons on some platforms. So one
> would have to wrap every PG related program into equally named shell scripts or
> aliases to just set it for the program call alone.
Why would any pg tools need to be setuid?
But it's just wrong to have a binary that doesn't run unless you have
environment variables set up.
> Relocatable installation means static linking of our tools against our own
> libs. This does not mean static linking entirely, but at least static linking
> against libpq.a.
The normal approach is to use rpath for relocatable installs.
That's what it's there for.
Static linking would work too but it's overkill.
But please don't use rpath for installs to standard paths like
/usr/{local,}/lib. That way lies madness.
--
greg
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
