[MacPorts] #67533: shared-mime-info @2.2_1: non sudo build clashes with sudo build

[MacPorts]

#67533: shared-mime-info @2.2_1: non sudo build clashes with sudo build
-------------------------------+----------------------
  Reporter:  lukaso            |      Owner:  mascguy
      Type:  defect            |     Status:  assigned
  Priority:  Normal            |  Milestone:
 Component:  ports             |    Version:  2.8.1
Resolution:                    |   Keywords:
      Port:  shared-mime-info  |
-------------------------------+----------------------

Comment (by neverpanic):

 Replying to [comment:18 lukaso]:
 > For the record, I definitely don't want the port to autostart. `dbus` is
 another port that seems to be creating a background task.

 The dbus port does not auto-start anything:

 {{{
 $ port notes dbus
 --->  dbus has the following notes:
   Startup items (named 'dbus-system, dbus-session') have been generated
 that will aid in starting dbus with launchd. They are disabled by default.
 Execute the following command to start them, and to cause them to launch
 at startup:

       sudo port load dbus
 }}}

 Even though some software will not work without dbus, we are not
 automatically starting a dbus-daemon for our users when the dbus port is
 installed, and I think this is the correct choice.

 Replying to [comment:20 mascguy]:
 > That's the reason override settings like `startupitem_autostart` exist
 in `macports.conf`. Set those as you wish, and you're done.

 I think this is making things too simple on ourselves. Most users won't
 know that the setting exists, and only a few users will even bother to
 ask. Other users will be appalled by the decision to auto-start something
 on their machines, and silently leave, patch locally, or rant about it on
 social media. Our users should never even be in the situation where they
 need to consider setting `startupitem_autostart no` in the first place. As
 a project contributor, I should have no incentive to set this option, and
 yet here we are and I just went and changed this setting on my system to
 prevent this from running automatically without my approval.

 I was aware of this risk when I implemented `startupitem.autostart` 10
 years ago (see #35474, r106810), and so far we managed to avoid using this
 in situations where it would surprise users, but it seems this is no
 longer the case. In fact, I regret building this.

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