Re: OT: Unix Version Control
- From: Jared Still <jkstill@xxxxxxxxx>
- To: raymond.feighery@xxxxxxxxxxxxx
- Date: Fri, 8 Oct 2004 20:12:20 +0100
On Fri, 8 Oct 2004 15:03:54 +0100, Feighery, Raymond (RBS Insurance)
<raymond.feighery@xxxxxxxxxxxxx> wrote:
> I've got a bunch of SQL, ksh and perl scripts that I want to organise,
> archive and delete where obsolete. I'd like to get these into some sort of
> version control repository (rather than the .old .bkp .date etc "system"
> currently employed) and I was wondering what systems (if any) you use. SCCS?
> RCS? CVS?
>
> Recommendations/experiences/gotchas gratefully received.
>
> Ray
>
Hi Ray,
Here's a synopsiis of my experience with these tools.
I've used all three, and currently use RCS for version
control on all Perl and Oracle scripts.
SCCS: I started out using sccs, but switched to RCS
when I was able, as RCS is much more capable.
RCS: Excellent tool for version control on scripts. You
don't often need to go back to an old version, but it's nice
to have when you do. There are many other features,
such as branching, but I think those are best exploited
via CVS.
RCS files can be transported between *nix systems without
any kind of conversion, including cygwin.
They may also be used directly with the Windows version
of RCS, with the proviso that the ',v' needs to be dropped
from the suffix of the RCS file names.
CVS: This is an application level versioning system. You
don't just version files, but entire releases.
I've used it in the past for a project, but it's been awhile.
There are also nice gui interfaces for it.
I would think that if used for scripts, it might be put to
good use to control releases of scripts for different
versions of Oracle, platforms, etc.
CVS is a bit of work to setup, but could be worthwhile if
you think you need it.
HTH
--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
--
//www.freelists.org/webpage/oracle-l
Other related posts:
