From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] neatvnc: version bump 0.6.0 -> 0.7.1
Date: Thu, 7 Dec 2023 12:09:59 +0100 [thread overview]
Message-ID: <20231207110959.1329069-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20231128095243.3994605-1-p.zabel@pengutronix.de>
Thanks, applied as cb9e1ff22d813ef65d4cb8743960611b24d24469.
Michael
[sent from post-receive hook]
On Thu, 07 Dec 2023 12:09:59 +0100, Philipp Zabel <p.zabel@pengutronix.de> wrote:
> https://github.com/any1/neatvnc/releases/tag/v0.7.1
>
> Incompatible API change in nvnc_enable_auth().
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> Message-Id: <20231128095243.3994605-1-p.zabel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/neatvnc.in b/rules/neatvnc.in
> index 0d0030ba772c..d962bf1907b9 100644
> --- a/rules/neatvnc.in
> +++ b/rules/neatvnc.in
> @@ -12,6 +12,7 @@ menuconfig NEATVNC
> select MESALIB if NEATVNC_GBM
> select MESALIB_GBM if NEATVNC_GBM
> select GNUTLS if NEATVNC_TLS
> + select NETTLE if NEATVNC_NETTLE
> prompt "neatvnc "
> help
> VNC Server library
> @@ -36,4 +37,8 @@ config NEATVNC_TLS
> bool
> prompt "enable encryption and authentication"
>
> +config NEATVNC_NETTLE
> + bool
> + prompt "enable websocket support"
> +
> endif
> diff --git a/rules/neatvnc.make b/rules/neatvnc.make
> index b71b269ac4c6..c4e63a2259a0 100644
> --- a/rules/neatvnc.make
> +++ b/rules/neatvnc.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_NEATVNC) += neatvnc
> #
> # Paths and names
> #
> -NEATVNC_VERSION := 0.6.0
> -NEATVNC_MD5 := 3a43fa75904990c023794b6057006c85
> +NEATVNC_VERSION := 0.7.1
> +NEATVNC_MD5 := 230c9d236686d79d9f72e96c9842b70a
> NEATVNC := neatvnc-$(NEATVNC_VERSION)
> NEATVNC_SUFFIX := tar.gz
> NEATVNC_URL := https://github.com/any1/neatvnc/archive/refs/tags/v$(NEATVNC_VERSION).$(NEATVNC_SUFFIX)
> @@ -38,6 +38,7 @@ NEATVNC_CONF_OPT := \
> -Dgbm=$(call ptx/endis,PTXCONF_NEATVNC_GBM)d \
> -Dh264=$(call ptx/endis,PTXCONF_NEATVNC_OPENH264)d \
> -Djpeg=$(call ptx/endis,PTXCONF_NEATVNC_JPEG)d \
> + -Dnettle=$(call ptx/endis,PTXCONF_NEATVNC_NETTLE)d \
> -Dsystemtap=false \
> -Dtests=false \
> -Dtls=$(call ptx/endis,PTXCONF_NEATVNC_TLS)d
prev parent reply other threads:[~2023-12-07 11:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 9:52 [ptxdist] [PATCH 1/2] " Philipp Zabel
2023-11-28 9:52 ` [ptxdist] [PATCH 2/2] weston: version bump 12.0.2 -> 13.0.0 Philipp Zabel
2023-12-07 11:09 ` Michael Olbrich [this message]
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=20231207110959.1329069-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=p.zabel@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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