Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!swrinde!cs.utexas.edu!uunet!apctrc!drd!ron From: ron@DRD.Com (Ron Madurski) Newsgroups: comp.lang.perl Subject: perl for SCCS Message-ID: <1990Dec7.173507.23538@DRD.Com> Date: 7 Dec 90 17:35:07 GMT Distribution: usa Organization: DRD Corporation Lines: 41 Summary:New user needs a starting point Keywords:source code control, SCCS, RCS Sender:ron@drd.com Here's my dilemna. I want to learn how to use perl. I need to set up a system to use the SCCS facility (or possibly others if one that works better and is easier to use is out there). I have never used perl, but I have been following the discussions here for a month or two. I don't expect anyone to write this stuff for me, I just want some direction, examples of using choice lists for user selection, do's and dont's of SCCS, and some help along the way if I get really stuck. We have been using SCCS as a way for the programmers here to keep from stepping on each others toes. Since we are getting ready for a major release of a new revision it would be helpful to be able to set a delta to get back to the 'pristine' version of the software (ie. delta 1.1). From there further development will continue on version 2. If bugs are found :^< we want to be able to go back to the 1.1 version and work from there with a new branch. Seems simple enough, now the nasty part (that I really want to work smoothly and figure the easiest way is to write a program to do it for me). The software rarely goes to more than one place without some sort of customization. So I want to have the original trunk to really never be touched (Except for new customers). ie.,: 1.1.1.1 Company A 1.1.2.1 Company B 1.1.3.1 Company C ... Work will always be continued on 2.x until the next major revision and at that time a comb(ine) will be done to get the deltas in line with each other again. Well, let me know what you think. Am I going to be able to do this in perl, is there a better way, will I have hair left when I finish? Thanks for your time, -- ron@DRD.Com uunet!apctrc!drd!ron