#15100: Define USE_CURL_MULTI for git-core --------------------------------+------------------------------------------- Reporter: svoop@delirium.ch | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.6.0 Resolution: | Keywords: git git-core curl --------------------------------+------------------------------------------- Changes (by raimue@macports.org): * cc: raimue@macports.org (added) Comment: There is `patch-http.h.diff` which explicitely removes the USE_CURL_MULTI option. I don't know if there is/was a valid reason to do so? -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/15100#comment:3> MacPorts </projects/macports> Ports system for Mac OS

#15100: Define USE_CURL_MULTI for git-core --------------------------------+------------------------------------------- Reporter: svoop@delirium.ch | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.6.0 Resolution: | Keywords: git git-core curl --------------------------------+------------------------------------------- Comment (by bryan@larsen.st): ticket 12008 did not introduce the patch: 12008 was simply a refactoring of previous patches to match the macports policy. The patches used to be arranged by function, now they are arranged by file. USE_CURL_MULTI used to be horribly broken, causing severe data corruption. Curl v7.16.0 was supposed to make USE_CURL_MULTI functional, but that caused severe data corruption, but on a much less frequent basis. Reproducing the bug required a very large checkout on a powerpc mac. By very large, I mean much larger than linux-kernel: I used an embedded linux distribution (which included 3 different linux kernel sources, 3 different libc's and hundreds of apps) for my testing. Intel macs appeared to work fine. Curl v7.16.2 may have fixed the problem, but the decision was made not to trust it since nobody had the days of effort required to do an exhaustive test. At that time, disabling multi only slowed down checkouts. We've had 8 releases of Curl since 7.16.0, most of which include some sort of patch to multi. So it's probably working fine now. Unfortunately, testing to make sure takes hours. Does somebody have the time to do so? -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/15100#comment:5> MacPorts </projects/macports> Ports system for Mac OS