summaryrefslogtreecommitdiff
path: root/www/cvs.t
diff options
context:
space:
mode:
authorBjörn Stenberg <bjorn@haxx.se>2002-04-12 15:30:08 +0000
committerBjörn Stenberg <bjorn@haxx.se>2002-04-12 15:30:08 +0000
commitfdc37cbd9d85afdb515ec3682b35c426307b554e (patch)
treeab350d3096551b8d0faf8caacb13bcb473250827 /www/cvs.t
parent705a6d9b46fffd36ad50e23817b02b83fcae89bb (diff)
downloadrockbox-fdc37cbd9d85afdb515ec3682b35c426307b554e.tar.gz
rockbox-fdc37cbd9d85afdb515ec3682b35c426307b554e.zip
Added CVS instructions
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@90 a1c6a512-1295-4272-9138-f99709370657
Diffstat (limited to 'www/cvs.t')
-rw-r--r--www/cvs.t106
1 files changed, 106 insertions, 0 deletions
diff --git a/www/cvs.t b/www/cvs.t
new file mode 100644
index 0000000000..0ca5000bde
--- /dev/null
+++ b/www/cvs.t
@@ -0,0 +1,106 @@
1#define _PAGE_ Accessing source code via CVS
2#include "head.t"
3
4<h2>Browsing the repositry</h2>
5
6<p>Just go <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/rockbox/">here</a>.
7
8<h2>Downloading (checking out) the source</h2>
9
10<p>You need to have
11<a href="http://www.cvshome.org">CVS</a> and
12<a href="http://www.openssh.com">SSH</a> installed.
13
14<h3>Anonymously</h3>
15
16<p>If you are not a registered developer, use this method.
17When asked for a password, just press enter:
18
19<p><tt>cvs -d:pserver:anonymous@cvs.rockbox.sourceforge.net:/cvsroot/rockbox login
20<br>cvs -z3 -d:pserver:anonymous@cvs.rockbox.sourceforge.net:/cvsroot/rockbox co firmware</tt>
21
22<p>A "firmware" directory will be created in your current directory, and all the source files go there.
23
24<h3>For developers</h3>
25
26<p>For this, you need to:
27
28<ol>
29<li> Have a <a href="http://sourceforge.net/account/register.php">SourceForge account</a>
30<li> Be a
31<a href="http://sourceforge.net/project/memberlist.php?group_id=44306">registered developer</a>
32of the Rockbox project
33<li> Have logged on to your account once (ssh <b>username</b>@rockbox.sourceforge.net) and then waited a few hours for SourceForge to set up your cvs
34</ol>
35
36<p>Then run:
37
38<p><tt>export CVS_RSH=ssh
39<br>cvs -z3 -d:ext:<b>username</b>@cvs.rockbox.sourceforge.net:/cvsroot/rockbox co firmware</tt>
40
41<h2>Checking in modifications</h2>
42
43<p>CVS is a "no-reserve" version control system. This means that you work on your local files without first reserving them. Any conflicts with other developers are resolved when you check-in, or "commit" as it's called in CVS:
44
45<p><tt>cvs commit <b>filename</b></tt>
46
47<p>This will start an editor and ask you to describe the changes you've made. If you want, you can use the -m command line option to specify the comment right there:
48
49<p><tt>cvs commit -m "This is my change comment" <b>filename</b></tt>
50
51
52<h2>Updating your repository</h2>
53
54<p>Since several people commit to the repository, you will need to periodically
55synchronize your local files with the changes made by others.
56This operation is called "update":
57
58<p><tt>cvs update</tt>
59
60
61<h2>Adding a new file</h2>
62n
63<p>Adding a file is very simple:
64
65<p><tt>cvs add <b>filename</b></tt>
66
67<p>If you are adding a binary file, you need to specify the -kb flag:
68
69<p><tt>cvs add -kb <b>filename</b></tt>
70
71<p>These changes, like any other change, has to be committed before they will be visible on the server.
72
73<h2>Querying the status of your files</h2>
74
75<p>Sometimes it is interesting to get a list of the status of your files versus
76those on the remote repository. This is called "status":
77
78<p><tt>cvs status</tt>
79
80<p>The output from "status" can be rather verbose. You may want to filter it with grep:
81
82<p><tt>cvs status | grep Status</tt>
83
84<p>To only list files who differ from the server, filter again:
85
86<p><tt>cvs status | grep Status | grep -v Up-to-date</tt>
87
88<h2>Getting rid of the password prompts</h2>
89
90<p>Each cvs operation has to be authenticated with ssh. This is normally done
91by you entering your password. This gets boring fast.
92Instead, you can register your public ssh key with your SourceForge account. This way, your connection is authenticated automatically.
93
94<p><a href="http://sourceforge.net/account/login.php">Log in</a>
95to your SourceForge account and go to your
96<a href="https://sourceforge.net/account/">account options</a>.
97On the bottom of the page, there is a link to
98<a href="https://sourceforge.net/account/editsshkeys.php">edit your ssh keys</a>.
99Copy the contents of your local <tt>.ssh/identity.pub</tt> or
100<tt>.ssh/id_rsa.pub</tt> there.
101
102<p>Like many things on SourceForge, they key change doesn't take effect immediately. You'll have to wait a few hours until some magic batch job kicks in and puts your keys where they should be. Then you can use cvs without entering your password.
103
104<p>If you work from several different computers, you must add the key for each of your accounts you are using.
105
106#include "foot.t"