[Fwd: Re: [Xastir] Question]

[Steve Huston]

Thought I sent this to the list too.. guess I didn't.  Since there's
been a lot of Linux talk lately, I thought I'd share one way I tend to
install programs as a user, makes things a little cleaner (and less use
of root needed)

-------- Original Message --------
Subject: Re: [Xastir] Question
Date: Wed, 22 Nov 2006 15:28:58 -0500
From: Steve Huston <huston at srhuston.net>
To: AC7YY <ac7yy at aikenco.net>
References: <00a201c70e6f$193ceb50$6401a8c0 at homexpmain>

On 11/22/2006 02:47 PM, AC7YY wrote:
> I am attempting a new install using SuSe 10.1. I have done this as a user in
> /home/kim/xastir
> cvs update
> ./bootstrap.sh
> ./configure
> make
> The summary shows ImageMagick = YES, prce - YES, all else is = NO
> No for the really stupid question....
> How do I start xastir? I have tried xastir and ./xastir I get a 'no such
> file or directory' error.

You still have to do a 'make install' since Xastir will expect certain
files in certain places.  If you want to do this completely as a user
(by default, it will install into (I believe) /usr/local), here's a
trick that I've done for a few years.

* Create a directory called Installs in your home directory (in your
case, /home/kim/Installs)
* Edit your shell startup files to include things from there.  If you
use bash, add this to your ~/.bashrc file:
for D in ~/Installs/* ; do
        if [ -d $D/bin ]; then export PATH=$PATH:$D/bin ; fi
        if [ -d $D/man ]; then export MANPATH=$MANPATH:$D/man ; fi
        if [ -d $D/lib ]; then export
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$D/lib ; fi
done
(that LD_LIBRARY_PATH line should be on the same line as the "export"
above it).  If you use csh/tcsh, then you'll have to change the syntax
of those lines slightly.
* When you run a ./configure, tell it to install things to your Installs
directory, such as './configure --prefix=/home/kim/Installs/xastir'
* make && make install

The program will now be fully installed in /home/kim/Installs/xastir,
including any share directories, includes, libraries, etc.  The next
time you start a shell, your PATH will pick up the new binaries.  The
added benefit of this is that when you back up your home directory,
you'll automatically be backing up all the little programs you've
installed as a user, without having to either backup /usr/local, or wade
through what you've changed in /usr/[bin,lib,include,etc].  For
upgrading a program, you can just move the ~/Installs/xastir tree out of
the way, and compile again (or make a backup copy of it).

Though the lines to add to your shell startup will make your path a bit
long if you do a few subshells.. one day I'll get ambitious enough to
rewrite that to see if the path exists in $PATH first...

-- 
Steve Huston - W2SRH - Unix Sysadmin, Dept. of Astrophysical Sciences
  Princeton University  |    ICBM Address: 40.346525   -74.651285
    126 Peyton Hall     |"On my ship, the Rocinante, wheeling through
  Princeton, NJ   08544 | the galaxies; headed for the heart of Cygnus,
    (609) 258-7375      | headlong into mystery."  -Rush, 'Cygnus X-1'


-- 
Steve Huston - W2SRH - Unix Sysadmin, Dept. of Astrophysical Sciences
  Princeton University  |    ICBM Address: 40.346525   -74.651285
    126 Peyton Hall     |"On my ship, the Rocinante, wheeling through
  Princeton, NJ   08544 | the galaxies; headed for the heart of Cygnus,
    (609) 258-7375      | headlong into mystery."  -Rush, 'Cygnus X-1'