LCFG Subversion Repository

This Page Is Now OBSOLETE!

This page is now obsolete. It has been superseded by the SubversionRepository page on the DICE wiki.

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 Subverison 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://

It is important that this is done into into a clean directory that at the very least has no existing subdirectory called ./lcfg/ as the checkout will attempt to create an ./lcfg/ subdirectory.

Repository Directory Structure

The top level directory structure of the LCFG Subversion Repository is as follows:

  • ./lcfg/README - Repository navigation overview.
  • ./lcfg/Makefile - Placeholder for future client side tasks, e.g. pre commit source checking.
  • ./lcfg/doc/ - Documentation that is useful to have within the repository itself.
  • ./lcfg/core/ - This is the main directory for the new release controlled LCFG header material. More information on the arrangement of files within this directory is available in the RearrangedHeaders and ReleaseManagement topics.
  • ./lcfg/legacy/ - A copy of the legacy, rfe managed LCFG source material. This is only for transition purposes. I don't think there needs to be much (if anything) in here once we are done transfering to the new structure. This is further explained in RearrangedHeaders and in the README file.
  • /lcfg/profiles/ - This allows profiles to be managed via subversion; it is used only for non-DICE hosts. DICE hosts profiles should continue to be edited using rfe.

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!

-- CarwynEdwards - 22 Jun 2005

-- AlastairScobie - 22 Jun 2005

-- ChrisCooke - 01 Dec 2005

Topic revision: r10 - 07 Feb 2022 - 15:30:14 - ChrisCooke
FC3upgrade.SubversionRepository moved from FC3upgrade.SubverisonRepository on 15 Apr 2005 - 16:20 by CarwynEdwards - put it back
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