-2975
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tony Gravagno
Sent: Friday, September 30, 2005 3:58 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Source Code Management
I'm glad Brian stepped up with his comments below. There is a differen
I'm glad Brian stepped up with his comments below. There is a difference
between "source control" and "software management". Everyone has different
requirements so when someone says "I need source control" and everyone
chimes in with CVS, etc, it's like proposing a helicopter to someone who
needs
, September 30, 2005 10:36 AM
Subject: RE: [U2] Source Code Management
> Karen
>
> I originally used to use RCS under UniVerse with some simple verbs that
> committed items in and out of a work directory using an index file to map
> account|file|item paths to work file keys. This mean
Karen
I originally used to use RCS under UniVerse with some simple verbs that
committed items in and out of a work directory using an index file to map
account|file|item paths to work file keys. This meant that I could easily
manage items from hashed files (eg dictionaries) using some simple RCSPU
We use CVS here. All file size info, dictionaries, VOC pointers, and other
source code are checked into CVS. Artifacts that can be generated from
source code are left out.
TortoiseCVS is a windows client for CVS that makes it easy to look thru the
scc library. If I had to do it all over again,
How are you using SCCS / CVS with U2 and hashed files? Or are you just
tracking BP source code?
>SCCS, CVS and RCS are all reasonable code management packages that are
cheap or free. There are
>many others which have a larger price tag, but often have more
functionality.
>We use sccs and cvs.
Check out PRC from Susan J. Gave us outstanding and easy control of
software movement/versioning. Was on a AIX with Universe.
Ron Bertrand
ISD/LIS
Group Health Coop
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, Septembe
> What tool are you using for source code management? What are its
> benefits and disadvantages? I'm specifically interested in version
> controlpreferably Unix-based. If you have vendor information, please
> provide that as well.
>
> In a previous life, I used something called sccs - I don't k
We created our own source code management routines.
Complete with string search in programs and dictionaries,
master program file, master dictionary file and dictionary
editor, moving of source code programs and dictionaries
from a developer account to a tester account, back to the
main source dire
