[MacPorts] #69240: Launch item "Joshua Root" created on installation without explanation

[MacPorts]

#69240: Launch item "Joshua Root" created on installation without explanation
---------------------+----------------------
  Reporter:  databu  |      Owner:  (none)
      Type:  defect  |     Status:  assigned
  Priority:  Normal  |  Milestone:
 Component:  base    |    Version:
Resolution:          |   Keywords:
      Port:          |
---------------------+----------------------

Comment (by databu):

 Replying to [comment:6 ryandesign]:
 > I wanted to point out that just installing MacPorts itself does not
 install a startup item or cause that notification to appear. But using
 MacPorts to install or upgrade particular ports will do so because those
 ports install startup items. For example, if you use MacPorts to install
 apache2 or a port that depends on it, then apache2 will be installed along
 with its startup item that lets you keep the Apache web server running in
 the background. For the vast majority of ports that have startup items,
 the startup items do not run anything until you use an additional command
 to tell them to start running. MacPorts prints a note to the terminal at
 the end of the installation process telling you these things so hopefully
 the additional notification that macOS now presents about it isn't much of
 a surprise.

 Right. I did the whole upgrade process from a previous version, including
 re-installing all ports. But I seem to remember that the notification
 appeared when installing the new Macports version, rather than when re-
 installing the ports. But I can't verify this now.

 > Not all ports that install startup items use `daemondo`. Those that
 don't will show notifications about whatever program they run. The vast
 majority of software installed by MacPorts is built by MacPorts from
 source so it is not signed so since the notification cannot pull the name
 of the entity that signed it, the notification shows the name of the
 executable. For example, if you install the dbus port, which is a
 dependency of many ports, on macOS 13 or later you would see this
 notification:
 >
 > > "dbus-daemon" is an item that can run in the background. You can
 manage this in Login Items Settings.

 That's actually much better; I hope more ports move away from daemondo...

 > If we want to move away from plastering Josh's name over every user's
 notification system, we could try to move away from using `daemondo`.
 [changeset:bc67106be86835090b8ee1c438b6dd4994e1afd8/macports-base daemondo
 was created] 19 years ago back when launchd was new in Mac OS X 10.4 and
 many server programs could not be started by launchd directly; they needed
 `daemondo` to act as an intermediary. These days, that's probably much
 less necessary.

 Maybe forcing them isn't necessary, if we can document it. You mentioned
 that there's terminal output about it, but if you miss that -- which is
 easy because there's a lot of terminal output e.g. when re-installing all
 ports --, it's not easy at all to find out what this startup item is
 about. If you have many packages installed, chances are that the reinstall
 command runs in a terminal in the background somewhere, while the user is
 doing other things.

 So when I noticed the notification, I wasn't even sure what might have
 caused it. And searching for it lead me to the above linked Reddit page,
 rather than a docs page on https://www.macports.org .

-- 
Ticket URL: <https://trac.macports.org/ticket/69240#comment:8>
MacPorts <https://www.macports.org/>
Ports system for macOS