[MacPorts] #65721: app portgroup: callback not used, causing issues when combined with other pgs

[MacPorts]

#65721: app portgroup: callback not used, causing issues when combined with other
pgs
----------------------+-----------------------
  Reporter:  mascguy  |      Owner:  mascguy
      Type:  defect   |     Status:  assigned
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.7.2
Resolution:           |   Keywords:  portgroup
      Port:  gramps   |
----------------------+-----------------------

Comment (by mascguy):

 Replying to [comment:9 kencu]:
 > I think you might try just using the app portgroup's launch script
 option instead for this?

 Yep, that's another option.

 Ditto for a few other alternatives:
 * Segregate app bundle into a separate port. But shouldn't be necessary,
 when we simply want to add an app bundle to an existing port.
 * Set `app.executable` to the real binary, per Ryan's previous suggestion.
 But this option is less simple than it could be, as it has to be done
 within a phase. (Simply because `python.bin` isn't set correctly until
 later.) For example:

 {{{
 post-build {
     # Can't do this outside of a phase, as `python.bin` isn't set to
 selected Python version until later
     app.executable ${python.bin}/${name}
 }
 }}}

 All of which further complicate what should otherwise "just work."

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