git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "martin f. krafft" <madduck@madduck.net>
To: git@vger.kernel.org
Subject: [PATCH] Install man3 manpages to $PREFIX/share/man/man3 even for site installs
Date: Thu, 19 Jul 2007 14:45:50 +0200	[thread overview]
Message-ID: <11848491502417-git-send-email-madduck@madduck.net> (raw)

MakeMaker supports three installation modes: perl, site, and vendor. The first
and third install manpages to $PREFIX/share/man, only site installs to
$PREFIX/man. For consistency with the rest of git, which does not make the
distinction and writes all manpages to $PREFIX/share/man, this change makes
sure that perl does too, even when it's installed in site mode.

Signed-off-by: martin f. krafft <madduck@madduck.net>
---
 perl/Makefile.PL |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/perl/Makefile.PL b/perl/Makefile.PL
index 4375161..6aecd89 100644
--- a/perl/Makefile.PL
+++ b/perl/Makefile.PL
@@ -29,5 +29,6 @@ WriteMakefile(
 	VERSION_FROM    => 'Git.pm',
 	PM		=> \%pm,
 	MAKEFILE	=> 'perl.mak',
+	INSTALLSITEMAN3DIR => '$(SITEPREFIX)/share/man/man3',
 	%extra
 );
-- 
1.5.3.rc2.19.gc4fba-dirty

             reply	other threads:[~2007-07-19 12:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19 12:45 martin f. krafft [this message]
2007-07-20  0:42 ` [PATCH] Install man3 manpages to $PREFIX/share/man/man3 even for site installs Junio C Hamano
2007-07-20  0:46   ` Randal L. Schwartz
  -- strict thread matches above, loose matches on Subject: below --
2007-08-20  7:23 Install section 3 manpages to .../share/man for consistency martin f. krafft
2007-08-20  7:23 ` [PATCH] Install man3 manpages to $PREFIX/share/man/man3 even for site installs martin f. krafft
2007-08-23  8:11   ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=11848491502417-git-send-email-madduck@madduck.net \
    --to=madduck@madduck.net \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).