From owner-freebsd-ports Thu Mar 4 16:10:20 1999 Delivered-To: freebsd-ports@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 26CC31504D for ; Thu, 4 Mar 1999 16:10:17 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.2/8.9.2) id QAA45475; Thu, 4 Mar 1999 16:10:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Thu, 4 Mar 1999 16:10:02 -0800 (PST) Message-Id: <199903050010.QAA45475@freefall.freebsd.org> To: freebsd-ports@FreeBSD.org Cc: From: Bill Fenner Subject: Re: ports/10377: `make' in ports does not honor {f,ht}tp_proxy settings Reply-To: Bill Fenner Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR ports/10377; it has been noted by GNATS. From: Bill Fenner To: shalunov@lynxhub.lz.att.com Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: ports/10377: `make' in ports does not honor {f,ht}tp_proxy settings Date: Thu, 4 Mar 1999 16:07:06 PST In message <199903032003.PAA13426@tuzik.lz.att.com> you write: > I have set ftp_proxy and http_proxy in the environment (using > IP numbers). Sigh. fetch had FTP_PROXY and HTTP_PROXY first; then the NetBSD ftp got imported which uses ftp_proxy and http_proxy, and now we have two different ways to do the same thing. > What was the reason to use `fetch' rather than `ftp' as > FETCH_CMD in /usr/ports/Mk/bsd.port.mk? "ftp" did not support http: URL's (since it's ... uh ... "ftp"). Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message