view contrib/plan9/proto @ 46325:e5e6282fa66a

hghave: split apart testing for the curses module and `tic` executable

ef771d329961 skipped the check for the `tic` executable, because the curses
module alone on Windows is enough to pass the `test-*-curses.t` tests.  However,
`test-status-color.t` uses this same check and explicitly invoked the
executable, which fails on Windows.  From the cursory searching I did, curses on
unix requires `tic`, which I assume is why they were tied together in the first
place.  So this continues to require both to get past the curses guards on non
Windows platforms.

Differential Revision: https://phab.mercurial-scm.org/D9814

lib	- sys sys
	mercurial	- sys sys
		hgrc.d	- sys sys
			9diff.rc	- sys sys
			factotum.rc	- sys sys
rc	- sys sys
	bin	- sys sys
		9diff	- sys sys
		hg	- sys sys
sys	- sys sys
	lib	- sys sys
		python	- sys sys
			lib	- sys sys
				python2.5	- sys sys
					site-packages	- sys sys
						hgext	- sys sys
							+	- sys sys
						mercurial	- sys sys
							+	- sys sys
						mercurial-VERSION-py2.5.egg-info	- sys sys
	src	- sys sys
		cmd	- sys sys
			hg	- sys sys
				+	- sys sys