git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J.H." <warthog9@kernel.org>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Dennis Huynh <dennis@brainstorm-digital.com>, git@vger.kernel.org
Subject: Re: problems installing git docs and gitweb on centos 5.5
Date: Wed, 29 Sep 2010 22:27:40 -0700	[thread overview]
Message-ID: <4CA41FCC.8050704@kernel.org> (raw)
In-Reply-To: <20100930024059.GA2373@burratino>

On 09/29/2010 07:40 PM, Jonathan Nieder wrote:
> (-cc: security@centos)
> 
> Hi Dennis,
> 
> Dennis Huynh wrote:
> 
>> Am I the only one having issues installing git docs?
> 
> Here's my advice:
> 
>  1. Breathe in, breathe out.
>  2. Look at the INSTALL file, section beginning "To build and install
>     documentation suite".  Among other things, it describes how to
>     retrieve pre-formatted documentation from the git.git repository
>     itself.  So you can try:
> 
> 	git clone git://git2.kernel.org/pub/scm/git/git.git

For the love of monkeys do *NOT* point people at specific git machines
like that.  Use git://git.kernel.org/pub/scm/git/git.git using a
specific machine causes a giant amount of headaches for me and
completely ruins any attempt at load balancing I might be able to
accomplish.

Couple that with the fact it will steer people to the wrong server if
they aren't in North America, it's just not a good idea.  Period.

> 	cd git
> 	make quick-install-doc
> 
>     after installing git, which should be relatively painless.
>  3. Look at gitweb/INSTALL.  The moment something seems unclear, note
>     that, so we can come up with a patch to make it clearer for the
>     next person.

As an overall note, git and gitweb, including my caching version of
gitweb are available in Fedora EPEL as rpm packages.  These are official
packages for Redhat / CentOS / Distro based on those things.  You
shouldn't need to compile your own really.

Unless you need the latest and greatest I would try those.  If you
really need the latest you might be better off grabbing the latest
.src.rpm from here:

http://www.kernel.org/pub/software/scm/git/RPMS/SRPMS/

http://www.kernel.org/pub/software/scm/git/RPMS/SRPMS/git-1.7.3.1-1.fc11.src.rpm

and doing an rpmbuild --rebuild git-1.7.3.1-1.fc11.src.rpm on it and
installing the rpm that it builds.

I'm not saying doing it completely from source is bad, but deviating
from what your distro uses / provides can cause other headaches and
maintenance issues down the line.

Bonus to going the RPM rebuild route is that it will tell you what your
missing to do the rebuild with.

- John 'Warthog9' Hawley

  reply	other threads:[~2010-09-30  6:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30  2:03 problems installing git docs and gitweb on centos 5.5 Dennis Huynh
2010-09-30  2:40 ` Jonathan Nieder
2010-09-30  5:27   ` J.H. [this message]
2010-09-30 12:38     ` Jonathan Nieder
2010-09-30 14:22     ` Dennis Huynh
2010-09-30 22:35       ` J.H.
2010-09-30 22:44         ` Dennis Huynh
2010-10-05 20:28           ` Dennis Huynh

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=4CA41FCC.8050704@kernel.org \
    --to=warthog9@kernel.org \
    --cc=dennis@brainstorm-digital.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.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).