All of lore.kernel.org
 help / color / mirror / Atom feed
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:53:29 -0800	[thread overview]
Message-ID: <86y7msr786.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <863b50snvv.fsf@blue.stonehenge.com> (Randal L. Schwartz's message of "Tue, 20 Feb 2007 10:08:20 -0800")

>>>>> "Randal" == Randal L Schwartz <merlyn@stonehenge.com> writes:

>>>>> "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.

Randal> Oddly enough, if I define NO_PERL_MAKEMAKER, I get the behavior I want.

Randal> I suggest that NO_PERL_MAKEMAKER is the *only* correct behavior in this case,
Randal> so I propose that the code be made unconditional, and the Makemaker stuff be
Randal> pulled out.

So, something spookier is happening on this solaris box then.  I can
see that if MakeMaker is used, the Makefile.PL is referring to INST_LIBDIR
which should indeed be private inside git's area.  And in fact, I can
verify on my laptop that Git.pm was indeed installed into /opt/git/lib/site_perl/5.8.8/

I don't know why this isn't working on solaris. :( It might be that the
MakeMaker is too old, and doesn't respect the same prefix elements.

Call off the hounds... I can locally work around it by setting
NO_PERL_MAKEMAKER, and suspect I won't have anything further to contribute to
the core on this matter.

-- 
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!

      reply	other threads:[~2007-02-20 18:53 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
2007-02-20 18:53   ` Randal L. Schwartz [this message]

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=86y7msr786.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.