Patch for preliminary Mercurial integration in kdevplatform

[Fabian Wiesel]

On Wed, 11 Mar 2009 15:13:47 +0300
Evgeniy Ivanov <pfx.kde at gmail.com> wrote:

> > So, when using a mercurial repository for tracking my local changes,
> > and subversion for the remote ones, I am supposed to switch back to
> > console? Which vcs should kdevelop integrate, and which neglect?
> 
> As for git git-svn might me used (for basic thing two things: "git
> svn rebase" and "git svn dcommit"), but unfortunately it's in TODO
> for a long time. Can't be done the same for Hg?

There is no standard hg-svn integration. But even if there were,
this would only solve the combination of hg and svn. How about git +
perforce? Or, god forbid, git + Visual Source Safe.
There are far to many possible combinations one could possibly expect
to implement.

> If you want to rewrite Hg plugin I would suggest to implement it in
> python calling Hg functions, but not exec- like calls to binaries.

Well, I was planning on trying that, but since there was already a
git-plugin and mercurial and git are quite similar, it was faster way
to get some results. Especially since I then have to have a look at
how to interface to python from C++.

There might be some possible downsides to the approach of
using the python-integration: AFAIK, the API of Hg is the command-line
tool. One can easily access the interna of mercurial, but I don't know
how stable the interface is.
The second, more critical part is that you probably cannot simply call
the python functions from a mercurial instance, as it is not
thread-safe. It will likely require some work on the side of the
hg-plugin to get it threadsafe.

My best regards,
  Fabian