Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 5 Sep 2012 08:46:26 -0600 (MDT)
From:      Warren Block <wblock@wonkity.com>
To:        Thomas Mueller <mueller23@insightbb.com>
Cc:        freebsd-ports@freebsd.org, Bryan Drewery <bryan@shatow.net>
Subject:   Re: dialogwrapper in ports
Message-ID:  <alpine.BSF.2.00.1209050840480.40112@wonkity.com>
In-Reply-To: <FB.A1.26260.8BE07405@smtp02.insight.synacor.com>
References:  <FB.A1.26260.8BE07405@smtp02.insight.synacor.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1209050840480.40112>