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

MacPorts noreply at macports.org
Tue May 30 23:35:01 UTC 2023


#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:4 RJVB]:
 > NB: this port is supposed to install its launchd plist and **its
 functionality is crippled** when that is prevented. Or will be crippled
 once all ports that install mime definitions start to rely on there being
 an automatic update of the mime cache (i.e. stop calling the updater
 themselves).
 > ''In fact, we should probably have made that modification, or at least
 created a PR like the one for the cmake 1.1 PG to ask all port maintainers
 to make the change and test it.''
 >
 > @mascguy as you know I developed this with good-old-fashioned use of a
 hand-written plist, in which case the use of `sudo` wasn't required (or
 only for the install and activate phases in case `$prefix` required that).
 >
 > I've been a proponent of not using `sudo` for MacPorts myself but 1) too
 many ports have functionality that does require them to be installed in
 privileged fashion and 2) things go wrong too easily and thus too often
 when `$prefix` has no protection at all (think things being installed in
 there instead of into `$destroot`).

 Rene, this is a very different situation, as the GIMP project is using
 MacPorts to build the macOS version of GIMP. Which is great! But it
 doesn't require daemon functionality.

 So please, if you'd like to collaborate further on a longer-term approach,
 then let's discuss via the original ticket. But this simply muddies the
 waters for this case, which isn't typical.

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


More information about the macports-tickets mailing list