svn commit: r471061 - head/audio/qjackctl

[Alexey Dokuchaev]

On Mon, May 28, 2018 at 01:35:41PM -0600, Sean Bruno wrote:
> On 05/28/18 13:11, Yuri wrote:
> ...
> > If some app doesn't support Qt4, you should complain to that app, IMO.
> > Your situation sounds like a fringe case that most users don't care
> > about.
> 
> But, this app DOES support QT4.  Until this change was made, it ran and
> built just fine.  It also builds and runs just fine with QT5, so I don't
> have any objection to the default of QT5.  Defaulting to QT5 seems very
> sensible to me.

That's exactly the right approach here: leave both options, let the user
choose.  I'm still defaulting my ports to Qt4 (at least trying to), and
sometimes even provide -qt4 as a separate port.  I'm perfectly happy with
Qt4, less happy with Qt5, and see no need to use Qt5.  But I'm just as
happy with Qt5 being default *as long as* I can tell the port that I want
Qt4 instead.

Removing working option just because it's not useful for you Yuri is not
your best act here, esp. after you've been explicitly asked for it.

./danfe