Re: set 1 file in repository to be read only

[Mark D. Baushke]

Tumy, Brad <address@hidden> writes:

> >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...
> 
> Is there a better to do this?

I am not able to think of any better way to do this.

> I want each developer to be able to have the entire project on their local
> machines so that they can test from their local install of Apache and Cold
> Fusion.  I don't want them to be able to overwrite this particular file
> though.

So, you want them to checkout the entire module or set of modules. Fine,
they can do that using cvs. If you want them to not be able to commit a
particular file, you need to instrument it with the hooks available. If
the cvs tool does not do what you need, then do not use it.

In any case, your developers could make local modifications of the file
that they do not checking to the system. Nothing prevents that at all.

Do you really have such a low opinion of your staff? Perhaps it is time
to either encourage management to hire new staff (may folks seem to be
looking for jobs in the current market), or perhaps you should consider
finding a place of employement where you can trust the staff around you
to do the right thing.

        Good luck,
        -- Mark

> Thanks,
> Brad
> 
> -----Original Message-----
> From: Mark D. Baushke [mailto:address@hidden
> Sent: Friday, June 06, 2003 4:36 PM
> To: Tumy, Brad
> Cc: address@hidden
> Subject: Re: set 1 file in repository to be read only 
> 
> 
> 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
> allowed.
> 
> 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:
> > http://www.cvshome.org/docs/manual/cvs-1.12.1/cvs_18.html#SEC167 for
> > more information.
> > 
> >     -- Mark