The Starlink source code is held in a CVS repository, which has public readonly access.
If you have an account on the repository machine, you have read and write access to the full source set. When you are making a fresh checkout, or giving other commands not within the context of a local check-out, you should refer to it as
where username is your username on that system; you will need to set the environment variable% cvs -d :ext:username@cvs.starlink.ac.uk:/cvs <cvs-command>
CVS_RSH to
ssh to connect to the repository.There is also anonymous CVS access to the repository. Use
There is also anonymous web-based access to the repository at% cvs -d :pserver:anonymous@cvs.starlink.ac.uk:/cvs login # password starlink % cvs -d :pserver:anonymous@cvs.starlink.ac.uk:/cvs <cvs-command>
<http://cvsweb.starlink.ac.uk>. See
<http://dev.starlink.ac.uk/> for news.There are a few more details about CVS, including a link to a CVS Primer, in Section 2.7.
Part of the point of the Starlink CVS repository is to give
users ready access to the fully up-to-date sources so that
more sophisticated users can build the most recent
application versions for themselves and even, if they find a
bug, offer fixes. Anyone who finds a bug is invited to
report it through the Project's bug-reporting system at
<http://dev.starlink.ac.uk/bugzilla/>, but if this
report comes with fixes, it will be particularly
welcome.
If you do have bugfixes to offer, then you should get in
touch with the `owner' of the component to discuss how to
give them to the project. You will find the owner of a
component by looking at the file component.xml
in the component's checkout directory; this should list
those who have worked on the component, along with someone
nominated as the component's `owner'.
If you make quite a few fixes, then it might be best to give you committer access to the repository, by giving you an account on the repository machine. Talk to someone from the project about setting that up.