Date: 10 Mar 2001 18:34:13 +0100 From: Dag-Erling Smorgrav <des@thinksec.com> To: Peter Pentchev <roam@orbitel.bg> Cc: Stephane.Lentz@ansf.alcatel.fr, ports@FreeBSD.ORG Subject: Re: curl 7.6.1 port : HTTP proxy not working Message-ID: <xzpn1atfrze.fsf@aes.thinksec.com> In-Reply-To: Peter Pentchev's message of "Sat, 10 Mar 2001 16:40:36 %2B0200" References: <20010309152555.A25496@nickfury.netfr.alcatel.fr> <xzpae6ultbx.fsf@aes.thinksec.com> <20010309200832.A25927@nickfury.netfr.alcatel.fr> <xzp1ys6lp76.fsf@aes.thinksec.com> <xzpvgphkdlc.fsf@aes.thinksec.com> <20010310164036.A400@ringworld.oblivion.bg>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Pentchev <roam@orbitel.bg> writes: > I don't know about downloading, but fetch(1) does not support uploads, > at least not that I'm aware of. That's why it's called fetch(1) :) > Besides, fetch(1) is more or less > FreeBSD-specific, and people with that Finnish-OS background might be > used to curl syntax already, or may choose to use the same tool under > various OS's. Yep - that Finnish OS is normally distributed with a C library that's too broken for libfetch to even build on that system. > I don't think this counts as 'much more powerful', but curl sure does > have some strong points (whereas fetch(1) unarguably has others :) I was actually hoping to hear something like "curl can fetch this file but fetch(1) can't" so that I could sit down with the code for an hour or two and then answer back "it can now" :) DES --=20 Dag-Erling Sm=F8rgrav - des@thinksec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpn1atfrze.fsf>