From fdc37cbd9d85afdb515ec3682b35c426307b554e Mon Sep 17 00:00:00 2001 From: Björn Stenberg Date: Fri, 12 Apr 2002 15:30:08 +0000 Subject: Added CVS instructions git-svn-id: svn://svn.rockbox.org/rockbox/trunk@90 a1c6a512-1295-4272-9138-f99709370657 --- www/cvs.t | 106 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 106 insertions(+) create mode 100644 www/cvs.t (limited to 'www/cvs.t') 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 @@ +#define _PAGE_ Accessing source code via CVS +#include "head.t" + +

Browsing the repositry

+ +

Just go here. + +

Downloading (checking out) the source

+ +

You need to have +CVS and +SSH installed. + +

Anonymously

+ +

If you are not a registered developer, use this method. +When asked for a password, just press enter: + +

cvs -d:pserver:anonymous@cvs.rockbox.sourceforge.net:/cvsroot/rockbox login +
cvs -z3 -d:pserver:anonymous@cvs.rockbox.sourceforge.net:/cvsroot/rockbox co firmware + +

A "firmware" directory will be created in your current directory, and all the source files go there. + +

For developers

+ +

For this, you need to: + +

    +
  1. Have a SourceForge account +
  2. Be a +registered developer +of the Rockbox project +
  3. Have logged on to your account once (ssh username@rockbox.sourceforge.net) and then waited a few hours for SourceForge to set up your cvs +
+ +

Then run: + +

export CVS_RSH=ssh +
cvs -z3 -d:ext:username@cvs.rockbox.sourceforge.net:/cvsroot/rockbox co firmware + +

Checking in modifications

+ +

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: + +

cvs commit filename + +

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: + +

cvs commit -m "This is my change comment" filename + + +

Updating your repository

+ +

Since several people commit to the repository, you will need to periodically +synchronize your local files with the changes made by others. +This operation is called "update": + +

cvs update + + +

Adding a new file

+n +

Adding a file is very simple: + +

cvs add filename + +

If you are adding a binary file, you need to specify the -kb flag: + +

cvs add -kb filename + +

These changes, like any other change, has to be committed before they will be visible on the server. + +

Querying the status of your files

+ +

Sometimes it is interesting to get a list of the status of your files versus +those on the remote repository. This is called "status": + +

cvs status + +

The output from "status" can be rather verbose. You may want to filter it with grep: + +

cvs status | grep Status + +

To only list files who differ from the server, filter again: + +

cvs status | grep Status | grep -v Up-to-date + +

Getting rid of the password prompts

+ +

Each cvs operation has to be authenticated with ssh. This is normally done +by you entering your password. This gets boring fast. +Instead, you can register your public ssh key with your SourceForge account. This way, your connection is authenticated automatically. + +

Log in +to your SourceForge account and go to your +account options. +On the bottom of the page, there is a link to +edit your ssh keys. +Copy the contents of your local .ssh/identity.pub or +.ssh/id_rsa.pub there. + +

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. + +

If you work from several different computers, you must add the key for each of your accounts you are using. + +#include "foot.t" -- cgit v1.2.3