| Re: Version control for IDL software [message #46430 is a reply to message #46302] |
Mon, 21 November 2005 10:49   |
JD Smith
Messages: 850
Registered: December 1999
|
Senior Member |
|
|
On Mon, 21 Nov 2005 17:48:02 +0100, Ben Panter wrote:
> Richard G. French wrote:
>
>> I'd appreciate hearing from UNIX folks about the relative merits of CVS
>> and RCS, or other approaches, to keeping track of versions of procedures
>> and functions that are called from other IDL routines, or if this is
>> even possible within the CVS/RCS paradigm.
>
> Just to add to the others singing the praises of CVS, it's great - even if
> you're not working in a team environment. Versioning and forcing myself to
> comment versions on a spiralling-out-of-control code base has helped me
> immensely.
>
> JD said a while ago that IDLWAVE can use the emacs CVS functions, but I
> tend to use eclipse - which looks exactly the same on my unix, linux and
> windows boxes. For a processor farm there is the script-friendly unix
> command line version.
Yep, but in fact it's just Emacs which interfaces to CVS via its VC
mode. It also interfaces to RCS, subversion, arch, and others, so
really you can use any of them. I use CVS and am relatively happy
with it. I especially like the color-coded "anotate" mode, which
shows who last modified which line when (Emacs 22 will improve this as
well). My most used command is C-x v =, which shows the differences
between the current and checked in versions of a file.
The only drawback to CVS (which is widely known, and part of the
impetus for developing new tools like Subversion) is that changing the
name of or relocating files is somewhat awkward. I can recommend this
free introductory book to CVS:
http://cvsbook.red-bean.com/cvsbook.html
JD
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
