Mercurial > hgsubversion
view Makefile @ 1002:117b3b421294
buildmeta: verify uuid when passed explicit url
2c87bdc43d3c changed buildmeta to read the uuid from local disk, if
it's available. As a side effect, it disabled the validation of the
uuid we've recorded locall in the commits against the uuid of the repo
we are building against. This is probably reasonable when someone
runs a bare updatemeta or rebuildmeta. I think it's a worthwhile
sanity check when someone passes an explicit repository url to
rebuild/updatemeta. This restores the validation in that case, and
fixes a failing test in the process.
author | David Schleimer <dschleimer@fb.com> |
---|---|
date | Fri, 12 Apr 2013 10:51:42 -0700 |
parents | 055f9254d790 |
children |
line wrap: on
line source
# Makefile for testing hgsubversion PYTHON=python .PHONY: all check check-demandimport check-subvertpy check-swig all: @echo "Use the following commands to build and install hgsubversion:" @echo @echo "$$ cd $(PWD)" @echo "$$ $(PYTHON) ./setup.py install" @echo @exit 1 check: check-demandimport check-subvertpy check-swig check-demandimport: # verify that hgsubversion loads properly without bindings, but fails # when actually used ! LC_ALL=C HGSUBVERSION_BINDINGS=none HGRCPATH=/dev/null \ hg --config extensions.hgsubversion=./hgsubversion \ version 2>&1 \ | egrep '(^abort:|failed to import extension)' LC_ALL=C HGSUBVERSION_BINDINGS=none HGRCPATH=/dev/null \ hg --config extensions.hgsubversion=./hgsubversion \ version --svn 2>&1 \ | egrep '(^abort:|failed to import extension)' check-subvertpy: $(PYTHON) tests/run.py --all --bindings=subvertpy check-swig: $(PYTHON) tests/run.py --all --bindings=swig