[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:7 ryandesign]:
 > I don't think changing the order in which the app portgroup's post-
 destroot block runs is a good idea at such a late time (so long after the
 app portgroup was created and deployed). All of the ports that already use
 the app portgroup work with the way the portgroup is currently designed.
 Changing it now (e.g. by using an end-of-portfile callback that registers
 the post-destroot at a different time) has the potential to break existing
 ports.

 Agreed, that was my big concern as well. And while we could theoretically
 add a new pg option to enable that behavior - disabled by default - it's
 safer not to touch it.

 That said, we could create a new 1.1 version of the pg... with minimal
 refactoring for a callback. What do you folks think?

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