port message

Ryan Schmidt ryandesign at macports.org
Fri Jan 8 20:31:45 PST 2010

On Jan 8, 2010, at 20:36, nox wrote:

> At the core, portfiles are TCL scripts. And excluding anything except ui_msg, any called procedure except ui_msg would be to transformed into a no-op. This can't be done at runtime, and we can't possibly write a list of those procedures. So your idea is unrealisable.

Maybe not in the form he suggested, but it would certainly be possible to modify ui_msg so that in addition to printing a message, it keeps it in an array, and prints them again at the end if in debug mode.

But I think we may be trying to solve the wrong problem. MacPorts 1.9.0 will introduce logging, so I think this makes most of the reasons one would use debug mode go away. The problem is not "There's too much information in debug mode and I can't see the stuff that's relevant to me"; the problem is "We ask users to run in debug mode." With logging, we no longer need to ask users to run in debug mode. So do we then really still need to change how messages are printed?

More information about the macports-dev mailing list