From: merlyn@stonehenge.com (Randal L. Schwartz)
To: git@vger.kernel.org
Subject: git installation (as private user) should NEVER write site_perl
Date: Tue, 20 Feb 2007 09:18:15 -0800 [thread overview]
Message-ID: <86sld0sq7c.fsf@blue.stonehenge.com> (raw)
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
But on a larger level, this should never have even been attempted, whether I
was a private user OR the box administrator. The git installation should NOT
be installing things into the site_perl directory, which is owned by the CPAN
installation tools, and also by the various packaging tools, and is also seen
by non-git users of Perl on the machine. (It would be bad to have two
different versions of Error.pm now being seen by all users.)
If git wants to add local Perl modules, they belong in ${prefix}/lib/perl/
or something, with the appropriate "use lib" added to the Perl scripts.
No patches attached, but this is a showstopper for my client, and a bit of a
shocker for me.
--
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 reply other threads:[~2007-02-20 17:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 17:18 Randal L. Schwartz [this message]
2007-02-20 17:55 ` git installation (as private user) should NEVER write site_perl 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
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=86sld0sq7c.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).