From owner-freebsd-ports@FreeBSD.ORG Wed Sep 5 14:47:00 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 09E9C106566B for ; Wed, 5 Sep 2012 14:47:00 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id B9B798FC1C for ; Wed, 5 Sep 2012 14:46:59 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q85EksIY040435; Wed, 5 Sep 2012 08:46:54 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q85EkQje040418; Wed, 5 Sep 2012 08:46:38 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 5 Sep 2012 08:46:26 -0600 (MDT) From: Warren Block To: Thomas Mueller In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Wed, 05 Sep 2012 08:46:54 -0600 (MDT) Cc: freebsd-ports@freebsd.org, Bryan Drewery Subject: Re: dialogwrapper in ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Sep 2012 14:47:00 -0000 On Wed, 5 Sep 2012, Thomas Mueller wrote: >> Configure port options as usual. It should look and work the same as >> usual, but handle long descriptions and bigger windows as described above. > > Brian Drewery responded: > >> I've set this in my make.conf and tried it out. It's really cool. > >> Would be nice to see this get more testing and possibly be set as default. > >> Bryan > > This whets my virtual appetite, I'd like to try. > > But does this avoid the problem of getting messed up with the dialog when generating a log file with script or > > make install clean | & tee build.log ? Probably not. I'm not sure if either dialog or dialogwrapper can do anything about what goes into a teed file. > I noticed on http://www.freshports.org/commits.php just a day ago, > devel/cdialog and x11/xdialog. > > Maybe xdialog avoids this messing up when generating a log file, but can only be used after xorg is built and installed. Either of these may be better than the dialog(1) in base. But one of the goals of dialogwrapper was to not need anything extra that would have to be installed from ports.