On Feb 15, 2008 4:04 PM, Jan Wieck <JanWieck at yahoo.com> wrote:
> On 2/15/2008 4:16 AM, slony1-bugs at lists.slony.info wrote:
> > http://www.slony.info/bugzilla/show_bug.cgi?id=35
> >
> > --- Comment #7 from Peter Eisentraut <peter_e at gmx.net>  2008-02-15 01:16:34 ---
> > I suppose you should alter get_share_path(), find_my_exec(), and so on to work
> > relative to Slony's installation directories, not PostgreSQL's.  Maybe a bit of
> > refactoring would do the trick.
>
> If the slony shared component installation path is not relative to
> Postgres' idea of where $libdir is, how will a slonik running on one
> machine know the slony shared install path of another? How will "store
> node" work remotely?

Further to that, how are you actually installing in this way Peter? In
working on the patch for this I find that the makefiles are
specifically designed to install the libraries into the pg libdir and
the scripts into the pg sharedir regardless of the installation prefix
etc. The changes to slonik should work fine with that.

The only way to do do something like you describe is along the lines of:

./configure --prefix=/usr/local/slony
...
make pgsharedir=/usr/local/slony/share pgpkglibdir=/usr/local/slony/lib install

but as Jan points out, how would that be found?

-- 
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Oracle-compatible database company