Sorry, I've been offline and missed this thread. I could have saved you some time. These are the instructions we've used at ReportLab to work with SourceForge on Win32. No problems so far despite several Unix and CVS newbies, myself included. They are adapted from an article by Jay Andrew Kay somewhere on Sourceforge and are generic rather than specific to the Python source. I have used the ReportLab project and my user name as an example but I'm sure you guys can adapt that.... 1. Get ftp.reportlab.com/tools/cvs-1.10-win.zip and ftp.reportlab.com/tools/ssh-1.2.14-win32bin.zip (copied from somewhere obscure for safety, I forget where) 2. Unzip these to a location on your path. Type 'cvs' or 'shh' from somewhere else to verify. 3. Choose where to keep your CVS projects; let's assume C:\code 4. Create a subdirectory c:\code\.ssh (yes, dot-ssh) 5. Create two environment variables: HOME=C:\CODE CVS_RSH=SSH On Win9x, this can be done in a batch file or autoexec.bat; on NT or 2000, go to Control Panel | System | Environment and set them at either user or machine level. The first must point to the directory above your .ssh directory. 6. If not done so, get a Sourceforge account and a project you can log in to. 7. Test SSH independently by doing SSH -l username myproject.sourceforge.net It should prompt for a password, then tell you that "myproject.sourceforge.net" is added to the list of known hosts; then give you a shell. 8. You will need either a lengthy command line or a batch file for each sourceforge project. I set cvsroot in a batch file in my 'c:\code' directory, and have one such file for each CVS project I use (about ten of them!): ------cvsreportlab.bat-------------- set HOME=C:\CODE set CVS_RSH=SSH set CVSROOT=:ext:my_user_name@cvs.myproject.sourceforge.net:/cvsroot/dirname --------------------------------------- 'dirname' is the top level directory in the CVS tree; a project can have several, but usually there is just one. 9. execute this batch file. You can now go to C:\Code and do cvs -z7 checkout myproject (z7 means 'compress network traffic', handy over dialup lines) 10. From now on, just use CVS normally. I wouldn't survive without Karl Fogel's book "Open Source Development with CVS", Coriolis Press. Footnote: for anonymous checkout, I think you just omit the 'my_user_name@' part from the CVSROOT variable. I hope this helps; let me know if people have any problems with the instructions. - Andy Robinson ReportLab
[Andy Robinson]
Sorry, I've been offline and missed this thread. I could have saved you some time. These are the instructions we've used at ReportLab to work with SourceForge on Win32. No problems so far despite several Unix and CVS newbies, myself included. ...
Thanks, Andy! I just *knew* that if I sat on my ass, someone would solve this one for me <wink>. I'll give these instructions a try, and also see what it takes to adapt them to wincvs. Note that I'm going to be putting similar (perhaps, by an amazing coincidence, even identical) instructions up on pythonlabs.com, so if you want to stop maintaining this, dump it on me.
participants (2)
-
Andy Robinson
-
Tim Peters