| Re: Version control for IDL software [message #46428 is a reply to message #46302] |
Mon, 21 November 2005 11:13   |
Michael Wallace
Messages: 409
Registered: December 2003
|
Senior Member |
|
|
Like everyone else, I'll recommend CVS. I've been using it for a while,
and it is especially powerful when you use the advanced features of
tagging and branching. While that level of version control might seem
overkill, tagging is a great way to keep your "freezes" frozen. That
is, one of your needs is to make sure that everything works well with
everything else. When you reach that point, you can create a tag for
your files/revisions. You can now work towards the next version, but
it's really easy to just pull one of your previous tags. So, people who
need a specific version of the files can get that, but others can
continue development.
> 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 am a fan of Subversion, but because it is newer, there aren't as many
tools that have it integrated in by default. If you're just going to
use it on the command line, this isn't an issue.
-Mike
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
