From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Relocatable installs |
Date: | 2004-05-17 23:02:39 |
Message-ID: | 200405172302.i4HN2dx08294@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jan Wieck wrote:
> > I think if we go for the plan outlined, we will not need a special
> > configure flag. (People might decide to move the install dir long after
> > they install it.) By default, everything sits under pgsql as pgsql/bin,
> > pgsql/lib, etc. I can't see how making it relative is going to bite us
> > unless folks move the binaries out of pgsql/bin. Is that common for
> > installs that don't specify a special bindir?
> >
>
> Does that include a mechanism for -rpath?
>
> Currently, if you have multiple installations of PostgreSQL on a server
> and call ones psql or whatever explicitly, it is not loading another
> ones libpq, but for sure the one belonging to its version. How does the
> plan you're talking about cover this?
Someone asked about rpath, and I didn't deal with it. How many
platforms use rpath? I am not sure.
I assume folks are going to have to modify their ld.so.conf to point to
the proper library, or for non-root, set an environment variable like
LD_LIBRARY_PATH.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-05-17 23:04:24 | Re: Table Spaces |
Previous Message | Mike Mascari | 2004-05-17 22:48:42 | Re: Call for 7.5 feature completion |