[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

cvs not ignoring permissions

From: Paul Shields
Subject: cvs not ignoring permissions
Date: Wed, 30 Jul 2003 11:11:17 -0400

Some of you may not think this is a bug; but currently this mis-feature is 
interfering with my use of cvs when the working directory is shared among 
several developers.

I am running a cvs 1.11.6 client on a debian linux. The working files are 
checked out from a repository on another host, (using cvs over ssh). 
When you commit a file, it seems that cvs removes the group write permission, 
on the working file.!  This seems to happen even if my umask is 002. This is an 
error. I don't care what permission gets removed in the repository, I just want 
to continue sharing the working file with the other developers.

Please fix the cvs command so that a commit will actually ignore the group 
I know about PreservePermissions, but it's not what I want.  I understand from 
the manual, as follows:
        In normal circumstances, CVS works only with regular files. Every file 
in a project is assumed to be persistent; it must be possible to open, read and 
close them; and so on. CVS also ignores file permissions and ownerships, 
leaving such issues to be resolved by the developer at installation time. In 
other words, it is not possible to "check in" a device into a repository; if 
the device file cannot be opened, CVS will refuse to handle it. Files also lose 
their ownerships and permissions during repository transactions.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]