On Mon, Jul 02, 2012 at 03:52:31PM -0400, Dan Johnson wrote: > > It builds correctly if you download the tarball from the official > > location in the [ANNOUNCE] message. This is because the build > > procedure for the official tarball does a bit more than just running > > "git archive-tar", which is what gitweb download interface does > > (namely, it adds the correct "version" file). > > I just noticed that the download buttons (for tarballs) on gitscm.com > all point to the github tag list ( https://github.com/git/git/tags ) > instead of the location pointed to by your [ANNOUNCE] message ( > http://code.google.com/p/git-core/downloads/list ) Ick. Yeah, I would think it would definitely want to point to Junio's built tarballs, because they contain the built 'configure' script. Otherwise, the downloader would need to have autoconf installed if they wanted to use configure. > If you do something special as part of releasing these tarballs, is > this something that should be corrected? I can look at the source and > do a pull request for gitscm.com a little later, if needed. I suspect that the tarballs link on git-scm.com should at the very least point to: http://code.google.com/p/git-core/downloads/list That list is a little overwhelming because it contains the html and manpage tarballs, too. It might make sense to provide a cut-down list (e.g., only source tarballs, and only the latest for each minor version, and omit -rc candidates for already-released versions). But that would be a lot more involved. -Peff -- 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