>>>>> "Donald" == Donald Sharp <[EMAIL PROTECTED]> writes:
> What you are looking for is the modules file. Split your
> project up into multiple modules. Each module being something
> you want to restrict access to. Within the CVSROOT/modules file
> use the -o <program> to specify what program to run to prevent
> checkout.
One drawback here is that the modules file can be bypassed by full
path specifications, etc. The checkoutinfo trigger could not be
bypassed.
> donald On Wed, May 03, 2000 at 02:22:46PM -0600, Erik Kluzek
> wrote:
>> Is there any interest in CVS having a "checkoutinfo"
>> administration file? This would be similar to "commitinfo" as
>> it would run a script before files are checked out. This way
>> checkout could limit the versions checked out or restrict
>> access to branches etcetera. There are various things I could
>> see doing with a "checkout" script. I'm just checking if anyone
>> else thinks this might be good or not...
Mike Sutton | public class
SAIC | software_failure : management_failure
Beavercreek, OH |
[EMAIL PROTECTED] | These are MY opinions, not SAIC's
