Local installs - Revision history

imported>Huston: Took out examples, provided link to dotfiles article instead.

2010-02-02T19:11:41Z

Took out examples, provided link to dotfiles article instead.

@@ Line 12: / Line 12: @@
 # When done compiling and installing, you will probably have directories like ~/Installs/FooGram/bin, ~/Installs/FooGram/lib and ~/Installs/FooGram/share, perhaps more.
 # Tell your shell where to look, so you can run the program just like any other.
-#: For bash, I have the following in my ~/.bashrc:
+#: Have a look at the [[Dotfiles|dotfiles]] article for information on setting this up and links to examples.
 Later on, if you decide to remove the program, you need only delete the entire ~/Installs/FooGram directory and it's gone - no more hunting in multiple shared/bin/sbin/lib/man directories to find all the files that go with some bit of software.  Or you can move the directory out of the way, install a newer version, and then remove the old one when you're sure it's working as expected.

imported>Huston: LD_LIBRARY_PATH considered harmful

2009-10-21T20:51:51Z

LD_LIBRARY_PATH considered harmful

← Older revision		Revision as of 20:51, 21 October 2009
Line 28:		Line 28:
	[[ "$MANPATH" =~ "(^\|:)$D/man($\|:)" ]] \|\| \		[[ "$MANPATH" =~ "(^\|:)$D/man($\|:)" ]] \|\| \
	export MANPATH=$D/man:${MANPATH:+$MANPATH}		export MANPATH=$D/man:${MANPATH:+$MANPATH}
	fi

	~~if [ -d $D/lib ]; then~~
	~~[[ "$LD_LIBRARY_PATH" =~ "(^\|:)$D/lib($\|:)" ]] \|\| \~~
	~~export LD_LIBRARY_PATH=$D/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}~~
	fi		fi
	done</nowiki>		done</nowiki>

imported>Huston: Updated for loop for path modifications

2009-04-17T01:52:04Z

Updated for loop for path modifications

