SVN support in kdevelop 3.4

Andreas Pakulat apaku at gmx.de
Tue Oct 25 15:19:04 UTC 2005


On 25.10.05 09:50:05, Mickael Marchand wrote:
> Andreas Pakulat a écrit :
> > I just like to know, wether svn support in kdevelop3.4 will be fixed? 
> > See the following bug reports for the problems I mean:
> > http://bugs.kde.org/show_bug.cgi?id=111159
> > http://bugs.kde.org/show_bug.cgi?id=109132
> > http://bugs.kde.org/show_bug.cgi?id=110222
> > 
> > Now, before you tell me to read the FAQ, I did read it and I do commit
> > to svn with the command line client ATM. I also removed all subversion
> > stuff from my project, before my last try (just 10 minutes ago with 3.4
> > SVN) and still SVN is broken.
> > 
> > I just like to know wether there are any plans on fixing this.
> > 
> > Andreas
> > 
> 
> first of all, never use compat/svn,

I didn't, at least I think so. I just ran configure with
--enable-subversion and makeing went through fine. When I start make in
the compat dir I get an error, so I'm pretty sure I use the ioslave from
kdesdk.

> secondly, I did not get any of these reports,

That's really sad. I'd like to add to those reports above that I
experience crashes of kdevelop when using the subversion plugin.
Kdevelop loads completely and then reads the project information. When
that's finished it crashes. I think this might be related to 109132, but
am not sure...

> thirdly, please specify subversion version you used to link your ioslave

Hmm, lets see  libsvn0 (>= 1.2.3a) (kdesdk-misc package from debian
experimental).

> finally, check you can open a svn+http:// URL in konqui (to check your
> installation is ok)

That works perfectly.

I had some time yesterday and started to find the way how the vcs-plugin
is loaded... I found that the restoreProjectSession function in the
vcs-plugin is never called, but couldn't find out why (yet). This is
probably one main cause of all the trouble as now the plugin uses
svn+http://blah/blub as svn url, which of course doesn't work. The other
source of trouble I could identify is that the vcs-plugin has no means
of setting the base url via the UI and doesn't read it from the
.svn-files. I mean if svn info shows the url that is used in a working
copy, the vcs plugin or the svn ioslave should be able to get the same
information.

I probably won't have time until the weekend to dig a bit deeper into
kdevelop and find out more.

Andreas

-- 
Your supervisor is thinking about you.




More information about the KDevelop-devel mailing list