[MacPorts] #48967: submission: port:qt5-kde
MacPorts
noreply at macports.org
Thu Oct 6 22:41:43 CEST 2016
#48967: submission: port:qt5-kde
--------------------------+----------------------
Reporter: rjvbertin@… | Owner: mk@…
Type: submission | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.3.3
Resolution: | Keywords:
Port: qt5-kde |
--------------------------+----------------------
Comment (by rjvbertin@…):
I think I have already tried to do something like this on several
occasions... without much success. But you're right. Or ... we could just
see what happens when we push the modifications ;) I say that as a joke,
but I do feel that certain other port devs have been ignoring my attempts
at a constructive dialog a bit too much for a bit too long. There's this
common wisdom that silence signals agreement ;)
Have you ever (recently) tried to see what happens when you don't use my
cmake-1.0 PortGroup? That one could theoretically get a version bump to
avoid issues with Michael. Since I'm not proposing a different cmake port
that works users can install in place of the other there is no real need
to replace the current cmake portgroup. As long as the KF5 portgroup
includes the right one we get all the benefits I introduced there were it
counts.
The qmake5 PortGroup has a dual mode, "mine" for qt5-kde, and "his" for
use with port:qt5. Funnily the situation is the opposite as with cmake
here: in qt5-kde mode it is less complex than in port:qt5 mode. We could
test what of "my mode" is really required.
I've just made the locale_select and clang_selection portgroups optional.
They'll be used if they're found in the same directory, otherwise the
features they introduce are simply skipped. That shouldn't cause any
issues, so I invite you NOT to copy these files in the future.
--
Ticket URL: <https://trac.macports.org/ticket/48967#comment:31>
MacPorts <https://www.macports.org/>
Ports system for the Mac operating system
More information about the macports-tickets
mailing list