From: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: Relocatable installs |
Date: | 2004-05-08 21:32:20 |
Message-ID: | 20040508182809.L189@ganymede.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, 8 May 2004, Bruce Momjian wrote:
> Win32 is going to need relocatable installs, and Unix packagers have
> asked for this too.
>
> A relocatable install is one where you can do 'gmake install', tar up
> the directory where you installed it, then untar it on to another
> machine with the same operating system, but into a different directory
> location.
>
> For example, if you use the defaults for directory locations, PostgreSQL
> will install into /usr/local/pgsql, and everything will be under that
> directory --- bin, lib, include, share. (Not sure about etc, doc, and
> man.)
>
> However, right now, if you try to move /usr/local/pgsql to /var/pgsql,
> the database will not work because there are hard-coded directory
> dependencies in the binaries:
>
> initdb has to find its *.bki files in /share
> initdb has to find the postgres binary in /bin
> pg_dumpall has to find pg_dump
> postgres has to find shared objects the /lib
> Win32 postgres has to find /share/timezone
>
> Maybe there are more.
Is there a reason why we can't use a PGSQL_PREFIX ENV variable or
something like that? If not defined, use compiled in default?
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
From | Date | Subject | |
---|---|---|---|
Next Message | elein | 2004-05-08 21:34:50 | |
Previous Message | Oleg Bartunov | 2004-05-08 21:03:07 | Re: Aggregation question |