From: Jeff King <peff@peff.net>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: git@vger.kernel.org
Subject: Re: better way to find Git.pm officially?
Date: Thu, 29 Mar 2012 02:13:36 -0400 [thread overview]
Message-ID: <20120329061336.GE27604@sigill.intra.peff.net> (raw)
In-Reply-To: <86r4wc9f6j.fsf@red.stonehenge.com>
On Wed, Mar 28, 2012 at 09:58:12PM -0700, Randal L. Schwartz wrote:
> As in, find the git-svn binary (via git --exec-path), parse its second
> line to see where the git installer put the GITPERLLIB, and then add
> that myself.
>
> Is there a simpler way? Can we get "git --perl-path" added to the
> binary or something?
I always assumed that it was the responsibility of the user or the
packager to put Git.pm into a sane place that is found by perl's normal
lookup (possibly via the user's PERL5LIB if it is a per-user
installation). Doesn't our use of MakeMaker generally pick such a
suitable directory?
-Peff
next prev parent reply other threads:[~2012-03-29 6:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 4:58 better way to find Git.pm officially? Randal L. Schwartz
2012-03-29 5:10 ` André Walker
2012-03-29 6:13 ` Jeff King [this message]
2012-03-29 6:45 ` Junio C Hamano
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=20120329061336.GE27604@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.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).