On Tuesday 21 May 2013 12:11:36 Marco Martin wrote:
> On Monday 20 May 2013 20:41:27 David Faure wrote:
> > Don't use API that's only in qtbase-dev, you would break compilation for
> > everyone else.
> >
> > At the last kf5 meeting we discussed setting up a KDE mirror of qt5.git
> > with more rece
On Monday 20 May 2013 20:41:27 David Faure wrote:
>
> Don't use API that's only in qtbase-dev, you would break compilation for
> everyone else.
>
> At the last kf5 meeting we discussed setting up a KDE mirror of qt5.git with
> more recent sha1s, but the meeting minutes don't actually say who's
>
On Tue, May 21, 2013 at 6:41 AM, David Faure wrote:
> On Monday 20 May 2013 10:11:15 Ian Monroe wrote:
>> On Mon, May 20, 2013 at 8:28 AM, David Faure wrote:
>> ...
>>
>> > qt5.git defines which sha1 of the submodules you should get.
>>
>> It hasn't been updated in a month.
>
> That's fine though
On Mon, May 20, 2013 at 6:17 AM, Alexander Neundorf wrote:
>
> On Tuesday 14 May 2013, Alexander Neundorf wrote:
> > On Tuesday 14 May 2013, Stephen Kelly wrote:
> > > Alexander Neundorf wrote:
> > > > Additionally we don't check in cmake that the Qt which has been found
> > > > is good enough.
>
On Mon, May 20, 2013 at 8:28 AM, David Faure wrote:
...
> qt5.git defines which sha1 of the submodules you should get.
It hasn't been updated in a month.
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/lis
On Monday 20 May 2013 10:11:15 Ian Monroe wrote:
> On Mon, May 20, 2013 at 8:28 AM, David Faure wrote:
> ...
>
> > qt5.git defines which sha1 of the submodules you should get.
>
> It hasn't been updated in a month.
That's fine though. It's the basis for KF5 development.
Don't use API that's on
