[Top][All Lists]

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

Re: set 1 file in repository to be read only

From: Mark D. Baushke
Subject: Re: set 1 file in repository to be read only
Date: Fri, 06 Jun 2003 13:35:52 -0700

Tumy, Brad <address@hidden> writes:

> So what it appears I would need to do using this method is have some sort of
> regular expression search for the file name that is restricted.  If this
> file name is found then it should return a non-zero exit status and the
> commit on that file will fail.
> Sounds complicated actually...maybe I am missing something.
> Easier way?

The comminfo script is called on a particular directory given as the
pattern, it is not file-based. The arguments typically passed to the
script will include the name of the file and the directory in which it
resides. Check to see if the directory matches and the name of the file
matches and exit with a non-zero return code and the commit will not be

This is sort of an abuse of the cvs system which is intended to allow
users to make changes to files they checkout of the repository...

        Good luck,
        -- Mark
> Thanks.
> Brad
> -----Original Message-----
> From: Mark D. Baushke [mailto:address@hidden
> Sent: Friday, June 06, 2003 4:03 PM
> To: Tumy, Brad
> Cc: address@hidden
> Subject: Re: set 1 file in repository to be read only 
> Tumy, Brad <address@hidden> writes:
> > This question is more for a sanity check then anything else.
> > 
> > If I want one specific file in the repository to be read-only (to all
> > developers) then I just set the permissions on that file (through OS
> > [Solaris]) to be read-only ...correct? 
> No.
> > We are developing a web-application in Cold Fusion and I want to lock down
> > the top Application.cfm file so that developers can check it out and
> include
> > it in their working directory but not be able to commit it back to the
> > repository.
> Use the commitinfo hook and have it know that particular file should
> never be allowed to be committed by normal developers. See the URL:
> for
> more information.
>       -- Mark

reply via email to

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