Re: [PATCH] tests: handle NO_PYTHON setting
- From
Jeff King <peff@peff.net>
- Date
- Nov 30, 2009, 07:59 UTC
- Message-ID
- <20091130075927.GA5767@coredump.intra.peff.net>
- In-Reply-To
- <fabb9a1e0911292355v260b9f0ck79d993e25f0c5c61@mail.gmail.com>
On Mon, Nov 30, 2009 at 08:55:51AM +0100, Sverre Rabbelier wrote:
Show 9 quoted lines
> > This feels a little funny for NO_PYTHON to mean "no remote helpers at > > all". But that is the way the Makefile is set up, since we seem to have > > only python helpers. > > I don't understand what you mean? Do you mean NO_PYTHON implies "no > remote helpers at all", or "not having any remote helpers" implies > NO_PYTHON? Either way, I'm not sure how to set it up differently, not > having that much Makefile foo myself, so maybe Johan and Daniel could > comment?
I mean, I would think that the "git_remote_helpers" directory contained remote helpers of all sorts, not just the python ones. Right now we _only_ have python ones. So checking for NO_PYTHON in test-lib.sh before looking at git_remote_helpers makes sense. But I am concerned that assumption will be broken silently in the future if non-python helpers are added to git_remote_helpers.
It is probably not worth caring about too much, though.
-Peff