Upgrading Software - Revision history

Admin: /* Sharing Information Among Versions */

2017-10-10T01:08:30Z

Sharing Information Among Versions

← Older revision		Revision as of 01:08, 10 October 2017
Line 29:		Line 29:
	If you want to share information across all versions of a program, there are some subtleties you will have to think about before you install your program. For example, you may want all versions of Apache to use a common configuration file, or a common web directory. Normally, each version creates its own web directory and configuration files. However, when configuring your program, you can set configure options to hard-code the location of the configure files. For example, for Apache:		If you want to share information across all versions of a program, there are some subtleties you will have to think about before you install your program. For example, you may want all versions of Apache to use a common configuration file, or a common web directory. Normally, each version creates its own web directory and configuration files. However, when configuring your program, you can set configure options to hard-code the location of the configure files. For example, for Apache:

	<~~syntaxhighlight lang="bash"~~>		<pre>
	# Example Apache configure line		# Example Apache configure line

Line 35:		Line 35:
	--prefix=$HOME/pkg/apache/2.2.17 \		--prefix=$HOME/pkg/apache/2.2.17 \
	--sysconfdir=$HOME/pkg/apache/conf		--sysconfdir=$HOME/pkg/apache/conf
	</~~syntaxhighlight~~>		</pre>

	Other programs, such as PHP, also have the same configure option:		Other programs, such as PHP, also have the same configure option:

	<~~syntaxhighlight lang="bash"~~>		<pre>
	# Example PHP configure line		# Example PHP configure line

Line 45:		Line 45:
	--prefix=$HOME/pkg/php/5.3.5 \		--prefix=$HOME/pkg/php/5.3.5 \
	--sysconfdir=$HOME/pkg/php/conf		--sysconfdir=$HOME/pkg/php/conf
	</~~syntaxhighlight~~>		</pre>

	To find the appropriate option, you can run <code>./configure --help</code>, which will print all configure options.		To find the appropriate option, you can run <code>./configure --help</code>, which will print all configure options.



	= Upgrading =		= Upgrading =

Admin: /* Directory Structure */

2017-10-10T01:08:14Z

Directory Structure

← Older revision		Revision as of 01:08, 10 October 2017
Line 15:		Line 15:
	* Inside the common program directory, have each version installed to its own directory; e.g.:		* Inside the common program directory, have each version installed to its own directory; e.g.:

	<~~syntaxhighlight lang="bash"~~>		<pre>
	$ ls ~/pkg/apache		$ ls ~/pkg/apache

Line 21:		Line 21:
	2.2 2.3 2.4 2.5 2.6 std		2.2 2.3 2.4 2.5 2.6 std

	</~~syntaxhighlight~~>		</pre>

	* Finally, make a symbolic link to the "default" version (I call this <code>std</code>, for the "standard version")		* Finally, make a symbolic link to the "default" version (I call this <code>std</code>, for the "standard version")

Admin at 16:46, 28 May 2011

2011-05-28T16:46:07Z

← Older revision		Revision as of 16:46, 28 May 2011
Line 64:		Line 64:

	The nicest part about this system is, you don't even have to update your <code>$PATH</code> (unless you're installing a brand-new program). You can set your <code>$PATH</code> variable to point to the standard version, so that when you upgrade to a new version, and replace the "standard version" soft link, the new version will automatically be on your path.		The nicest part about this system is, you don't even have to update your <code>$PATH</code> (unless you're installing a brand-new program). You can set your <code>$PATH</code> variable to point to the standard version, so that when you upgrade to a new version, and replace the "standard version" soft link, the new version will automatically be on your path.



			{{Programs}}
			{{Unix Programs}}

			[[Category:Build Tools]]

Admin: /* Directory Structure */

2011-03-13T07:57:35Z

Directory Structure

← Older revision		Revision as of 07:57, 13 March 2011
Line 19:		Line 19:

	1.0 1.1 1.2 1.3 1.4 2.0 2.1		1.0 1.1 1.2 1.3 1.4 2.0 2.1
	2.2 2.3 2.4 2.5 2.6		2.2 2.3 2.4 2.5 2.6 std

	</syntaxhighlight>		</syntaxhighlight>

	* Finally, make a symbolic link to the "default" version (I call this <code>std</code> for standard version)		* Finally, make a symbolic link to the "default" version (I call this <code>std</code>, for the "standard version")



	== Sharing Information Among Versions ==		== Sharing Information Among Versions ==

Admin: Created page with "This is a short guide to upgrading software. = Before You Upgrade = == Directory Structure == In order to make it easy to upgrade software, it's important to maintain an org..."

2011-03-13T07:56:56Z

Created page with "This is a short guide to upgrading software. = Before You Upgrade = == Directory Structure == In order to make it easy to upgrade software, it's important to maintain an org..."

New page

This is a short guide to upgrading software.

= Before You Upgrade =

== Directory Structure ==

In order to make it easy to upgrade software, it's important to maintain an organized directory structure. I recommend the following:

* Keep all of your installed programs in a common folder - I use <code>~/pkg</code>

* Keep all versions of a given program in a common directory - for example, all versions of Apache should be kept in <code>~/pkg/apache/</code>

* Inside the common program directory, have each version installed to its own directory; e.g.:

<syntaxhighlight lang="bash">
$ ls ~/pkg/apache

1.0 1.1 1.2 1.3 1.4 2.0 2.1
2.2 2.3 2.4 2.5 2.6

</syntaxhighlight>

* Finally, make a symbolic link to the "default" version (I call this <code>std</code> for standard version)

== Sharing Information Among Versions ==

If you want to share information across all versions of a program, there are some subtleties you will have to think about before you install your program. For example, you may want all versions of Apache to use a common configuration file, or a common web directory. Normally, each version creates its own web directory and configuration files. However, when configuring your program, you can set configure options to hard-code the location of the configure files. For example, for Apache:

<syntaxhighlight lang="bash">
# Example Apache configure line

./configure \
--prefix=$HOME/pkg/apache/2.2.17 \
--sysconfdir=$HOME/pkg/apache/conf
</syntaxhighlight>

Other programs, such as PHP, also have the same configure option:

<syntaxhighlight lang="bash">
# Example PHP configure line

./configure \
--prefix=$HOME/pkg/php/5.3.5 \
--sysconfdir=$HOME/pkg/php/conf
</syntaxhighlight>

To find the appropriate option, you can run <code>./configure --help</code>, which will print all configure options.

= Upgrading =

Once you have the above directory structure, upgrading is simple.

First, download and (if necessary) untar the source code.

Next, run configure, using the appropriate options (see above) so that the build will use the right configuration files, etc. Set the prefix to be the appropriate version number in the appropriate program directory.

Run make, make install, etc.

Test the new version of the program to ensure that it works properly. Once you are convinced it is working as expected, you can replace the "standard version" soft link (<code>std</code>) to point to the latest version.

The nicest part about this system is, you don't even have to update your <code>$PATH</code> (unless you're installing a brand-new program). You can set your <code>$PATH</code> variable to point to the standard version, so that when you upgrade to a new version, and replace the "standard version" soft link, the new version will automatically be on your path.