Building RKWard on Mac (continued from private discussion)
thomas.friedrichsmeier at ruhr-uni-bochum.de
Thu Jun 8 20:11:28 UTC 2017
Sorry to bombard you with questions, but one more:
On Thu, 08 Jun 2017 17:40:37 +0200
René J.V. Bertin <rjvbertin at gmail.com> wrote:
> qt5-kde is designed to be (and "somewhat tested") a drop-in
> replacement for qt5-qtbase c.s. Once you install it all ports
> depending on Qt5 change their "depspecs" and will thus not attempt to
> install a wrong Qt5 port in addition to what you already have.
> Despite being a drop-in replacement you'll still rebuilding the Qt5
> ports from source, though. That's hopefully not more than a
> precaution, but a necessary one if I want to get my ports accepted.
In turning this around, does that mean that all kf5 ports (currently in
your personal tree, only), could be expected to "mostly" work with
non-patched qt5? And they would automatically profit from switching to
qt5-kde, at some later point?
_If_ so, wouldn't it also be useful to try getting the kf5 ports into
MacPorts, independent of qt5-kde?
(Note that any really detailed answer may be lost on me, so no need to
elaborate. Just testing your defenses, so to speak...)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the kde-mac