Re: [RFC-CLI] changes from 1.1 -> 1.2

[Derek Robert Price]

Alexey Mahotkin wrote:

> As per Corey's comments:
>
> Index: acl-cli.txt
> ===================================================================
> RCS file: /cvsroot/cvs-nserver/cvs-nserver/www/Attic/acl-cli.txt,v
> retrieving revision 1.1.2.1
> diff -u -r1.1.2.1 acl-cli.txt

What would you think of considering a slightly more generic solution?

First of all, I am working with another developer on a generic XML-RPC
interface for CVS to an external auth/log server.  What this would mean is
that CVS would provide a pre and post action notification for all actions
(tag, commit, checkout, etc.) with as much data as possible to an external
program which could then return "allow", "skip", or "die" for each
individual action and file, as well as any error text to send the user.

The current functionality of the *info suite could be duplicated using
this interface and this auth/log program distributed with CVS for
backwards compatibility, but then only this module (the auth/log program)
would need to be replaced to add something like your ACL functionality.

This simple interface doesn't allow for your new client commands, but it
seems to me that some sort of generic client/server script interface,
where the arguments from unrecognized commands are simply passed on to the
XML-RPC server or via some sort of map admin file interface might be
plausible.

Anyway, much of the code for this is already written, but isn't quite
generic enough and hasn't been hooked into all the locations I'd like to
see it hooked into.  Backwards compatibility is also currently being
achieved by executing the old code when a command line option specifiying
the auth/log program isn't specified, so this will need to be worked on.

I can forward the XML specification, but I should probably finish
reworking it first.

Derek