If you have Linux or any other Un*x, then all you need is CVS 1.8 or better. If it's not already on your system (type cvs to find out), fetch if from one of the many GNU mirrors and install it in your $HOME.
Then get the AROS developer archive from the AmiNET and compile crypt.c (just say make crypt. Think of a good password and use crypt to encode it, like this:
> make crypt > crypt my_password Encrypting my_password: cbEVHg0j9uNRs
Now skip the next section and read on in "How get access to the AROS CVS server".
If you have an Amiga, you can participate, too. Just get the CVS from ADE, install it and get the demo for AmiTCP 4.0 (AmiTCP-demo-40.lha in comm/tcp) from AmiNET. You also must have ixemul.library 45.0 (should come with ADE) and ixnet.library in LIBS:. Then you can create your password with crypt out of the AROScrypt.lha archive from AmiNET (in dev/misc) like this:
> run amitcp:amitcp [CLI 8] > crypt my_password Encrypting my_password: cbEVHg0j9uNRs
(you must have the directory where crypt is stored in, in your path or you must do this in the same directory where crypt is). CVS doesn't work with Miami.
Miami uses a different routine for encrypting data than Un*x and therefore passwords generated with Miami won't work. Sorry.
Mail the password you have created to me: digulla@aros.fh-konstanz.de. The subject must be Access to AROS CVS Server and with this text in the mail:
Please add <my_login, eg. digulla> <password, eg. cbEVHg0j9uNRs>
Don't forget to fill in the information :-)
Wait until I confirm this. While you wait, look for CVS 1.8 or better if you haven't already done so.
Before you can use any CVS commands, you must log into the server. To do this, use the CVS command "login":
> cvs -d :pserver:user@aros.fh-konstanz.de:/home/AROS/CVS login
where user is your login, eg. digulla:
> cvs -d :pserver:digulla@aros.fh-konstanz.de:/home/AROS/CVS login
This should ask you for your password. Type it in and if there is no error displayed, you are connected. If there is an error, try to omit the ":pserver:". If this still doesn't work, double check for typos and if you really, really, really can't find anything, then you got my email.
If the login has succeeded, then you can save you some typing by storing the argument to the -d option in the environment variable CVSROOT. Use
setenv CVSROOT :pserver:user@aros.fh-konstanz.de:/home/AROS/CVS
on Amiga or if you have a C shell (csh) and
export CVSROOT=:pserver:user@aros.fh-konstanz.de:/home/AROS/CVS
for Bourne/Korn shells (bash, ksh).
On Amiga, you can make this permanent by copy env:CVSROOT envarc:, on Unix, you must add this to the shell's startup file (.cshrc, .profile, .bashrc, .tcshrc, etc. Read the manual of your shell to find out). If you don't know what kind of shell you have, just try echo $SHELL or echo $shell. This should print the name of your shell.
If you haven't set this variable, you must add -d ... right after cvs in the following examples.
Now you can use any CVS command to get a copy of all AROS sources, update your sources or commit the changes you made.
Use the CVS checkout command for this:
> cvs checkout AROS
This will create a directory AROS and populate it with all sources.
If you have some sources and just want to update them, you can use the CVS update command. Change to the AROS directory and do this:
> cvs update
This should merge any changes that other users have made into your sources and create all new directories and files. If you and someone else has changed the same file, then CVS will try to merge the changes. That is, if he changed the first part and you the end of the file, CVS will do all the work for you. If there are changes which CVS can't resolve (eg. you said x--; and the other one x=x-1;), then CVS will put both versions in the file. Search for <<<< to find such problems.
You should do this before any commit in case this happens. So before you commit, do an update, call make if any changes were made, fix the problems and then commit.
If you have changed a file, then you of course want to share your work with the other guys. To do this, use the CVS commit command:
> cvs commit
You can specify a list of files after the commit or just do that in the AROS directory to commit all changes. CVS will then ask you what you did and send the changes to the CVS server for inclusion. Before you do that, you should always make an update (see the previous section) to avoid problems.
You can also add new files or directories with the CVS add command:
> cvs add file.c
or
> cvs add dir
Note that cvs add dir/file doesn't work. You can only add files in the current directory.
Well, CVS has man pages and info files and here is a nice link.
Well, it's more a task server. Its purpose is to allow multiple people to work at the same project at the same time without any two persons doing the same work twice. This is accomplished by the jobserver. It has a database with all tasks that are still to do, tasks that are currently under construction and tasks which are finished.
Just send an EMail to
aros@aros.fh-konstanz.de
with the Subject: jobserv and in the body of the mail
help
It will list all commands that jobserv currently understands. Note that this is an automated service so the subject must match. jobserv ignores all lines in an email that it doesn't understand and stops reading at the first end or -- on a line of its own. jobserv will answer your EMails telling you what it did, what commands it did understand, which it did execute and which not and if not, why not. jobserv will also remember your EMail so others can see who added/requested/did which job - So don't worry you won't be credited for your work.
add exec00001 Write AddHeadIf the command was successful, the reply will tell you that a new job has been added to the database. If it wasn't successful, it will tell you why not (eg. because there is already a job with the same id).
show free done bymeNote that jobserv doesn't remember that you added a task if someone else allocated it. The most useful variants will be:
show freewhich shows everything that's still open and
show work bymewhich shows what jobs you did allocate and haven't finished yet.
If you have comments or suggestions, email me at digulla@aros.fh-konstanz.de . 03 Feb 1997