[MacPorts] #48967: submission: port:qt5-kde

MacPorts noreply at macports.org
Mon Nov 14 00:12:37 CET 2016


#48967: submission: port:qt5-kde
-------------------------+----------------------
  Reporter:  RJVB        |      Owner:  mkae
      Type:  submission  |     Status:  accepted
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:
      Port:  qt5-kde     |
-------------------------+----------------------

Comment (by RJVB):

 Thanks for the heads-up Marcus, if that's what it was.

 I have a vague impression that maybe you're considering making a single
 Qt5 portgroup. In a way that would be the preferred solution but I'm not
 sure it's the most practical and feasible because we'd surely end up with
 something that has 2 sections. And that'd be the more cumbersome version
 of what I'm doing now and what has been tested by several people: 1 file
 per section and an "interface" or header PortGroup that decides which
 section to include.

 As to 5.6LTS: I've brought up the idea of keeping it around in MacPorts
 and the reception was luke-warm, which I can imagine. It'll depend on how
 minimum OS version requirements evolve with 5.7.x and upwards, and what
 advantages updates to 5.6 have over the latest 5.7+ version that supports
 OS X 10.7 .

 I do think I'll wait for 5.7.1 before I upgrade, though. Shouldn't be too
 long now, and it saves including upstream patches.

 @Marko: I synced my version of the qmake5 PG with the upstream changes, as
 well as `qt5-mac-1.0.tcl` .  I haven't seen anything in the other changes
 that is directly (immediately) useful for my own port. I'm monitoring
 though. The intention of my port is not to break anything.

 I personally try to make a distinction between variables that are relevant
 for every port and those that are only relevant for the main port (Qt or
 KF5). Those that aren't relevant in dependent ports are put in a true
 namespace (qt5:: or kf5::). If we both did this that would make it a bit
 easier to see which ones are important to copy, or that could be moved to
 the header PortGroup when the time comes.

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



More information about the macports-tickets mailing list