Package: hypersan Severity: wishlist Dear hyperscan maintainers,
thanks for your work with the hyperscan package in debian, it's really appreciated. I just knew that hyperscan v4.4 (which is about to be released by upstream) will include the so-called 'fat runtime' which enables hyperscan to choose the instruction set at runtime [0]. Upstream states that "there are no changes to how user applications are built againts the library". That's great. >From the suricata package point of view we rely on some details of the current hyperscan debian implementation: * the hyperscan install-time warning, which will perhaps no longer be relevant. * we build twice the suricata binary package, with and w/o hyperscan support. * we diverge the suricata binary at package install time. These things (and some more others) will probably require a spin of adjustement from our suricata side regarding hyperscan. Given the close dates of the stretch release, what do you think about timings? Also, please, let this bug be a coordination place for the change in hyperscan vs suricata. Feel free to reassign to suricata if you think this bug better fit there. [0] https://lists.01.org/pipermail/hyperscan/2017-January/000077.html
