Sorry, Mark. What I gave were directions for developer access, and none of
you had been made developers yet. I have now made you a developer so that
you can update the CVS, so please try again with the same instructions.
Anyone else who believes they may be editing or contributing Python code,
let me know and I'll make you a developer. Make sure I have your
SourceForge user ID.
For those who want to pull down the files via an anonymous login (and using
CVS), substitute in something like the following commands:
cvs -d:pserver:anonymous@... login
cvs -z3 -d:pserver:anonymous@...
You can also browse the CVS online and then right-click the "as text" link
to save a copy locally.
At 01:22 PM 12/16/2002 -0700, Mark Watson wrote:
>Everything goes OK until CVS asked for my password. Then,
>I have tried entering three different things (to no avail):
>1. my usual Sourceforge password
>2. the password emailed to me when invited to this mailing list
>3. a blank line
>On Monday, December 16, 2002, at 10:43 AM, John De Oliveira wrote:
>>I'm new to CVS, and these are the notes I made for myself concerning
>>accessing/using the python code that we just posted. Hope this is useful
>>to someone. For those of you who will be posting code, I may need to set
>>you up as developers on the OpenCyc project on SourceForge.
>># These instructions are for Linux. For Windows, the method of setting
>># environment variables will be different. "sf" means SourceForge.
>># EACH TIME:
>># set environmental variable to CVS_RSH to ssh
>># This has to happen for every new xterm that will issue CVS commands
>># related to SourceForge.
>># FIRST TIME:
>># Make a dirctory locally (in your home dir?) to keep
>># your version of the files from sf CVS.
>># You should only need to do the following once
>># Initial checkout of python code
>>cvs -z3 checkout python
>># Initial checkout of Java code (optional -- if you're interested)
>>cvs -z3 checkout org
>># AS NEEDED:
>>cvs update -d #updates local directory you're in and below and creates
>>cvs commit #commits your changes up into the sf repository; prompts for
>># After creating a file locally, do the following to add it to sf CVS tree
>>cvs add filename #do it locally, doesn't take effect until commit
>>cvs add directoryname # Same as above, but for directories
>>cvs remove filename #removes file from sf CVS tree; do after deleting
>>file locally; doesn't take effect until commit
>>cvs remove -f filename #removes file from sf CVS tree and deletes file
>>locally; change to cvs tree takes effect after commit
>-- Mark Watson, Java consultant and author
>-- http://www.markwatson.com for Free Web Books