Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

SVN plugin

<< < (6/19) > >>

thomas:

--- Quote from: squizzz ---Do you plan adding your plugin to official C::B /plugins/contrib CVS repository some day?
--- End quote ---

Hmm... does this work at all? If it does, then I don't know how. It sure is very easy with CVS to set svn:externals on a directory to include another SVN repository in the tree, but I have no idea if CVS has any such thing. Rather, I think it would be necessary to migrate the project to CVS.
But you are of course very right, generally. It sure would be better for its popularity if it was in the CVS tree.
Lets wait until it is in a little more finished. For now, I dread to think about using CVS. If I get the CVS support right, though, maybe CVS could be lived with ;)
 

--- Quote from: squizzz ---Note that not many users use version control system at all
--- End quote ---

Lol, yes, and CVS contributed a lot to that ;)
When I first thought about using revision control (somewhere around 1995), I was told there was RCS and CVS, the latter being the tool of choice, as it was so much better. So I looked at CVS, and this experience put me off revision control entirely.
At some point in 2002, however, I decided that no matter how painful, I had to start using revision control, as I spent a good quarter of my time messing with a hundred local copies of every file (well you know... you've been there).
Much to my surprise, subversion turned out to be not much of a pain at all. Setting up a functional repo and successfully importing a project took me 30 seconds after reading the docs (as opposed to 2 hours with CVS). And apart from very few occasions, it causes very very little grief (rarely, it gets a file access conflict, and bdb is not backwards compatible, so upgrading to Fedora 4 made my repos unusable - but well, one should use fsfs, anyway).
Thus it became he used subversion, and he lived long and happily ever after.


--- Quote from: rickg22 ---After all, look at this thread title
--- End quote ---

Ah yes, but a man can dream, can't he :)
Maybe Sourceforge finally releases SVN access one day, then no one will be wanting to use CVS any more. At BerliOS (which uses the sourceforge web interface, too), they have it running.

thomas:
Added another snapshot of today's sources as well as a binary release:
http://developer.berlios.de/project/showfiles.php?group_id=4084&release_id=6571

This one has support for TortoiseCVS and should do CVS checkout, update, and commit.

Should do? Well yes... should do. Lacking write access to a CVS server, I have no possibility to confirm that commit actually does anything, but I guess it does :)
The CVS code is quite awkward, but CVS is a really picky with its paramters, too. In particular, it messed around a lot when passed directories as targets. Finally, the code ended up with changing working directory and calling cvs with no target for directories. This is ugly and awkward, but it does not crash and burn...
Checking out code::blocks and freeBSD as "test suite" did work fine, and update seems to work, too. Authentication does work, I believe.
So if you have been waiting for CVS support, then this is the time to try and send feedback.

It seems to me that CVS is unable to do anything without network access. That implies that custom menus according to a file's state cannot be implemented for CVS-controlled projects (you would not want to possibly wait 30 seconds before the menu opens?).
The only way around seems to be parsing CVS/Root and comparing the commit times to file modification times manually.
Should this be a misconception of mine (being a no-CVS user, it is quite possible that I only lack the knowledge about the necessary switch), then I would appreciate being hinted to it :)
Is there anything like "svn status" in CVS?

Ah yes, and most important, the project now has a useless home page with a nice picture, and the dll has a new icon, too.
If you don't get something to work, then at least make it look good ;)

mandrav:

--- Quote ---It seems to me that CVS is unable to do anything without network access.
--- End quote ---

Correct.

--- Quote ---The only way around seems to be parsing CVS/Root and comparing the commit times to file modification times manually.
--- End quote ---

Yup, it's the only solution and it's a nightmare, especially around daylight saving times...

Yiannis.

mandrav:
I downloaded the sources and noticed a few things.
First, you 're using the VERSION_1_0 branch of C::B. It's not bad, just something that should be mentioned.
I compiled it using wx2.6.1 and many things (mainly event handlers) were wrong.
I 've corrected all the errors and will upload a patch for you at berlios.
I 've also updated your project file to use the latest and greatest: custom variables. This allows for setting the main paths (wx, codeblocks, etc) in one place (project build options->custom variables) and all project settings are updated :)

Now for the usage:
I tried using your plugin with a project of mine which I have under SVN control (as I do with all my personal projects ;) ). I had 14 files modified to be commited. When I tried to commit them, I got this response:

--- Quote ---svn: Commit failed (details follow):
svn: Can't create tunnel: The system cannot find the file specified.  
--- End quote ---

Any insight? (I've already setup the plugin's configuration)

Keep up the good work :)

Yiannis.

mandrav:

--- Quote from: mandrav ---I 've corrected all the errors and will upload a patch for you at berlios.
--- End quote ---

Tough luck. Either berlios doesn't have a patch tracker or you haven't enabled it...
Anyway, here's the patch.

Yiannis.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version