Re: [bug] 2.5.0 build with NO_PERL is broken

From: Eric Sunshine <sunshine@sunshineco.com>
Date: Aug 14, 2015, 20:49 UTC
Message-ID: <CAPig+cR77oFo6D3f8BjAB_yM-xPt+3EUGK4vZr3eYWJGTtksAQ@mail.gmail.com>
In-Reply-To: <xmqq7foxiqu6.fsf@gitster.dls.corp.google.com>

On Fri, Aug 14, 2015 at 3:59 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 10 quoted lines

> Renato Botelho <garga@FreeBSD.org> writes:
>> I also found that some commands require perl when NO_PERL is set:
>
> NO_PERL merely means "I want to build a subset of Git that is meant
> to be usable on a system without a working Perl installed".  These
> scripts that do require Perl installed are indeed not expected to
> work under NO_PERL (if you think about it, that would be natural and
> the only sensible expectation---otherwise we would have coded them
> without using Perl at all, in which case there will be no need for
> NO_PERL in the first place).

Nevertheless, there's still the problem, due to 527ec39 (generate-cmdlist: parse common group commands, 2015-05-21), that git doesn't build at all anymore when Perl is unavailable.

One option would be to go with the awk version of 'generate-cmdlist'[1], which restricts itself to POSIX and was tested on Linux, FreeBSD, and Mac OS X[2], though I'm not sure we really want to go there, particularly if you're uncomfortable[3] about introducing awk into the toolchain.

Another option would be to rewrite the (more complex) generate-cmdlist in shell, which I think should be possible, though it will be uglier and more verbose.

[1]: http://article.gmane.org/gmane.comp.version-control.git/269307/ [2]: http://article.gmane.org/gmane.comp.version-control.git/269336/ [3]: http://article.gmane.org/gmane.comp.version-control.git/269324/