Re: area51 bsd.qt.mk and net/wireshark-qt5

[Tobias C. Berner]

I think you're referring to our work around for the 2017Q1 branch we have
in bsd.qt.mk of plasma5/QT/bsd.qt.mk. We needed to add this, as the diverse
fixes to the ports that were needed for the Qt-5.7.1 import (say
graphics/poppler-qt5) have not been MFHed, and would have blocked
compilation of most of the ports in branches/plasma5.

As the next quarterly prorts tree will be cut soon, this can then be
dropped again, and wireshark-qt5 should work again -- sorry,  that I never
tested that one with the workaround.


mfg Tobias




On 27 March 2017 at 19:02, Dwayne MacKinnon  wrote:

> Hi all,
>
> Just a heads up. I was experimenting with poudriere to keep my area51
> granted kf5 stuff up to date and decided to add wireshark-qt5 to the
> build. Took me ages to figure out what was going on, but it turned out
> to be the "temporary workaround" of forcing c++11 on every qt5 using
> port in bsd.qt.mk.
>
> Rather than rewrite everything I'll just point you at the now-closed bug
> report I had filed with the wireshark maintainer.
>
> Cheers,
> Dwayne
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218066
>

area51 bsd.qt.mk and net/wireshark-qt5

[Dwayne MacKinnon]

Hi all,

Just a heads up. I was experimenting with poudriere to keep my area51
granted kf5 stuff up to date and decided to add wireshark-qt5 to the
build. Took me ages to figure out what was going on, but it turned out
to be the "temporary workaround" of forcing c++11 on every qt5 using
port in bsd.qt.mk.

Rather than rewrite everything I'll just point you at the now-closed bug
report I had filed with the wireshark maintainer.

Cheers,
Dwayne

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218066