Roddie wrote: A lot of stuff that sounds pretty good. Plus: > The shared directory holds libraries and other files needed > by all the other > sites. Each site uses symlinks so that the shared files > appear to be in the > correct place for that site. As I understand it, the symlinks > should not be > part of the repository, but created manually. Not sure where you heard that, but it will cause you much more work. I use symlinks in the repository, with no problems.
You might consider using ampersand modules instead - that's what they're designed for. Have a closer look at the documentation of the modules file (in the "administrative files" section of the manual, IIRC). > Is all this correct, complete and sensible? I'm open to any advice. Other than the symlink comments above, sounds good to me. Make sure your web server knows to ignore directories named 'CVS' (I believe Apache has an option to allow you to do that). -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. ( http://www.leitch.com ) Columnist, C/C++ Users Journal ( http://www.cuj.com/experts ) _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs