On Fri, 2011-03-18 at 10:51 -0400, Todd Zullinger wrote: > Hi Drew, > > Drew Northup wrote: > > At the very least I'm considering making a man page for the > > configuration file. I don't know off-hand how much that will be > > seemingly repetitive of the README, but I suspect I'm not the only > > one who often finds monolithic files tucked away in /usr/share/doc > > (/usr/doc for some systems) a daunting reading prospect > [...] > > FWIW, with git-1.7.4.1 in EPEL we now include a commented > /etc/gitweb.conf in the package. This wasn't present in the very old > 1.5.5.6 we had in EPEL until recently. This config file doesn't list > all the available options, but it does point to the README and INSTALL > files for further help. I did find that following Jonathan's prompting. I hadn't been using the EPEL git packages but had been building my own. Alas I also haven't figured out yet how to auto-exclude individual package sets from upgrade via channel (something for a discussion somewhere else--when I have time to mess with it) and I missed the new EPEL ones in the list. (It's my test/dev box so I let it run packages there for a while first before rolling them out elsewhere.) > (Also worth noting is that the package was in the epel-testing > repository for 3 weeks and was announced on both epel-devel and > epel-announce to try and get testing from folks before pushing it > stable. Sadly, very few folks do so, and issues are sometimes not > caught.) > > Sorry if the update caused you trouble. The main thing that annoyed me was that EPEL and git's "make rpm" seem to still have very different ideas about where stuff belongs on a machine. I wish I had more time to read the "epel-testing" release notes, but that wouldn't have actually helped me in this case. -- -Drew Northup ________________________________________________ "As opposed to vegetable or mineral error?" -John Pescatore, SANS NewsBites Vol. 12 Num. 59 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html