From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: Quick merge status updates.
Date: Sun, 02 Jul 2006 17:06:01 -0700 [thread overview]
Message-ID: <7v1wt31riu.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0607021655440.12404@g5.osdl.org> (Linus Torvalds's message of "Sun, 2 Jul 2006 17:00:40 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> On Sun, 2 Jul 2006, Junio C Hamano wrote:
>> Yuck; that means we would need to have something evil like this.
>
> That's just disgusting.
>
> How about a _much_ simpler approach.
>
> Just make it do
>
> BEGIN { push ENV{'GIT_PERL_EXEC_DIR'}; }
>
> And then simply _require_ that the setup code sets up GIT_PERL_EXEC_DIR.
No, we are not mucking with /usr/bin but are talking about a
directory for platform specific Perl libraries, which we need to
ask Perl at build-time.
And the standard way to say that is to do:
use lib '@@INSTLIBDIR@@';
but that always prepends the directory to the search path, and
the ugly stuff is to allow test scripts to override it when
needed.
next prev parent reply other threads:[~2006-07-03 0:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 21:40 Making perl scripts include the correct Git.pm Petr Baudis
2006-07-03 0:02 ` Junio C Hamano
2006-06-28 0:23 ` Quick merge status updates Junio C Hamano
2006-06-28 5:04 ` Pavel Roskin
2006-06-28 8:49 ` Junio C Hamano
2006-06-28 10:05 ` Pavel Roskin
2006-06-28 10:14 ` Junio C Hamano
2006-07-02 20:49 ` Petr Baudis
2006-07-02 21:33 ` Junio C Hamano
2006-07-02 21:49 ` Petr Baudis
2006-07-02 22:50 ` Junio C Hamano
2006-07-02 23:49 ` Junio C Hamano
2006-07-03 0:00 ` Linus Torvalds
2006-07-03 0:06 ` Junio C Hamano [this message]
2006-07-03 20:29 ` Petr Baudis
2006-07-03 21:16 ` [PATCH] Use $GITPERLLIB instead of $RUNNING_GIT_TESTS and centralize @INC munging Petr Baudis
2006-07-08 7:36 ` Quick merge status updates Pavel Roskin
2006-06-28 7:32 ` Johannes Schindelin
2006-06-28 7:39 ` Johannes Schindelin
2006-06-28 8:51 ` Junio C Hamano
2006-06-28 9:13 ` Johannes Schindelin
2006-07-01 23:48 ` [PATCH] Git.pm: Avoid ppport.h Petr Baudis
2006-07-02 9:52 ` Johannes Schindelin
2006-07-02 19:05 ` Junio C Hamano
2006-07-02 20:57 ` [PATCH] Git.pm: Don't #define around die Petr Baudis
2006-07-03 1:38 ` Making perl scripts include the correct Git.pm Junio C Hamano
2006-07-04 19:01 ` Marco Costalba
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=7v1wt31riu.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).