view hgext3rd/topic/README @ 4332:9980df8eda98 stable

tests: fix PYTHONPATH manipulation on Windows

Without the semicolon separator and quotes, the variables ends up like this:

    c:\Users\Matt\projects\hg-evolve:c:\Users\Matt\projects\hg-evolve:
    c:\Users\Matt\projects\hg;c:\Users\Matt\projects\hg-evolve\tests;
    c:\Users\Matt\projects\hg\tests

That in turn makes the local evolve code unreachable, and the system installed
code is tested instead.

I'm testing against `uname` instead of a trivial python script printing os.name
because maybe one day tests will run on WSL.

Topic Extension
================

This packages also provides the ``topic`` experiment in an independent
extension. It implements a new experimental concept to provide lightweight
feature branches for the mutable parts of the history. The experiments is still
at an early stage and have significant usability and performance issues when
enabled.

How to Install
==============

The ``topic`` extension is included into the ``evolve` package, so the same instruction apply.

Using Pip
---------

You can install the latest version using pip::

    $ pip install --user hg-evolve

Then just enable it in you hgrc::

    $ hg config --edit # adds the two line below:
    [extensions]
    topic =

From Source
-----------

To install a local version from source::

    $ hg clone https://www.mercurial-scm.org/repo/evolve/
    $ cd evolve
    $ make install-home

Enable
------

The topic extensions is included in the evolve package. See the install instruction for evolve.

Then enable it in you configuration::

    $ hg config --edit # adds the two line below:
    [extensions]
    topic =

Documentation
-------------

* See 'hg help -e topic' for a generic help.
* See 'hg help topics' and 'hg help stack' for help on specific commands.
* See the 'tests/test-topic-tutorial.t' file for a quick tutorial.