Marcelo Saldanha wrote: > > First, from my concept of Client/Server, > I supposed there should be 2 cvs programs, sort of a Listener and a > Client. But (if I didn't get the wrong file...) there is only 1 file > (cvs.exe).
<http://www.cvshome.org/docs/manual/cvs_2.html#SEC26> > First of my problems, this cvs.exe was command-line program. If it was > the server, no problem, I can deal with command line. But for the clients > I *must* have GUI, or at least something very easy to use. According to your statements below, you already have *several* GUIs... CVS only comes in command-line form. The GUIs are just front-ends to the command-line program. > Since there's no installation, I don't know if I have to setup something > else, > or should I just setup the remote repository via this cvs.exe and starting > using it. There isn't any automatic setup, per-se. You usually only have to configure some environment variables to get it working. See the manual for more help: <http://www.cvshome.org/docs/manual/cvs.html> > I've also got many GUI's for cvs, most written in Java, like jCVS, WinCVS, > SmartCVS, TortoiseCVS, etc... but, (what the heck) they're all need CVS and > Java SDK or JRE already configurated. I've only used TortoiseCVS and WinCVS, but you can use both to configure the environment for CVS. > By the way, what are the differences between pserver and those other methods > of accessing the cvs server? <http://www.cvshome.org/docs/manual/cvs_2.html#SEC26> -Matt _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
