Source Control - Revision history

Trevor O'Brien: Put your code into CVS in $G moved to Source Control

2010-04-19T15:37:18Z

Put your code into CVS in $G moved to Source Control

← Older revision		Revision as of 15:37, 19 April 2010
(No difference)

Brad Berg at 13:50, 27 August 2009

2009-08-27T13:50:04Z

← Older revision		Revision as of 13:50, 27 August 2009
Line 1:		Line 1:
	== ~~Before~~ Using CVS ==		== Using CVS ==

	Active projects are being migrated to a new directory structure using a common set of make files. Have Brad help you set up any new project. Students actively working on legacy projects can also begin to migrate to the new directory structure.		Active projects are being migrated to a new directory structure using a common set of make files. Have Brad help you set up any new project. Students actively working on legacy projects can also begin to migrate to the new directory structure.
Line 6:		Line 6:

	:[http://www.nongnu.org/cvs/#TOCintroduction Introduction to CVS]		:[http://www.nongnu.org/cvs/#TOCintroduction Introduction to CVS]

	~~:[http://ximbiot.com/cvs/wiki/CVS--Concurrent%20Versions%20System%20v1.12.12.1 CVS Manual]~~


Line 17:		Line 15:
	On Windows set CVSROOT to: <code>Y:\map\gfx0\cvsroot\</code>		On Windows set CVSROOT to: <code>Y:\map\gfx0\cvsroot\</code>


			The scripts in <code>$G/common/build/setup/</code> can be used to perform common CVS operations. They simplify check ins and use integrity checks to avoid common mistakes.


	=== CVS commands you might find handy ===		=== CVS commands you might find handy ===

Brad Berg at 13:40, 27 August 2009

2009-08-27T13:40:09Z

@@ Line 1: / Line 1: @@
-== How to Use CVS ==
+== Before Using CVS ==
-This page describes how the bulk of existing code in <code>$G</code> is organized.  Active projects are being migrated to a new directory structure using a common set of make files.  Until the procedures are in place have Brad help you set up any new project.  Students actively working on projects can also begin to migrate to the new directory structure.
+Active projects are being migrated to a new directory structure using a common set of make files.  Have Brad help you set up any new project.  Students actively working on legacy projects can also begin to migrate to the new directory structure.
-The <code>$G</code> tree is not intended for users to write to directly, and future IT plans for our group include enforcing this restriction.  Instead, we use the [[w:revision control system|revision control system]] [[w:Concurrent Versions System|CVS]] as an interface to the directory structure in <code>$G</code>.  CVS keeps track of changes to every file, allows concurrent editing of source code by multiple people, and provides an easy means for copying source trees to new locations.
+> cvs checkout -D yesterday <directory>    # Get previous versions of a directory.
-== How Not To Use CVS ==
+=== How Not To Use CVS ===
 * Avoid checking in entire directory trees with junk files.
@@ Line 37: / Line 60: @@
 * Think Twice about Creating Directories.
 CVS does not have a command for renaming or deleting directories.
 [[Category:$G HOWTO]][[Category:Software Development]]

Brad Berg at 14:02, 19 August 2009

2009-08-19T14:02:22Z

@@ Line 1: / Line 1: @@
 This page describes how the bulk of existing code in <code>$G</code> is organized.  Active projects are being migrated to a new directory structure using a common set of make files.  Until the procedures are in place have Brad help you set up any new project.  Students actively working on projects can also begin to migrate to the new directory structure.
@@ Line 16: / Line 18: @@
 ## After adding all the files, run: <pre>cvs commit -m "&lt;commit message&gt;"</pre>
 # Your project should have been automatically added to the <code>$G/src</code> directory on the filesystem you are on now. To get it in the <code>$G/src</code> directory somewhere else, like at the [[Cave]], run this command from within <code>$G/src</code>: <pre>cvs update -d &lt;projectname&gt;</pre>  You may also need to use the same command in <code>$G/lib</code> and <code>$G/doc</code>.
 [[Category:$G HOWTO]][[Category:Software Development]]

Jadrian Miles at 22:25, 14 January 2009

2009-01-14T22:25:02Z

← Older revision		Revision as of 22:25, 14 January 2009
Line 17:		Line 17:
	# Your project should have been automatically added to the <code>$G/src</code> directory on the filesystem you are on now. To get it in the <code>$G/src</code> directory somewhere else, like at the [[Cave]], run this command from within <code>$G/src</code>: <pre>cvs update -d <projectname></pre> You may also need to use the same command in <code>$G/lib</code> and <code>$G/doc</code>.		# Your project should have been automatically added to the <code>$G/src</code> directory on the filesystem you are on now. To get it in the <code>$G/src</code> directory somewhere else, like at the [[Cave]], run this command from within <code>$G/src</code>: <pre>cvs update -d <projectname></pre> You may also need to use the same command in <code>$G/lib</code> and <code>$G/doc</code>.

	~~[[Category:HOWTO]]~~[[Category:$G]][[Category:Software Development]]		[[Category:$G HOWTO]][[Category:Software Development]]

Jadrian Miles at 22:27, 12 January 2009

2009-01-12T22:27:39Z

← Older revision		Revision as of 22:27, 12 January 2009
Line 5:		Line 5:
	Ordinarily, the first steps of development for your own software project happens somewhere in your homedir. This doesn't allow other people to work with your code, though, so once your project is nontrivial you should add it to <code>$G</code> using the <code>gfxprojinit</code> script. This script creates a home for your project in <code>$G/src</code>, but not everything associated with a given project belongs there. To get everything into the right place, follow these steps:		Ordinarily, the first steps of development for your own software project happens somewhere in your homedir. This doesn't allow other people to work with your code, though, so once your project is nontrivial you should add it to <code>$G</code> using the <code>gfxprojinit</code> script. This script creates a home for your project in <code>$G/src</code>, but not everything associated with a given project belongs there. To get everything into the right place, follow these steps:
	# Go to the directory that has your source in it.		# Go to the directory that has your source in it.
	# Delete or move away anything you don't want to go into CVS. If you already have something compiled, do <code>make clean</code> to get rid of the object files~~—~~you don't want to put them in CVS. In general, just leave the Makefile and the source files.		# Delete or move away anything you don't want to go into CVS. If you already have something compiled, do <code>make clean</code> to get rid of the object files --- you don't want to put them in CVS. In general, just leave the Makefile and the source files.
	#* '''Note:''' even though non-source files are sometimes necessary for builds of complex projects, data and config files don't belong in <code>$G/src</code>! Carefully consider whether non-source files belong in the <code>$G/src</code>; they most likely do not and belong in <code>$G/lib</code> (or <code>$G/data</code> for example data on which your program runs) instead. Move these out of the directory temporarily; we'll check them into the appropriate locations later.		#* '''Note:''' even though non-source files are sometimes necessary for builds of complex projects, data and config files don't belong in <code>$G/src</code>! Carefully consider whether non-source files belong in the <code>$G/src</code>; they most likely do not and belong in <code>$G/lib</code> (or <code>$G/data</code> for example data on which your program runs) instead. Move these out of the directory temporarily; we'll check them into the appropriate locations later.
	# If you have any binary files, like images, that you want to go in CVS, move them out of this directory temporarily. We will add them later because CVS requires non-text files to be added with a special flag. Once again, keep in mind that most binary files are program resources and belong in <code>$G/lib</code> rather than <code>$G/src</code>.		# If you have any binary files, like images, that you want to go in CVS, move them out of this directory temporarily. We will add them later because CVS requires non-text files to be added with a special flag. Once again, keep in mind that most binary files are program resources and belong in <code>$G/lib</code> rather than <code>$G/src</code>.
	# Run the following command, replacing <projectname> with the name you want your project to have~~—~~that will become a new directory under <code>$G/src</code>: <pre>gfxprojinit <projectname> .</pre>		# Run the following command, replacing <projectname> with the name you want your project to have --- that will become a new directory under <code>$G/src</code>: <pre>gfxprojinit <projectname> .</pre>
	#* Note the period at the end of that command. It might be hard to see, but it is important.		#* Note the period at the end of that command. It might be hard to see, but it is important.
	#* It's worth knowing, for those familiar with CVS, that <code>gfxprojinit</code> is essentially a fancy wrapper around <code>cvs import</code>. Please be sure to use <code>gfxprojinit</code> anyway, as it maintains important metadata and may do even more in the future.		#* It's worth knowing, for those familiar with CVS, that <code>gfxprojinit</code> is essentially a fancy wrapper around <code>cvs import</code>. Please be sure to use <code>gfxprojinit</code> anyway, as it maintains important metadata and may do even more in the future.

Bradley Berg at 19:49, 6 January 2009

2009-01-06T19:49:13Z

← Older revision		Revision as of 19:49, 6 January 2009
Line 1:		Line 1:
			This page describes how the bulk of existing code in <code>$G</code> is organized. Active projects are being migrated to a new directory structure using a common set of make files. Until the procedures are in place have Brad help you set up any new project. Students actively working on projects can also begin to migrate to the new directory structure.

	The <code>$G</code> tree is not intended for users to write to directly, and future IT plans for our group include enforcing this restriction. Instead, we use the [[w:revision control system\|revision control system]] [[w:Concurrent Versions System\|CVS]] as an interface to the directory structure in <code>$G</code>. CVS keeps track of changes to every file, allows concurrent editing of source code by multiple people, and provides an easy means for copying source trees to new locations.		The <code>$G</code> tree is not intended for users to write to directly, and future IT plans for our group include enforcing this restriction. Instead, we use the [[w:revision control system\|revision control system]] [[w:Concurrent Versions System\|CVS]] as an interface to the directory structure in <code>$G</code>. CVS keeps track of changes to every file, allows concurrent editing of source code by multiple people, and provides an easy means for copying source trees to new locations.

Jadrian Miles at 13:48, 24 September 2008

2008-09-24T13:48:26Z

← Older revision		Revision as of 13:48, 24 September 2008
Line 15:		Line 15:
	# Your project should have been automatically added to the <code>$G/src</code> directory on the filesystem you are on now. To get it in the <code>$G/src</code> directory somewhere else, like at the [[Cave]], run this command from within <code>$G/src</code>: <pre>cvs update -d <projectname></pre> You may also need to use the same command in <code>$G/lib</code> and <code>$G/doc</code>.		# Your project should have been automatically added to the <code>$G/src</code> directory on the filesystem you are on now. To get it in the <code>$G/src</code> directory somewhere else, like at the [[Cave]], run this command from within <code>$G/src</code>: <pre>cvs update -d <projectname></pre> You may also need to use the same command in <code>$G/lib</code> and <code>$G/doc</code>.

	[[Category:HOWTO]][[Category:$G]][[Category:Development]]		[[Category:HOWTO]][[Category:$G]][[Category:Software Development]]

Jadrian Miles at 13:48, 24 September 2008

2008-09-24T13:48:15Z

← Older revision		Revision as of 13:48, 24 September 2008
Line 15:		Line 15:
	# Your project should have been automatically added to the <code>$G/src</code> directory on the filesystem you are on now. To get it in the <code>$G/src</code> directory somewhere else, like at the [[Cave]], run this command from within <code>$G/src</code>: <pre>cvs update -d <projectname></pre> You may also need to use the same command in <code>$G/lib</code> and <code>$G/doc</code>.		# Your project should have been automatically added to the <code>$G/src</code> directory on the filesystem you are on now. To get it in the <code>$G/src</code> directory somewhere else, like at the [[Cave]], run this command from within <code>$G/src</code>: <pre>cvs update -d <projectname></pre> You may also need to use the same command in <code>$G/lib</code> and <code>$G/doc</code>.

	[[Category:HOWTO]][[Category:$G]]		[[Category:HOWTO]][[Category:$G]][[Category:Development]]

Jadrian Miles at 13:45, 24 September 2008

2008-09-24T13:45:41Z

← Older revision		Revision as of 13:45, 24 September 2008
Line 15:		Line 15:
	# Your project should have been automatically added to the <code>$G/src</code> directory on the filesystem you are on now. To get it in the <code>$G/src</code> directory somewhere else, like at the [[Cave]], run this command from within <code>$G/src</code>: <pre>cvs update -d <projectname></pre> You may also need to use the same command in <code>$G/lib</code> and <code>$G/doc</code>.		# Your project should have been automatically added to the <code>$G/src</code> directory on the filesystem you are on now. To get it in the <code>$G/src</code> directory somewhere else, like at the [[Cave]], run this command from within <code>$G/src</code>: <pre>cvs update -d <projectname></pre> You may also need to use the same command in <code>$G/lib</code> and <code>$G/doc</code>.

	[[Category:HOWTO]][[Category:$G~~]][[Category:IT Tools~~]]		[[Category:HOWTO]][[Category:$G]]