[darcs-users] Re: DARCS_PUSH_HTTPS="curl -d @-" via internal libcurl?

[Adam Megacz]

>     Adam> Is there a way to get darcs to wrap up a bundle of patches
>     Adam> and transmit them via HTTPS POST to the URL associated with
>     Adam> a repository using libcurl

> If that is what you want,

Yes, it is what I want.

I have a CGI script on the other end that runs darcs (using HTTP
authentication mechanisms for access control).  Basically I just need
to use HTTP as the transport because many of the users I'm working
with are stuck behind a firewall that doesn't let anything else
through.  Many don't even really have a reliable or trustworthy SMTP
server.

There are other factors (non-darcs users get very confused by the fact
that commits aren't immediate, the symmetry between http-get and
http-send, etc), but the firewall situation is the primary one.

> it should be easy to modify the darcs send--email--darcs apply
> method to use POST instead of SMTP as the transport, though.  I
> don't think I'd use the same URL, though.

Yes, this is more or less what I propose to do.  However, I'm
interested in hearing peoples' thoughts (particularly David's, of
course) on whether this could ultimately be accepted as part of the
upstream darcs.

I'm experienced in Haskell and quite happy to spend the time writing
the patch, but I'm not really interested in permanently maintaining a
darcs fork for our firewalled users (ie beyond the next release of
darcs), and I know there are plenty of others in the same situation.

Hence my question.

  - a

-- 
PGP/GPG: 5C9F F366 C9CF 2145 E770  B1B8 EFB1 462D A146 C380

Q: "Won't the pendulum swing back?"
A: "It has never been a pendulum. Think tectonic plates instead."
                                              -- from patrick.net