<pre style='margin:0'>
Joshua Root (jmroot) pushed a commit to branch master
in repository macports-base.
</pre>
<p><a href="https://github.com/macports/macports-base/commit/f6348091f6b10b2ea257553efd63beeb1512b8fe">https://github.com/macports/macports-base/commit/f6348091f6b10b2ea257553efd63beeb1512b8fe</a></p>
<pre style="white-space: pre; background: #F8F8F8">The following commit(s) were added to refs/heads/master by this push:
<span style='display:block; white-space:pre;color:#404040;'> new f6348091f Remove "Creating launchd control script" message
</span>f6348091f is described below
<span style='display:block; white-space:pre;color:#808000;'>commit f6348091f6b10b2ea257553efd63beeb1512b8fe
</span>Author: Ryan Carsten Schmidt <git@ryandesign.com>
AuthorDate: Mon Apr 29 22:44:17 2024 -0500
<span style='display:block; white-space:pre;color:#404040;'> Remove "Creating launchd control script" message
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> Remove "Creating launchd control script" message from the user-visible
</span><span style='display:block; white-space:pre;color:#404040;'> terminal output and print it only in the log and debug output. This
</span><span style='display:block; white-space:pre;color:#404040;'> message or one of its prior wordings has been present ever since the
</span><span style='display:block; white-space:pre;color:#404040;'> startup item code was originally added in 3ffdaf3 in 2005.
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> I presume the purpose of this message was to inform the user that a
</span><span style='display:block; white-space:pre;color:#404040;'> startup item existed for this port. It no longer accomplishes that
</span><span style='display:block; white-space:pre;color:#404040;'> purpose because it only appears during the destroot phase which most
</span><span style='display:block; white-space:pre;color:#404040;'> users will not see because they install pre-built archives instead of
</span><span style='display:block; white-space:pre;color:#404040;'> building from source. Meanwhile a better message in the form of notes
</span><span style='display:block; white-space:pre;color:#404040;'> that display at the end of installation, regardless of whether it was
</span><span style='display:block; white-space:pre;color:#404040;'> from source or via pre-built archive, was added in 6faf3f8 in 2018.
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> Originally, the startup item was created at the end of the destroot
</span><span style='display:block; white-space:pre;color:#404040;'> phase, so users would first see the "Staging into destroot" message,
</span><span style='display:block; white-space:pre;color:#404040;'> followed by a delay as staging occurred, followed by the "Creating
</span><span style='display:block; white-space:pre;color:#404040;'> launchd control script" message, followed almost immediately by the
</span><span style='display:block; white-space:pre;color:#404040;'> install phase messages. In 6f7ed40 in 2020 it was changed so that
</span><span style='display:block; white-space:pre;color:#404040;'> startup items would be created at the beginning of the destroot phase.
</span><span style='display:block; white-space:pre;color:#404040;'> This made the output more confusing: now, "Staging into destroot" was
</span><span style='display:block; white-space:pre;color:#404040;'> followed immediately by "Creating launchd control script", which would
</span><span style='display:block; white-space:pre;color:#404040;'> then remain until staging had completed, giving the erroneous impression
</span><span style='display:block; white-space:pre;color:#404040;'> that staging completed instantly while creating the control script took
</span><span style='display:block; white-space:pre;color:#404040;'> a long time.
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> Nothing else in the destroot phase gets the special privilege of
</span><span style='display:block; white-space:pre;color:#404040;'> printing an extra line to the terminal; there's no reason why creating
</span><span style='display:block; white-space:pre;color:#404040;'> the launchd control script should do so.
</span>---
src/port1.0/portstartupitem.tcl | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
<span style='display:block; white-space:pre;color:#808080;'>diff --git a/src/port1.0/portstartupitem.tcl b/src/port1.0/portstartupitem.tcl
</span><span style='display:block; white-space:pre;color:#808080;'>index b6ed93ea1..eb361fe9c 100644
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>--- a/src/port1.0/portstartupitem.tcl
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>+++ b/src/port1.0/portstartupitem.tcl
</span><span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -520,9 +520,9 @@ proc portstartupitem::startupitem_create {} {
</span> foreach_startupitem {
if {${si_type} ne "none" && ([tbool si_create] || $si_custom_file ne "")} {
if {[tbool si_create]} {
<span style='display:block; white-space:pre;background:#ffe0e0;'>- ui_notice "$UI_PREFIX [msgcat::mc "Creating ${si_type} control script '$si_name'"]"
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ ui_debug "Creating ${si_type} control script '$si_name'"
</span> } else {
<span style='display:block; white-space:pre;background:#ffe0e0;'>- ui_notice "$UI_PREFIX [msgcat::mc "Installing ${si_type} control script '$si_name'"]"
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ ui_debug "Installing ${si_type} control script '$si_name'"
</span> }
switch -- ${si_type} {
</pre><pre style='margin:0'>
</pre>