Path: utzoo!attcan!uunet!tank!ncar!ames!mailrus!iuvax!rutgers!bellcore!tness7!petro!iquery!matt
From: matt@iquery.UUCP (Matt Reedy)
Newsgroups: comp.software-eng
Subject: Re: Version control across machines
Summary: How we manage version ctrl on multiple machines
Keywords: SCCS, porting, nightmare
Message-ID: <137@iquery.UUCP>
Date: 7 Sep 88 12:25:05 GMT
References: <832@vsi.UUCP>
Distribution: comp
Organization: Programmed Intelligence, San Antonio
Lines: 28

In article <832@vsi.UUCP>, sullivan@vsi.UUCP (Michael T Sullivan) writes:
> What I'm asking is, are there any
> references on how to keep version control between machines manageable?

This is really a sticky problem for us.  We have a horizontal application (a
report writer/data analysis tool) that runs on PC's, Unix/Xenix, and VAX/VMS.
We've been struggling for a long time trying to manage source code control.
What we currently have isn't the best but it seems to work.  Since we like
to do most of our development on PC's, each of the 5 developers has a 286 MS-
DOS machine connected via Starlan to an AT&T 3B2 server.  Starlan lets us
access the 3B2 Unix file system as remote DOS drives.  This provides for
transparency between Unix & DOS.  

We maintain the One True Source on the 3B2 and use a Make file and shell 
scripts to keep track of the date/time things were last updated on a 
particular machine.  Anytime any changes are made in one of the other env-
ironments, we update the One True Source to reflect this (with conditional
compilations, etc.)  Then as the need arises, we use the Makefile to update
the other target systems.

matt


-- 
Matthew Reedy                 UUCP: {harvard!adelie,gatech!petro}!iquery!matt
Programmed Intelligence Corp. "Lots of people without brains do alot of talking"
400 N Loop 1604 E, Suite 330  Scarecrow - "Wizard of Oz"
San Antonio, TX  78232        (512) 490 6684