Re: [RFC] dropping support for ancient versions of curl

From: Tom G. Christensen <tgc@jupiterrise.com>
Date: Apr 5, 2017, 09:33 UTC
Message-ID: <d6ba17f0-3da9-8699-8d5c-5ebf1eaef00e@jupiterrise.com>
In-Reply-To: <20170404025438.bgxz5sfmrawqswcj@sigill.intra.peff.net>

On 04/04/17 04:54, Jeff King wrote:

Show 12 quoted lines

> A nearby thread raised the question of whether we can rely on a version
> of libcurl that contains a particular feature. The version in question
> is curl 7.11.1, which came out in March 2004.
>
> My feeling is that this is old enough to stop caring about. Which means
> we can drop some of the #ifdefs that clutter the HTTP code (and there's
> a patch at the end of this mail dropping support for everything older
> than 7.11.1). But that made wonder: how old is too old? I think it's
> nice that we don't force people to upgrade to the latest version of
> curl. But at some point, if you are running a 13-year-old version of
> libcurl, how likely are you to run a brand new version of Git? :)
>

FWIW I maintain freely available updated git packages for RHEL 3, 4, 5, 6 and 7.

They can be found here: https://jupiterrise.com/blog/jrpms/

And direct access here: https://jupiterrise.com/jrpms/ (for el3,el4,el5) https://jupiterrise.com/jrpmsplus/ (for el6, el7)

They are built against system versions of curl though a few patches are required for 7.10.6 (el3) and 7.12.1 (el4) support. Patches can be found in the src.rpm, though I can also post them here as patch series, they cover more than just curl.

I don't use the el3 and el4 versions much any more and el5 use will also drop of now as I'm busy converting machines from el5 to el7.

-tgc