Difference between revisions of "Revision Control"
Jump to navigation
Jump to search
m |
m |
||
Line 2: | Line 2: | ||
==CVS== | ==CVS== | ||
− | [18:00] <djgreen> ergh. CVS server request... seriously, I'm with Corley on this -- central CVS needed. | + | <pre>[18:00] <djgreen> ergh. CVS server request... seriously, I'm with Corley on this -- central CVS needed. |
[18:01] <macolon> central subversion I think is perhaps what you mean? | [18:01] <macolon> central subversion I think is perhaps what you mean? | ||
[18:01] <djgreen> one, both, can't tell. | [18:01] <djgreen> one, both, can't tell. | ||
Line 38: | Line 38: | ||
[09:27] *** bpcarty has left the conference. | [09:27] *** bpcarty has left the conference. | ||
[09:27] <djgreen> hmm. ok. | [09:27] <djgreen> hmm. ok. | ||
+ | </pre> |
Latest revision as of 09:30, 30 October 2006
Need instructions on CVS/Subversion at NCSU.
CVS
[18:00] <djgreen> ergh. CVS server request... seriously, I'm with Corley on this -- central CVS needed. [18:01] <macolon> central subversion I think is perhaps what you mean? [18:01] <djgreen> one, both, can't tell. [18:02] <djgreen> user says CVS, I say CVS [18:02] <djgreen> was under the impression that Subversion was just one of many CVS servers/clients [18:07] <Billy> The main stumbling block so far is delegation [18:08] <Billy> but no, subversion and cvs are different: http://en.wikipedia.org/wiki/Comparison_of_revision_control_software [18:09] <Billy> I think there is an add-able cvs setup in AFS already, and if a group needs it, they could just put the repo in a locker. [18:09] <djgreen> oh, CVS is a brandname. Didn't rezalize. [18:09] <djgreen> there is "Add cvs" ... just no docs that I've found. [18:09] <djgreen> thats what we've pointed people at in the past. [09:20] <jacorley> if you have access to a cvs client (either via add or a local cvs install) you can do cvs+ssh without the need for anyone to do anything [09:21] <djgreen> ssh tunnel to the ITD CVS server? [09:21] <jacorley> um... what? there's no server in the cvs+ssh scenario [09:21] <djgreen> sry, not a big user of CVS... the CLIENT is the one doing the revisioning? [09:22] <jacorley> basically the steps are CVS has to be in the user's path on whatever system they're logging in to [09:22] <jacorley> on the local system they're ssh'ing from, they run (assuming tcsh) [09:22] <jacorley> setenv CVS_RSH ssh [09:23] <jacorley> cvs -d :ext:username@server:/path/to/repo cvscommand [09:23] <jacorley> i.e. if I'm using ssh.ncsu.edu to access a CVS repository in AFS: [09:24] <jacorley> cvs -d :ext:jacorley@ssh.ncsu.edu:/afs/eos/lockers/admin/foo-cvs co module [09:24] *** Sherry Li has returned (). [09:24] <jacorley> no server required, access is client to filesystem, tunneled over SSH [09:25] <jacorley> although if memory serves me correctly there can be locking issues with CVS and AFS [09:25] *** Aaron Peeler went away (Away). [09:25] *** cjmuller went away (Out in the Labs). [09:25] <djgreen> hmm... and if the client is Windows -- any chance of it using the Wolfcall paths "J:"? Or ssh prefered again? [09:25] *** Rob went away (helping user, back in 5 ). [09:26] *** Josh went away. [09:27] <jacorley> if it's a path the local system has access to no ssh required [09:27] <jacorley> just cvs client and write access to path [09:27] *** bpcarty has left the conference. [09:27] <djgreen> hmm. ok.