Re: Version control for IDL software [message #46583 is a reply to message #46513] |
Mon, 28 November 2005 14:04   |
Paul Van Delst[1]
Messages: 1157 Registered: April 2002
|
Senior Member |
|
|
Craig Markwardt wrote:
> "Richard G. French" <rfrench@wellesley.edu> writes:
>
>> Thanks to Jean and Craig and others - I've now started using CVS and I'm
>> beginning to get the hang of it. I haven't yet sorted out the 'tags' part of
>> things, or freezing versions of a full set of routines, but I'm getting
>> there!
>
>
> Here's a data point for you: I've never used CVS tags or frozen
> versions in my life. I use CVS to document changes; to embed version
> info into source modules; to synchronize changes between environments;
> to clone a library to another machine, and in my "real job," to
> synchronize with multiple developers.
>
> My suggestion is for you to get used to CVS check-in/out, update and
> commit, and that will probably be all you need.
I'm not disagreeing with you, but I also don't think investigation into how to use CVS
tags should be dismissed so lightly. I think it depends greatly on how someone sets up or
uses their repository or, more likely, structures their software development. Your case is
just a single data point.
Tags can be a powerful help when he has to retrieve a particular release of software from
XX months/years ago, or he wants to patch older software (via branches) for some users. If
he never needs to do either of those things, then, yes, tags and branches may complicate
rather than simplify his life.
To Richard: the standard documentation that typically comes with CVS (the Cederqvist et al
manual) is a great resource but I've found it a bit light on examples when it comes to
doing more than the basic things. Experimentation on a dummy repository, or subdirectory
within your "regular" repository, may be helpful in that case. The CVS newsgroup is also a
trove (especially if you're prepared to search the group).
paulv
--
Paul van Delst
CIMSS @ NOAA/NCEP/EMC
|
|
|