tests: `hg init` after resetting HGRCPATH
Otherwise extensions loaded via --extra-config-opt could prevent
access to the repo by introducing requirements file. This does mean
that custom extensions loaded in this way won't impact this test.
I'm fine with that.
Differential Revision: https://phab.mercurial-scm.org/D3115
--- a/tests/test-hgrc.t Wed Apr 04 17:33:59 2018 -0700
+++ b/tests/test-hgrc.t Wed Apr 04 17:40:09 2018 -0700
@@ -1,11 +1,11 @@
-hide outer repo
- $ hg init
-
Use hgrc within $TESTTMP
$ HGRCPATH=`pwd`/hgrc
$ export HGRCPATH
+hide outer repo
+ $ hg init
+
Use an alternate var for scribbling on hgrc to keep check-code from
complaining about the important settings we may be overwriting: