> > Yes. When you mentioned the SS GET updating the source, I > thought "How could have I missed such a rudimentary principle > of an SCC". But alas, a good couple of months ago I > investigated having a "working set" in a specified location > to improve build performance. At the time I realized the > Removes never removed from the local machine. This was why I > headed off looking to see if keeping a working set > programmatically, using the output from the history, could > allow us to delete when a Remove occurs. I dont know how the > others report updates/adds/removes - I doubt they would be consistent. >
Subversion and CVS both remove files from a working directory if they have been removed in the repository. I think the moral of the story is that VSS is not suited to modern development practices. That's about as polite as I can get. Have you tried looking at Vault? Cheers Mark ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Draconet-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/draconet-users
