Re: setting up a cvs repository
-- Derrick 'dman' Hudson <email@example.com> wrote
(on Monday, 09 December 2002, 11:52 PM -0500):
> On Mon, Dec 09, 2002 at 06:09:04PM -0500, Michael P. Soulier wrote:
> | On 09/12/02 Derrick 'dman' Hudson did speaketh:
> | > Ok, what is the right way to set up a CVS repository?
> | >
> | > The problem is that new files created with 'cvs add ; cvs com' are not
> | > group writable. They need to be group writable so other developers in
> | > the group can modify them later. If I manually set the writable bit
> | > then everything is fine. (manually means logging on to the server
> | > with the repository and running 'chmod' on the ,v file) How can I
> | > make the file be group writable without the need for manual
> | > intervention?
> | Try setting your CVS_UMASK environment variable appropriately.
> Thanks for the direction. It's actually CVSUMASK, and it doesn't
> achieve what I thought I wanted. cvs doesn't set the group-write bit
> in the first place, and a umask can only clear bits.
> However, after a bit more searching and reading and testing it seems
> that the ,v files /don't/ need to be group-writable; just the
> directory they are in does. (this experimenting was all with the
> 'cvs' command on my own debian system)
Try looking into debian's cvs pserver chroot jail (package cvsd). I just
did this, and you can specify default umasks both for the server in
general and for the individual projects.
Matthew Weier O'Phinney