git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Building Git with HTTPS support: avoiding libcurl?

From
Thiago Farina <tfransosi@gmail.com>
Date
Dec 24, 2015, 22:36 UTC
Message-ID
<CACnwZYdLS7F-crNu0RjdYw__82nbaTujnjDc+q2jAXZ2Qoja+Q@mail.gmail.com>
In-Reply-To
<1450798780.11255.22.camel@mad-scientist.net>
On Tue, Dec 22, 2015 at 1:39 PM, Paul Smith <paul@mad-scientist.net> wrote:
Show 7 quoted lines
> I'm trying to build Git (2.6.4) on GNU/Linux, but without any
> requirements (other than basic libc etc.) on the local system.  This
> works fine except for one thing: git-remote-https.
>
> In order to build this I need to have libcurl, but libcurl is a MONSTER
> library with an enormous number of prerequisites (see below).
>

I think Git would have to be changed to use raw sockets and implement everything it needs on top of that, like libgit2 already does. Certainly this won't be a trivial task.

-- 
Thiago Farina
Previous: Johannes Schindelin
Message 6 of 6 in “Building Git with HTTPS support: avoiding libcurl?”
  1. Paul SmithDec 22, 2015
  2. Dave BorowitzDec 22, 2015
  3. Paul SmithDec 22, 2015
  4. Daniel StenbergDec 23, 2015
  5. Johannes SchindelinDec 23, 2015
  6. Thiago FarinaDec 24, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.