On Feb 19, 2008 7:44 AM, Peter Eisentraut <peter_e at gmx.net> wrote:
> Dave Page wrote:
> > > You can set --with-pgsharedir=whatever, and then it doesn't work.
> >
> > Right, but that option is there to tell the build system where the
> > PostgreSQL share directory is, not for you to specify where you want
> > the Slony share directory - that's how the description of the
> > parameter reads to me at least (plus of course it falls back to
> > whatever pg_config says iirc):
> >
> >   --with-pgsharedir=<dir>          Location of the PostgreSQL share
> > dir. E.g. postgresql.conf.sample
>
> Well, let's put this differently:  The Slony installation path selection
> procedure is insane.  I have beaten it around long enough to make it
> installable in an FHS-like way.  If that breaks because I was using the
> options in a sneaky way, I accept that, but please provide an alternative.

I have no desire to make your life difficult - I'd rather find a
solution that works for all of us than just revert the change and be
done with it.

> > Additionally, the use case you suggested for doing this would also
> > require the lib dir to be altered, so I still don't see how that will
> > work - at least without you manually editing the SQL scripts.
>
> I can easily edit the SQL scripts, but I can't easily edit the slonik binary.
>

So what are we expecting to happen?

- Obviously the libraries need to be in the PostgreSQL lib directory.

- The share directory needs to be one of:

  $PGDIR/share
  $PGDIR/postgresql/share
  $PREFIX/share
  $PREFIX/slony/share

- Everything else should go under one of

  $PGDIR/
  $PREFIX/

So how can we specify which layout the user wants? The required
changes to slonik should be relatively straightforward, but the build
system less so (for me at least). Plus of course, do we want such
changes in the stable branch?

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