Making cabal-install SSL capable
michael at snoyman.com
Tue Apr 28 08:21:04 UTC 2015
On Tue, Apr 28, 2015 at 11:12 AM Herbert Valerio Riedel <hvriedel at gmail.com>
> On 2015-04-28 at 06:08:38 +0200, Michael Snoyman wrote:
> > I offered Duncan last week that I'd port cabal-install over to
> > http-client/http-client-tls to add SSL support. That offer still stands.
> I did a quick check trying to find out the additional dependencies
> (relative to what 'cabal-install' currently depends on) http-client-tls
> would pull in (it seems http-client and tls each roughly account for
> half the ~50 deps below):
> In contrast, I was surprised to see, that extending the HTTP package (or
> maybe just writing a 'HTTPS'-companion package) to use HsOpenSSL seems
> to pull in 'HsOpenSSL' as the only additional package...
> For comparision here's what http-streams (which I'm not suggesting right
> now, as I think going the 'HTTP'+'HsOpenSSL'-route would be better
> currently) would pull in (which could have a few deps less if it didn't
> pull in 'aeson'...):
I have no intention of playing the "minimal dependency" game (though I
don't mind dropping data-default, which accounts for 6 of the dependencies
listed there). I will point out- as Gershom already did- that in many cases
it's likely easier to install a few extra Haskell packages than it is to
pull in OpenSSL as a dependency, especially on Windows. (And that's
ignoring the fact that http-client-openssl exists.)
As a historical point of interest, I originally wrote http-client (or, as
it was called at the time, http-enumerator) because I was trying to add
OpenID support to an application, and the openid package had done
exactly what you've described: add HsOpenSSL to the HTTP package. I could
never get a single connection to work with that combination. But maybe a
brand new approach at writing that code will work.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cabal-devel