[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:  neverpanic
      Type:  defect            |     Status:  assigned
  Priority:  Normal            |  Milestone:
 Component:  ports             |    Version:  2.8.1
Resolution:                    |   Keywords:
      Port:  shared-mime-info  |
-------------------------------+------------------------

Comment (by RJVB):

 Replying to [comment:22 mascguy]:
 > Sure, but MacPorts base supports this already, via config option
 `startupitem_autostart`.

 Is there a hole in our bucket? :) As I tried to convey, I find that all-
 or-nothing switch too coarse.

 I just took DBus as an example as it had already been named and I had
 noticed it now uses the autostart feature when I (finally) upgraded my
 personal copy not long ago. Regardless of whether the daemon *can* be
 auto-started I can see how one would not want it to be. Nothing should be
 crippled if you only ever install a single runtime dependency of the DBus
 daemon, for instance (given how the daemon is for IPC).

 FWIW, I don't see what's wrong with select ports starting this kind of
 service and above all I don't see why a single person would be able to ban
 such behaviour for the entire community.

 I've given my opinion, offered a number of solutions for the case at hand
 (MP used *in* a build system), for the rest it's now blissfully out of my
 hands.

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