Kallithea issues archive

Issue #192: Remove mercurial dependency

Reported by:
State: new
Created on: 2016-02-14 23:31
Updated on: 2016-05-27 18:45


As the project can support mercurial xor git, the mercurial support should not be mandatory.



Comment by Mads Kiilerich, on 2016-02-15 00:09

All software has features and dependencies you don't need or use. You can choose which VCS is your default. Is it really a problem that Mercurial is on that list?

Comment on 2016-02-15 00:10

When the release upgrade to 0.3 bug on the last release of mercurial. If mercurial is not mandatory it should be removed.

Comment by Mads Kiilerich, on 2016-02-15 00:17

Sorry, I don't understand that sentence.

Comment by Thomas De Schampheleire, on 2016-02-15 12:45

Do you mean that the 0.3 version does not work with the last release of Mercurial? Which version of Mercurial do you see a problem with, and which bug do you see?

It is true that Kallithea may need some changes to support a newer Mercurial version, but that is why the requirements list places a maximum version number for Mercurial, so that only a working version is used.

Comment by domruf, on 2016-02-15 13:24

This would be quite a big endeavor.

The current code base depends heavily on mercurial not only for the hg backend. (kallithea.lib.vcs.utils.hgcompat)

Comment by Long Vu, on 2016-02-15 15:55

@encolpe I have Kallithea 0.3 and it works perfectly with the mercurial version specified in setup.py and that specified mercurial version has both an lower and upper bound ("mercurial>=2.9,<3.6"). If you respect that specified range, you should be fine.

Comment by EirN, on 2016-05-24 17:10

We can use Mercurial command line using hgapi and not depend on Python 2 anymore.

Comment by domruf, on 2016-05-27 18:45

Again this would require HUGH changes to the code. A lot had to be re-written.