Modify a pre-existing program - Revision history

Brad Berg at 13:52, 27 August 2009

2009-08-27T13:52:39Z

← Older revision		Revision as of 13:52, 27 August 2009
Line 2:		Line 2:
	NOTE: This section on modifications is incomplete.		NOTE: This section on modifications is incomplete.

	~~Here are some CVS commands you might find handy.~~

	~~<pre>~~
	~~> cvs update -d <directory> # Bring a new directory into your sandbox.~~
	~~> cvs log <file> # List log messages for a file.~~

	~~> cvs add -m "add directory" <directory> # Create a new directory.~~

	~~> cvs add -m "add file" <file> # Create a new file.~~
	~~> cvs commit -m "commit file" <file>~~

	~~> cvs delete <file> # To delete first remove the file from your sandbox.~~
	~~> cvs commit -m "gone" <file>~~

	~~> cvs export -D NOW <directory> # Snapshot without administative directories.~~
	~~> tar cvf <project>.tar <directory> # Make a tar ball.~~
	~~> gzip <project>.tar # Compress it into: <project>.tar.gz~~

	~~> cvs checkout -D yesterday <directory> # Get previous versions of a directory.~~
	~~> cvs checkout -D "<#> hour ago"~~
	~~> cvs checkout -D "<month>/<day>/<year>"~~
	~~</pre>~~

	== Install a program or library. ==		== Install a program or library. ==

Brad Berg at 13:36, 5 August 2009

2009-08-05T13:36:18Z

@@ Line 1: / Line 1: @@
 == Modify a program or library. ==
-A section on modifications is not yet written.
+NOTE:  This section on modifications is incomplete.
 == Install a program or library. ==

Brad Berg at 16:34, 29 May 2009

2009-05-29T16:34:21Z

← Older revision		Revision as of 16:34, 29 May 2009
Line 5:		Line 5:
	Programs and libraries can be installed to your sandbox or the shared public $G installation directories. The installation directory is named <code>install_$GARCH</code>; where <code>$GARCH</code> is the platform name (e.g. <code>install_linux</code> or <code>install_WIN32</code>). By default the installation directory is at the top of your sandbox; which can be your home directory or in the $G user area.		Programs and libraries can be installed to your sandbox or the shared public $G installation directories. The installation directory is named <code>install_$GARCH</code>; where <code>$GARCH</code> is the platform name (e.g. <code>install_linux</code> or <code>install_WIN32</code>). By default the installation directory is at the top of your sandbox; which can be your home directory or in the $G user area.

	Advanced users can designate any location by setting the <code>$GTO</code> variable. This variable should be used with caution and you should fully understand its usage before setting it. When it is not set the make files will prevent you from building or installing programs into any sub-directory of the public $G area. This helps protects public areas from accidental corruption.		Advanced users can designate any installation location by setting the <code>$GTO</code> variable. This variable should be used with caution and you should fully understand its usage before setting it. When it is not set the make files will prevent you from building or installing programs into any sub-directory of the public $G area. This helps protects public areas from accidental corruption.

	To set up an installation directory in your sandbox first you need to create the directory. If you do not want to use either of the default locations you will also need to set the GTO variable to the parent directory.		To set up an installation directory in your sandbox first you need to create the directory. If you do not want to use either of the default locations you will also need to set the <code>GTO</code> variable to the parent directory.

	<pre>		<pre>
	> mkdir -p $GROOT/users/$USER/~~sandbox~~/install_$GARCH/		> mkdir -p $GROOT/users/$USER/my_sandbox/install_$GARCH/
	> setenv GTO $GROOT/users/$USER/~~sandbox~~		> setenv GTO $GROOT/users/$USER/my_sandbox
	</pre>		</pre>

Brad Berg: /* Install a program or library. */

2009-05-29T16:31:55Z

Install a program or library.

← Older revision		Revision as of 16:31, 29 May 2009
Line 5:		Line 5:
	Programs and libraries can be installed to your sandbox or the shared public $G installation directories. The installation directory is named <code>install_$GARCH</code>; where <code>$GARCH</code> is the platform name (e.g. <code>install_linux</code> or <code>install_WIN32</code>). By default the installation directory is at the top of your sandbox; which can be your home directory or in the $G user area.		Programs and libraries can be installed to your sandbox or the shared public $G installation directories. The installation directory is named <code>install_$GARCH</code>; where <code>$GARCH</code> is the platform name (e.g. <code>install_linux</code> or <code>install_WIN32</code>). By default the installation directory is at the top of your sandbox; which can be your home directory or in the $G user area.

	Advanced users can designate any location by setting the <code>$GTO</code> variable. This variable should be used with caution and you should fully understand its usage before setting it. When it is not set make files will prevent you from building or installing programs into any sub-directory of the public $G area. This protects public areas from accidental corruption.		Advanced users can designate any location by setting the <code>$GTO</code> variable. This variable should be used with caution and you should fully understand its usage before setting it. When it is not set the make files will prevent you from building or installing programs into any sub-directory of the public $G area. This helps protects public areas from accidental corruption.

			To set up an installation directory in your sandbox first you need to create the directory. If you do not want to use either of the default locations you will also need to set the GTO variable to the parent directory.

			<pre>
			> mkdir -p $GROOT/users/$USER/sandbox/install_$GARCH/
			> setenv GTO $GROOT/users/$USER/sandbox
			</pre>

			When you run <code>make install</code> software will be copied to the <code>$GTO/install_$GARCH/</code> directory. Then you can install and test software in your sandbox without interfering with the public $G installations.

			After you are confident the software works you can install it in the public area by setting <code>GTO</code> to <code>G</code>. Always unset this when you are done to avoid unintentionally corrupting the public installations.

			<pre>
			> setenv GTO $G # Allow installs into $G.
			> make install # Copy files to: $G/install_$GARCH
			> unsetenv GTO # GTO considered harmful.
			</pre>

Brad Berg: New page: == Modify a program or library. == A section on modifications is not yet written. == Install a program or library. == Programs and libraries can be installed to your sandbox or the shared...

2009-05-29T15:55:13Z

New page: == Modify a program or library. == A section on modifications is not yet written. == Install a program or library. == Programs and libraries can be installed to your sandbox or the shared...

New page

== Modify a program or library. ==
A section on modifications is not yet written.

== Install a program or library. ==
Programs and libraries can be installed to your sandbox or the shared public $G installation directories. The installation directory is named <code>install_$GARCH</code>; where <code>$GARCH</code> is the platform name (e.g. <code>install_linux</code> or <code>install_WIN32</code>). By default the installation directory is at the top of your sandbox; which can be your home directory or in the $G user area.

Advanced users can designate any location by setting the <code>$GTO</code> variable. This variable should be used with caution and you should fully understand its usage before setting it. When it is not set make files will prevent you from building or installing programs into any sub-directory of the public $G area. This protects public areas from accidental corruption.