Hi Gilles-Eric (french?)
The (one disk server) problem has also bothered us.
We are planing to buy some commercial products soon (continuus or clearcase)
But they are @(#* expensive! And we will stick to CVS for small projects (<20).
Clearcase solves somehow the shared file pbm at the expense of BW.
Continuus uses symlinks (at least on UNIX) and is probably less resource
consuming.
But the point is that you may add layers to CVS to emulate a cache.
In some of our teams here we use the following scheme:
- 'base' directory that holds a checkout of the last stable version of the whole
project. (belonging to an admin user)
- one shadow (see further) directory for each user wotking on this project
The shadow dir is in fact a virual copy of the 'base' directory
It reproduce the complete tree directory strucuture but populate it with
symlinks to the files in the 'base'
Thus each user own a 'shadow' copy of all the files in base (saving an enormous
amount of space)
When you edit or regenerate a file the emacs/makefile (or whatether tool you use
to change files) removes the symlink and replace it by a local copy of the
file.
Thus each user has only local copies of files he has changed.
You see the trick?
To build such a shadow copy of the 'base' we use the mkshadowdir perl script
(IIRC bundled with perl distrib)
We also have some small shell scripts to easily switch between local and shadow
copies of files
If this solution sounds interesting to you I may send you all these small
things.
Cheers
Olivier
vvvvvvvvvvvvvvvvvvvvvvvvvvv sorry for this garbage vvvvvvvvvvvvvvvvvvvvvvvv
