[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 mascguy):

 Replying to [comment:21 RJVB]:
 > Yes, and no. I agree with Clemens that most ports shouldn't autostart
 their launchd services. I'd say even DBus is among those (because it
 launches an actual daemon that provides services you might not want to
 have active).
 >
 > This port is different, as you point out yourself. So yeah, I think it'd
 be preferable to not cripple it if users opt not to auto-start all launchd
 services, via a variant.
 >
 > The alternative would be to provide some kind of level control over the
 kind of services you accept to have auto-started (a lot more complex) or
 simply not auto-starting anything when the activation isn't done with
 elevated privileges (both options would require rolling out). Using a
 dedicated env. variable would work too and will be less visible to common
 users.

 Sure, but MacPorts base supports this already, via config option
 `startupitem_autostart`. So if a user doesn't want to auto-start things,
 they simply set `startupitem_autostart no` in `macports.conf`. (Either
 globally via `${prefix}/etc/macports/macports.conf`, or in their user-
 override config at `~/.macports/macports.conf`.)

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