Re: gEDA-user: Notes from last night's Free Dog meeting (11.3.2005)

[sdb@xxxxxxxxxx (Stuart Brorson)]

> Stuart Brorson wrote:
> > Always install gEDA into its own
> > directory!  Then, when upgrade time comes, just blow away the
> > directory and start afresh.  Also, make sure that the env variables
> > are set correctly!
> >=20
> > Note that this is good advice for any application suite on unix, not
> > just gEDA.
> 
> That's what /usr/local and /opt were thought for so I think that's a=20
> good idea. Of course one should still allow for easy packaging because=20
> packages from distro vendor are better for 90% of the tasks than any=20
> compiling from source or binary tarballs.

I always install into /usr/local/geda (i.e. I set
--prefix=/usr/local/geda at configure time).  Then, the executables
live in /usr/local/geda/bin, the libraries live in
/usr/local/geda/lib, and so on.  That way the gEDA stuff is available
to all users system wide.  

You can also set --prefix=${HOME}/geda if you are the only one using
gEDA on a particular machine.  That's what the gEDA/gaf tarballs do by
default (not the CD installer).

Don't forget to set your $PATH and other env variables aftewards.

Also, don't just set the --prefix to /usr/local, because then things
will end up in directories with lots of other files, and you won't be
able to easily delete them! 

Stuart