Making cabal-install SSL capable

[Gershom B]

I've been happily using the curl backend for a bit now and it seems to work
fine, so I'd like to get this polished and committed.

Since the curl backend works, then even if the wget and powershell backends
aren't fully tested, the workaround can just be to tell users to install
curl and make sure it is in their path (or to pass the insecure-http option
that falls back to the existing implementation).

So perhaps we can just patch cabal to warn on using wget or powershell
backends that if there are issues they should try one of the fully finished
options, and then we can merge?

Alternately, someone can jump in and try to give a hand with the other two
backends -- they're very close.

-g


On Fri, May 8, 2015 at 12:46 PM, Mikhail Glushenkov <
the.dead.shall.rise at gmail.com> wrote:

> On 8 May 2015 at 00:14, Gershom B <gershomb at gmail.com> wrote:
> > On my branch now, everything "should" work:
> > https://github.com/gbaz/Cabal/tree/https
>
> Thanks for working on this. I only had time to take a brief glance,
> but everything looks good so far. Hope we can merge your patches soon.
>
> > (note that even though I branched before the digest fix, I ported it
> over to
> > this branch, so that the insecure-http transport _should_ be using digest
> > auth properly already).
>
> You could've just rebased (which is a good practice anyway).
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/cabal-devel/attachments/20150518/078f8ca9/attachment.html>