git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: problems installing git docs and gitweb on centos 5.5

From
DHDennis Huynh <dennis@brainstorm-digital.com>
Date
Sep 30, 2010, 14:22 UTC
Message-ID
<4CA49D39.1020403@brainstorm-digital.com>
In-Reply-To
<4CA41FCC.8050704@kernel.org>

Alright, I'm going with the Fedora EPEL repositories. But last I checked the latest version available via that method was 1.5.x. Since this is a server, I preferred to use the latest and greatest so to last in the long run from any major patches or cover any major upgrades, but if that's the version that's preferred, who am I to argue. One problem I recall in yum'ing the install for git however was the man pages weren't installed either. I could be wrong however. I'll keep you guys up to date. Wish me luck! Thanks for all your help and the timely responses.

Also, is there how-tos you'd suggest I use in setting up the git/gitweb combo with the yum install? I noticed yum installs files in different locations then the source does. Thanks again!

On 9/30/10 1:27 AM, J.H. wrote:
Show 66 quoted lines
> 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
>
>
>    
Previous: Jonathan NiederNext: J.H.
Message 5 of 8 in “problems installing git docs and gitweb on centos 5.5”
  1. Dennis HuynhSep 30, 2010
  2. Jonathan NiederSep 30, 2010
  3. J.H.Sep 30, 2010
  4. Jonathan NiederSep 30, 2010
  5. Dennis HuynhSep 30, 2010
  6. J.H.Sep 30, 2010
  7. Dennis HuynhSep 30, 2010
  8. Dennis HuynhOct 5, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.