On Tue, Aug 09, 2005 at 10:13:32AM -0700, Junio C Hamano wrote: > Junio C Hamano <[EMAIL PROTECTED]> writes: > > >> But the resulting RPM cannot be installed either, at least not in > >> standard Fedora Core 2/3/4 installations: > >> ... > >> Is there at least some documentation which external packages are > >> needed, and where to find these? > > The problematic one is git-send-email-script.
Yup. I'll take the blame for that one - I forget how inclusive the Debian packaging is compared to the other distributions. > I have to admit that it was a mistake to take that patch; I was > trying to be _too_ inclusive. The script does not even read > from nor write into a git repository, and the only relevance to > git is that it is useful for people to patchbomb the list with > git generated patches. In other words, the program may be > useful, but its usefulness does not have much to do with git, so > it does not belong to git. Well, here I think I disagree. I think it's a valid, possibly vital, part of the suggested workflow for maintainers of projects. Admittedly, the emails can be sent by hand in many cases - but for the "clean up the history" goal of exporting things out as patches, the email step is important. > My short-term plan is to downgrade it to "contrib" status, and > not touch it from the main Makefile. It will be in the 0.99.4 > sources but will not be installed nor made into binary package. > I hope Ryan does not mind this decision. Not at all. I agree that the RPM dependency problem is a good reason to not install it by default. What I will do is make this the beginning of my directory structure reorganization. I'll probably also convert the Debian package to a multi-package system, so we have a demonstration of splitting these two items up. -- Ryan Anderson sometimes Pug Majere - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html