Hi, On Fri, Sep 23, 2022 at 10:01:11AM +0100, Lukas Oberhuber wrote: > I've now run into the opposite problem, which is "Too long with no > output (exceeded 10m0s): context deadline exceeded".
If you need regular output, I'd just recommend running macports in verbose mode, i.e. port -v install … This will generate more output, but not nearly as often as the progress bar updates, it will help you figure out what went wrong if the build fails, and it will correctly abort if a build appears to hang for whatever reason. On Fri, Sep 23, 2022 at 01:28:37PM +0100, Lukas Oberhuber wrote: > I'm very unfamiliar with Tcl, but I can't find the definition of > `ui_progress_generic` anywhere, which seems to be the code I need to > modify. It's called in portprogress.tcl. Or could this be a red > herring and it's actually dead code. The code in src/port1.0 runs in a Portfile context. The code in src/macports1.0 allows using MacPorts as a library. Code that's for the user interface is in src/port. If you follow the code path and variables, you'll see that src/port/port.tcl defines the functions, passes them to macports1.0/macports.tcl in the ui_options argument of mportinit, and [1] passes them into the Portfile Tcl interpreter, where you'll see them invoked as ui_progress_generic from src/port1.0. If you want to modify the progress bar layout, you thus need to change src/port/port.tcl. > In addition, it seems there isn't a debugger that comes with Tcl, > unless someone has a recommendation for a macports included one. I always just used printf debugging. I'm not sure whether there are better tools these days. [1] https://github.com/macports/macports-base/blob/master/src/macports1.0/macports.tcl#L1524-L1531
