From owner-freebsd-ports Thu Mar 4 7:57:25 1999 Delivered-To: freebsd-ports@freebsd.org Received: from ckgppxy1.proxy.att.com (ckmsfw1.att.com [12.20.58.157]) by hub.freebsd.org (Postfix) with ESMTP id E576E14F30 for ; Thu, 4 Mar 1999 07:57:23 -0800 (PST) (envelope-from shalunov@lynxhub.lz.att.com) Received: from lynxhub.lz.att.com ([135.25.200.90]) by ckgppxy1.proxy.att.com (AT&T/IPNS/GW-1.0) with SMTP id KAA15331 for ; Thu, 4 Mar 1999 10:57:05 -0500 (EST) Received: by lynxhub.lz.att.com (5.x/EMS-1.2 sol2) id AA00720; Thu, 4 Mar 1999 10:53:26 -0500 Message-Id: <9903041553.AA00720@lynxhub.lz.att.com> Subject: Re: ports/10377: `make' in ports does not honor {f,ht}tp_proxy settings To: reg@shale.csir.co.za (Jeremy Lea) Date: Thu, 4 Mar 1999 10:53:26 -0500 (EST) Cc: freebsd-ports@FreeBSD.ORG In-Reply-To: <19990304174149.F85737@shale.csir.co.za> from "Jeremy Lea" at Mar 4, 99 05:41:49 pm From: Stanislav Shalunov X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jeremy Lea has written: > I've not looked at the man page for fetch, but if you define > HTTP_PROXY and leave FTP_PROXY undefined, then it will use an HTTP based > proxy for ftp://... URLs. This should be on the man page... I just checked it and fetch really uses HTTP_PROXY if FTP_PROXY is not set. HTTP_PROXY and http_proxy use different formats: `http://host:port/' is an invalid HTTP_PROXY. It's very difficult to infer the fact you mention from the man page. And anyway, the procedure for building ports behind a firewall should probably be at least documented if not made more robust by setting FETCH_CMD to `ftp' if http_proxy and ftp_proxy are set. -- stanislav shalunov@lynxhub.att.com | 732-576-3252 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message