From: Junio C Hamano <gitster@pobox.com>
Date: Fri, 14 Aug 2015 22:22:47 GMT
Subject: Re: [bug] 2.5.0 build with NO_PERL is broken
Message-ID: <xmqqzj1tfr2g.fsf@gitster.dls.corp.google.com>
In-Reply-To: <CAPig+cR6iT=AC8zq-vHHTkXMzRmDA-o9JLi0h8gbR1tzbqNyKA@mail.gmail.com>

Eric Sunshine <sunshine@sunshineco.com> writes:

> On Fri, Aug 14, 2015 at 5:02 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> Eric Sunshine <sunshine@sunshineco.com> writes:
>>> 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.
>>
>> I do not think that is anything new.  We always have assumed "some"
>> version of Perl available in order to run t/ scripts.
>
> True, but prior to 527ec39, without Perl available, git itself could
> at least be built and used (with some commands unavailable), even if
> it couldn't be fully tested. As of 527ec39, however, git won't even
> build because common-cmds.h can't be generated.

I wouldn't bother digging in the history myself, but I am reasonably
sure that the current genereate-common-cmds is not the sole instance
that we relied on Perl to build (not test) in the past, and that is
another reason why I do not think this is anything new.