Date: Fri, 16 Oct 1998 14:51:05 -0700
Reply-To: "Self, Karsten" <kself@VISA.COM>
Sender: "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From: "Self, Karsten" <kself@VISA.COM>
Subject: Re: SAS and version control systems
I've used RCS in small workgroups with good success. There are more
comprehensive tools including CVS and BitKeeper
(http://www.bitmover.com/bitkeeper/), all of which are freely available.
Most of these are command-line based systems, which works fine for me.
There are a number of products (mostly proprietary) which provide a GUI
My suggestion is to stick with a system based on RCS or SCCS for portability
and open access. There are a number of books available on the subject,
include "Applying RCS and SCCS" by O'Reilly, and one from Hewlett-Packard
whose title slips my mind at the moment. Email me at email@example.com
and I'll dig it up for you.
Version control is best applied to source code and possible program logs.
For datasets, databases, and most large binary structures, I prefer
alternate versioning or recovery methods (data regeneration, backups, RDBMS
Karsten M. Self (firstname.lastname@example.org)
What part of "Gestalt" don't you understand?
> From: Brucken, Nancy[SMTP:Nancy.Brucken@wl.com]
> Sent: Friday, October 16, 1998 11:57 AM
> To: SAS-L@UGA.CC.UGA.EDU
> Subject: SAS and version control systems
> Has anyone had experience using SAS and some sort of
> commercially-available version control system for tracking changes to
> programs, macros and/or databases under either Windows NT 4.0 or HP-UX?
> If so, what version control package have you used, and how well has it
> worked for you? We've just started looking into purchasing a version
> control system, and an initial search has turned up at least 20
> different packages, so we're trying to narrow things down before doing a
> more detailed evaluation.
> Nancy Brucken
> Parke-Davis, QIP
> (734) 622-5767
> Internet address: Nancy.Brucken@wl.com