On Fri, 14 Apr 2000, Gilles-Eric Descamps wrote:
> Hi all,
>
> Is there a way to configure CVS to work by default in
> a read-only workspaces with concurrent edit:
> [...]
> By default each file is checked-out as read-only. The data
> of the file goes into some kind of shared cache, and
> the programmer's workspace is only populated with
> links to that file. By that way we would use only 1x the disk space.
> Of course, upon editing one file, the link is suppressed
> and replaced by a copy of the file, and several developers
> can work concurrently on the same file.
> [...]
I'm not sure if I understand your problem right, but maybe this helps.
CVS allows to maintain a checked out copy of the latest version in the
repository via a loginfo script. Look at chapter C.7.2 of the Cederqvist
Manual: Keeping a checked out copy. Every developer only needs to check
out the files (s)he wants to modify. The only thing you have to do is to
configure your development tools so that they search for the files in that
directory of they are not found in the developers working directory.
With a more sophisticated script it should be possible to maintain copies
of branches, too.
Lars
-------------------------------------------------------------------
aerodata Flugmesstechnik GmbH Email [EMAIL PROTECTED]
Lars-Christian Schulze WWW www.aerodata.de
Hermann-Blenk-Str. 36 Voice +49 531 2359-188
D-38108 Braunschweig Fax +49 531 2359-158
