Hi, [a little background, feel free to skim]
The company I have been working for have been considering moving over to a CVS based version control system for a while and I have been elected to investiate the fesability. We have a network of PHP files linked together via include / require / require_once etc inside the source tree in a multitude of directories. A sample tree structure might be something like: + Project Base files | +-- Core Handlers (mysql, sessions, authentication, security etc) +-- Data Handlers (abstraction layer between project and various db models) +-- General Functionality (smtp / nntp / imap abstract classes as well as custom functions for things like data conversion) +-- Output Handlers (conversion modules for things like outputting stuff in XML / HTML / XHTML / UML / CSV / even some things as word documents etc) [ stop skimming here ] Because these files are stored in the CVS repository, if I was to check out (for example) an XML output handler and make some modifications to the encoding types ... how would I test my changes before commital? (I obviously wouldnt want to break the repository files) As these files need to be executed via a web browser, I can only think I would have to check out *all* the files, and then point my webserver at my local directory. Then I only check back in the ones I change, releasing the others. This is not too bad if Im on my own but when multiple people are working on the same tree together there will be locks all over the place as CVS wont know which file I am working on. It will just know Ive checked out all the files. Ideas and Samples of how other people have broached this issue are most welcome. Please include my email address in the reply and remove the [PHP] tag from the subject. Thanks -- Dan Hardiker [[EMAIL PROTECTED]] ADAM Software & Systems Engineer First Creative Ltd -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
