Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
SVN plugin
rickg22:
i'm just wondering if it wouldn't be easier to fix the CVS problems between thomas and sourceforge...
kagerato:
--- Quote from: rickg22 ---i'm just wondering if it wouldn't be easier to fix the CVS problems between thomas and sourceforge...
--- End quote ---
There are problems? I thought he just massively prefers SVN.
Anyway, let him develop what he feels is the best solution. At some point, SVN is very likely to become equally popular as CVS; by then, all the little phantom issues and conflicts between the versioning systems will have dissipated.
As of this moment, I've not heard about any serious bugs or detrimental factors in the SVN implementation. It seems many people are hailing it as all-around superior to CVS. The only reasons for not adopting it now seem to be: a.) familiarity with the existing system (and resultingly, a reluctance to learn new methods), and b.) a high degree of prudence and skepticism about new technology (the "let's wait and see" approach).
mandrav:
--- Quote ---The only reasons for not adopting it now seem to be: a.) familiarity with the existing system (and resultingly, a reluctance to learn new methods), and b.) a high degree of prudence and skepticism about new technology (the "let's wait and see" approach).
--- End quote ---
Let me add the more important reason, I think:
The majority of open-source projects are hosted on sf.net and sf does not support svn yet.
Yiannis.
thomas:
--- Quote from: 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.
--- End quote ---
Thank you :)
Now lets see if I get through the wxCompile hell alive :)
--- Quote ---Tough luck. Either berlios doesn't have a patch tracker or you haven't enabled it...
--- End quote ---
The latter. My bad, sorry. Did enable now and uploaded your patch.
--- Quote from: mandrav ---svn: Commit failed (details follow):
svn: Can't create tunnel: The system cannot find the file specified.
--- End quote ---
Ah, tunnelling is about the only thing that can make you really hate svn. Took me hours to get it running the first time, and the amount of helpful documentation on the internet is near zero.
I do assume that you have a tunnel running to start with, i.e. you can open a functional ssh window to the server (for example using pageant/putty).
The likely reason for this error message is that you used a native file path to your plink executable inside {CommonFiles}\subversion\config, like it is the obvious way to do. Unluckily, the obvious way does not work. You must use all forward slashes like this:
--- Code: ---[tunnels]
ssh = $SVN_SSH C:/tools/plink.exe
--- End code ---
Rick:
No problems with Sourceforge :)
Just CVS is giving me the creeps every time I use it. Using SVN proved straighforward from the first minute, and CVS still makes me think "Darn, where is the manual, this is confusing" quite often.
It is also things like this that drive me crazy:
--- Code: ---cvs -d :pserver:someone@the.server:/cvsroot/something checkout module -d somedir
--- End code ---
There are two "-d" switches in the same command line, they mean entirely different things. And worse, the order of parameters can matter, too. I don't recall an example for that now, but I had a case. Those are things that turn me off. No offense taken if someone uses CVS, but it is just not a thing for everyone.
Another thing that gets me each time is the naming scheme for repositories (I forget to type one of the many colons, mostly the third one, about 50% of the time). Sure enough, CVS existed long before most everybody had heard the word 'URL', so that somehow excuses. But then what is the deal, after one decade, in letting people write "cvs checkout pserver://someone@the.server/cvsroot/something/module -d somedir" instead.
Certainly, TortoiseCVS makes it somewhat less painful, but I still feel uncomfortable with it.
Do not grieve, Sourceforge will soon offer SVN, they announced months ago :)
mandrav:
--- Quote from: thomas ---
--- Quote from: mandrav ---svn: Commit failed (details follow):
svn: Can't create tunnel: The system cannot find the file specified.
--- End quote ---
Ah, tunnelling is about the only thing that can make you really hate svn. Took me hours to get it running the first time, and the amount of helpful documentation on the internet is near zero.
I do assume that you have a tunnel running to start with, i.e. you can open a functional ssh window to the server (for example using pageant/putty).
The likely reason for this error message is that you used a native file path to your plink executable inside {CommonFiles}\subversion\config, like it is the obvious way to do. Unluckily, the obvious way does not work. You must use all forward slashes like this:
--- Code: ---[tunnels]
ssh = $SVN_SSH C:/tools/plink.exe
--- End code ---
--- End quote ---
Here's my setup (quite common, I think):
My repositories are on a separate linux server, already setup and working.
In my windows machine, I 've installed TortoiseSVN and that's it. Everything Just Works(tm).
I downloaded and built your plugin. Upon first C::B launch with your plugin, I went to "Settings->Configure plugins->Subversion".
This dialog has two text boxes. The first one was empty (the subversion path). The second contained the path to tortoise's plink.
I looked around a bit and dismissed the dialog (I didn't edit anything). Btw, nice options you got there ;)
Opened a project (under svn control) and right-clicked on the project root. I clicked on "Subversion->Commit (14 files changed)" and I got some assertions.
Note: It would be better to display a friendly error dialog, explaining what to do :)
Anyway, I realized that I had to install subversion for this to work.
Downloaded subversion, installed it and set the path to svn.exe in your plugin's configuration.
I then retried the same procedure as above, to commit the changes of my project.
That's when this error came up:
--- Code: ---svn: Commit failed (details follow):
svn: Can't create tunnel: The system cannot find the file specified.
--- End code ---
[EDIT]I can't find {CommonFiles}\subversion\config. Where is it hidden? [/EDIT]
[EDIT 2]Found it: It's in %USERPROFILE%/Application Data/Subversion/config[/EDIT 2]
As you can see I haven't touched {CommonFiles}\subversion\config. Should I?
How should I know?
I mean, I use TortoiseSVN and never had to tamper with anything of this sort.
Don't get me wrong. I appreciate all the hard work you 're doing. I just put myself in the average joe's shoes and see if she could make anything out of it.
Conclusion: a little bit more polish and a helpful README with the common pitfalls and you 're set :)
Yiannis.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version