As for the install targets, I do not think it is a good idea to install 
the loadable modules, xxid.so and slony1_funcs.so, anywhere else than in 
the postgresql lib directory. The reason for this is that the slonik 
utility, which initializes the database and defines all the C functions 
contained in those modules, often runs remotely and might even run on a 
different platform (slonik running on your linux workstation can 
initialize databases on your BSD, Sun and AIX servers). Installing those 
shared objects anywhere else than what the postgres backend considers 
$libdir (used in pg_proc.prosrc) is going to be a major confusion.

That being so, I didn't bother to make any finer distinction for all the 
other slony components and they simply get installed into the respective 
postgres build targets.


Jan

On 6/11/2004 4:03 AM, Julian Scarfe wrote:

> Being a cautious sort of guy, I like to build into RPMs before installation,
> even (especially?) for betas.
> 
> What's the intended mode of use of 'make dist' and 'make rpm' please (and
> for that matter, the buildroot for install since configure with --prefix
> doesn't seem to have the desired effect)?
> 
> I did manage to kludge together my own RPM spec specifying the install
> directories explicitly using configure, but there's an issue with
> src/slonik/Makefile in that
> 
> -DPGSHARE="\"$(datadir)\""
> 
> seems to hardwire slonik to the buildroot in a non-relocatable way.
> 
> What's the medium- and long-term plan for RPMs and other binaries?
> 
> Thanks for any guidance.
> 
> Julian Scarfe
> 
> 
> 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general


-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #