[MacPorts] #53351: shared-mime-info: support mpgk/mdmg packaging

[MacPorts]

#53351: shared-mime-info: support mpgk/mdmg packaging
-------------------------------+-------------------------------
  Reporter:  ctreleaven        |      Owner:  mkae, rjvbertin@…
      Type:  defect            |     Status:  new
  Priority:  Normal            |  Milestone:
 Component:  ports             |    Version:
Resolution:                    |   Keywords:
      Port:  shared-mime-info  |
-------------------------------+-------------------------------

Comment (by RJVB):

 Replying to [comment:4 ctreleaven]:
 > Sorry, is there a word missing in the second sentence ("we'll ... if")?
 I don't have a reason to package KF5.

 Yes, "we'll ''see'' ... if". Sorry about that.

 > Without looking at the PortGroup, perhaps the script(s) just need to be
 added to whatever is the base port that the others will always include.

 Yes, that would make sense of course. Not the base port in this case, but
 the subport that installs the command that's run as the post-activate
 action.

 > Ie any port that has a dependency on shared-mime-info will (if packaged)
 'inherit' the above postinstall script.  For example, a stand-alone
 > installer for gramps3 (the genealogy program) will include a mime
 database update 'for free'.

 I haven't tried to figure out how that works, presumably because
 `package.dir` is actually a port-specific location under ${prefix}? If not
 I don't see where the postinstall script is installed so that other ports
 can invoke it. Unless this is automatic because the installer for any port
 depending on shared-mime-info will include a shared-mime-info installer?
 If that's how it works, would that also prevent the "issue" that not every
 port depending on shared-mime-info needs to provoke a database update,
 because the shared-mime-info installer won't be run if the port is already
 installed?

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