--- loncom/build/readme.html	2002/07/31 18:14:31	1.19
+++ loncom/build/readme.html	2011/01/09 19:01:23	1.23
@@ -1,27 +1,22 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!-- The LearningOnline Network with CAPA -->
-<!-- $Id: readme.html,v 1.19 2002/07/31 18:14:31 harris41 Exp $ -->
-<html>
+<!-- $Id: readme.html,v 1.23 2011/01/09 19:01:23 raeburn Exp $ -->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8"></meta>
-<meta name="GENERATOR"
-      content="Scott Harrison and Emacs Version 3.14159265358979"></meta>
 <title>LON-CAPA Software Developer Guide</title>
 </head>
 <body>
 <h1>LON-CAPA Software Developer Guide</h1>
 <p>
-<br /><i>Written by Scott,<br />
-<a href="mailto:sharrison@users.sourceforge.net">
-sharrison@users.sourceforge.net</a>,<br />
-January 17, 2001</i>
-<br /><i>Last updated, July 31, 2002</i>
+Created: <i>January 17, 2001</i>
+<br />Last updated: <i>January 9, 2011</i>
 </p>
 <ol>
 <li><a href="#Using_CVS">Using CVS</a>
 <ul>
-<li><a href="#cvslog">Logging in and out (cvs login; cvs logout)</a></li>
+<li><a href="#cvslog">Setting up cvs access</a></li>
 <li><a href="#cvsupdate">Updating files (cvs update -d)</a></li>
 <li><a href="#cvssave">Saving files (cvs commit)</a></li>
 <li><a href="#cvsadd">Adding files (cvs add)</a></li>
@@ -49,29 +44,25 @@ These instructions assume that you are u
 terminal.
 <ul>
 <li><a name="cvslog" />
-    <h3>Using CVS: Logging in and out (cvs login; cvs logout)</h3>
+    <h3>Setting up cvs access</h3>
 <p>
-In order to log into CVS, CVS needs to be part of your system environment.
+CVS needs to be part of your system environment in order to access the LON-CAPA CVS repository, 
 You can do this by:
 </p>
 <p>
 <font color="#008800">
-<tt>export CVSROOT=:pserver:USERNAME@install.lon-capa.org:/home/cvs</tt>
+<tt>export CVS_RSH=ssh</tt><br />
+<tt>export CVSROOT=:ext:USERNAME@source.lon-capa.org:/home/cvs</tt>
 </font>
 </p>
-<p>
-To actually login, you will need to execute the following command:
-</p>
-<p>
-<font color="#008800">
-<tt>cvs login</tt>
-</font>
-</p>
-<p>
-You are then prompted for a password.
-If you do not have a password, or the password is not working, you
-should contact <a href="mailto:helen@lon-capa.org">helen@lon-capa.org</a>.
-</p>
+<br />
+To actually issue CVS commands you will need to: 
+<br /><br />
+<ol>
+<li>Have installed the CVS client, e.g., <font color="#008800"><tt>yum install cvs</tt></font></li>
+<li>Have been issued a CVS account, (send a request to the <a href="mailto:helpdesk@loncapa.org">LON-CAPA helpdesk</a>)</li>
+<li>Have generated public and private keys via <font color="#008800"><tt>ssh-keygen -t dsa</tt></font> and sent the public key to the LON-CAPA helpdesk for installation on the CVS server.</li>
+</ol>
 <p>
 The first time you use CVS, you need to CHECKOUT the repository.
 Generally speaking, you need to checkout <tt>loncapa</tt> only once
@@ -85,14 +76,6 @@ To check-out the repository, use the <tt
 <tt>cd loncapa</tt>
 </font>
 </p>
-<p>After completing work with the CVS repository,
-you can log out:
-</p>
-<p>
-<font color="#008800">
-<tt>cvs logout</tt>
-</font>
-</p>
 </li>
 <li><a name="cvsupdate" />
     <h3>Using CVS: Updating files (cvs update -d)</h3>
@@ -201,10 +184,10 @@ cvs commit FILENAME
 Note that CVS typically invokes the
 <a href="http://www.eng.hawaii.edu/Tutor/vi.html">vi</a> editor and solicits
 comments about your latest changes to the software.   Your comments should be
-both short yet uniquely descriptive.  For example:
+descriptive and informative.  For example:
 </p>
 <ul>
-<li><strong>BAD</strong> - "made some changes and am drinking soda"</li>
+<li><strong>BAD</strong> - "saving my work"</li>
 <li><strong>GOOD</strong> - "implemented syntax checking of perl scripts
 with -c flag"</li>
 </ul>
@@ -564,7 +547,7 @@ For safety reasons (so as to preserve a
 configuration files are NOT installed during this step.  This means
 that files such as <tt>/etc/httpd/conf/loncapa.conf</tt>,
 <tt>/home/httpd/html/res/adm/includes/copyright.tab</tt>, and
-<tt>/home/httpd/spare.tab are not overwritten</tt>, but remain as old,
+<tt>/home/httpd/spare.tab</tt> are not overwritten, but remain as old,
 non-updated copies.  (To automatically update these files and save/restore
 their encoded machine configuration, you must run "make configinstall").
 </p>
@@ -659,7 +642,7 @@ RPM: BinaryRoot base_rpm_file_list
 	cat $(SOURCE)/doc/loncapafiles/loncapafiles.lpml | \
 	perl lpml_parse.pl make_rpm $(CATEGORY) $(DIST) $(SOURCE) $(TARGET) \
 	> base_customizerpm.xml
-	cat base_rpm_file_list.txt | perl make_rpm.pl base 3.2 '' '' \
+	cat base_rpm_file_list.txt | perl make_rpm.pl base 3.2 1 '' '' \
 	BinaryRoot base_customizerpm.xml
 
 BinaryRoot: base_rpm_file_list
@@ -683,7 +666,7 @@ occur on the '/' filesystem location.
 span of months) and, unlike other automated RPM-builders, cleanly
 builds new RPMs without any after-effect of temporary files left
 on the system.  The generated RPM is labeled in the format
-LON-CAPA-base-(VERSION)-1.i386.  VERSION is specified inside the
+LON-CAPA-base-(VERSION)-(RELEASE).i386.  VERSION is specified inside the
 Makefile.
 </p>
 </li>
