|
DataCore has switched from CVS to using Subversion for a source code repository.
The information below explains how to access it and use it.
This repository is:
- much easier to access from behind corporate firewalls.
- secure accessible with a browser or a Subversion client by SSL with the HTTPS protocol.
- does not need user accounts on the server to provide authorisation.
- allows for client authorisation with X509 certificates or by password over SSL.
- allows for server authentication with a X509 cerificate.
You can find more information on Subversion on the Subversion webserver.
Further help can be found in the IRC channel #svn on irc.freenode.net.
A good (and short) documentation can be found on the Zynot Wiki Subversion Documentation page.
To access the repository without warnings you must pick up DataCore GmbH's Root CA certificate.
Click on the link and the certificate will be imported into your browser.
Now set the browser's _trust level according to your needs.
To use that certificate with your Subversion client save the certificate and add the following to the "$HOME/.subversion/servers" file:
[groups]
srrd = srrd.org
[open]
ssl-authorities-file = <path/to/the/DataCore/root/ca>
There are multiple ways you can access our Subversion repository, by browser or by Subversion client. Tarballs are provided by the viewcvs Web view. You can choose a different version to download by choosing to browse a particular revision using viewcvs and then clicking the "download tarball" link at the bottom of the page.
This will give you the most (browser based) features and the best insight into the sources. It allows to view all stored revisions and to make diffs between arbitrary versions.
This will give you a simple insight into the current head revision of the repsoitory.
With the Subversion client you get the most out of our repositories. You can check out arbitrary subtrees of the repository of every stored revision in the repoitory.
There are many project directories in the root directory of the repository.
All subtrees have the same structure:
- branches/
- releases/
- tags/
- trunk/
The trunk/ is the equivalent of the HEAD revision in CVS. Directories under branches/ are equivalent to a CVS branch (Subversion uses logical copies for branches, tags and releases). The tags/ directory contains logical tags (the same as one would expect as CVS tags). These represent some sort of milestone in the main (trunk) tree. The releases/ directory contains the releases.
Because Subversion has tried to emulate CVS commands as much as possible, this is pretty intuitive for CVS users. The repository is located at the locations described above.
You find there a subdirectory for every project we host. under each project directory there are four subdirectories. The "trunk/" is the equivalent of the "HEAD" revision. Directories under "branches/" are equivalent to a CVS branch (Subversion uses logical copies for branches and tags). The "tags/" directory contains logical tags (the same as one would expect under CVS). These mostly represent some sort of milestone in the main tree. For instance, when the tree is merged with the main kernel source, we tag it.
So to check out the head, do this:
svn checkout <url from above>/srrd/trunk srrd/trunk
The trailing "srrd/trunk" argument merely creates the local copy as a directory
called "srrd/trunk" as opposed to the default of "trunk".
So to check out the SRRD project with read-only access, You would have to write:
svn checkout https://srrd.org/read-only/srrd/trunk srrd/trunk
This will create a directory srrd with a subdirectory srrd/trunk in which the project's HEAD revision source files can be found.
You do this just like with CVS:
cd <project>/trunk; svn up
It's fairly simple.
Have fun!
Go to top
|
|
This page last changed on 29-Sep-2004 23:27:01 MEST by unknown.
|
|