← Older revision		Revision as of 01:52, 17 April 2009
Line 14:		Line 14:
	#: For bash, I have the following in my ~/.bashrc:		#: For bash, I have the following in my ~/.bashrc:

	<nowiki>for D in ~/Installs/* ; do		<nowiki>for D in $HOME/Installs/* ; do
	if [ -d $D/bin ]; then		if [ -d $D/bin ]; then
	[[ "$PATH" =~ "$D/bin" ]] \|\| export PATH=$D/bin${PATH:+:$PATH} ; fi		[[ "$PATH" =~ "(^\|:)$D/bin($\|:)" ]] \|\| \
	if [ -d $D/share/man ]; then		export PATH=$D/bin${PATH:+:$PATH}
	[[ "$MANPATH" =~ "$D/share/man" ]] \|\| export MANPATH=$D/share/man:${MANPATH:+$MANPATH} ; fi		fi

			if [ -d $D/share/man ]; then
			[[ "$MANPATH" =~ "(^\|:)$D/share/man($\|:)" ]] \|\| \
			export MANPATH=$D/share/man:${MANPATH:+$MANPATH}
			fi

	if [ -d $D/man ]; then		if [ -d $D/man ]; then
	[[ "$MANPATH" =~ "$D/man" ]] \|\| export MANPATH=$D/man:${MANPATH:+$MANPATH} ; fi		[[ "$MANPATH" =~ "(^\|:)$D/man($\|:)" ]] \|\| \
			export MANPATH=$D/man:${MANPATH:+$MANPATH}
			fi

	if [ -d $D/lib ]; then		if [ -d $D/lib ]; then
	[[ "$LD_LIBRARY_PATH" =~ "$D/lib" ]] \|\| export LD_LIBRARY_PATH=$D/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH} ; fi		[[ "$LD_LIBRARY_PATH" =~ "(^\|:)$D/lib($\|:)" ]] \|\| \
			export LD_LIBRARY_PATH=$D/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}
			fi
	done</nowiki>		done</nowiki>

imported>Huston: Added $D/share/man since some things put manpages there

2007-06-20T16:41:09Z

Added $D/share/man since some things put manpages there

← Older revision		Revision as of 16:41, 20 June 2007
Line 17:		Line 17:
	if [ -d $D/bin ]; then		if [ -d $D/bin ]; then
	[[ "$PATH" =~ "$D/bin" ]] \|\| export PATH=$D/bin${PATH:+:$PATH} ; fi		[[ "$PATH" =~ "$D/bin" ]] \|\| export PATH=$D/bin${PATH:+:$PATH} ; fi
			if [ -d $D/share/man ]; then
			[[ "$MANPATH" =~ "$D/share/man" ]] \|\| export MANPATH=$D/share/man:${MANPATH:+$MANPATH} ; fi
	if [ -d $D/man ]; then		if [ -d $D/man ]; then
	[[ "$MANPATH" =~ "$D/man" ]] \|\| export MANPATH=$D/man${MANPATH:+:$MANPATH} ; fi		[[ "$MANPATH" =~ "$D/man" ]] \|\| export MANPATH=$D/man:${MANPATH:+$MANPATH} ; fi
	if [ -d $D/lib ]; then		if [ -d $D/lib ]; then
	[[ "$LD_LIBRARY_PATH" =~ "$D/lib" ]] \|\| export LD_LIBRARY_PATH=$D/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH} ; fi		[[ "$LD_LIBRARY_PATH" =~ "$D/lib" ]] \|\| export LD_LIBRARY_PATH=$D/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH} ; fi

imported>Huston: Updated for loop

2007-05-24T17:31:04Z

Updated for loop

← Older revision		Revision as of 17:31, 24 May 2007
Line 13:		Line 13:
	# Tell your shell where to look, so you can run the program just like any other.		# Tell your shell where to look, so you can run the program just like any other.
	#: For bash, I have the following in my ~/.bashrc:		#: For bash, I have the following in my ~/.bashrc:
	~~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~~
	~~done~~

	Now for each of the directories in which I have software installed, the proper PATH value is ~~appended~~ to my normal $PATH. So I can just run "foogram" from a prompt, instead of running "~/Installs/FooGram/bin/foogram". Also, since $MANPATH is updated, I can type 'man foogram' and have it work. Note that after a new install, you will have to logout and login again for the change to be noticed - but that's a pretty small price to pay.		<nowiki>for D in ~/Installs/* ; do
			if [ -d $D/bin ]; then
			[[ "$PATH" =~ "$D/bin" ]] \|\| export PATH=$D/bin${PATH:+:$PATH} ; fi
			if [ -d $D/man ]; then
			[[ "$MANPATH" =~ "$D/man" ]] \|\| export MANPATH=$D/man${MANPATH:+:$MANPATH} ; fi
			if [ -d $D/lib ]; then
			[[ "$LD_LIBRARY_PATH" =~ "$D/lib" ]] \|\| export LD_LIBRARY_PATH=$D/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH} ; fi
			done</nowiki>

			Now for each of the directories in which I have software installed, the proper PATH value is prepended to my normal $PATH. So I can just run "foogram" from a prompt, instead of running "~/Installs/FooGram/bin/foogram". Also, since $MANPATH is updated, I can type 'man foogram' and have it work. Note that after a new install, you will have to logout and login again for the change to be noticed - but that's a pretty small price to pay.

	Later on, if you decide to remove the program, you need only delete the entire ~/Installs/FooGram directory and it's gone - no more hunting in multiple shared/bin/sbin/lib/man directories to find all the files that go with some bit of software. Or you can move the directory out of the way, install a newer version, and then remove the old one when you're sure it's working as expected.		Later on, if you decide to remove the program, you need only delete the entire ~/Installs/FooGram directory and it's gone - no more hunting in multiple shared/bin/sbin/lib/man directories to find all the files that go with some bit of software. Or you can move the directory out of the way, install a newer version, and then remove the old one when you're sure it's working as expected.

imported>Huston at 20:32, 21 May 2007

2007-05-21T20:32:23Z

← Older revision		Revision as of 20:32, 21 May 2007
Line 23:		Line 23:

	'''''NOTE:'''''		'''''NOTE:'''''
	: You should not install a program to your network home directory. /u is backed up regularly, and storing a program there is wasteful (and expensive). Instead, install programs to scratch disks, which are still accessible by most of the machines in the building. The above example is written if you're looking to install things on a laptop or home machine, but it's not difficult to adapt the instructions to a scratch disk install.		: You should not install a program to your network home directory. /u is backed up regularly, and storing a program there is wasteful (and expensive). Instead, install programs to scratch disks, which are still accessible by most of the machines in the building. The above example is written if you're looking to install things on a laptop or home machine, but it's not difficult to adapt the instructions to a [[Scratch disks\|scratch disk]] install.

	[[Category:Software]]		[[Category:Software]]

imported>Huston: I should note against installing stuff in /u...

2007-05-15T19:19:13Z

I should note against installing stuff in /u...

← Older revision		Revision as of 19:19, 15 May 2007
Line 21:		Line 21:

	Later on, if you decide to remove the program, you need only delete the entire ~/Installs/FooGram directory and it's gone - no more hunting in multiple shared/bin/sbin/lib/man directories to find all the files that go with some bit of software. Or you can move the directory out of the way, install a newer version, and then remove the old one when you're sure it's working as expected.		Later on, if you decide to remove the program, you need only delete the entire ~/Installs/FooGram directory and it's gone - no more hunting in multiple shared/bin/sbin/lib/man directories to find all the files that go with some bit of software. Or you can move the directory out of the way, install a newer version, and then remove the old one when you're sure it's working as expected.

			'''''NOTE:'''''
			: You should not install a program to your network home directory. /u is backed up regularly, and storing a program there is wasteful (and expensive). Instead, install programs to scratch disks, which are still accessible by most of the machines in the building. The above example is written if you're looking to install things on a laptop or home machine, but it's not difficult to adapt the instructions to a scratch disk install.

	[[Category:Software]]		[[Category:Software]]

imported>Huston at 19:12, 15 May 2007

2007-05-15T19:12:48Z

@@ Line 1: / Line 1: @@
-{{oldfaq|NUM=170}}
+Even with the amount of software available on the network, sometimes you can't live without a certain program.  Or maybe you want to install it on your laptop, but don't want to have to bother with putting it in a "normal" system location (and having to be root or an administrator to deal with it).  Here's a trick which I've started doing on my Mac, and you can do on any other machine to make it simple to install software without needing administrative privileges (and it's easy to clean up if you reinstall/remove the software later on, too!)
   for D in ~/Installs/* ; do
-        if [ -d $D/bin ]; then export PATH=$PATH:$D/bin ; fi
+    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/man ]; then export MANPATH=$MANPATH:$D/man ; fi
   done
-Now, for each of the directories in which I have software installed, the proper PATH value is appended to my normal $PATH. So I can just run "foogram" from a prompt, instead of running "~/Installs/FooGram/bin/foogram". Also, since $MANPATH is updated, I can type 'man foogram' and have it work. Note that after a new install, you will have to logout and login again for the change to be noticed - but that's a pretty small price to pay.
+Now for each of the directories in which I have software installed, the proper PATH value is appended to my normal $PATH.  So I can just run "foogram" from a prompt, instead of running "~/Installs/FooGram/bin/foogram".  Also, since $MANPATH is updated, I can type 'man foogram' and have it work.  Note that after a new install, you will have to logout and login again for the change to be noticed - but that's a pretty small price to pay.
-Later on, if you decide to remove the program, you need only delete the entire ~/Installs/FooGram directory and it's gone - no more hunting in multiple shared/bin/sbin/lib/man directories to find all the files that go with some bit of software. Or you can move the directory out of the way, install a newer version, and then remove the old one when you're sure it's working as expected.
+[[Category:Software]]

imported>Huston: Local or "Home Directory" installs moved to Local installs

2007-05-15T19:02:31Z

Local or "Home Directory" installs moved to Local installs

← Older revision	Revision as of 19:02, 15 May 2007
(No difference)

imported>Huston: New page: {{oldfaq|NUM=170}} Here's a trick which I've started doing on my Mac, and you can do on any other machine to make it simple to install software without needing administrative privileges (...

2007-05-02T17:48:44Z

New page: {{oldfaq|NUM=170}} Here's a trick which I've started doing on my Mac, and you can do on any other machine to make it simple to install software without needing administrative privileges (...

New page

{{oldfaq|NUM=170}}

Here's a trick which I've started doing on my Mac, and you can do on any other machine to make it simple to install software without needing administrative privileges (and it's easy to clean up if you reinstall/remove the software later on, too!)

First, create a directory where your software installs will live. I call mine "Installs", so

mkdir ~/Installs

is the command to run. Now, let's say the program you want to install is called FooGram. I create a directory called ~/Installs/FooGram, and download the source to that directory. Uncompress it like usual, which will normally create a directory called ~/Installs/FooGram/FooGram-1.2.3 for example. This directory contains the source. Go to compile as you normally would, however if the program uses 'configure' as the first step, use the following:

./configure --prefix=~/Installs/FooGram

This tells configure that you want to install the software not in the normal /usr/bin or /usr/local/bin location, but in a directory tree based from ~/Installs/FooGram. When done compiling and installing, you will probably have directories like this:

~/Installs/FooGram/bin
~/Installs/FooGram/lib
~/Installs/FooGram/share

..and perhaps others. Now, to tell your shell how to handle these things, so that you can run the program just like any other. For bash, I have the following in my ~/.bashrc:

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
done

Now, for each of the directories in which I have software installed, the proper PATH value is appended to my normal $PATH. So I can just run "foogram" from a prompt, instead of running "~/Installs/FooGram/bin/foogram". Also, since $MANPATH is updated, I can type 'man foogram' and have it work. Note that after a new install, you will have to logout and login again for the change to be noticed - but that's a pretty small price to pay.

Later on, if you decide to remove the program, you need only delete the entire ~/Installs/FooGram directory and it's gone - no more hunting in multiple shared/bin/sbin/lib/man directories to find all the files that go with some bit of software. Or you can move the directory out of the way, install a newer version, and then remove the old one when you're sure it's working as expected.