Locking or making a folder read-only

[Rez P]

In our CVS repository we have 2 main project folders:

LegacyCode
NewCode

LegacyCode is no longer being developed and I would like to freeze it or lock it and make it read-only but make it accessible for future research. Is it possible to do that and how?

Thanks

Rez
_________________________________________________________________
Your E-mail and More On-the-Go. Get Windows Live Hotmail Free.
http://clk.atdmt.com/GBL/go/201469229/direct/01/

[Todd Denniston]

Rez P wrote, On 02/08/2010 07:02 PM:
> In our CVS repository we have 2 main project folders:
>
> LegacyCode
> NewCode
>
> LegacyCode is no longer being developed and I would like to freeze it or lock it and make it read-only but make it accessible for future research. Is it possible to do that and how?
>
> Thanks
>
> Rez

from memory...
setup the LockDir directive.
set the permissions on the current LegacyCode _Directories_ as read only.
set the permissions on $LockDir/LegacyCode _Directory_ as read write by the user/groups you want to
allow reading from.
set the permissions on the current NewCode _Directories_ so that the appropriate user/groups can
read & write them.
set the permissions on $LockDir/NewCodeDirectory_ as read write by the user/groups you want to allow
reading from.
http://ximbiot.com/cvs/manual/cvs-1.11.23/cvs_18.html#IDX284

--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter

[Rez P]

Great and thank you as always. I'll play around and hopefully get it working. Thanks again.

> Date: Tue, 9 Feb 2010 08:24:03 -0500
> From: ***@tsb.cranrdte.navy.mil
> To: info-***@nongnu.org
> Subject: Re: Locking or making a folder read-only
>
> Rez P wrote, On 02/08/2010 07:02 PM:
> > In our CVS repository we have 2 main project folders:
> >
> > LegacyCode
> > NewCode
> >
> > LegacyCode is no longer being developed and I would like to freeze it or lock it and make it read-only but make it accessible for future research. Is it possible to do that and how?
> >
> > Thanks
> >
> > Rez
>
> from memory...
> setup the LockDir directive.
> set the permissions on the current LegacyCode _Directories_ as read only.
> set the permissions on $LockDir/LegacyCode _Directory_ as read write by the user/groups you want to
> allow reading from.
> set the permissions on the current NewCode _Directories_ so that the appropriate user/groups can
> read & write them.
> set the permissions on $LockDir/NewCodeDirectory_ as read write by the user/groups you want to allow
> reading from.
> http://ximbiot.com/cvs/manual/cvs-1.11.23/cvs_18.html#IDX284
>
> --
> Todd Denniston
> Crane Division, Naval Surface Warfare Center (NSWC Crane)
> Harnessing the Power of Technology for the Warfighter
>
>

_________________________________________________________________
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
http://clk.atdmt.com/GBL/go/201469226/direct/01/

[Girish Kulkarni]

On Mon, 8 Feb 2010 16:02:11 -0800 Rez P wrote:
> In our CVS repository we have 2 main project folders:
>
> LegacyCode
> NewCode
>
> LegacyCode is no longer being developed and I would like to freeze it
> or lock it and make it read-only but make it accessible for future
> research. Is it possible to do that and how? Thanks

Making the corresponding subdirectory of the repository read-only using
the operating system's settings (chmod or acls on GNU/Linux, for
example) should be sufficient to give read-only access to a project.

You will then continue to be able to checkout or export, but not commit
to that project. Write access to LockDir will still be required
though.

--
Girish Kulkarni - Allahabad, India - http://athene.org.in/girish