Re: Staying on top of Qt security

[Andreas Enge <andreas@enge.fr>]

On Thu, Feb 25, 2016 at 10:06:42AM +0100, Andreas Enge wrote:
> Probably we can:
> "jalv.qt (...) This is a versionm of Jalv with a GUI implemented in Qt.
> It is mainly for developer testing purposes, for a production ready program
> use jalv.gtk."

Qt-4 support dropped in commit 03d55ee.

This does not have much impact, however, since there is still a dependency
on suil, which depends on qt-4.

So the question still stands:
On Thu, Feb 25, 2016 at 09:22:29PM +0100, Andreas Enge wrote:
> On Thu, Feb 25, 2016 at 10:38:32AM +0100, Ricardo Wurmus wrote:
> > We cannot know what toolkit the GUI of audio plugins will use.  Suil
> > supports the three most popular ones so plugin authors providing GUIs
> > don’t need to worry about support in popular hosts such as Ardour.
> So you would keep the dependency on qt? What is annoying is that right now,
> this must be qt-4. The library had its last release in August 2014, but
> I see the following svn commit:
> r5725 | drobilla | 2015-09-12 18:02:02 +0200 (Sa, 12 Sep 2015) | 1 line
> Add Gtk2 and X11 in Qt5 wrappers.
>
> Should we try to package an svn checkout? And convince the author to make
> a new release?

Andreas