Max Battcher <[email protected]> writes: > By "authentication not supported", I assume you tried "HTTP Digest > Auth" and it doesn't work? (That is, a URL of the form > http://user:[email protected]) > > Both sound like features that should be supported in the HTTP > libraries that darcs uses, and maybe should be reported "upstream"...
curl(1) supports digest auth, and therefore I would be surprised if libcurl didn't. I expect Darcs needs to be taught how to pass the appropriate magic to libcurl. > Beyond that, you can do "darcs send" to HTTP POST (in darcs >= 2.0), > which can provide HTTP-based change pushing. You simply add a > _darcs/prefs/post with an HTTP URL. The POST response from darcs is > then the email that darcs send generates (so you'll need an email > parsing library like Python's email module). Patches can be > authenticated in "the usual ways" for darcs send: signed by GPG or > (Open)SSL certificates. > > Darcs send to HTTP POST seems to me to be the most useful for > "relatively untrusted users to push changes". Is there a production-ready implementation of the glue receive darcs send's HTTP POST and feed it into a darcs apply? _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
