TWiki> DICE Web>SubversionRepository (revision 3)EditAttach

LCFG Subversion Repository

Accessing the Repository

The first thing you should do prior to actually accessing the LCFG Subversion Repository is read the subversion documentation. This is available in the Version Control with Subversion book. Note that we are using version 1.1 of Subversion.

People familiar with CVS may want to read Appendix A. Subversion for CVS Users first and use the remainder of the book for reference.

To grab a working copy of the LCFG Subversion Repository you need to check it out as follows:

bash$ svn checkout svn+ssh://
bash$ svn checkout svn+ssh://

You can also check out both directories in one command if you like - just list both the URLs above in the same svn checkout command.

It is important that this is done into a clean directory that at the very least has no existing subdirectories called ./core/ or ./live/ as the checkout will attempt to create these.

Don't Check Out The Whole Repository

Note that the above checkout does not give you a copy of the entire repository. Doing that would now be a bad idea as the repository's releases directory will grow by at least two new complete releases of DICE per week. In the repository this is manageable as each release is just stored as diffs, but if you check them all out, each release will get full copies of each file and your checkout will quickly become unmanageably large!

Users were formerly advised to check out the entire repository. Anyone who still has a checked out copy of the whole repository (the top level directory of the checkout will be called lcfg) should delete it and instead just check out the core and live directories as described above.

Repository Directory Structure

This contains most of the headers (in core/include) and all of the package files (in core/packages) for DICE. Everything in core goes into the weekly DICE releases.
This contains the network headers (in live/include). These are excluded from release management so that changes to them can go quickly to all hosts.

Important Tips For Using Subversion With The LCFG Sources

There are some very important things people need to get used to doing when using Subversion to manage the LCFG sources:

Make sure you write something meaningful in the commit comment
It doesn't matter how small the change is, write something in the commit comment when you commit. Even if it's as small as "typo" it means people know what kind of thing you did.
Get into the habit of following the Basic Work Cycle
This is very important as it ensures that you always have an up to date copy of LCFG sources before you start making changes. It is also a very good idea to use the svn status and svn diff commands on a frequent basis to keep track of what you have changed.
Take advantage of the tools provided to Examine The Repository History
Be nosey and see what other people have done. This is especially important for examining updates that you pull into your working copy when using svn update.
Use the svn commands to perform operations
Use the svn versions of the file management commands rather than the standard commands where possible. This ensures that as much history information is retained and helps when performing svn merge opertaions. The most prominent commands this applies to are:
  • svn cp rather than cp
  • svn mv rather than mv
Use the Subversion Documentation
It's actually quite good and will help you a lot!

This page is based on the earlier FC3upgrade/SubversionRepository page.

-- ChrisCooke - 07 Jul 2006

Edit | Attach | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r3 - 07 Jul 2006 - 13:08:31 - ChrisCooke
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
This Wiki uses Cookies