1.7 & 1.6.1-2 cannot co-exist?

[Bill Gribble]

On Tue, Jul 17, 2001 at 10:37:33AM +1000, Jonathan David Wheelhouse wrote:
> Anyhow, off on a tangent - teach me: how should I keep the development
> version from interfering with the stable version given I want to have
> both on the same box?

It's not too hard.  You just need to give each version its own
playground to install in.

On my development system, I have 3 concurrent gnucash installs from 3
gnucash source trees (1.6, 1.7, and some larger-scale changes I'm
making to a 1.7 snapshot from a couple weeks back).  I use the
--prefix argument to the gnucash autogen.sh script to set a different
$prefix for each one:

  (in gnucash-1.6 directory)
  $ ./autogen.sh --prefix=/usr/local/gnucash-1.6
  
  (in gnucash-1.7 dir)
  $ ./autogen.sh --prefix=/usr/local/gnucash-1.7

etc.

The only runtime change to select between them is to change my $PATH
to find the right bin directory:

 $ export PATH=${PATH}:/usr/local/gnucash-1.7/bin

You don't need to set LD_LIBRARY_PATH..  the executable is built with
-rpath arguments so it knows where to find the libs it was linked
with. You may need to set LD_LIBRARY_PATH to include g-wrap's lib
directory (if it's not intalled in a standard place) so it can
configure itself correctly but not to run gnucash.

Good luck!
Bill Gribble