Integrating with TortoiseCVS and CVSNT server?

[miggl]

I appologize if this question has already been raised, but I couldn't find an answer to it:

How do I integrate TortoiseCVS and CVSNT into Code:Blocks? The SVN plugin doesn't seem to work right, since I don't have SVN installed.

Thanks for any help you guys can send my way

[David Perfors]

I don't think it is possible yet. unless someone is willing to "hack" the svn plugin to work with cvs correctly. I think you have to wait till the svn plugin is corrected so it can be used with cvs to.

[thomas]

The SVN plugin used to work reasonably well with CVS back in the old days, although CVS support was always a secondary priority. In fact, the additional code to support CVS was what effectively made the project nearly unmaintainable.

I haven't been working on that plugin for about 2-3 months now, been busy with Code::Blocks core during that time. The next (long awaited) release of the SVN plugin will only support Subversion, and everything related to CVS will be made into a separate, independent module after that.

CVS will always be secondary to me, as more and more projects are moving to Subversion which is a lot better anyway. If you can't wait and need CVS support now, feel welcome to make a plugin of your own (but please let me know, so we don't do the same work twice).

[David Perfors]

Thomas. is it possible to use the svn plugin as base for the cvs plugin? A lot of things looks the same for both cvs and svn (only the commands are diffrent... as far as I know...)

[takeshimiya]

Have a base class:

Common
    SVN
    CVS
    Perforce
    Others

[thomas]

Thomas. is it possible to use the svn plugin as base for the cvs plugin? A lot of things looks the same for both cvs and svn (only the commands are diffrent... as far as I know...)

Yes, 99% of it is exactly the same. Both the svn and the cvs path of the plugin use the same base class to call the respective tool. It only gets difficult when building the menu or implementing error handling with asynchronous execution, because you have two tools to consider all the time. This is why I am now doing a svn-only rewrite.
Technically, implementing cvs is almost as easy as replacing "svn.exe" with "cvs.exe" globally, changing a few commandline options, and inverting the return code for diff -- which is what I'll be doing in the end.
But first, svn gotta work.