Git development
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Alejandro R. Sedeño" <asedeno@mit.edu>
Cc: Git List <git@vger.kernel.org>
Subject: Re: minimum curl version effectively changed
Date: Thu, 10 Oct 2024 21:52:24 +0000	[thread overview]
Message-ID: <ZwhMmGt0kZvaSzSL@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <CAOO-Oz1KhFcyErVx1Qb142PtPJS=UpgSD-FacckqNS4_okAtFQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]

On 2024-10-10 at 21:30:04, Alejandro R. Sedeño wrote:
> I have a patch I plan to send in tomorrow that will properly
> conditionalize using the symbol on versions of curl that have it, and
> emitting a warning otherwise. It will also follow up with some
> corrections to errors in git-curl-compat.h.
> 
> I don't think a new feature should unilaterally change the minimum
> requirements of git without some announcement and forethought.

We already have a platform support policy, which guides our behaviour
here, and it was discussed very recently.  It says this:

  Uses versions of dependencies which are generally accepted as stable and
  supportable, e.g., in line with the version used by other long-term-support
  distributions

No major Linux distributions are still using such an old version of
libcurl.  CentOS 7 is dead, and we don't typically support extended
long-term support because it comes at a cost, and it's not fair to
Git developers to require them to pay for a secure system to test
against.  I don't know of any other major OS which is providing support
for such an old version of curl either.  Usually the BSDs have a much
shorter life span for versions, for example.

So I think the oldest supported version we're going to be willing to
accept is in a clone of RHEL 8, which would be curl 7.61.  It's
certainly a mistake on our part that we neglected to update INSTALL
accordingly, but it's not a mistake that we unconditionally added
support for a feature from over a decade ago.
-- 
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

      reply	other threads:[~2024-10-10 21:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10 18:24 minimum curl version effectively changed Alejandro R. Sedeño
2024-10-10 21:23 ` brian m. carlson
2024-10-10 21:30   ` Alejandro R. Sedeño
2024-10-10 21:52     ` brian m. carlson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZwhMmGt0kZvaSzSL@tapette.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=asedeno@mit.edu \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox