From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
"Randall S. Becker" <the.n.e.key@gmail.com>,
git@vger.kernel.org,
"Randall S. Becker" <randall.becker@nexbridge.ca>,
"Randall S . Becker" <rsbecker@nexbridge.com>
Subject: Re: [PATCH v2 1/2] Teach git version --build-options about libcurl
Date: Mon, 24 Jun 2024 19:55:57 -0400 [thread overview]
Message-ID: <20240624235557.GA2727@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqqed8me36c.fsf@gitster.g>
On Mon, Jun 24, 2024 at 09:06:03AM -0700, Junio C Hamano wrote:
> > Wouldn't calling `curl_version()` make more sense here?
>
> I wouldn't give that question an outright "no", but unless "git
> version" is split out of the builtin suite of commands and made into
> a standalone binary, I would *not* be able to give an unconditional
> "yes".
>
> For now, let's stop at the simplest solution---if the library
> project gives us a CPP macro to use for _this exact purpose_, let's
> take the offer.
Here's another point of view: libcurl is not a dependency of the git
binary at all! It is a dependency of the "curl" remote helper. Would it
make sense for "git remote-https --build-options" to exist?
I'm not sure. It resolves the linking problem and matches how the actual
programs are structured. But it is also not something that normal users
would tend to think about (even if you are having trouble with https
remotes, you might not know that is implemented as a remote helper).
But we could also have "git version --build-options" call "remote-https
--build-options" automatically, and just let it dump to the shared
stdout stream.
-Peff
next prev parent reply other threads:[~2024-06-24 23:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 18:09 [PATCH v2 0/2] Teach git version --build-options about zlib+libcurl Randall S. Becker
2024-06-21 18:09 ` [PATCH v2 1/2] Teach git version --build-options about libcurl Randall S. Becker
2024-06-24 14:13 ` Johannes Schindelin
2024-06-24 14:33 ` Randall Becker
2024-06-24 17:08 ` Dragan Simic
2024-06-24 21:15 ` rsbecker
2024-06-24 21:52 ` Dragan Simic
2024-06-24 21:56 ` Randall Becker
2024-07-24 10:51 ` Johannes Schindelin
2024-06-24 15:29 ` Jeff King
2024-06-24 16:06 ` Junio C Hamano
2024-06-24 23:55 ` Jeff King [this message]
2024-06-25 0:00 ` Junio C Hamano
2024-07-24 10:48 ` Johannes Schindelin
2024-07-24 20:55 ` Jeff King
2024-07-24 22:17 ` Johannes Schindelin
2024-07-25 6:52 ` Jeff King
2024-07-25 15:28 ` Junio C Hamano
2024-07-26 0:41 ` Jeff King
2024-06-21 18:09 ` [PATCH v2 2/2] Teach git version --build-options about zlib versions Randall S. Becker
2024-06-24 14:15 ` Johannes Schindelin
2024-06-24 14:38 ` Randall Becker
2024-07-24 11:02 ` Johannes Schindelin
2024-07-24 13:36 ` Randall Becker
2024-07-24 16:21 ` Junio C Hamano
2024-07-24 16:33 ` rsbecker
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=20240624235557.GA2727@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=randall.becker@nexbridge.ca \
--cc=rsbecker@nexbridge.com \
--cc=the.n.e.key@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).