From: ne-vlezay80 <ne-vlezay80@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Enable nfqueue support
Date: Sat, 21 Oct 2023 01:18:47 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46807@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
There is a new pull request by ne-vlezay80 against master on the void-packages repository
https://github.com/ne-vlezay80/void-packages patch-1
https://github.com/void-linux/void-packages/pull/46807
Enable nfqueue support
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**|**briefly**|**NO**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/46807.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-1-46807.patch --]
[-- Type: text/x-diff, Size: 1268 bytes --]
From 2c38d2890e35e2b314350057bb56ef2be413a60c Mon Sep 17 00:00:00 2001
From: ne-vlezay80 <ne-vlezay80@yandex.ru>
Date: Sat, 21 Oct 2023 02:18:37 +0300
Subject: [PATCH] Enable nfqueue support
---
srcpkgs/suricata/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/suricata/template b/srcpkgs/suricata/template
index 3e4f58bae137d..2817475301bad 100644
--- a/srcpkgs/suricata/template
+++ b/srcpkgs/suricata/template
@@ -6,12 +6,12 @@ build_style=gnu-configure
build_helper="$(vopt_if rust rust)"
configure_args="--disable-gccmarch-native $(vopt_enable rust)
$(vopt_enable lua) $(vopt_enable hiredis) --disable-suricata-update
- --disable-static --enable-non-bundled-htp"
+ --disable-static --enable-non-bundled-htp --enable-nfqueue"
hostmakedepends="pkg-config $(vopt_if rust cargo)"
makedepends="libnet-devel libpcap-devel pcre-devel libyaml-devel libcap-ng-devel
liblz4-devel liblzma-devel file-devel jansson-devel nss-devel libhtp-devel
$(vopt_if rust rust-std) $(vopt_if lua lua53-devel)
- $(vopt_if hiredis hiredis-devel)"
+ $(vopt_if hiredis hiredis-devel) libnetfilter_queue-devel"
short_desc="Suricata is a network IDS, IPS and NSM engine"
maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-2.0-only"
next reply other threads:[~2023-10-20 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 23:18 ne-vlezay80 [this message]
2024-01-20 1:46 ` github-actions
2024-02-04 1:45 ` [PR PATCH] [Closed]: " github-actions
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46807@inbox.vuxu.org \
--to=ne-vlezay80@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).