From owner-freebsd-ports Sat Mar 10 6:41:13 2001 Delivered-To: freebsd-ports@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id F2B3937B718 for ; Sat, 10 Mar 2001 06:41:09 -0800 (PST) (envelope-from roam@orbitel.bg) Received: (qmail 443 invoked by uid 1000); 10 Mar 2001 14:40:36 -0000 Date: Sat, 10 Mar 2001 16:40:36 +0200 From: Peter Pentchev To: Dag-Erling Smorgrav Cc: Stephane.Lentz@ansf.alcatel.fr, ports@FreeBSD.ORG Subject: Re: curl 7.6.1 port : HTTP proxy not working Message-ID: <20010310164036.A400@ringworld.oblivion.bg> Mail-Followup-To: Dag-Erling Smorgrav , Stephane.Lentz@ansf.alcatel.fr, ports@FreeBSD.ORG References: <20010309152555.A25496@nickfury.netfr.alcatel.fr> <20010309200832.A25927@nickfury.netfr.alcatel.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@thinksec.com on Sat, Mar 10, 2001 at 01:33:51PM +0100 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Mar 10, 2001 at 01:33:51PM +0100, Dag-Erling Smorgrav wrote: > OBTW, I'd still be interested in hearing why you think curl is much > more powerful. Disclaimer: I am only writing the following as a more-or-less curl port maintainer :) I like fetch, and I use it for all downloads on my FreeBSD systems (even going as far as invoking it from a portal mount.. but that's a different story). So.. I don't know about downloading, but fetch(1) does not support uploads, at least not that I'm aware of. 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. I don't think this counts as 'much more powerful', but curl sure does have some strong points (whereas fetch(1) unarguably has others :) G'luck, Peter -- What would this sentence be like if it weren't self-referential? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message