I've wondered about this too. Mainly, if you have multiple developers working with the same web server, how would you test your scripts without running into each other? it seems like CVS would work well if everyone was developing on his/her own box.
Nate > -----Original Message----- > From: Hsiao, Chang-Ping [mailto:CHsiao@;corp.untd.com] > Sent: Wednesday, October 30, 2002 4:29 PM > To: 'Richard Clarke'; [EMAIL PROTECTED] > Subject: RE: [OTish] Version Control? > > > CVS is easy to use but confusing at first. > Once you get used to it, you should not complain. > > I don't quite get your saying "I don't however feel that the > organizational > logic of a websites code base fits well into the CVS paradigm." > Isn't your > files hierarchical? If so, why is CVS not fitting your purpose? > > Chang-Ping Hsiao > > -----Original Message----- > From: Richard Clarke [mailto:ric@;likewhoa.com] > Sent: Wednesday, October 30, 2002 1:09 PM > To: [EMAIL PROTECTED] > Subject: [OTish] Version Control? > > > Does anyone in the list use any kind of version control (e.g. CVS) for > the perl/template codebase of their website? > Now that my code base is growing I feel the increasing need to provide > better version/backup control than my current hourly crontab tar. > I don't however feel that the organizational logic of a websites code > base fits well into the CVS paradigm. Am I being to short sighted in > this assumption? > Does anyone have any recommended method? I don't use version numbers at > all? Does anyone? > > Richard. > > > . > >
