On Thu, 12 Mar 2009, Mike Ralphson wrote:
May I suggest perhaps require a libcurl version that is no older than three
years or something like that?
It might be a plan 8-) Though I was thinking technically in terms of
features we think git needs. Though doubtless there are several security
fixes it would be beneficial to keep up to date with.
Right, but if you set a common lowest denominator first you know what features
to expect to be there _at least_, then there might of course be a set of
additional ones brought by newer versions. It would reduce the amount of
conditionals in the code and what-if-this-is-used scenarios (in the code and
in support/docs). It also reduces the risks of git getting odd problems due to
very old libcurl bugs.
(spoiler: libcurl 7.9.3 is more than seven years old!)
And still the release IBM package for AIX [1]. 8-(
However, someone who's building/getting git might also be able to build/get a
newer libcurl.
The summary of automatic builds (http://curl.haxx.se/auto/) is very nicely
presented. Is that custom code?
The code is custom (perl) but present in the curl CVS repo for the web site
and could probably fairly easy be adapted for other purposes/projects.
In the curl project we provide scripts for distributed automatic tests and
then we have a central server that receives the reports by mail and the
automatic summary script displays the status of those tests on that page.
--
/ daniel.haxx.se
--
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
