On 08/06/2015, at 5:13 PM, David Faure wrote:
> On Monday 08 June 2015 15:22:20 Ben Cooksley wrote:
>> The maintainer(s) of
>> the QStandardPaths class never reviewed our patch
>
> That would be me, and since I don't know how things should work on OSX,
a)
https://developer.apple.com/library/mac/d
On Mon, Jun 8, 2015 at 8:25 PM, Christoph Cullmann wrote:
> Hi,
>
> for frameworks, it is all very nice and automatic, the version in the
> CMakeLists.txt get auto-updated on each KF 5.x release.
>
> It seems to me, for the "applications" collection, something similar might
> make sense.
>
> E.g
Hi,
for frameworks, it is all very nice and automatic, the version in the
CMakeLists.txt get auto-updated on each KF 5.x release.
It seems to me, for the "applications" collection, something similar might make
sense.
E.g. I missed to ever update the Kate version since 5.0 and other application
On Mon, Jun 8, 2015 at 7:13 PM, David Faure wrote:
> That wasn't very constructive/positive...
Sorry, i've spent way too much time fighting with the Qt folks on this one.
>
> On Monday 08 June 2015 15:22:20 Ben Cooksley wrote:
>> The Qt developers
>> didn't want to provide any infrastructure at
That wasn't very constructive/positive...
On Monday 08 June 2015 15:22:20 Ben Cooksley wrote:
> The Qt developers
> didn't want to provide any infrastructure at all to make developer
> environments (including our CI system) easier.
The *any* here is too broad. One approach was rejected, there ar
