##// END OF EJS Templates
setup: don't skip the search for global hg.exe if there is no local instance...
setup: don't skip the search for global hg.exe if there is no local instance The point of trying not to blindly execute `hg` on Windows is that the local hg.exe would be given precedence, and if py3 isn't on PATH, it errors out with a modal dialog. But that's not a problem if there is no local executable that could be run. The problem that I recently ran into was I upgraded the repo format to use zstd. But doing a `make clean` deletes all of the supporting libraries, causing the next run to abort with a message about not understanding the `revlog-compression-zstd` requirement. By getting rid of the local executable in the previous commit when cleaning, we avoid leaving a broken executable around, and avoid the py3 PATH problem too. There is still a small hole in that `hg.exe` needs to be deleted before switching between py2/py3/PyOxidizer builds, because the zstd module won't load. But that seems like good hygiene anyway. Differential Revision: https://phab.mercurial-scm.org/D8038

File last commit:

r43815:e182deb5 default
r44684:a7f8160c default
Show More
Vagrantfile
13 lines | 415 B | text/x-ruby | RubyLexer
anatoly techtonik
contrib/vagrant: use Vagrant for running tests on virtual machine...
r21874 # -*- mode: ruby -*-
Vagrant.configure('2') do |config|
Augie Fackler
vagrant: update vagrant image to buster from jessie...
r43909 # Debian 10.1 x86_64 without configuration management software
config.vm.box = "debian/buster64"
anatoly techtonik
contrib/vagrant: use Vagrant for running tests on virtual machine...
r21874 config.vm.hostname = "tests"
config.vm.define "tests" do |conf|
conf.vm.provision :file, source: "run-tests.sh", destination:"run-tests.sh"
conf.vm.provision :shell, path: "provision.sh"
conf.vm.synced_folder "../..", "/hgshared"
end
end