> -----Original Message-----
> From: Ronald Bourret [mailto:rpbourret@...]
> Sent: 21 May 2001 22:48
> To: email@example.com
> Subject: Re: [xml-dbms] 2.0 map objects
> adam flinton wrote:
> > B) We use CVS (I use either the straight Commandline &/or
> the WinCVS GNU
> > product (which makes it all seem easier.....)
> > So.....while I have no experience with SourceForge....try
> firing em @ me.
> 1) How do you control update access? It appears that
> SourceForge grants
> everyone update access through the "anonymous" user.
I'll find out from sourceForge. We use a thing called "PServer" (password
server) which is tied in with CVS to do this. I'll find out how & what we
need to do something similar.
> 2) How is locking done? Since it appears that CVS uses the same verb
> (checkout) both to check out sources and simply to download
> them, how do
> you use the system for one developer essentially to tell another
> developer, "You can't check this out -- I'm working on it."
Ahhh... easy question. CVS = Concurrent Versioning System. i.e it actively
is built to support many people making manyu changes to the code @ once.
What you do when you "check out" the code is to build an exact image of the
directory structure on the CVS server locally. e.g. if you had
com/adam/mycode then if you designated a local folder (e.g. D:\CVS_Stuff)
checking out would create you D:\CVS_Stuff\com\adam\mycode with all the
source files in the correct folders. It allows you to store any file such
that you could include a bunch of docs in the com folder.
You can always check out ("Hotel California"? <G>). It's the writing back
bit which is where the action is....
i.e. I d/l the map object (check out). You do too. Neither you nor I know /
need to know that the other has done so. When you check it in it will go in
& when I do it will do the same however we will have different versions. We
will then need to merge / discard any clashing code.
WinCVS comes with all the Diff / merge stuff (as does Cervisa if running on
> Basically, I'd like to allow everybody to be able to download sources,
> but highly restrict who can check them out for update and
> check modified
> sources back in. Since this is such a reasonable request (it would be
> insane to grant the world update access to your code), I assume I am
> missing something obvious.
This you can do (it's what it's designed to do). I'll find out how WRT
sourceForge in a short while. The permissions can be finegrained down to the
level of a single file (e.g. I might have it set such that I could write to
just one file, a directory (package) or the whole tree).