git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: fork0@t-online.de (Alex Riesen)
To: Junio C Hamano <junkio@cox.net>
Cc: Michal Rokos <michal.rokos@nextsoft.cz>, git@vger.kernel.org
Subject: Re: [Patch] Using 'perl' in *.sh
Date: Sun, 9 Jul 2006 11:46:30 +0200	[thread overview]
Message-ID: <20060709094630.GB5919@steel.home> (raw)
In-Reply-To: <7v3bdcq7dy.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano, Sat, Jul 08, 2006 20:27:37 +0200:
> >
> > some GIT's shell script are using bare 'perl' for perl invocation. It's 
> > causing me problems... I compile git with PERL_PATH set and I'd suggest to 
> > use it everywhere.
> >
> > So @@PERL@@ would be replaced with PERL_PATH_SQ instead.
> >
> > What do you think?
> 
> Absolutely.

Now imagine a non-posix system where an upgrade was made. Amongst
other things perl was moved, i.e. from /opt/perl-5.8.8 to
/usr/local/{bin,lib}. Suddenly git breaks.

  reply	other threads:[~2006-07-09  9:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-08 15:32 [Patch] Using 'perl' in *.sh Michal Rokos
2006-07-08 18:27 ` Junio C Hamano
2006-07-09  9:46   ` Alex Riesen [this message]
2006-07-09  9:51     ` Jan-Benedict Glaw
2006-07-09 10:14       ` Junio C Hamano
2006-07-09 12:41         ` Michal Rokos
2006-07-09 14:02           ` Randal L. Schwartz
2006-07-09 16:24             ` Jan-Benedict Glaw
2006-07-09 20:33           ` Junio C Hamano
2006-07-09 21:20             ` Jan-Benedict Glaw
2006-07-10  5:41             ` Michal Rokos
2006-07-10 13:09               ` Randal L. Schwartz
2006-07-10 13:16                 ` Johannes Schindelin
2006-07-10 13:29                   ` Randal L. Schwartz
2006-07-09 10:09     ` Yakov Lerner
2006-07-09 12:17       ` Alex Riesen

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=20060709094630.GB5919@steel.home \
    --to=fork0@t-online.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=michal.rokos@nextsoft.cz \
    --cc=raa.lkml@gmail.com \
    /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).