next message in archive
next message in thread
previous message in archive
Index of Subjects
RCS seems to cause occasional problems for FTP and online users alike. * online users occasionally get bumped off, and unless they re-edit to reliquesh the lock, other editors can't edit * FTP users often download the entire tree, including the RCS directory, which causes massive headaches * in a multi-editor site, one editor might download all files in the site, thereby locking them against other editors, even if they only mean to work on one or two files * in a single-editor site, RCS is useless since we've never developed a user interface to support user access to it. RCS is great for version control of Chebucto scripts and documents, but most IPs will never know about it until it gets in the way. * in a multi-editor site, RCS is only useful for locking, which IMHO isn't that much of a problem: if two editors edit a file at the same time, the latest save will win regardless * RCS takes up a lot of space (50 megs between NSChess and FSCNS alone) I'm thinking we can just modify the editing and IP-FTP scripts not to use RCS if an RCS directory doesn't already exist. That way new IPs won't have RCS, and we can slowly phase it out where it isn't needed, and keep it where it's useful (Chebucto stuff). Comments? Michael -------------------------------------------------------------------------- Michael Smith michael@csuite.ns.ca Director of information warfare Pager: 458-5699 Chebucto Community Net http://www.chebucto.ns.ca/~aa529/ ==========================================================================
next message in archive
next message in thread
previous message in archive
Index of Subjects