From: merlyn@stonehenge.com (Randal L. Schwartz)
To: git@vger.kernel.org
Subject: Re: git installation (as private user) should NEVER write site_perl
Date: Tue, 20 Feb 2007 10:08:20 -0800 [thread overview]
Message-ID: <863b50snvv.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <86sld0sq7c.fsf@blue.stonehenge.com> (Randal L. Schwartz's message of "Tue, 20 Feb 2007 09:18:15 -0800")
>>>>> "Randal" == Randal L Schwartz <merlyn@stonehenge.com> writes:
Randal> If git wants to add local Perl modules, they belong in
Randal> ${prefix}/lib/perl/ or something, with the appropriate "use lib" added
Randal> to the Perl scripts.
>From a bit further research, it looks like git prefers installing git-only
Perl modules using the standard MakeMaker, which of course will try to
install them in site_lib.
Oddly enough, if I define NO_PERL_MAKEMAKER, I get the behavior I want.
I suggest that NO_PERL_MAKEMAKER is the *only* correct behavior in this case,
so I propose that the code be made unconditional, and the Makemaker stuff be
pulled out.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2007-02-20 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 17:18 git installation (as private user) should NEVER write site_perl Randal L. Schwartz
2007-02-20 17:55 ` Erik Mouw
2007-02-20 17:57 ` Randal L. Schwartz
2007-02-20 18:12 ` Erik Mouw
2007-02-20 18:21 ` Junio C Hamano
2007-02-20 18:08 ` Randal L. Schwartz [this message]
2007-02-20 18:53 ` Randal L. Schwartz
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=863b50snvv.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--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 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).