RE: twisted CVS

[Noel Yap]

--- Brandon Brinkley <address@hidden> wrote:
> > > 1. Can CVS be made more hack-proof (e.g. owner
> > > permissions on RCS files in
> > > the CVSROOT)?
> > 
> > Depending on how much protection you want, you
> can:
> > 1. Use the usual file permissioning to prevent
> > unwanted people from reading/writing to the
> > files/repository.
> > 2. Use POSIX ACLs to prevent unwanted people from
> > reading/writing to the files/repository.
> > 3. Use SSH to force users to use CVS to access the
> > repository.
> 
> 
> Can the repository be chowned and chmoded without
> causing problems?  Also,
> do you suspect this will affect WinCVS usage in any
> way?

Read up on how CVS uses file system permissions.

The gist is that those that need to check out need to
be able to read the RCS file, read and execute
permissions to the repo directories, and write
permissions to the directories where internal locks
are created (the repo directories by default).  Those
that need checkin priveleges need read permissions on
the RCS files and rwx permissions on the repo
directories.

> > > 2. Can tags be made permanent (no deletions or
> > > reuse)?
> > 
> > I think there might be a patch out there for this.
> > OTOH, since tags reside within the RCS files,
> you'll
> > need to manage the RCS file access as well.
> 
> 
> I'll look for it.  And yes, this was one of the
> reasons I asked the first
> question.

I think the best solution would be to use SSH to
control access to the server then possibly patch CVS
so that tag creation is a priveleged command.

> > > Based on what I've read, I don't expect either
> > > exercise to be a trivial
> > > undertaking, but I'd be very interested in
> hearing
> > > success stories, ideas,
> > > possible approaches, etc.
> > 
> > It really depends on exactly what you want to do. 
> Can
> > you be a little more specific in your
> requirements?
> > Noel
> 
> 
> The big picture is that management has decided to
> improve control over the
> development lifecycle (and for those familiar with
> the analogy, shopkeepers
> from the Bazaar have been recruited to build
> Cathedrals).  I have to
> determine if CVS (already in use) is still the most
> appropriate choice based
> on the company's new goals.  Caveat: I have to
> minimize the customization to
> any tool I evaluate, so as not to cross the line
> between 'build' and 'buy'.

I think, so far, the largest part here is the patch to
control tagging.  If this isn't too much to keep CVS,
then it sounds like CVS is a go.  OTOH, it does sound
like you're very close to the line so any other
requirements may push you over the edge.

HTH,
Noel


__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com