From: Jeff King <peff@peff.net>
To: Nicholas Harteau <nrh@ikami.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] perl/Makefile: use 'installsitelib' even with NO_PERL_MAKEMAKER
Date: Mon, 6 Feb 2012 15:26:10 -0500 [thread overview]
Message-ID: <20120206202610.GC30776@sigill.intra.peff.net> (raw)
In-Reply-To: <7328033C-8A11-452D-A927-E81E2DC4ABD6@spotify.com>
On Mon, Feb 06, 2012 at 02:38:20PM -0500, Nicholas Harteau wrote:
> > perl/Makefile installs Git.pm into $prefix/lib when ExtUtils::MakeMaker
> > is not present. perl can't "use Git;" in that scenario, as $prefix/lib
> > isn't in perl's include path.
> >
> > This patch installs Git.pm into perl's 'installsitelib', generally
> > $prefix/lib/perl5/site_perl, so that even when ExtUtils::MakeMaker isn't
> > present, Git.pm gets installed in a location where 'use Git;' just
> > works.
> [...]
> > ifdef NO_PERL_MAKEMAKER
> > -instdir_SQ = $(subst ','\'',$(prefix)/lib)
> > +instdir_SQ = $(subst ','\'',$(subst installsitelib=,'',$(shell $(PERL_PATH_SQ) -V:installsitelib)))
Isn't this a regression if I am a non-root user installing into
$HOME/local or similar? With MakeMaker, I end up with this in my
perl.mak:
PREFIX = /home/peff/local
...
SITEPREFIX = $(PREFIX)
...
INSTALLSITELIB = $(SITEPREFIX)/share/perl/5.14.2
which works great. Before your patch, without MakeMaker, git would
install into /home/peff/local/lib, which is also OK. But with your
patch, it will try:
$ perl -V:installsitelib
installsitelib='/usr/local/share/perl/5.14.2';
which is not writable by me, and the install will fail.
I know it's more convenient for some uses, because we know that
installsitelib will be in perl's @INC. But git has always installed out
of the box for non-root users, and I don't think we want to change that.
-Peff
next prev parent reply other threads:[~2012-02-06 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 10:51 [PATCH] use 'installsitelib' even with NO_PERL_MAKEMAKER Nicholas Harteau
2012-02-06 19:38 ` [PATCH] perl/Makefile: " Nicholas Harteau
2012-02-06 20:26 ` Jeff King [this message]
2012-02-06 20:30 ` Nicholas Harteau
2012-02-06 20:34 ` Jeff King
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=20120206202610.GC30776@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=nrh@ikami.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).