My initial reaction is ACK! The install is messy enough
for new users.  Most users will have only one slony installation.

But of course your reasons for multiple installations are
very good ones and so just go with caution.  Make sure calling
paths and PATH are correct if necessary.  Don't go deeper than
you have to.  Follow the pg model where possible.  (All of that
usual stuff.) Just be sure it is easier for the single slony
install user than for the sophisticated multi-version user.

--elein

On Mon, Sep 25, 2006 at 11:30:45AM -0700, Darcy Buskermolen wrote:
> A few things about our installed files.
> 
> A) The more I've been thinking about this, the more I'm inclined to think we 
> should move the default install location for the *.sql functions.  I think it 
> might be worthwhile to mvoe them all into share/slony-I/
> 
> B) I've run into a situation where I want to run 2 diffrent versions of slony 
> (on 2 diffrent DB's) on the same cluster. While yes I can do it via 
> manipulation of the configure options, this  feels cumbersome.  What are 
> proples thoughts on expanding on the first item and, moving the files one 
> level deeper, share/slony-I/1.3 , and going along with this, would it be 
> worth while to do something simular the same thing with the .so's ?
> 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general
>