[MacPorts] #53230: preparing port:qt5-kde step 2 : the qt5 PortGroup(s)

[MacPorts]

#53230: preparing port:qt5-kde step 2 : the qt5 PortGroup(s)
----------------------+-----------------
  Reporter:  RJVB     |      Owner:
      Type:  request  |     Status:  new
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:
Resolution:           |   Keywords:
      Port:  qt5-kde  |
----------------------+-----------------

Comment (by RJVB):

 A work about the main hurdle we've been dealing with: communication with
 the current Qt5 maintainer. Without claiming anything as to the underlying
 reasons (and trying hard not to be judgemental), this is what has mostly
 been happening in those past 2 years or so: I keep everyone involved in
 the loop the issues I face and the solutions I found for them (e.g.
 qt4/qt5 co-installability, and now qt5/qt5-kde exchangeability) but
 without getting constructive feedback from the main other person involved.
 Then at some point there appears to be a wake-up call, and things get done
 .... differently. Recent examples: a boolean state variable that is
 intended to be set once/read-only has been implemented as an options
 variable (trivial, but unnecessary complexity) and the relatively simple
 depspec procedure I proposed that would work for both ports has been
 morphed into something much more complicated using a component table that
 I simply cannot justify for port:qt5-kde [[BR]]
 This is what made Marko and I decide to implement port:qt5-kde in the
 first place.

 We can't do that at the level of the PortGroups (qt5 and likely also
 qmake5), not if dependent ports are to be agnostic as to which Qt5 flavour
 is installed.

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