hghave: allow adding customized features at runtime Before this patch, there is no way to add customized features to `hghave` without changing `hghave` and `hghave.py` themselves. This decreases reusability of `run-tests.py` framework for third party tools, because they may want to examine custom features at runtime (e.g. existence of some external tools). To allow adding customized features at runtime, this patch makes `hghave` import `hghaveaddon` module, only when `hghaveaddon.py` file can be found in directories below: - `TESTDIR` for invocation via `run-tests.py` - `.` for invocation via command line The path to the directory where `hghaveaddon.py` should be placed is added to `sys.path` only while importing `hghaveaddon`, because: - `.` may not be added to `PYTHONPATH` - adding additional path to `sys.path` may change behavior of subsequent `import` for other features `hghave` is terminated with exit code '2' at failure of `import hghaveaddon`, because exit code '2' terminates `run-tests.py` immediately. This is a one of preparations for issue4677.

     1

# this file holds the definitions that are used in various bzr tests

     2

     3

"$TESTDIR/hghave" bzr || exit 80

     4

     5

TERM=dumb; export TERM

     6

echo '[extensions]' >> $HGRCPATH

     7

echo 'convert = ' >> $HGRCPATH

     8

     9

glog()

    10

{

    11

    hg log -G --template '{rev}@{branch} "{desc|firstline}" files: {files}\n' "$@"

    12

}

    13

    14

manifest()

    15

{

    16

    echo "% manifest of $2"

    17

    hg -R $1 manifest -v -r $2

    18

}