+ +

+ i-scream CVS Repository +

+ The i-scream CVS Repository contains all code, + documentation, and other files pertaining to all i-scream + projects. +

+ All code available in the CVS Repository is + licensed under the GPL. +

+ Web Access +

+ We use viewcvs + to provide a visual frontend to the CVS Repository. It + allows you to browse around the repository, viewing any + version of a file, and the differences between different + versions. There is also a link to download the latest + version of any section. +

+ http://cvs.i-scream.org/ +

+ We also have a facility to allow people to keep tabs on + what's changed recently. The following are available: +

+ Commits today: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=today
+ Commits this week: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=thisweek
+ Commits in the past 7 days: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=days&days=7
+ Commits made since 29/03/2001: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=since&date=2001/03/29 +

+ Anonymous CVS Access (read-only) +

+ Anyone can access the i-scream CVS repository in anonymous + mode read-only mode. The following commands will allow you + to check out a portion of the CVS repository. To see what + is available it is recommended that you first look at the + web frontend. +

+cvs -d :pserver:anonymous@cvs.i-scream.org:/cvs/i-scream login
+cvs -d :pserver:anonymous@cvs.i-scream.org:/cvs/i-scream checkout [module]
+

+ When asked for a password, simply press enter. Replace + [module] with the section you wish to checkout. +

+ Developer CVS Access (write) +

+ The i-scream development team have full write access to the + CVS repository. This is only available over SSH, and can be + done on most clients. First the following environment + variables need to be set. +

+CVS_RSH = ssh
+CVSROOT = :ext:username@cvs.i-scream.org:/cvs/i-scream
+

+ You should know your username and password already. After + setting these you will need to enter your password each + time you use a CVS command. Obviously this is a time + wasting event, so an RSA key can be generated and placed on + the server for you. Please view the relevant ssh manpages + on how to generate an RSA key pair. +

+ After this you will be able to work with CVS as normal. +

+ Other means of accessing CVS +

+ We currently provide CVSup + access to the repository, either for mirroring or for + maintaining an up-to-date local copy. You will probably + want to create a supfile that looks something like this; +

+*default host=cvsup.i-scream.org
+*default base=/home/user/sup
+*default prefix=/home/user/i-scream
+*default release=cvs
+*default delete use-rel-suffix
+*default compress
+i-scream.cms.source tag=.
+

+ The last item in that list is the collection you which to + get. The collection "i-scream" is simply the whole + repository, and is best used with no tag specified for + mirroring. It is most likely that you will want to do that + given above, which gets the latest copy of the i-scream + source code. +

+ CVS Statistics +

+ There are some statistics available on the cms module + of the CVS repository, generated by + cvsplot, + that allow you to see the progress of development. + They're not that exciting, but do show when the work + was done. +

+ http://www.i-scream.org/cvsplot/ +

+ +