* Dermot McCluskey <[EMAIL PROTECTED]> [2006-04-13 10:52]: > Stephen, > > > Does one of the existing hooks do what you want with respect to > > committers/branches? > > > The template pre-commit hook script, which calls > commit-access-control.pl, which in turn reads > commit-access-control.cfg, seems to work very well. I'd be > happy to have a go at converting it to Python, if that would > help? It would. (I had thought benr would have popped into this apparently pro-Python thread by now.)
The reason I am trying to contain this problem is because of the likelihood that the hook scripts will require database access in the future. My intention is to minimize the number of per-language MySQL access libraries we have to track to deploy a service. Given the amount of Python we've effectively got in place, this choice I hope balances go-fast against number-of-versions. (I know, I wrote "go fast" about opensolaris.org--snicker, snicker.) > >>The important point for me is how easily can I update the > >>configuration file that defines the access control rules. If it can > >>be done with a COMMIT, then great. If I need to send a request to an > >>administrator to be actioned in <1 business day, then I've got > >>problems... > > > If by problems, you mean "presented with an inconvenience", then, > > sure, I agree. > > This could be a showstopper for us. Module owners need a way > to directly change the access control (eg lockdown a branch) > and have this take effect immediately, without involving third > parties. So: let's make this work, but let's not have the first SCM deployment version require it. - Stephen -- Stephen Hahn, PhD Solaris Kernel Development, Sun Microsystems [EMAIL PROTECTED] http://blogs.sun.com/sch/ _______________________________________________ tools-discuss mailing list [email protected]
