MacPorts Base: Support for a lower level of debug output, like ui_trace, or ui_debug2/ui_debug3?

[Ryan Schmidt]

On May 26, 2021, at 08:38, Christopher Nielsen wrote:

> I’m referring to debug output like the following, in this cases taken from one of our builtbot logs. Some of these are generated by base, while others are generated by the portgroups themselves.
> 
> While I’m not necessarily advocating that we hide all of these (via output at level debug2 or debug3), we’d have the option.
> 
> Does that make sense?

Not yet.


> DEBUG: Sourcing PortGroup legacysupport 1.1 from /opt/bblocal/var/buildworker/ports/build/ports/_resources/port1.0/group/legacysupport-1.1.tcl
> DEBUG: Sourcing PortGroup compiler_wrapper 1.0 from /opt/bblocal/var/buildworker/ports/build/ports/_resources/port1.0/group/compiler_wrapper-1.0.tcl
> DEBUG: Re-registering default for universal_variant
> DEBUG: Re-registering default for use_configure
> DEBUG: Re-registering default for dist_subdir
> DEBUG: Re-registering default for worksrcdir
> DEBUG: Re-registering default for build.cmd
> DEBUG: Re-registering default for build.target
> DEBUG: Re-registering default for test.cmd
> DEBUG: Re-registering default for test.target
> DEBUG: Re-registering default for configure.env
> DEBUG: Sourcing PortGroup golang 1.0 from /opt/bblocal/var/buildworker/ports/build/ports/_resources/port1.0/group/golang-1.0.tcl
> DEBUG: Re-registering default for legacysupport.newest_darwin_requires_legacy
> DEBUG: Will append MACPORTS_LEGACY_SUPPORT_DISABLED=1 to extract.env
> DEBUG: Will append MACPORTS_LEGACY_SUPPORT_DISABLED=1 to configure.env
> DEBUG: Will append MACPORTS_LEGACY_SUPPORT_DISABLED=1 to build.env
> DEBUG: Will append MACPORTS_LEGACY_SUPPORT_DISABLED=1 to destroot.env
> DEBUG: Will append MACPORTS_LEGACY_SUPPORT_DISABLED=1 to test.env
> DEBUG: Re-registering default for legacysupport.header_search
> DEBUG: Re-registering default for legacysupport.library_name
> DEBUG: Re-registering default for legacysupport.use_static
> DEBUG: Re-registering default for legacysupport.redirect_bins
> DEBUG: Sourcing PortGroup legacysupport 1.1 from /opt/bblocal/var/buildworker/ports/build/ports/_resources/port1.0/group/legacysupport-1.1.tcl
> DEBUG: Sourcing PortGroup github 1.0 from /opt/bblocal/var/buildworker/ports/build/ports/_resources/port1.0/group/github-1.0.tcl
> DEBUG: Re-registering default for livecheck.url
> DEBUG: Re-registering default for livecheck.regex
> DEBUG: universal_variant is false, so not adding the default universal variant
> DEBUG: Running callback portconfigure::add_automatic_compiler_dependencies
> DEBUG: Finished running callback portconfigure::add_automatic_compiler_dependencies
> DEBUG: Running callback portbuild::add_automatic_buildsystem_dependencies
> DEBUG: Finished running callback portbuild::add_automatic_buildsystem_dependencies
> DEBUG: Running callback portstartupitem::add_notes
> DEBUG: Finished running callback portstartupitem::add_notes
> DEBUG: Running callback legacysupport::add_legacysupport

Which of this output do you propose to change to different debug levels any why?

I don't know which of this output is generated by portgroups and which by base but I can guess that output like "Will append MACPORTS_LEGACY_SUPPORT_DISABLED=1 to extract.env" is generated by the legacysupport portgroup and I wonder why this output for example is needed at all when one can already see in later debug lines what extract.env gets set to.