[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:12 RJVB]:
 > Replying to [comment:9 jmroot]:
 > > The Portfile is setting `startupitem.install yes`, overriding what the
 user set in macports.conf. So multiple installations of the port in
 different prefixes will always conflict.
 >
 > Is there a way to determine if the default for that setting has been
 changed by the user?
 >
 > I'll admit that I didn't consider specific use cases like this but I do
 think that they shouldn't make things more complicated for the average J.
 User. Dev-teams using MacPorts to build their projects by definition have
 the know-how and means to take additional steps that Joe and Jane don't
 have...
 >
 > The easy way out would be to provide a build variant that disables the
 auto-loading.

 Per Josh's point, the key is to not specify `startupitem.install yes`.
 That way we defer to the user's configuration settings, which by default
 are set to auto-start these. (But in Lukas' case, it will be explicitly
 disabled.)

 So there's no need for a variant. Does that make sense?

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