Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'source code?' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
source code?
Authored by: semios on Apr 21, '03 05:41:42PM

Looks like you have to use cvs to play with it. Don't worry, it's easy. Here's how:


$ cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/iterm 
login
$ cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/
iterm co iTerm


[ Reply to This | # ]
source code?
Authored by: martinx on Apr 22, '03 09:52:12AM

Thanks! that was (almost) painless. The way the text got posted I
almost didn't realize that the wrapped lines were supposed to be part of
their preceding lines.

Anyways, my main complaint against CVS only access is that it makes it
a bit harder to figure out which version of the source code you have. (for
example, is it 0.6.5? Or is it newer than that, possibly with newly added
bugs?)



[ Reply to This | # ]
source code?
Authored by: greed on Apr 22, '03 01:51:12PM

I suppose this really belongs as a separate hint, but what the heck.

Once you have something checked out with CVS, you can find out what versions are available. Examine an "important" file, like "README", "configure", "Makefile" or "Makefile.in". It just has to be a file that is likely to have been around for a while.

Now do:
cvs status -v README

This will show the "tags" available on that file. Now you can re-set your code to a named tag by doing:
cvs update -rTAGNAME

If you knew the tag name in advance, you could have used "-rTAGNAME" on the "cvs co" command instead. You can usually find the tags in the web interface, in one of the log or history displays.



[ Reply to This | # ]