Re: [Development] Mime database size

Mathias Hasselmann schreef op 23-2-2015 om 07:48: > Am 17.02.2015 um 14:36 schrieb Cristian Adam: >> One could rewrite this small utility into Qt and then it would be >> available everywhere. > Somehow I thought that one of the big benefits of free software and open > source is, that you _don't_ ha

Re: [Development] Mime database size

On Monday 23 February 2015 07:48:37 Mathias Hasselmann wrote: > Am 17.02.2015 um 14:36 schrieb Cristian Adam: > > One could rewrite this small utility into Qt and then it would be > > available everywhere. > > Somehow I thought that one of the big benefits of free software and open > source is, th

Re: [Development] Mime database size

Am 17.02.2015 um 14:36 schrieb Cristian Adam: > One could rewrite this small utility into Qt and then it would be > available everywhere. Somehow I thought that one of the big benefits of free software and open source is, that you _don't_ have to rewrite each and every simple tool. Obviously I'v

[Development] CI failing due to tst_licenses.pl test

Hi, Changing are failing to integrated because the license header used by the tst_licenses.pl test does not match the existing headers in the source. Errors like the following are seen: > # Failed test 'Mismatch in license text in examples/qml/dynamicscene/content/Button.qml > # Actual:

Re: [Development] SSL Plans for Qt 5.6

On 22 February 2015 at 20:08, Sorvig Morten wrote: > > > On 22 Feb 2015, at 18:50, Jeremy Lainé wrote: > > > > On 02/22/2015 06:42 PM, Richard Moore wrote: > >> > >> > >> On 22 February 2015 at 17:39, Jeremy Lainé > wrote: > >> > >> Whilst I agree with the goal of dropping support for old / unm

Re: [Development] SSL Plans for Qt 5.6

> On 22 Feb 2015, at 18:50, Jeremy Lainé wrote: > > On 02/22/2015 06:42 PM, Richard Moore wrote: >> >> >> On 22 February 2015 at 17:39, Jeremy Lainé wrote: >> >> Whilst I agree with the goal of dropping support for old / unmaintained >> OpenSSL versions, in the case of OS X we probably need

Re: [Development] SSL Plans for Qt 5.6

On 02/22/2015 06:57 PM, Richard Moore wrote: > > > > Slightly off-topic but related : does the Qt Company have any > privileged access to Apple engineers working on Secure Transport? > I would like to understand what the plans are regarding support > for NPN / ALPN. > > > No idea

Re: [Development] Mime database size

On Thursday 19 February 2015 01:55:01 Kevin Kofler wrote: > Arnaud Vrac wrote: > > Commit fbeeaf2 in qtbase adds QT_NO_MIMETYPE: > > > > "The mime type stuff generates one of the biggest translation units in > > QtCore due to the compressed 1.7MB freedesktop.org.xml resource. With > > QT_NO_MIMETY

Re: [Development] SSL Plans for Qt 5.6

On Sunday 22 February 2015 13:37:36 Richard Moore wrote: > On 21 February 2015 at 18:38, Thiago Macieira > > wrote: > > > I suspect enterprise distros etc. will continue to support 1.0.0 for a > > > while. I'm not sure of the level of adoption of 1.0.1 at the moment, so > > > I > > > was erring o

Re: [Development] SSL Plans for Qt 5.6

On Sunday 22 February 2015 18:50:24 Jeremy Lainé wrote: > I understood what you were saying, I think I just expressed my concerns > poorly. When I said "now way to build even from source", I meant "no way > to build support for OpenSSL as shipped by Apple". Anyway, my main > concern is : how do we

Re: [Development] SSL Plans for Qt 5.6

On 22 February 2015 at 17:50, Jeremy Lainé wrote: > On 02/22/2015 06:42 PM, Richard Moore wrote: > > > > On 22 February 2015 at 17:39, Jeremy Lainé wrote: > >> >> Whilst I agree with the goal of dropping support for old / unmaintained >> OpenSSL versions, in the case of OS X we probably need to

Re: [Development] SSL Plans for Qt 5.6

On 02/22/2015 06:42 PM, Richard Moore wrote: > > > On 22 February 2015 at 17:39, Jeremy Lainé > wrote: > > > Whilst I agree with the goal of dropping support for old / > unmaintained > OpenSSL versions, in the case of OS X we probably need to map out the >

Re: [Development] SSL Plans for Qt 5.6

On 22 February 2015 at 17:39, Jeremy Lainé wrote: > Hi Rich, > > On 02/21/2015 06:30 PM, Richard Moore wrote: > > Here's an outline of stuff I'd like to see get done in the Qt 5.6 time > > frame: > > > > * Complete removal of openssl 0.9.8 support > > > > This has been unsupported for a while and

Re: [Development] SSL Plans for Qt 5.6

Hi Rich, On 02/21/2015 06:30 PM, Richard Moore wrote: > Here's an outline of stuff I'd like to see get done in the Qt 5.6 time > frame: > > * Complete removal of openssl 0.9.8 support > > This has been unsupported for a while and was really only retained > since it is the only version apple ship o

Re: [Development] SSL Plans for Qt 5.6

Gingerbrad is using 1.0.0  https://android.googlesource.com/platform/external/openssl.git/+/gingerbread/openssl.version First 1.0.1 was used in Jelly Bean  https://android.googlesource.com/platform/external/openssl.git/+/jb-mr0-release/openssl.version So, for Android the minimum SSL version is 1.0.

Re: [Development] SSL Plans for Qt 5.6

On 21 February 2015 at 19:06, Richard Moore wrote: > I suspect enterprise distros etc. will continue to support 1.0.0 for a > while. I'm not sure of the level of adoption of 1.0.1 at the moment, so I > was erring on the side of caution. Any feedback on this is welcome. Quick investigation, * Debi

Re: [Development] SSL Plans for Qt 5.6

On 21 February 2015 at 18:38, Thiago Macieira wrote: > > I suspect enterprise distros etc. will continue to support 1.0.0 for a > > while. I'm not sure of the level of adoption of 1.0.1 at the moment, so I > > was erring on the side of caution. Any feedback on this is welcome. > > And with CII su