#40782: wireshark-devel: update to 1.11.0 ------------------------------+----------------------- Reporter: ryandesign@… | Owner: hsivank@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: wireshark-devel | ------------------------------+----------------------- Comment (by macports@…): Replying to [comment:29 hsivank@…]:
This options are not provided by cmake (I ask myself : Is there a reason to disable ipv6 or ssl ?) Indeed, I don't see a good reason to disable them either. I'm just comparing to the stable wireshark port, but I'd bet very few people turn those off. Kerberos5 breaks build for now, so it is not enabled by default Is that specific to the cmake build? I had no trouble building with kerberos enabled without cmake. i agree, maybe we can make *fake* x11 and rtp variants to support legacy ? Good point, especially since your variants have more descriptive names. Aliases can be created if and when they are needed (e.g. variant x11 requires gtk2).
[[br]]Replying to [comment:31 hsivank@…]:
Replying to [comment:30 mojca@…]:
* `checksums`: you should use `rmd160` and `sha256`. You may remove `md5` and `sha1`. I would prefer *official* wireshark hash (md5,sha1,ripemd160) : https://www.wireshark.org/download/src/all-versions/SIGNATURES-1.99.8.txt I had made the same call in my proposed patch. Using the same checksums as upstream makes it easier to compare and verify.[[br]][[br]] {{{ default_variants +portaudio +zlib +lua +libsmi +gnutls +libgcrypt +cares +geoip
if {![variant_isset qt4] && ![variant_isset qt5] && ![variant_isset gtk2] && ![variant_isset gtk3] && ![variant_isset no_gui]} { default_variants +qt5 } }}} Is it correct ? That's pretty much what the current wireshark port uses, so that sounds right IMO.
-- Ticket URL: <https://trac.macports.org/ticket/40782#comment:32> MacPorts <https://www.macports.org/> Ports system for OS X