Hi,

Here is the port, corrected with nice suggestions from sthen@ and bket@, including the patch which was in the original branch from github instead of my own patches. This seems to solve the table test problem.

Any more comments? OK to import?

Regards

On 4/7/20 2:04 PM, Stuart Henderson wrote:
Here's a diff with some fixes/tidying on top. (-c used in rc script
because the default path is a hardcoded /etc and it's easier to do this
than patch+SUBST_CMD :)

diff b7a3662a673d3be3318e448e144b808cc0159d8f /usr/ports/mystuff
blob - f5412a15261fab82c2ec2bbe9a9630896e3e95a4
file + net/sniproxy/Makefile
--- net/sniproxy/Makefile
+++ net/sniproxy/Makefile
@@ -12,18 +12,14 @@ HOMEPAGE =  https://github.com/dlundquist/sniproxy
MAINTAINER = Renaud Allard <ren...@allard.it> -# BSD2CLAUSE
+# BSD
  PERMIT_PACKAGE = Yes
-WANTLIB += c
+WANTLIB += c ev pcre udns
-# Dependencies
-BUILD_DEPENDS =        net/udns \
-               devel/libev \
-               devel/pcre \
-               devel/gettext,-tools
+BUILD_DEPENDS =        devel/gettext,-tools
-RUN_DEPENDS = net/udns \
+LIB_DEPENDS =  net/udns \
                devel/libev \
                devel/pcre
@@ -33,12 +29,12 @@ CONFIGURE_STYLE = autoreconf
  AUTORECONF =          ./autogen.sh
CONFIGURE_ARGS = --disable-rpath
-CONFIGURE_ENV =        CFLAGS="${CFLAGS} -I${LOCALBASE}/include" \
+CONFIGURE_ENV =        CPPFLAGS="-I${LOCALBASE}/include" \
                LDFLAGS="${LDFLAGS} -L${LOCALBASE}/lib"
post-install:
        ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/sniproxy
-       cd ${WRKSRC}; \
-          cp sniproxy.conf ${PREFIX}/share/examples/sniproxy
+       ${INSTALL_DATA} ${WRKSRC}/sniproxy.conf \
+               ${PREFIX}/share/examples/sniproxy
.include <bsd.port.mk>
blob - eb4e3707821a5330807784704349fab97c735dab
file + net/sniproxy/pkg/DESCR
--- net/sniproxy/pkg/DESCR
+++ net/sniproxy/pkg/DESCR
@@ -1,19 +1,12 @@
-SNIproxy - Proxies incoming HTTP and TLS connections based on the
-hostname contained in the initial request of the TCP session. This
-enables HTTPS name-based virtual hosting to separate backend servers
-without installing the private key on the proxy machine.
+Proxies incoming HTTP and TLS connections based on the hostname
+contained in the initial request of the TCP session without decrypting
+traffic. This enables HTTPS name-based virtual hosting to separate
+backend servers without installing the private key on the proxy machine.
-Features:
-
-Name-based proxying of HTTPS without decrypting traffic. No keys or
-certificates required.
-
-Supports both TLS and HTTP protocols.
-
-Supports IPv4, IPv6 and Unix domain sockets for both back end
+- Supports IPv4, IPv6 and Unix domain sockets for both back end
  servers and listeners.
-Supports multiple listening sockets per instance.
+- Supports multiple listening sockets per instance.
-Supports HAProxy proxy protocol to propagate original source address
-to backend servers.
+- Supports HAProxy protocol to propagate original source address to
+backend servers.
blob - 05ad720023af0204f35bdcea18f19b4d30af2b0e
file + net/sniproxy/pkg/PLIST
--- net/sniproxy/pkg/PLIST
+++ net/sniproxy/pkg/PLIST
@@ -1,9 +1,10 @@
  @comment $OpenBSD: PLIST,v$
-@newgroup _sniproxy:852
-@newuser _sniproxy:852:852:daemon:sniproxy daemon:/var/empty:/sbin/nologin
+@newgroup _sniproxy:853
+@newuser _sniproxy:853:853:daemon:sniproxy daemon:/var/empty:/sbin/nologin
  @rcscript ${RCDIR}/sniproxy
  @man man/man5/sniproxy.conf.5
  @man man/man8/sniproxy.8
  @bin sbin/sniproxy
  share/examples/sniproxy/
  share/examples/sniproxy/sniproxy.conf
+@sample ${SYSCONFDIR}/sniproxy.conf
blob - c3518a2e4a98c46864fd79e6de4f90d660b0a41e
file + net/sniproxy/pkg/sniproxy.rc
--- net/sniproxy/pkg/sniproxy.rc
+++ net/sniproxy/pkg/sniproxy.rc
@@ -3,6 +3,7 @@
  # $OpenBSD: rc.template,v 1.12 2018/01/11 19:30:18 rpe Exp $
daemon="${TRUEPREFIX}/sbin/sniproxy"
+daemon_flags="-c ${SYSCONFDIR}/sniproxy.conf"
. /etc/rc.d/rc.subr

Attachment: sniproxy.tgz
Description: application/compressed-tar

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to