[postgis-devel] autoconf paths
strk at refractions.net
strk at refractions.net
Tue Apr 19 03:46:46 PDT 2005
In HEAD branch you can find another proposal on configuration.
The bad thing is you can't fully override --datadir, --bindir etc..
due to unavailability of an answer to the question: did user
specify this ? (it only works with --prefix).
Based on presence of --prefix we select pgsql-tight and custom
layout:
If you DONT specify --prefix installation layout will
be like the one used in 1.0.0 and no paths override is possible.
# ./configure
...
PREFIX: /extra/pgroot-8.0.0
EPREFIX: ${prefix}
DOC: ${prefix}/doc/postgresql/contrib
DATA: ${prefix}/share/postgresql/contrib
MAN: ${prefix}/man
BIN: ${exec_prefix}/bin
EXT: /home/extra/pgroot-8.0.0/lib/postgresql
If you DO specify --prefix installation will be fully layed out
under that dir, with 'postgis' suffix added to docdir and datadir:
# ./configure --prefix=/tmp/postgis
...
PREFIX: /tmp/postgis
EPREFIX: ${prefix}
DOC: ${prefix}/doc/postgis
DATA: ${prefix}/share/postgis
MAN: ${prefix}/man
BIN: ${exec_prefix}/bin
EXT: ${exec_prefix}/libexec
You DO can change docdir, datadir, mandir, bindir and libexecdir
(postgis extension lib dir) but you can't remove the 'postgis' prefix
from docdir and datadir:
# ./configure --prefix=/tmp/postgis \
--datadir=/tmp/postgis_data \
--with-docdir=/var/www \
--bindir=/usr/local/bin \
--libexecdir=/tmp/pgis/mods
...
PREFIX: /tmp/postgis
EPREFIX: ${prefix}
DOC: /var/www/postgis
DATA: /tmp/postgis_data/postgis
MAN: ${prefix}/man
BIN: /usr/local/bin
EXT: /tmp/pgis/mods
Comments ? Thoughts ?
--strk;
On Fri, Apr 15, 2005 at 10:10:57PM +0200, Markus Schaber wrote:
> Hi, Strk,
>
> strk at refractions.net schrieb:
> >I'm not sure we should keep relying on pgsql layout, although
> >your solution is viable. Actually I was thinking that allowing
> >storage of extension lib itself in a postgis-specific directory
> >would permit using different postgis versions for different
> >databases of the same cluster (does it make any sense?).
>
> Yes, it does make sense, it is what I do on my developer machines all
> day. :-)
>
> Sometimes, it is not possible to migrate one database to a new postgis
> version because the app is incompatible, but another app that uses a
> different database relies on the new features.
>
> So I think the most flexible may be to use the output of "pg_config
> --configure" by default, but allow both overriding individual parameters
> via --docdir, --bindir etc. or using --prefix to have everything bundled
> together in $PREFIX/bin, $PREFIX/lib etc. However, I think this may make
> the configuring process too complex.
>
> Markus
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
More information about the postgis-devel
mailing list