[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:
 Keywords:           |       Port:  qt5-kde
---------------------+---------------------
 We're in the middle of preparing the terrain for the submission of
 port:qt5-kde and I think another ticket is in order, given the trac[k]
 record of how my 2+ years worth of effort on Qt5 (and ultimately, KF5)
 have been trickling into MacPorts but mostly brushed aside.

 I'll be keeping this (relatively) short and put most in the comments
 because those I can edit post-hoc if necessary.

 The topic at hand is making the port:qt5 and port:qt5-kde as much
 interchangeable as possible as seen from dependent ports. I have already
 bootstrapped the discussion about this on the devel ML ("port:libressl vs
 port:openssl, path-style variants and prebuilt binaries").[[BR]]
 That is the context: ultimately port:qt5 and port:qt5-kde should be
 exchangeable at user discretion, and ports depending on Qt5 should work
 regardless which of those ports is installed and without having to
 implement complex depspecs themselves. The situation is however quite a
 bit more complex because port:qt5 and port:qt5-kde both have subports
 which shouldn't mingle, and it is thus important that we come to an
 agreement how to get this right before I will consider committing or
 submitting port:qt5-kde. And it's crucial that we stick to that
 agreement.[[BR]]
 If port:qt5-kde is to have the interest it should have, and, ultimately,
 if there are to be official, feature-rich KF5 ports anytime soon.

 FWIW I won't claim that the solution I currently have in mind is the only
 or the best, but it does everything I want and it's been reliable in my
 testing. I *can* claim that Marko and I are the only ones who have
 experience using qt5-kde and KF5 (among the current CC'ees) as well as
 with publishing a select few Qt5-dependent ports developed against qt5-kde
 and apparently working fine with port:qt5 (as intended).

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