DeeDS Development


The DRTS-group has two servers:

  • anubis (Linux,
  • bast (Solaris,

After you get an account, you should change the password as soon as possible - this is done with yppasswd (not passwd)

When you have an account, you can ssh to anubis using the address <>.

Source Control

The DeeDS source code is stored in a CVS repository. To access it you need a CVS client which is installed on most UNIX/Linux systems. To be able to make changes to the repository you need an account on our server. Otherwise you can only get anonymous read-only access to our repository (you may still of course make any changes you want in your own work area, but you cannot check in your modifications).

Local Checkout

If you logged in to one of our servers and want to check out the code, enter an empty directory and write:

cvs -d /home/cvsrep/deeds co .

Remote Checkout using SSH

To check out the code from another computer, enter an empty directory and write (replace <user> with your user name):

cvs -d :ssh;username=<user>;
/home/cvsrep/deeds co .

If you are using an older version of CVS this may not work. You can then use the following instead:

export CVS_RSH=ssh

cvs -d :ext:<user> co .

With this method, you must always enter your password when you want to do an operation on the repository. This can be avoided by creating SSH keys (see man-page for ssh-keygen).

Remote Checkout using Pserver

An alternative is to use pserver access. This requires that an administrator adds your username to the repository. 

Anyone can check out the code anonymously, with read-only access, by writing:

cvs -d co .

Independent of which method you used to check out the code, the following command updates your working area with the newest code (merging any modifications done by you):

cvs update -d

Known Problem

The code can not be checked out on Windows. The reason for this is that a directory in the source tree is called "con", which is not allowed in Windows. If it is important for you to be able to check out on Windows, this can probably be fixed.


Instructions on how to build DeeDS are found in a number of README-files that are located in the root of the DeeDS source tree.

Coding Conventions

  • Do not use tab characters at all. Use space characters instead. In most editors it is possible to configure it to insert space characters instead of tab characters. An indentation level of two space characters is recommended.
  • Use camel style naming for identifiers. Type names should begin with a large character and function and variable names should begin with a small character (e.g. MyClass, myMemberFunction). Preprocessor macros should be written in all caps (e.g. MY_MACRO).

Bug Tracking

Whenever a bug is found or when needed functionality is missing, a change request should be submitted. In the DeeDS project, a bug-tracking system called JitterBug is used for this. JitterBug has a web-based interface which can be reached at Anyone using this address will be logged in as guest, which allows the user to view and submit change requests. To be able to move or add comments to existing change requests, an account is needed and the address should be used instead.

Change requests are grouped in different directories. When a new change request is submitted, it is placed in the directory “incoming”. The change request can later be moved to another directory by someone with proper privileges. When the requested changes have been realized, the change request should be moved to the directory “fixed”.

When a change request has been submitted it will obtain a unique number. To later refer to this change request, an identifier with the form “DeeDS-CR*” is used, where * is the unique number. We refer to this identifier as a "change request identifier".


Uppdaterad: 2008-11-27
Sidansvarig: DRTS-gruppen