[KDev4] VCS Integration

Matt Rogers mattr at kde.org
Wed Mar 14 03:53:29 UTC 2007


On Mar 13, 2007, at 10:43 PM, dukju ahn wrote:

> 2007/3/14, Matt Rogers <mattr at kde.org>:
>
>> Please don't commit it. Submit it to the list for review first.
>> Incorporate the feedback received and then commit after that.
>
> Yes, I will review it first. I am new to this kind of collaboration.
> Sorry for that.
>
> And I have one more question to everyone. Do youguys have any
> idea or preferences about how the VCS core engine should be
> implemented?
> In KDev3, subversion part used ioslave, CVS part used CVS DCOP
> service. Both of them is not part of KDevelop. Users had to
> install additional plugin to use VCS integration.
>
> In other thread of mailling-list, I read andreas' article that KDev4
> will be directly linked to subversion library, not using ioslaves.
> Then, what could be the candidate for such core framework?
>
> I think using Multi Thread or threadweaver could be one solution.
> Also, I think extending existing ioslave in kdesdk is also good.
>
>

It's my general opinion that we need to avoid the use of ioslaves for  
SCM integration as much as possible. So the subversion plugin should  
use subversion's client API directly. As for CVS and others, I'm not  
entirely sure how that would work yet.
--

Matt






More information about the KDevelop-devel mailing list