git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: vfr@lyx.org
Cc: git@vger.kernel.org, gitster@pobox.om
Subject: Re: [PATCH] t: Replace 'perl' by $PERL_PATH
Date: Mon, 11 Jun 2012 12:15:03 -0700	[thread overview]
Message-ID: <7v1ull7j9k.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1339441313-5296-1-git-send-email-vfr@lyx.org> (vfr@lyx.org's message of "Mon, 11 Jun 2012 19:01:53 +0000")

vfr@lyx.org writes:

> From: Vincent van Ravesteijn <vfr@lyx.org>
>
> GIT-BUILD-OPTIONS defines PERL_PATH to be used in the test suite. Only a
> few tests already actually use this variable when perl is needed. The
> other test just call 'perl' and it might happen that the wrong perl
> interpreter is used.
>
> This becomes problematic on Windows, when the perl interpreter that is
> compiled and installed on the Windows system is used, because this perl
> interpreter might introduce some unexpected LF->CRLF conversions.
>
> This patch makes sure that $PERL_PATH is used everywhere in the test suite
> and that the correct perl interpreter is used.
>
> Signed-off-by: Vincent van Ravesteijn <vfr@lyx.org>
> ---

There was already this discussion:

    http://thread.gmane.org/gmane.comp.version-control.git/132560/focus=132561

which basically dismissed effort along this line with "If the perl
in your PATH is so broken that it can't be used for simple helpers,
then you should fix your PATH."

I personally do not mind if we do this consistently, but I am not
sure your $PERL_PATH that is not quoted is the right way to invoke
it; look for PERL_PATH in t/ to see the existing uses.

  reply	other threads:[~2012-06-11 19:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 19:01 [PATCH] t: Replace 'perl' by $PERL_PATH vfr
2012-06-11 19:15 ` Junio C Hamano [this message]
2012-06-12 12:34   ` Jeff King
2012-06-12 14:56     ` Junio C Hamano
2012-06-12 14:59       ` Jeff King
2012-06-12 15:36   ` Erik Faye-Lund
2012-06-12 16:08     ` Junio C Hamano
2012-06-12 16:44       ` Junio C Hamano
2012-06-12 17:05         ` Jeff King
2012-06-12 19:29         ` Vincent van Ravesteijn
2012-06-17  6:36 ` Torsten Bögershausen
2012-06-17  7:15   ` Junio C Hamano
2012-06-17  8:50     ` Torsten Bögershausen
2012-06-17 22:23       ` Junio C Hamano
2012-06-20 20:16         ` Torsten Bögershausen

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=7v1ull7j9k.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.om \
    --cc=vfr@lyx.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).