[KDev4] VCS Integration

[Kuba Ober]

On Tuesday 13 March 2007, Andreas Pakulat wrote:
> On 13.03.07 08:52:15, Robert Gruber wrote:
> > Hello!
> >
> > As I've seen from the recent posts to the mailinglist, dukju ahn is
> > already working on bringing SVN support to KDevelop4, aren't you?
> >
> > Is anybody working on the CVS integration? If not, I could take that
> > task.
> >
> > However, to me, there are still some important questions to solve?
> > Has there been any decicion on how to integrate version controll systems?
>
> No, I have a few things in my mind but nothing thought out yet...
>
> > Maybe like in KDevelop3 where each plugin has been able to add items to a
> > context menu? This method was very easy to use for the VCS plugin, as it
> > alredy got a list of files to work on from the Context object.
>
> Well, context menu will happen one way or another. More important is
> that we define a minimal extension interface that every VCS can
> implement. A quick thought brings up the following actions:
>
> import (into repository)
> chechkout
> update
> commit
> diff
> log

Hmm.

What would all those do? What's an "import"? Is this adding a file to a 
change? Then checkout -- is it for whole tree, or for a single file? What 
does an update do?

Aegis, a nice software configuration systen, works on whole trees, i.e. you 
check out a read-only tree (a change), which has no writable files, and only 
symlinks, hardlinks/copies or even no links at all to the read-only baseline. 

In the tree that you checked out you can copy individual files to be 
read-write, and work on them. Depending on the build tool, you need symlinks, 
hardlinks/copies, or you may live without links at all.

Cheers, Kuba