Main Page | Namespace List | Class Hierarchy | Alphabetical List | Class List | File List | Namespace Members | Class Members | File Members | Related Pages | Examples

Contributing (A small CVS guide)


Our project is hosted at savannah. The mailing lists and the CVS repository are located there.

Check out the sources from CVS :

ParaGUI's CVS repository can be checked out through anonymous CVS over SSH with the following instruction set. When prompted for a password for anoncvs, simply press the Enter key.

The SSHv2 public key fingerprints for the machine hosting the cvs trees are:

RSA: 1024 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5 DSA: 1024 4d:c8:dc:9a:99:96:ae:cc:ce:d3:2b:b0:a3:a4:95:a5

Stable software repository :

export CVS_RSH="ssh"
cvs -z3 -d:ext:anoncvs@savannah.nongnu.org:/cvsroot/paragui co -r devel-1-0 paragui
Development software repository :
export CVS_RSH="ssh"
cvs -z3 -d:ext:anoncvs@savannah.nongnu.org:/cvsroot/paragui co -r devel-1-1 paragui

When you update from within the module's directory (with cvs update) you do not need the -d option anymore.

Sync with the repository :

cvs -z3 update -d -P

Create a patch/diff :

After editing the sources it's easy to create a difference set of the current repository. Change to the modules directory and issue the following commands (asuming you're using something UNIX like):

cvs -z3 diff -u > whatever_the_name_of_the_patch_is.patch

Get your patch commited :

Send the resulting file to the "paragui-dev@nongnu.org" mailing list describing what it does and why do you want the patch to be commited.


The ParaGUI Project - Alexander Pipelka