hgview #137242 using alternate hg [open]

I may be mistaken but I believe there is no way to tell setup.py to use an alternate Mercurial version.

On my Ubuntu machine the version of Mercurial provided by the distribution is installed in /usr. I have installed Mercurial 2.5 under the alternate /volatile/local location, with /volatile/local/bin in my path, because Mercurial 2.5 is needed by the Evolve extension. Unfortinately Mercurial 2.5 cannot be installed as an Ubuntu package due to apt bugs/lack of documentation.

I cannot get HgView to use the Mercurial in /volatile/local instead of the one in /usr.

prioritynormal
typebug
done in<not specified>
closed by<not specified>

Comments

  • 2013/05/15 08:55, written by acampeas

    running hgview from the sources I can use whatever mercurial version I want

  • 2013/05/15 09:21, written by dimitri

    I cannot. How to specify a different Mercurial version?

    • 2013/05/16 10:03, written by acampeas

      I do a home install of mercurial and adjust the PYTHONPATH (in my .bashrc).

      • 2013/05/16 21:08, written by dimitri

        The home install I had already done:

        setup.py install --prefix=...

        You're right, setting the PYTHONPATH whithin an alternate hgview script should indeed work. I was looking for some hgview install-time option that would select the Mercurial installation directory and avoid the need for setting PYTHONPATH in a second script - I don't want to set PYTHONPATH just to run a program, especially in ~/.bashrc.

  • 2013/05/25 16:14, written by aleufroy

    The best way is to configure hgview as a mercurial extension in your "~/.hgrc":

    [extensions]
hgview = /path/to/hgview/hgext/hgview.py

    Once done you can choose any version of mercurial:

    $ /volatile/local/bin/hg qv
add comment

Ticket #137242 - latest update on 2013/05/25, created on 2013/05/07 by Dimitri Papadopoulos