#49721: dangerous bug in Qt5 --------------------------+------------------------ Reporter: rjvbertin@… | Owner: mcalhoun@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5 | --------------------------+------------------------ Comment (by rjvbertin@…): Replying to [comment:8 rjvbertin@…]:
(and KF5 is being built without my QSP patch).
In my current approach, the QSP/XDG activator gets linked to all KF5 frameworks if the `+QspXDG` variant is set. - That variant is the default if the activator is detected locally (but can of course be overridden from the commandline, using `-QspXDG`) - This is the case if `port:qt5-kde` is installed - The KF5 frameworks indicate a preference for `port:qt5-kde` - That means that `port:qt5-kde` will be installed when starting from a clean slate like on the build bots. Thus, subports providing individual KF5 frameworks can simply check if +QspXDG is set; if not, `test.cmd` and `test.args` can be set so that a warning is printed. Ports can also use `${qt_bins_dir}/qtpath --testmode --writable-path ApplicationsDir` to check the actual location used, but that is not going to inform whether about QSP's operating mode during the tests. -- Ticket URL: <https://trac.macports.org/ticket/49721#comment:9> MacPorts <https://www.macports.org/> Ports system for OS X