CSL-Tools — Tools for Linux Computer Systems Labs

We're still trying to get stuff set up, but for now you can see our Mercurial (HG) repositories here: (NOTE: They do not currently have any content, and therefore do not properly load for viewing)
http://csl-tools.sourceforge.net/cgi-bin/hg/

Our SourceForge project page is here:
http://www.sourceforge.net/projects/csl-tools/

If you're wondering how to download code from a Mercurial repository, you're probably not alone, as it was only started a month or two ago by Matt Mackall. You can find more information (and some download links) here:
http://www.selenic.com/mercurial/

Once you've got Mercurial (hg) installed, you can download the latest development version from our official repository with the following commands:

zeus:~ kyle$ mkdir csl-tools zeus:~ kyle$ cd csl-tools zeus:~/csl-tools kyle$ hg init zeus:~/csl-tools kyle$ hg pull -u $URL

The URL should be one of the repositories listed here (An "Official Repository" is likely to have more stable and/or useable code):
http://csl-tools.sourceforge.net/cgi-bin/hg/

To sync your local repository up with recent changes, just rerun the last command again. You may also try developers' private repositories hosted on SourceForge by using one of those URLs, however, those are not as well tested as the Official Repositories or are in active development and not presently expected to work.

If you're looking for help getting started developing with Mercurial and submitting patches, please read the README file that ships with Mercurial, as well as the copious "hg help" output. If you want to get started hacking on CSL-Tools, please send an email to Kyle Moffett (mrmacman_g4) or John Livingston (experiment6) at their SourceForge email addresses: <user>@sourceforge.net), they will be more than happy to assist (if they aren't too busy with school-work :-D).

We'll try to get this page looking a little better as soon as we can, but we're a little busy working on other things at the moment. Maybe we'll even find time to put the code in repository, and do an actual file-release, too, and (if we're feeling really productive) write an install-script!

Cheers,
Kyle Moffett

 

Courteously hosted by: