[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:17 neverpanic]:
 > While MacPorts does have the capability to autostart launchd agents and
 daemons, very very few ports use this, and I would prefer if we kept it
 this way. So far, it seems net/wireshark_chmodbpf uses it (because without
 it, the port doesn't make sense), security/certsync uses it (again, the
 port doesn't make sense without it), sysutils/mpstats uses it (same
 reason, the user wouldn't have it installed if they didn't want the
 autostart), www/edbrowse uses it (but not to actually start the service,
 just to create a directory, it seems), and science/SDRplay3 uses it (I
 disagree with its use, it shouldn't auto-start, but it's not a commonly
 installed port, so I don't care).
 >
 > You are now adding an autostarted item to a port that's commonly
 installed as a dependency. I really really don't want a random service to
 run just because something depends on shared-mime-info. Please revert the
 autostart.

 If you review the prior ticket - issue:45396 - you'll see that none of
 this works properly without something monitoring the `shared-mime-info`
 area. (At least not unless we add hooks in one or more other portgroups,
 to try and catch when things are added/removed. And that could be both
 fragile, and potentially error-prone.)

 Furthermore, if you review the daemon itself, you'll see that it's based
 on a filewatcher. So it's not continuously doing things, until/unless the
 MIME area is touched. That's a very efficient way to do it.

 Can you offer a better alternative, that ensures auto-updates to the MIME
 database?

 Regardless, let's debate this via issue:45395, rather than this ticket.

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