[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Triggers on update and checkout
From: |
Maarten de Boer |
Subject: |
Triggers on update and checkout |
Date: |
Thu, 10 Jun 2004 13:31:28 +0200 |
Hello,
I am looking for patch that would add *info-style triggers on checkout,
update and export, similar to how commitinfo works on commits. The idea
would be to have a checkoutinfo file. I found some messages on this
subject way back in the list archives, but nothing concrete...
I want to use this to have more fine-grained (more fine-grained than
unix-permissions) control over who can checkout specific modules or
even branches. We use a similar mechanism to control who can commit
on a specific branch with commitinfo.
The alternative would be add ACLs to CVS, like the
cvsacl.sourceforge.net project, but I think a trigger-based solution
would be a lot less intrusive in the CVS code, and could be more easily
kept up-to-date with CVS itself. I think many of you will agree that
complex ACLs do not belong in CVS, but would approve of a "checkoutinfo"
based solution.
If no such patch exists, could you please tell me if such functionality
is planned, or where in the source it could be added?
FYI, I run cvs inside a chroot jail, and through ssh.
Maarten
- Triggers on update and checkout,
Maarten de Boer <=