Re: [PATCH 1/2] configure: Allow GIT_ARG_SET_PATH to handle --without-PROGRAM
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 1, 2010, 21:14 UTC
- Message-ID
- <7vwrywu08v.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <1264990505-29578-2-git-send-email-bwalton@artsci.utoronto.ca>
Ben Walton <bwalton@artsci.utoronto.ca> writes:
Show 12 quoted lines
> Add an optional second argument to both GIT_ARG_SET_PATH and > GIT_CONF_APPEND_PATH such that any value of the second argument will > enable configure to set NO_$PROGRAM in addition to an empty > $PROGRAM_PATH. This is initially useful for allowing configure to > disable the use of python, as the remote helper code has nothing > leveraging it yet. > > The Makefile already recognizes NO_PYTHON, but configure provided no > way to set it appropriately. > > Signed-off-by: Ben Walton <bwalton@artsci.utoronto.ca> > ---
Interesting.
I noticed that even without this patch we seem to honor --without-tcltk just fine and wondered why. It turns out that we already do the right thing when TCLTK_PATH is empty to set NO_TCLTK in our Makefile, but we at the same time have a long custom code in configure.ac to support tcltk.
Perhaps we can clean-up with-/without-tcltk part in configure.ac using this?