From: Andrew Ruder <andy@aeruder.net>
To: git <git@vger.kernel.org>
Subject: Re: [PATCH] Try 2: Allow PERL_PATH="/usr/bin/env perl"
Date: Thu, 3 May 2007 19:03:39 -0500 [thread overview]
Message-ID: <20070504000339.GA2476@localdomain> (raw)
In-Reply-To: <7vfy6dzf25.fsf@assigned-by-dhcp.cox.net>
On Thu, May 03, 2007 at 04:02:26PM -0700, Junio C Hamano wrote:
> I do not get this whole business. Why would you even want to
> support that to begin with?
The biggest problem being that on macs it is typical to have two copies
of perl installed (/usr/bin/perl and /opt/local/bin/perl with
DarwinPorts or otherwise). It'd be nice to have a way to tell git
makefiles to put #!/usr/bin/env perl at the top so it just pulls
what is first in the path rather than having to hardcode it to either
/opt/local/bin/perl or /usr/bin/perl.
Say you are packaging a mac os x package of git. Now for the user to
run something like git-svn they'd need the svn bindings obviously, but
of course, some people install them against their system perl, lots of
people install them against their darwinports or otherwise, and it'd be
really nice to just have those various perl scripts use whatever the
person has set up (going by what they have first in their path).
- Andy
--
Andrew Ruder <andy@aeruder.net>
http://www.aeruder.net
next prev parent reply other threads:[~2007-05-04 0:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 22:58 [PATCH] Try 2: Allow PERL_PATH="/usr/bin/env perl" Bryan Larsen
2007-05-03 23:02 ` Junio C Hamano
2007-05-03 23:35 ` Bryan Larsen
2007-05-04 0:43 ` Junio C Hamano
2007-05-04 3:30 ` Bryan Larsen
2007-05-04 0:03 ` Andrew Ruder [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-03 23:00 Bryan Larsen
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=20070504000339.GA2476@localdomain \
--to=andy@aeruder.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.