On Sat, Apr 19, 2014 at 11:50:32PM +0100, Tim Retout wrote: > This software works! It was forked from the apt HTTPS transport. It doesn't > yet have a build system or any packaging, but hopefully that's the easy part. It is also such a trivial modification¹ that I wonder why a fork is needed as the required metadata will easily exceed the code changes. Just provide a patch which does those settings based on the name of the binary called, like apt is handling it for its gzip/bzip2/lzma/xz methods and be done with it forever instead of maintaining a fork. Or even better just add SOCKS proxy support to the existing methods… Where does it lead us to, when DDs prefer to do forks of Debian native packages? I am bit scared of the answer… (it explains though why my apt3 in brainfuck is going nowhere. ;) ) Best regards David Kalnischkies ¹ 1 file changed, 23 insertions(+), 37 deletions(-) before s/https/tor/ was done yesterday. I wonder why curl is forbidden to redirect from http to https in this commit btw. At least we have a bigger diff this way, I guess…
Attachment:
signature.asc
Description: Digital signature