Hello, in that new ebuild we have introduced the qt4 useflag. Unfortunately in the src_configure step, the econf and use_enable is missused. We have both $(use_enable gtk wireshark) and $(use_enable qt4 wireshark) so if both useflags are not enabled it will result to something like --enable-wireshark --disable-wireshark and the binary won't be build. Reproducible: Always
I don't see what you mean. If neither is enabled, USE="-gtk -qt4", you don't want the wireshark binary, right? This is precisely what happens with the -r0 ebuild when you set USE=-gtk. When you disable both USE flags, then you don't get the wireshark executable. Is that what you meant? $ grep executable metadata.xml <flag name='gtk'>Build the wireshark executable with a GTK+ UI.</flag> <flag name='qt4'>Build the wireshark executable with a Qt UI.</flag>
I guess this is what you meant.
I mean if you have something like `USE="gtk -qt4" emerge wireshark` you will have something like ./configure --enable-wireshark (due to the $(use_enable gtk wireshark)) --dissable-wireshark (due to the $(use_enable qt4 wireshark))
Created attachment 350886 [details, diff] wireshark-1.10.0-r1.ebuild.diff possible fix...
(In reply to Lars Wendler (Polynomial-C) from comment #4) > Created attachment 350886 [details, diff] [details, diff] > wireshark-1.10.0-r1.ebuild.diff > > possible fix... That looks good.
works for me, thanks for the quick fix.
Fixed in CVS. Thanks for the report and for the patch!
*** Bug 473348 has been marked as a duplicate of this bug. ***
