[KDev4] VCS Integration

[Andreas Pakulat]

On 15.03.07 10:08:15, Kris Wong wrote:
> > The library is pretty much "on its own" in the kdesvn source, i.e. its
> > not a large problem to extract it (tried it, was a matter of minutes,
> > except that I needed some kde4-libs cmake stuff to "fix" the missing
> > cmake code for finding the library dir). So I think we should talk to
> > the maintainer how much time he has and wether he'd like to move the
> > library out of kdesvn and release it separately (because for kdevelop
> > its probably better to depend on a lib than on a whole application,
> even
> > though some distros package the library separately).
> 
> Since kdesvn is not actually a part of KDE, and this library (if it were
> broken out, which would take some convincing) would only be installed
> with kdesvn, you would essentially be dependent on kdesvn. 

Uhm, no. Breaking it out of kdesvn means making it a standalone library
that has no other dependecy, except svn libs. So if kdevelop would use a
svnqt library this wouldn't need kdesvn to be installed.

> Personally, I don't think this would be the right way to go.
> Especially given how often we've recommended that users build out of
> svn lately on IRC.

Hmm, how does that make a difference? Granted they'd have to install
libsvn-dev + libsvnqt-dev, however we can as well tell them to install
libsvnqt-dev which will pull in libsvn-dev because of dependecy (unless
the distro maintainers broke the packages). 

> IMHO, it looks like using client libraries directly is really the right
> way to go.

Now I convinced you to that too :(

As it seems I'm the only one that likes using an existing lib better
than the svn-C-API, so I guess thats the way to go (especially as I
wasn't going to implement it anyway).

Andreas

PS: as far as CVS is concerned, I think we should try to use the cmdline
client, so we won't depend on kdesdk and can have the cvs plugin in the
platform.

Andreas

-- 
You will have domestic happiness and faithful friends.