> Am 30.01.2020 um 15:56 schrieb João Valverde
> :
>
>
>
>> On 28/01/20 13:30, Roland Knall wrote:
>> A good overview by one of the KDE developers, focussing - obviously - on the
>> Linux side:
>>
>> https://tsdgeos.blogspot.com/2020/01/the-qt-company-is-stopping-qt-lts.html
>>
>> Long
On 27/01/20 20:05, Gerald Combs wrote:
The Qt Company recently announced upcoming changes in the distribution of their
official binaries:
https://www.qt.io/blog/qt-offering-changes-2020
https://lists.qt-project.org/pipermail/development/2020-January/thread.html#38316
Two of the changes
On 28/01/20 13:30, Roland Knall wrote:
A good overview by one of the KDE developers, focussing - obviously -
on the Linux side:
https://tsdgeos.blogspot.com/2020/01/the-qt-company-is-stopping-qt-lts.html
Long story short - we may have to host our own version at some point.
I think this
A good overview by one of the KDE developers, focussing - obviously - on
the Linux side:
https://tsdgeos.blogspot.com/2020/01/the-qt-company-is-stopping-qt-lts.html
Long story short - we may have to host our own version at some point.
Am Di., 28. Jan. 2020 um 12:44 Uhr schrieb Roland Knall :
>
Am Di., 28. Jan. 2020 um 01:43 Uhr schrieb Peter Wu :
>
>
> I think it is worth emphasizing that it only affects users who build or
> develop Wireshark from source. The final Wireshark installer will still
> bundle the Qt bits.
>
We need to get those bundles from somewhere, meaning we either
On Jan 28, 2020, at 2:24 AM, Graham Bloice wrote:
> As noted somewhere in the linked discussion, I suspect that the end result
> will be projects caching a "suitable" version for a while and then
> periodically, e.g. major releases, updating to the current latest. It's too
> much work to
On Tue, 28 Jan 2020 at 00:43, Peter Wu wrote:
>
>
> > > As folks noted in the thread you linked to, how will CI systems handle
> > > this?
>
> Good question... I have automated Qt installation for Travis CI with
>
>
On Mon, Jan 27, 2020 at 09:53:11PM +0100, Roland Knall wrote:
> Well it took me a while to read through all the comments.
Indeed, some highlights:
* A Qt community contributor suggests potential adverse effects for the
Qt Company such as forking and less contributions.
On Jan 27, 2020, at 12:53 PM, Roland Knall wrote:
> Finally, I would not call it a day yet. Qt has become a very strategic
> project for a lot of people. I could imagine, that the outcry over this
> decision will be as big as the one 2015 over the first attempt to close down
> the installer.
Well it took me a while to read through all the comments.
First of all, I understand their - Qt's - reasoning. It makes sense from a
business side of things, and they are getting rather big. Developing that
framework is not the easiest task and they need money (sounds too
familiar). This sucks,
On Mon, 27 Jan 2020 at 20:06, Gerald Combs wrote:
> The Qt Company recently announced upcoming changes in the distribution of
> their official binaries:
>
> https://www.qt.io/blog/qt-offering-changes-2020
>
> https://lists.qt-project.org/pipermail/development/2020-January/thread.html#38316
>
>
The Qt Company recently announced upcoming changes in the distribution of their
official binaries:
https://www.qt.io/blog/qt-offering-changes-2020
https://lists.qt-project.org/pipermail/development/2020-January/thread.html#38316
Two of the changes adversely affect how we develop and build
12 matches
Mail list logo
