> >> We probably could make all our workspaces share the same "cvs" > >> directory, i.e. the directory holding the clean working copies, > >> this would give us a few GB additional disk space.
We could (for the least amount of coding effort) probably have gump lock each module's root directory as it attempts an update (cvs|svn) so that we could share the download repository. Since we have this part multi-threaded (and working in back-ground threads w/ the core build thread waiting as needed) it oughtn't matter if the lock was initiated by another thread, or another process. We'd replicate the effort of cvs|svn figuring out what updates (often none) where needed, but that is no big deal. There are other approaches, but this seems easiest/cheapest within the code. BTW: If not already, could things like "stray locks" get filed into JIRA, just in case I ever do find myself spare cycles? [That, and if JIRA ever reminds me of my account information so I can go check.] regards, Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
