Hi Nigel, You've convinced me that this probably shouldn't go into the tree.
Nigel Taylor writes: > If you look in git repositories like github, the tar ball created > automatically is not the same as the tar ball distributed, they have > some process for creating the distribution tar ball and including just > those autoconf archive macros required, so doing a git clone of github > project, and building within the clone you might need the autoconf > archive, this is not about building ports. Unfortunately, this is a common problem on Github: they tend *not* to provide dist tarballs, and they don't keep generated configure scripts in Git. So you have no choice but to fetch the autogenerated "tarballs" of the source using GH_*, and run autoconf yourself. Yet another example of bad upstream behavior that we have to push against to keep our sanity... -- Anthony J. Bentley
