From: Renato Botelho <garga@freebsd.org>
Date: Tue, 18 Aug 2015 18:09:12 GMT
Subject: Re: [bug] 2.5.0 build with NO_PERL is broken
Message-ID: <loom.20150818T200305-434@post.gmane.org>
In-Reply-To: <CAPig+cTvNQ74G4T3McNd2JUXLvxe-yX+ApFrevXDi4GXsFQ_3g@mail.gmail.com>

> Eric Sunshine <sunshine <at> sunshineco.com> writes:
> 
> Hmm, I was under the impression from your initial mail[1] that Git
> wouldn't even build without Perl available:
> 
>     /bin/sh: /usr/bin/perl: not found
>     Makefile:1701: recipe for target 'common-cmds.h' failed
>     gmake[2]: *** [common-cmds.h] Error 127

This assumption is correct, current 2.5.0 doesn't build without perl.

> Doesn't this failure prevent generation of the 'git' executable altogether?
> 
> > git-submodule
> > git-request-pull
> > git-am
> 
> Also...
> 
> git-add--interactive
> git-archimport
> git-cvsexportcommit
> git-cvsimport
> git-cvsserver
> git-difftool
> git-instaweb
> git-relink
> git-send-email
> git-svn

When I build with NO_PERL=1, above files are a simple shell script saying
git was built without it:

#!/bin/sh

echo >&2 "fatal: git was built without support for `basename $0` (NO_PERL=1)."
exit 128

But the same doesn't happen with submodule, request-pull and am.

> A C rewrite of git-am has recently graduated to 'master'.

cool!

> That might make sense. Although some of the above commands may not be
> used widely, others, such as git-send-email, probably are used
> regularly.

There is a port called git-lite with few dependencies, sometimes people
install it on servers that only need to clone and update local copies of
repos. It's interesting to keep it working as expected with NO_PERL, since
it offers this option.