From owner-freebsd-ports  Sun Jul  4  4:54: 4 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 144A414D35; Sun,  4 Jul 1999 04:54:03 -0700 (PDT)
	(envelope-from hoek@FreeBSD.org)
Received: (from hoek@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id EAA89108;
	Sun, 4 Jul 1999 04:54:03 -0700 (PDT)
	(envelope-from hoek@FreeBSD.org)
Date: Sun, 4 Jul 1999 04:54:03 -0700 (PDT)
From: <hoek@FreeBSD.org>
Message-Id: <199907041154.EAA89108@freefall.freebsd.org>
To: shalunov@lynxhub.lz.att.com, hoek@FreeBSD.org,
	freebsd-ports@FreeBSD.org
Subject: Re: ports/10377: `make' in ports does not honor {f,ht}tp_proxy settings
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: `make' in ports does not honor {f,ht}tp_proxy settings

State-Changed-From-To: open->closed
State-Changed-By: hoek
State-Changed-When: Sun Jul 4 04:51:57 PDT 1999
State-Changed-Why: 
This PR finishes by making the reccomendation that we ditch fetch and
use ftp(1) in its place.  This action has been discussed before and it
seems more likely that we will someday remove the http: capability
(damn gnats editor...  I meant: "suptid http: capability") from ftp
instead of removing fetch.

Somewhere along the discussion of this PR, the originator had his
question answered too, it seems, so I'm saved that.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message