Rex,
[EMAIL PROTECTED] wrote:
> Greg is correct. There is currently no API included in the CVS distribution.
> There is only the command line client, which can be activated programmatically
> using the windows API (WinExec). There is also the client-server protocol
> which is documented. One could write an API, and perhaps convince the
> maintainers of CVS to include it in the contrib directory. But it is
> debatable whether anything would be gained by adding an API to the main
> codeline.
Greg is not.... It's important to have an API in cvs. The protocol is
enough for those who choosed to use it. Now we want (our users and
contributors on wincvs.org) an SCC version, a COM version, possibly
integrate it into other applications (ex. Metrowerks, VisualC++) and so
on. And the protocol is just not enough. It's just *not* reasonnable to
rewrite all the handling of the protocol for *each* client.
Look at gcvs : it uses the gimp (http://www.gimp.org) mechanism for
plug-ins in order to expose a C-API of cvs to a client (a GTK
application). A C-API for CVS makes sense. Just you don't care, that's
different.
Regards,
alex.
http://www.wincvs.org
