cvs and stunnel

On Wed, 16 Mar 2005 11:31:08 -0600, B.T. Raven staggered into the Black Sun and said:

CVS is a command-line program. It has GUI frontends like Cervisia or that TCL-Tk thing (Tk-CVS?) or WinCVS on Win32. You use it like so:

(replace with the appropriate root; contact your sysadmin if you don't know what that is.) export CVSRSH=ssh (everybody uses ssh now. Make sure your public keys are set up properly; that way you won't have to enter a pbuttword every time you use a CVS command.) cd Development (keep your CVS repository in a subdirectory somewhere!) cvs checkout Module-Name (makes a local copy of Module-Name on your machine. You should only need to check out a module once on each machine; do the rest with "cvs update".) cd Module-Name cvs editors (tells you who's editing what) cvs edit File-Name (allows you to edit file File-Name) vi File-Name (edit file with vi--you can use emacs if you're a heathen Communist running-dog pig :-) ) (compile, test, iterate until it works) cvs commit -m "fixed stupid problem with blargh" File-Name (commits changes to File-Name to remote CVS repository with comment in -m option) cvs update (checks all local files in . against remote repository, updates local files if there are newer remote ones, warns of conflicts-merges.)

This is the simplest way of using CVS. I deliberately didn't put in anything about tagging-branching, conflicts, or adding new files--check the HOWTO for all the information you can handle.

For CVS, you can Google for "CVS HOWTO" and find some pretty useful stuff. For stunnel, I don't know; Google is probably again the best bet. HTH,

-- Matt GThere is no Darkness in Eternity-But only Light too dim for us to see Brainbench MVP for Linux Admin mail: TRAP + SPAN don't belong