From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 5/5] Optionally work without python
Date: Fri, 17 Feb 2006 22:50:28 -0800 [thread overview]
Message-ID: <7vvevdtb2j.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: Pine.LNX.4.63.0602171523510.24274@wbgn013.biozentrum.uni-wuerzburg.de
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> In some setups (notably server setups) you do not need that dependency.
> Gracefully handle the absence of python when NO_PYTHON is defined.
> +ifdef NO_PYTHON
> + TEST_DEFS += NO_PYTHON=YesPlease
> +endif
I wonder if there is a better way to do this. All future
NO_BLAH that may affect tests need to have something like this
otherwise.
> -default_strategies='recursive'
> +if test -z "@@NO_PYTHON@@"; then
> + default_strategies='recursive'
> +else
> + default_strategies='resolve'
> +fi
Somebody commented on this part to make it shorter...
I'll take 2, 3, and 4 from this series for now. They will
appear in "next". Thanks.
next prev parent reply other threads:[~2006-02-18 6:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 14:24 [PATCH 5/5] Optionally work without python Johannes Schindelin
2006-02-17 21:07 ` Radoslaw Szkodzinski
2006-02-18 6:50 ` Junio C Hamano [this message]
2006-02-18 12:01 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vvevdtb2j.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).