LCFG Subversion Repository
Accessing the Repository
The first thing you should do is
look at the subversion documentation. This is available on the
Subversion website and in the
Version Control with Subversion book, which is available free online.
To grab a working copy of the LCFG Subversion Repository you need to check it out as follows:
bash$ svn checkout https://svn.lcfg.org/svn/lcfg/core
bash$ svn checkout https://svn.lcfg.org/svn/lcfg/live
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 be a
bad idea as the repository's
releases
directory grows 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!
Repository Directory Structure
-
core
- 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.
-
live
- This contains the LCFG source files (in
live/profiles
) and the live headers (in live/include
). These are excluded from release management so that changes to them can go quickly to their hosts.
Tips
- 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.
- Take advantage of the tools provided to examine a file's 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
file management commands when you want to keep the file's previous history. This mainly means:
-
svn cp
rather than cp
-
svn mv
rather than mv
- Use the Subversion documentation.
Topic revision: r7 - 05 Jan 2021 - 10:09:09 -
ChrisCooke