Home
Support
Get the SDK
|
|
 Amiga Inc. Faq-O-Matic : Amiga SDK FAQ :
Information about the CVS server at amiga.com |
Amiga has setup a CVS server so Amiga developers can exchange source code and develop software together and concurrently all over the world. For more information on CVS, see http://cvshome.org/.
Beginners can just follow the link "Click here if you're new to CVS" on the CVS homepage (http://cvshome.org/). Another very good resource for CVS information is CVS Bubbles at http://www.loria.fr/~molli/cvs-index.html. This site also offers a FAQ-O-Matic like this one where all your CVS problems are explained
To access the CVS server as read-only so that you can build your own binaries, simply point your CVS client at
:pserver:anon@amiga.com/usr/local/cvs
No password is required for read-only access. To see what is on the server already, browse to http://www.amigadev.net/cvs/.
At a later date, CVS access will be automated via a web interface where you can apply for a username/password but until then, those who want to actively participate in cvs-controlled ports, please send a PGP encrypted username and password to rakey@cnetbbs.net and he will set up a CVS account for you. His public key is attached below. When you have your own account, replace the string "anon" by your CVS login in the pserver-string above.
Type Bits/KeyID Date User ID
pub 1024/B285C3D9 2000/06/01 Ray A. Akey
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.3ia
mQCNAzk1rWwAAAEEAKYb/CXTPlq5wD93eVUTps7xB8TQOr6ztqGPejJBxZDAFkTb
t4LjnnL5I6itunI5Lgq9FcU6+ie5kSy3kJv1gRmN2WenqkpljntA+VbLFq4GQ3Q9
AGB5SYZw1RgUWA49QDZhpwZAC77XD/9oMAJjCAf8b4gHddE0VLZAVCeyhcPZAAUR
tB9SYXkgQS4gQWtleSA8cmFrZXlAY25ldGJicy5uZXQ+iQCVAwUQOTWtbbZAVCey
hcPZAQFyZwP/Y6TCgFUI7C6L2RRYIdxfwORy5fKBLAjtuWMTf0LUAlWEqs2fgGnE
TNJu6YJ7l+U7y1Sn/pEK9dERVaFLq+xYva/BONSh7ty2GQOQ95+er1PqmJrF8Pd8
Y4YYyW501hPNF3WOCajRyDR0CwBN8upi0K2yqhjFl3ZkoFVJz11fuN0=
=vpRo
-----END PGP PUBLIC KEY BLOCK-----
|
Here is a short example how to create a new repository for some software (say, GNU patch version 2.5-2). You must use the CVS import command for this:
cvs -d CVSROOT import -m "message" name company revisiontag
Replace CVSROOT by your CVSROOT (:pserver:yourlogin@amiga.com:/usr/local/cvs/), message should tell what you are importing ("GNU patch version 2.5-2"), name is the name of the software you import (patch), company is the "owner" of the software (FSF in this case, the Free Software Foundation) and revisiontag is a string with the software name and the version (patch_2_5_2). CVS doesn't accept anything besides A-Z, _ and numbers, so just replace all minuses and dots by an underscore. GCC 2.95.2 would become gcc_2_95_2.
You run the import command in the main directory of the software. In this example, you would run it in the directory patch-2.5/, that is in the same directory in which you also find the configure script. CVS will create a repository for you with the name name (here: patch). Then it will copy all files in the current directory and in all directories below the current one into the new repository. That's why you should not try to import your software from the directory in which the patch-2.5/ directory is: It would import this software and anything else thats in this directory. Also, when you request a copy of the new import, you would have to use patch/patch-2.5/ as path.
So now, the software is copied onto the CVS server. Now all you have to do is to ask CVS for a copy of the software so you can start your work. You need the checkout command for this. Run it in the same directory where the patch-2.5 directory is (ie. cd .. after you did the import):
cvs -d CVSROOT checkout name
will give you a copy of the repository name in the current directory.
Notes:
- You can move the copy of the repository to a different place. CVS doesn't care in which directory you keep your copy. You cannot, however, move the directories *inside* the repository around.
- You should always import an unmodified version of the sources. This way, you can do another import when the next version of the software comes out and CVS will help you to merge your changes with those made by the original authors. For this to work, there must be tags for every version (the tag is the last string in the import command). These tell CVS which version is the unmodified original, what is the next version of the software and what was changed by you.
|
| [Append to This Answer] |
address-suppressed, address-suppressed
|
This document is: http://www.amiga.com/cgi-bin/fom.cgi?file=45
|
More info on Amiga SDK