On Jan 8, 2010, at 9:03 AM, Scott Haneda wrote:
I hope there is. My method is always port edit and read them there. Seems there is always good data in the port messages at the end, that I need later.
You might use port cat instead.And "port cat php5 | grep ui_msg" kinda works but I bet you can use \ line continuation which this will not help you with.
I was hoping for port message to print all the ui_msg's from the port and all deps. This is where it makes the most sense to me or do as I suggested a while back and store the ui_msg till the end of the port process and print them all together. Otherwise you will probably never see "with -v or -d anyways" the ui_msg's for any ports other then the last.
// Brad
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
