git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: "C. Benson Manica" <cbmanica@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: progit build instructions and ExtUtils::MakeMaker
Date: Wed, 18 Jun 2014 04:01:56 -0400	[thread overview]
Message-ID: <20140618080156.GA11027@sigill.intra.peff.net> (raw)
In-Reply-To: <CA+kozekeTOBZFauhU2EY18hTzhpZ-VUnbBH91CtErnD4UGSNsw@mail.gmail.com>

[I added a subject to the thread; that is likely part of why you didn't
 get any responses sooner]

On Sun, Jun 01, 2014 at 02:24:54PM -0700, C. Benson Manica wrote:

> The documentation for installing git from source here,
> http://git-scm.com/book/en/Getting-Started-Installing-Git, incorrectly
> fails to mention that the MakeMaker perl module is also required and
> is installable via
> 
> $ yum install perl-ExtUtils-MakeMaker

The content at git-scm.com/book is pulled from the Creative Commons "Pro
Git" book. Errata and corrections are generally handled by opening an
issue there:

  https://github.com/progit/progit/issues

Note that ExtUtils::MakeMaker is part of the perl core (and has been for
quite a long time). So on many systems, I would not expect it to need to
be installed separately. If you propose a change for Pro Git, you may
want to find out which systems package it separately and which do not
(Debian, for example, does not, but it also does not use yum).

> Also, you might want to let people know that you've configured your
> mail system for 1987 mode and do not accept HTML-formatted mail.

Come on, MIME wasn't standardized until 1996. We're easily state of the
art for the mid-1990's. :)

-Peff

      reply	other threads:[~2014-06-18  8:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-01 21:24 (unknown), C. Benson Manica
2014-06-18  8:01 ` Jeff King [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=20140618080156.GA11027@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=cbmanica@gmail.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).