From owner-freebsd-ports Sat Feb 23 16:26: 8 2002 Delivered-To: freebsd-ports@freebsd.org Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.8.210.226]) by hub.freebsd.org (Postfix) with ESMTP id 9081437B402 for ; Sat, 23 Feb 2002 16:26:04 -0800 (PST) Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.6/8.11.6) id g1O0Nds40944 for ports@freebsd.org; Sat, 23 Feb 2002 19:23:39 -0500 (EST) (envelope-from alane) Date: Sat, 23 Feb 2002 19:23:39 -0500 From: Alan Eldridge To: FreeBSD Ports List Subject: CONFIGURE_LOG spewage Message-ID: <20020224002339.GB28899@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.26i X-message-flag: Magic 8-Ball says "Outlook not so good." I'll ask it about Exchange next. Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org What is going to ever get done about that code in bsd.port.mk that spews the ${CONFIGURE_LOG} if configure fails? That is positively abominable IMO. Can't we at least make it conditional on ${SPEW_CONFIGURE_LOG_AND_BLOW_OUT_ALL_YOUR_SCOLLBACK_BUFFERS_WITH_TONS_OF_MOSTLY_USELESS_TEXT_IF_CONFIGURE_DOESNT_WORK}? ;) Is there any good reason to not limit this to, say, 100 lines or so? This was brought up a long time ago, but no resolution ever happened. -- Alan Eldridge "Dave's not here, man." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message