* curl
@ 2015-04-28 2:49 Thiago Farina
2015-04-28 4:57 ` curl Jeff King
0 siblings, 1 reply; 3+ messages in thread
From: Thiago Farina @ 2015-04-28 2:49 UTC (permalink / raw)
To: Git Mailing List
Hi,
Is it right that git uses libcurl to download while libgit2 does without it?
--
Thiago Farina
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: curl
2015-04-28 2:49 curl Thiago Farina
@ 2015-04-28 4:57 ` Jeff King
2015-04-28 9:27 ` curl Carlos Martín Nieto
0 siblings, 1 reply; 3+ messages in thread
From: Jeff King @ 2015-04-28 4:57 UTC (permalink / raw)
To: Thiago Farina; +Cc: Carlos Martín Nieto, Git Mailing List
On Mon, Apr 27, 2015 at 11:49:51PM -0300, Thiago Farina wrote:
> Is it right that git uses libcurl to download while libgit2 does without it?
I'm not sure if you mean "right" as in "this statement is true" or as in
"is this a good thing that it is the case".
For the former, yes, libgit2 does not use curl. On Windows, it can use
the native http calls (which do nice things like using the system proxy
and auth systems). On Unix, I think it is a combination of hand-rolled
code, openssl, and an imported http parser (from nginx).
Whether that is a good idea or not, I can't comment too much. From what
I have seen discussed in libgit2 issues, the stock http transport is
meant to be bare-bones (but with minimal dependencies). But it could
co-exist with a curl transport (just as it does with the WinHTTP
transport). Maybe Carlos (cc'd) can say more.
-Peff
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: curl
2015-04-28 4:57 ` curl Jeff King
@ 2015-04-28 9:27 ` Carlos Martín Nieto
0 siblings, 0 replies; 3+ messages in thread
From: Carlos Martín Nieto @ 2015-04-28 9:27 UTC (permalink / raw)
To: Jeff King; +Cc: Thiago Farina, Git Mailing List
On Tue, 2015-04-28 at 00:57 -0400, Jeff King wrote:
> On Mon, Apr 27, 2015 at 11:49:51PM -0300, Thiago Farina wrote:
>
> > Is it right that git uses libcurl to download while libgit2 does without it?
>
> I'm not sure if you mean "right" as in "this statement is true" or as in
> "is this a good thing that it is the case".
>
> For the former, yes, libgit2 does not use curl. On Windows, it can use
> the native http calls (which do nice things like using the system proxy
> and auth systems). On Unix, I think it is a combination of hand-rolled
> code, openssl, and an imported http parser (from nginx).
>
> Whether that is a good idea or not, I can't comment too much. From what
> I have seen discussed in libgit2 issues, the stock http transport is
> meant to be bare-bones (but with minimal dependencies). But it could
> co-exist with a curl transport (just as it does with the WinHTTP
> transport). Maybe Carlos (cc'd) can say more.
This is accurate, though I'll add that the development version of
libgit2 now uses SecureTransport instead of OpenSSL on Mac OS X.
But this is just the default. You can replace what libgit2 will use as a
transport if you have special needs. Visual Studio use their own network
code, and the cargo package manager uses libcurl. Eventually libcurl
support will likely be added to mainline libgit2, when we find time.
cmn
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-04-28 9:27 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-04-28 2:49 curl Thiago Farina
2015-04-28 4:57 ` curl Jeff King
2015-04-28 9:27 ` curl Carlos Martín Nieto
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).