On Sunday 06 July 2014 14:00:18 Luca Beltrame wrote:
> Does anyone know the reason?
Yes, blind porting :-)
> Should we all change them to GenericConfigLocation?
Yes.
--
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5
___
On 06 Jul 2014, at 14:53 , David Faure wrote:
> https://community.kde.org/Frameworks/Epics/Contributions_to_Qt5
That, indeed, is an impressive list! :)
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listi
On Sunday 06 July 2014 13:25:25 Marko Käning wrote:
> On 06 Jul 2014, at 13:19 , David Faure wrote:
> > kf5-config is deprecated, qtpaths replaces it.
>
> Does this mean that KF5 now tries to use as much infrastructure delivered by
> Qt5 as possible? (IIRC I saw changes of KIcon to QIcon and alre
David Faure wrote:
> Well, kde4-config --path lib never included ~/.local so that's not really
> a bug.
It used to include $KDEHOME, on which startkde relied, that's probably the
cause of the bug.
> Shall we say ~/.config/startkde/env/ ?
If that's the case, we have a problem elsewhere. ;) syst
On 06 Jul 2014, at 13:19 , David Faure wrote:
> kf5-config is deprecated, qtpaths replaces it.
Does this mean that KF5 now tries to use as much infrastructure delivered by Qt5
as possible? (IIRC I saw changes of KIcon to QIcon and already wondered what’s
going on there...)
___
On Sunday 06 July 2014 11:49:22 Luca Beltrame wrote:
> Hello,
>
> I set out an attempt to fix bug 333793 [1] and to port kf5-config in
> kdelibs4support to QCommandLineParser and QStandardPaths where possible.
>
> The issue in the bug is that kf5-config --path lib misses ~/.local (XDG)
> because
Hello,
I set out an attempt to fix bug 333793 [1] and to port kf5-config in
kdelibs4support to QCommandLineParser and QStandardPaths where possible.
The issue in the bug is that kf5-config --path lib misses ~/.local (XDG)
because basePrefixForResource (kstandarddirs.cpp) says (lines 244-250):
