Comment # 4 on bug 1023846 from Heiko Br�mmer

Thanks for clarification.

(In reply to Andrei Dziahel from comment #3)
> There was such dependency and I have it removed as someday I've needed both
> latest Mercurial and not so latest TortoiseHG. IMO only way to reliably
> resolve this dependency is to bundle Mercurial with TortoiseHG in a way it
> is done for Windows. Or package it separately for tortoisehg.

IMHO, this dependency should be kept for the "ordinary" user. Installing
different or maybe incompatible versions can be achieved with zypper/yast on
demand, but that is a rare case, I guess. 

> Anyway, this is quite a piece of work, so patches welcome.
> 
> Still, I've done as asked (user experience is a priority): tortoisehg 4.0
> now requires Mercurial 3.9 to 4.0. I'm not sure how to get Mercurial 4.0
> package except from building it yourself (`osc co -r 178
> devel:tools:scm/mercurial ; osc build -k ./packages`), but hope that helps
> anyway.
Last year, it took one or two weeks to get a version of tortoisehg that was
compatible with the latest version of mercurial. So I'll wait some days before
building it on my own @home.