Hi René, Well, I think we really are (getting somewhere). Keep pushing! :-)
On 12/03/2015, at 5:44 AM, René J.V. Bertin wrote: > Not that it's getting any easier to convince the powers that be what *I* > think will be ideal for the QStandardPaths in port:qt5-mac, but at least I > seem to have gotten the message across that any hard-coded solution is > sub-optimal. > > My latest proposition is here: > https://bugreports.qt.io/browse/QTBUG-44473?focusedCommentId=275639&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-275639 I have read through the patch in detail and it looks great. A couple of points: a. Is it necessary to initialise QStandardPaths::usingXDGLocations in every platform file (android, blackberry, etc.)? Could it be done in conditional code in qstandardpaths.cpp? b. How does the qstandardpaths_use_xdg.cpp component work? I guess it is intended to be loaded with any build that wants to use Qt with XDG paths (e.g. all KF5 Frameworks and apps), but what actually makes it execute and when? > The only path that remains a bit elusive is the (Generic)ConfigLocation; it's > /etc/xdg on Linux, but does it really make sense to set it to > ${prefix}/etc/xdg in MacPorts (when using XDG-style locations, of course)? I see that MacPorts currently uses /opt/local/etc and has quite a few subdirs in it already, including /opt/local/etc/xdg, which contains a few things: Tara:~>ls /opt/local/etc/xdg/* /opt/local/etc/xdg/autostart: at-spi-dbus-bus.desktop gsettings-data-convert.desktop /opt/local/etc/xdg/menus: kde-information.menu kde4-applications.menu So perhaps it does make sense to re-use ${prefix}/etc/xdg in Qt5/KF5. All the best, Ian W. _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev