From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Erik Mouw <mouw@nl.linux.org>
Cc: git@vger.kernel.org
Subject: Re: git installation (as private user) should NEVER write site_perl
Date: Tue, 20 Feb 2007 09:57:46 -0800 [thread overview]
Message-ID: <86abz8sodh.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <20070220175536.GC26444@gateway.home> (Erik Mouw's message of "Tue, 20 Feb 2007 18:55:37 +0100")
>>>>> "Erik" == Erik Mouw <mouw@nl.linux.org> writes:
Erik> On Tue, Feb 20, 2007 at 09:18:15AM -0800, Randal L. Schwartz wrote:
>> I tried to install git on a system where I was a normal user. Of course,
>> this step fails:
>>
>> Installing /usr/perl5/site_perl/5.6.1/Error.pm
>> Installing /usr/perl5/site_perl/5.6.1/Git.pm
Erik> It gets installed in ~/share/perl/5.8.4/ when I compile as a normal
Erik> user (git-1.5.0.1):
Erik> Installing /home/erik/share/perl/5.8.4/Error.pm
Erik> Installing /home/erik/share/perl/5.8.4/Git.pm
Erik> Installing /home/erik/man/man3/private-Error.3pm
Erik> Installing /home/erik/man/man3/Git.3pm
Is that a personally-installed Perl though? Those paths look suspicious.
--
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 17:58 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 [this message]
2007-02-20 18:12 ` Erik Mouw
2007-02-20 18:21 ` Junio C Hamano
2007-02-20 18:08 ` Randal L. Schwartz
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=86abz8sodh.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=git@vger.kernel.org \
--cc=mouw@nl.linux.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).