On Sun, 2002-11-17 at 07:25, Greg A. Woods wrote: > [ On Saturday, November 16, 2002 at 12:18:19 (+0100), Fredrik Wendt wrote: ] > > Subject: Re: Moving to Pserver from .rhosts > > > > True, but to us, there's actually only one developer, person X. > > Then why even bother with remote access via CVS? If that one developer > wants to work on files on some other host then they can easily copy them > over to it as necessary, and back again when they're done.
I'm doing single-user development with CVS at the moment, and using a remote host. (Yes, Greg, I'm using ssh.) Why CVS? For the version and revision control. Why a remote host? Because this way I automatically have two copies, in two different locations, at all times. We do also have a backup system, which backs the repository up to tape, but I'm comfortable knowing that whatever gets cvs committed is sent to a different machine, with a different hard disk, in a different building. Besides, the remote host is the one that already had a repository which was already in our backup script. :) Occasionally the right tool for the job is the one which takes least effort. But speaking of minimal effort: ssh takes, IMO, less effort to set up than correctly setting up pserver, especially if you have a package manager on the server and are running Unix or Linux. Install ssh on both machines, generate keys, set CVS_RSH to ssh, set your CVS connection method to :ext:. Done. Yes, SSH is a little more annoying to set up on Windows. I recommend recent versions of Putty. Do read the docs - you'll need to use the key generator and to set 'pageant' (putty key agent) running. Plink is the command line ssh client. Jenn V. -- "Do you ever wonder if there's a whole section of geek culture you miss out on by being a geek?" - Dancer. [EMAIL PROTECTED] http://anthill.echidna.id.au/~jenn/ _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs