Re: SV: SV: file access

[Donald Sharp]

1)  get rid of the history file.

2)  for the pserver setup, modify the CVSROOT/config file to
have:

LockDir=<some/directory/where/everyone has write access>

This should solve the problem ;)

donald
On Wed, Jan 10, 2001 at 09:37:03PM +0100, address@hidden wrote:
> ..after som thinking....
> 
> Since this applies to the CVSROOT catalog, I don't think this is possible
> since some of the files has to permit writeaccess to all users of the
> repository.
> 
> -Thomas
> 
> -----Opprinnelig melding-----
> Fra: Donald Sharp [mailto:address@hidden
> Sendt: 10. januar 2001 21:13
> Til: address@hidden
> Kopi: address@hidden; address@hidden
> Emne: Re: SV: file access
> 
> 
> Ways to get around this:
> 
> 1)  Before you edit and checkin a file do a newgrp admin.  This will
> change your group to the correct thing.
> 
> -or-
> 
> 2)  Make directories in the repository setgid to the correct group.  This
> should force all files in the directory to have the correct group.
> 
> donald
> 
> On Wed, Jan 10, 2001 at 09:06:29PM +0100, address@hidden
> wrote:
> > Correct me if I'm wrong, but if my default group is developers. But I am
> > also a member of the group admin. If I checkout and edit a file that
> belongs
> > to the group admin and check the file in to the repository again. The file
> > will not longer belong to the group admin but instead to my default group
> > developers. Is this correct behavior or is something very wrong??
> > 
> > -Thomas
> > 
> > 
> > -----Opprinnelig melding-----
> > Fra: Donald Sharp [mailto:address@hidden
> > Sendt: 10. januar 2001 19:38
> > Til: Largent, Jim
> > Kopi: 'address@hidden'
> > Emne: Re: file access
> > 
> > 
> > If you would read the documentation it clearly states the reasons why 
> > you don't add users to files for write access. 
> > 
> > Using groups is a good way to prevent write access on a per directory
> > basis, and I don't see why it wouldn't apply here.
> > 
> > donald
> > On Wed, Jan 10, 2001 at 01:26:24PM -0500, Largent, Jim wrote:
> > > I'm well versed in RCS but new to CVS.  In RCS, you can add users to
> files
> > > for write access.  Why isn't this available in CVS?  Is there a simple
> way
> > > to block write access?  All developers on the Unix box are in the same
> > > group, but there are different projects going on so using Unix groups is
> > not
> > > practical.  There's no need to block read access, just want to make sure
> > > that there is no inadvertent modifications going on.  Any thoughts?
> > > 
> > > _______________________________________________
> > > Info-cvs mailing list
> > > address@hidden
> > > http://mail.gnu.org/mailman/listinfo/info-cvs
> > 
> > _______________________________________________
> > Info-cvs mailing list
> > address@hidden
> > http://mail.gnu.org/mailman/listinfo/info-cvs