Download area

Both developers and end-users can obtain OSDL from at least five ways, listed in decreasing interest order:

In case of trouble, please consult our support section, where issues ought to be solved.

Our CVS nano-guide

Getting OSDL and related directly from our CVS tree

OSDL's CVS repository can be checked out through anonymous (pserver) CVS with the following instruction set.

Getting OSDL as a pure end-user

In this case, one just wants all the necessary sources and does not intend to make any change which would have to be backported to our CVS. No CVS information is needed, therefore the export command should be used. One has only to issue:

cvs export -Dtomorrow Ceylan OSDL

When prompted for a password for anonymous, simply press the Enter key.

With this method, one would have the "latest" CVS snapshot of our projects. Not so "latest" however, since Sourceforge's CVS are mirrored. Anonymously-accessed repositories have a constant offset of a few hours: data is currently synchronized between the developer CVS servers (SSH) and the anonymous CVS servers (pserver) every 5 hours. There may be a delay of up to five hours between the time a developer commits a file and when it becomes available via pserver.

Besides, end users are merely interested in stable releases, whereas our latest CVS snapshot is often in broken compile state: while we are working on a project, we iterate from a stable release to another one, but the main part of the time, between them, the work in progress does not behave well by construction. Therefore, as much as possible, we tag stable releases with their date, according to the following conventions: STABLE_yyyymmdd, like STABLE_20040227, for 2004, February 27. Thus, if one wants to retrieve from CVS the latest stable release of our project, he could:

  1. peer into our anonymous CVS on SourceForge
  2. find the lastest stable release tag (ex: STABLE_20040227)
  3. get the version corresponding to that tag, thanks to:
    cvs co -r <my found tag> <the module I target>
    for instance:
    cvs co -r STABLE_20040227 Ceylan/Ceylan-0.2
  4. he would then end up with the latest complete stable release

To have a working installation, we hereby assume that all other software OSDL's pre requesites, not depending of OSDL's project, will be available before one compiles our library (for instance, SDL should be installed prior to OSDL).

Getting OSDL as a potential developer

In this case, one wants all informations, including CVS metadata, and the checkout (co) command is to be used. One might want to select the module(s) to retrieve. A good start would be to replace in the command below modulename by Ceylan OSDL. To perform more accurate CVS retrieval, one can determine all the names of the modules created for our project, by examining our CVS repository via the provided web-based CVS repository viewer.

The module you wish to check out must be specified as the modulename. When prompted for a password for anonymous, simply press the Enter key.

To retrieve modulename from our CVS server, please enter (do not forget to substitute modulename with the name of the module you want to check out):

Just once, to start your CVS session:
cvs login
Then, for every module to retrieve:
cvs -z3 co modulename

Informations about SourceForge's CVS

Please react!

If you have information more detailed or more recent than those presented in this document, if you noticed errors, neglects or points insufficiently discussed, or if you would like to contribute and help us, even a little bit, drop us a line!


Last update: Saturday, April 11, 2009