<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<HTML>
<HEAD>
<title>uClibc Anonymous CVS Instructions</title>
</HEAD>
<body text="#000000" alink="#660000" link="#660000" bgcolor="#dee2de" vlink="#660000">
<basefont face="lucida, helvetica, arial" size="3">
<H3>Accessing the uClibc CVS Repository</H3>
<CENTER>
<TABLE BORDER=0 CELLSPACING=1 CELLPADDING=2>
<TR>
<td bgcolor="#000000">
<FONT FACE="lucida, helvetica" COLOR="#ccccc0">
<B>u C l i b c</B>
</FONT>
</TD>
</TR>
</TABLE>
</CENTER>
<TABLE WIDTH="95%" CELLSPACING=1 CELLPADDING=4 BORDER=1>
<TR><TD BGCOLOR="#ccccc0" ALIGN=center>
<A NAME="intro"> <BIG><B>
Anonymous CVS
</B></BIG></A>
</TD></TR>
<TR><TD BGCOLOR="#eeeee0">
We allow anonymous (read-only) CVS access to everyone. The first command you
need to run for anonymous CVS access is:
<pre>
cvs -d:pserver:anonymous@uclibc.org:/var/cvs login</pre>
<p>
CVS will prompt you for a password. Just press Enter. This step only
needs to be done once, the first time you attempt to access CVS.
<p>
Once the login is complete, you can then check the list of available
CVS modules by running the following command (all on one line):
<pre>
cvs -z3 -d:pserver:anonymous@uclibc.org:/var/cvs co -c </pre>
<p>
If you wish, you can then check out a local copy of any of the
available modules. The following is an example of how to grab
a copy of the uClibc source code:
<pre>
cvs -z3 -d:pserver:anonymous@uclibc.org:/var/cvs co -P uClibc</pre>
This will create a directory called <b>uClibc</b> in the current
directory which contains the latest and greatest source code for
uClibc.
<p>
I usually create a ~/.cvsrc file with the following things in it, and I
recommend you should use the same:
<pre>
-z3
update -dP
rdiff -u
diff -ubBwpN
checkout -P</pre>
<p>
Once you've checked out a copy of the source tree, you can update your
source tree at any time so it is in sync with the latest and greatest by
running the command:
<pre>
cvs update</pre>
Because you've only been granted anonymous access to the tree, you won't be
able to commit any changes. Changes can be submitted for inclusion by posting
them to the appropriate <a
href="http://www.uclibc.org/mailman/listinfo/uclibc">mailing list</a>.
<!-- End of Table -->
</TD></TR>
</TABLE>
<TABLE WIDTH="95%" CELLSPACING=1 CELLPADDING=4 BORDER=1>
<TR><TD BGCOLOR="#ccccc0" ALIGN=center>
<A NAME="howto"> <BIG><B>
How to use CVS
</B></BIG></A>
</TD></TR>
<TR><TD BGCOLOR="#eeeee0">
If you want to know all the gory details, you will want to visit
<a href="http://www.cvshome.org/">the CVS main web page</a>.<p>
For the impatient, the following is probably about all you need to know:
<p>
<dl>
<dt><pre>cvs checkout -c</pre>
<dd>Will list the modules available for checkout
<dt><pre>cvs checkout < module name ></pre>
<dd>Will checkout the named module
<dt><pre>cvs co < module name ></pre>
<dd>Same thing
<dt><pre>cvs update</pre>
<dd>Updates your local archive so it is in sync with the repository
-- your local updates are left intact. Tries to merge upstream updates
into your local updates. You will see the following tags when it is
updating your local repository: C means conflict, U means update,
P means patched, and M means modified.
<dt><pre>cvs up</pre>
<dd>Same thing
<dt><pre>cvs update < file name ></pre>
<dd>Same thing but for just the named file(s)/directory(s).
<dt><pre>cvs commit</pre>
<dd>Will check in all your work.
<dt><pre>cvs add < file name ></pre>
<dd>Adds the named file/directory into CVS
<dt><pre>cvs remove < file name ></pre>
<dd>Removes the named file/directory from the upstream repository.
<dt><pre>cvs rm < file name ></pre>
<dd>Same thing
<dt><pre>cvs log < file name ></pre>
<dd>Gives you the complete version history of what has happened to the named file(s).
Along with all tags, all commit messages, etc...
<dt><pre>cvs status < file name ></pre>
<dd>Gives you the current version number of the file(s) in question.
<dt><pre>cvs tag TAGNAME</pre>
<dd>Tags the versions of everything in the repository with the TAGNAME label.
<dt><pre>cvs tag TAGNAME < file name ></pre>
<dd>Tags the named file(s) in the repository with the TAGNAME label.
<dt><pre>cvs diff</pre>
<dd>Gives you the difference between the local repository and the upstream repository.
<dt><pre>cvs diff < file name ></pre>
<dd>Same but for the named file(s).
<dt><pre>cvs diff -r 1.5 < file name ></pre>
<dd>Same but gives you the difference between the named file(s) and
version 1.5 of the named file(s).
<dt><pre>cvs diff -r TAGNAME < file name ></pre>
<dd>Same but gives you the difference between the named file(s) and the
of the file tagged TAGNAME in the upstream repository.
<dt><pre>cvs rdiff -r TAGNAME module</pre>
<dd>Gives you a diff (that you can actually use with patch) between the current
version of module and the specified tagged version.
<dt><pre>cvs import < directory to import > < name for new module > start</pre>
<dd>Add a new module into the CVS archive.
<p>
</dl>
<!-- End of Table -->
</TD></TR>
</TABLE>
<!-- Footer -->
<HR>
<TABLE WIDTH="100%">
<TR>
<TD>
<font size="-1" face="arial, helvetica, sans-serif">
Mail all comments, insults, suggestions and bribes to
<a href="mailto:andersen@codepoet.org">Erik Andersen</a><BR>
</font>
</TD>
<TD>
<a href="http://www.vim.org"><img border=0 width=90 height=36
src="images/written.in.vi.png"
alt="This site created with the vi editor"></a>
</TD>
<TD>
<a href="http://www.gimp.org/"><img border=0 width=90 height=36
src="images/gfx_by_gimp.png" alt="Graphics by GIMP"></a>
</TD>
<TD>
<a href="http://www.linuxtoday.com"><img width=90 height=36
src="images/ltbutton2.png" alt="Linux Today"></a>
</TD>
<TD>
<p><a href="http://slashdot.org"><img width=90 height=36
src="images/sdsmall.png" alt="Slashdot"></a>
</TD>
<TD>
<a href="http://freshmeat.net"><img width=90 height=36
src="images/fm.mini.png" alt="Freshmeat"></a>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>