| 1 |
<html> |
| 2 |
|
| 3 |
<head> |
| 4 |
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> |
| 5 |
<meta name="GENERATOR" content="Microsoft FrontPage 4.0"> |
| 6 |
<meta name="ProgId" content="FrontPage.Editor.Document"> |
| 7 |
<title>How To Obtain All ESRG Source Code And Materials Using Anonymous CVS |
| 8 |
Access</title> |
| 9 |
<base target="main"> |
| 10 |
</head> |
| 11 |
|
| 12 |
<body background="../../bkgnds/bk10.gif"> |
| 13 |
|
| 14 |
<p align="center"><b><font size="4">How To Obtain All ESRG Source Code And |
| 15 |
Materials Using Anonymous CVS Access</font></b></p> |
| 16 |
<hr> |
| 17 |
<p><a href="../../glossary/glossary.htm#cvs_vc" target="_blank">CVS</a> is the |
| 18 |
version control system most in favor with the open-source community. Using |
| 19 |
CVS, one can collaborate with other software developers in the development of |
| 20 |
source files and other documents. <a href="http://sourceforge.net" target="_blank">SourceForge</a> |
| 21 |
has cryptographic security in place for those wishing to collaborate in |
| 22 |
development (i.e. to change or add files using CVS), and getting set up to collaborate |
| 23 |
in this way is |
| 24 |
a complicated process. However, if you only wish to obtain the newest |
| 25 |
revisions or specific revisions of files (but do not wish to modify the CVS |
| 26 |
repository), the process is much simpler, and is described on this page.</p> |
| 27 |
<ol> |
| 28 |
<li><b>Be sure that you wish to obtain the materials via CVS.</b> |
| 29 |
Obtaining the materials via CVS has the disadvantage that the files you |
| 30 |
obtain may not correspond to any released version of <i>The ESRG Tool Set</i>. |
| 31 |
The differences between anonymous CVS access and using one of the source |
| 32 |
distributions are described <a href="../esrg_src_howtos/anon_cvs_vs_targz.htm" target="_blank">here</a>. |
| 33 |
If you wish to obtain material via anonymous CVS, it should be for one of |
| 34 |
the following reasons:</li> |
| 35 |
<ul> |
| 36 |
<li>You require materials more recent than the latest source distribution. </li> |
| 37 |
<li>You wish to obtain materials that are not packaged in any distribution |
| 38 |
(the <a href="../../glossary/glossary.htm#installshield_express" target="_blank">InstallShield |
| 39 |
Express</a> project file, for example). </li> |
| 40 |
</ul> |
| 41 |
<li><b>Obtain a list of all CVS modules.</b> "module" is a CVS |
| 42 |
term for a top-level directory in the CVS repository. The easiest way |
| 43 |
to obtain a list of all CVS modules is to view <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/esrg/" target="_blank">this |
| 44 |
web page</a> and print it or write down all the folder names (except <i>CVSROOT</i>, |
| 45 |
which can be ignored). </li> |
| 46 |
<li><b>Obtain a CVS client.</b> For a Windows® system, the CVS |
| 47 |
executable and brief instructions are <a href="../../arch_sw_etc/cvs_1_11/index.html" target="_blank">here</a>. |
| 48 |
If you type "<i>cvs</i>" at a DOS command prompt and receive a |
| 49 |
message from the CVS program, you have installed the client |
| 50 |
successfully. The following screen snapshot shows a typical message |
| 51 |
from a CVS client when only "<i>cvs</i>" is typed. |
| 52 |
<p align="center"><img border="0" src="cvs_msg_no_cmd.gif" width="612" height="251"></p> |
| 53 |
</li> |
| 54 |
<li><b>Open a [DOS] shell.</b> On Windows® systems, this is normally |
| 55 |
done from the <i>Start</i> menu, <i>Start</i> <font face="Wingdings 3">g</font> |
| 56 |
<i>Programs</i> <font face="Wingdings 3">g</font> <i>Accessories</i> <font face="Wingdings 3">g</font> |
| 57 |
<i>Command Prompt</i>. On *nix systems, the procedure to obtain a |
| 58 |
shell varies.</li> |
| 59 |
<li><b>Change directories to "c:\" (Window® systems only).</b> |
| 60 |
On Windows® systems, the checkout must be performed from the root directory |
| 61 |
of the C: drive. On *nix systems, any directory will do.</li> |
| 62 |
<li><b>Issue the CVS checkout commands, specifying the modules gathered |
| 63 |
earlier.</b> For example, as of April 2003, the following command |
| 64 |
would be appropriate (the list of modules may have changed or grown since |
| 65 |
then):<br> |
| 66 |
<br> |
| 67 |
<font face="Courier" size="2">cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/esrg |
| 68 |
checkout esrgdocs esrgdstb esrgnxpj esrgpcpj esrgpubs esrgubka esrgweba<br> |
| 69 |
</font><br> |
| 70 |
Also as of April, 2003, the total number quantity of data to be downloaded |
| 71 |
is about 40 Mb (at least 4 hours over a typical modem connection).<br> |
| 72 |
<br> |
| 73 |
A CVS checkout has the advantage that if the checkout is interrupted (by a |
| 74 |
dropped modem connection, for example), issuing the same command again will |
| 75 |
effectively resume where the previous attempt left off. CVS recognizes |
| 76 |
files which have already been checked out and skips them on subsequent |
| 77 |
checkout attempts.<br> |
| 78 |
<br> |
| 79 |
It is also possible that you require only a subset of the modules listed |
| 80 |
above. If this is the case, only list those modules you need on the |
| 81 |
CVS command line.</li> |
| 82 |
</ol> |
| 83 |
<hr> |
| 84 |
<p align="center" style="margin-top: -2; margin-bottom: -1"><font size="1">This |
| 85 |
web page is maintained by <a href="mailto:dtashley@users.sourceforge.net">David |
| 86 |
T. Ashley</a>.<br>$Header: /cvsroot/esrg/sfesrg/esrgweba/htdocs/howtos/sourceforge/esrg_all_src_cvs_anonymous.htm,v 1.5 2003/04/28 18:05:35 dtashley Exp $</font></p> |
| 87 |
<hr noshade size="5"> |
| 88 |
|
| 89 |
</body> |
| 90 |
|
| 91 |
</html> |
Parent Directory
| 
Revision Log