Wireshark mailing list archives
Re: Qt availability changes
From: Guy Harris <guy () alum mit edu>
Date: Tue, 28 Jan 2020 02:32:02 -0800
On Jan 28, 2020, at 2:24 AM, Graham Bloice <graham.bloice () trihedral com> 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 track latest with the potential for introducing new bugs. In summary this will have the opposite effect to that which Qt expects.
The FOSS community interprets annoying licensing terms as damage and routes around them? ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Qt availability changes Gerald Combs (Jan 27)
- Re: Qt availability changes Graham Bloice (Jan 27)
- Re: Qt availability changes Roland Knall (Jan 27)
- Re: Qt availability changes Guy Harris (Jan 27)
- Re: Qt availability changes Peter Wu (Jan 27)
- Re: Qt availability changes Graham Bloice (Jan 28)
- Re: Qt availability changes Guy Harris (Jan 28)
- Re: Qt availability changes Roland Knall (Jan 28)
- Re: Qt availability changes Roland Knall (Jan 28)
- Re: Qt availability changes João Valverde (Jan 30)
- Re: Qt availability changes Roland Knall (Jan 30)
- Re: Qt availability changes Roland Knall (Jan 27)
- Re: Qt availability changes Graham Bloice (Jan 27)