Re: What's cooking in git.git (Apr 2014, #09; Tue, 29)

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: May 7, 2014, 00:17 UTC
Message-ID: <53697b9f6b978_1b76e132f05d@nysa.notmuch>
In-Reply-To: <xmqqd2fqcv7s.fsf@gitster.dls.corp.google.com>

Junio C Hamano wrote:

Show 9 quoted lines

> I _think_ it probably is OK for git-imerge.git/Makefile to peek into
> our Makefile, e.g.
> 
>     $ cd git-imerge.git
>     $ make GIT_SOURCE_DIR=../git.git install
> 
> to learn where imerge should install its subcommand implementation and
> documentation.  It might even want to borrow the test framework by
> using $GIT_SOURCE_DIR/t/test-lib.sh or somesuch.

Since Git's test framework heavily tied to git.git, sharness[1] is the only sensible option. It might not have all the latest features of Git's test framework, but it's standalone.

[1] https://github.com/mlafeldt/sharness

-- 
Felipe Contreras