lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ANN: Frescobaldi 3.1 has been released!


From: Urs Liska
Subject: Re: ANN: Frescobaldi 3.1 has been released!
Date: Sat, 28 Dec 2019 09:46:29 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2


Am 28.12.19 um 01:01 schrieb address@hidden:
On 12/28, Simon Albrecht wrote:
I happen to have a little problem with that as well; here on my Ubuntu
16.04 machine neither apt nor synaptic can find any variation of
qtwebengine5. There are several variations of webkit or so, but that’s
probably something different, right? What can I do?
The first version of Ubuntu to package qtwebengine was 18.04 Bionic.[1]
Is upgrading an option for you, or do you need to stick with 16.04?


Ubuntu 16.04 is a LTS release with (IIRC) five years of support. So it is not unreasonable for someone to use it. However, we (Frescobaldi) seem to have been hit by this five-year term since we're dealing with a change in the Qt framework that has phased out support for a module over (again, IIRC) 2-3 years. So all *current* Linux distributions ship with a Qt version that only includes QtWebEngine and not QtWebKit anymore. There has been a range of Qt versions including both.

The question is whether a project like Frescobaldi can reasonably be expected to actively support such an old OS, even if it's LTS. I'd assume that lTS guarantees you security patches but not that every new software will run.

Before upgrading to a newer OS it might be an option to use a current Qt/PyQt downloaded or compiled from somewhere. @Simon you could do us a huge favor by exploring that possibility and providing information about it for the Wiki. In addition it would be good to have a list of distributions that include the "new" module, both modules, or only the "old" modules (i.e. won't work with Frescobaldi 3.1).

Urs


Mason

[1]
https://packages.ubuntu.com/search?keywords=qtwebengine&searchon=sourcenames




reply via email to

[Prev in Thread] Current Thread [Next in Thread]