From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Alexander Dahl <ada@thorsis.com>
Subject: Re: [ptxdist] [APPLIED] libnet: version bump 1.1.6 -> 1.3
Date: Thu, 25 Jun 2026 21:23:36 +0200 [thread overview]
Message-ID: <20260625192336.832641-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260622081230.187757-2-ada@thorsis.com>
Thanks, applied as 147d1c9114fe88de7a7d025d9878d5acec748e2f.
Michael
[sent from post-receive hook]
On Thu, 25 Jun 2026 21:23:36 +0200, Alexander Dahl <ada@thorsis.com> wrote:
> Project moved from SourceForge to GitHub before v1.2
> (see hint on old sourceforge website).
>
> While v1.1.6 was released back in 2012, v1.2 was released in 2019,
> and v1.3 in 2023. Noteworthy changes in addition to accumulated fixes:
>
> - Removed lua bindings
> - Added pkg-config support
> - Added support for LLDP, mandatory TLVs
> - Added support for Cisco UniDirectional Link Detection (UDLD)
> - Assume everyone on Linux has PF_PACKET now
>
> See release notes for details.
>
> Link: https://github.com/libnet/libnet/releases/tag/v1.2
> Link: https://github.com/libnet/libnet/releases/tag/v1.3
> Link: https://sourceforge.net/projects/libnet-dev/
> Signed-off-by: Alexander Dahl <ada@thorsis.com>
> Message-Id: <20260622081230.187757-2-ada@thorsis.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libnet.make b/rules/libnet.make
> index 939285ffde23..59f193b30382 100644
> --- a/rules/libnet.make
> +++ b/rules/libnet.make
> @@ -15,11 +15,11 @@ PACKAGES-$(PTXCONF_LIBNET) += libnet
> #
> # Paths and names
> #
> -LIBNET_VERSION := 1.1.6
> -LIBNET_SHA256 := d392bb5825c4b6b672fc93a0268433c86dc964e1500c279dc6d0711ea6ec467a
> +LIBNET_VERSION := 1.3
> +LIBNET_SHA256 := ad1e2dd9b500c58ee462acd839d0a0ea9a2b9248a1287840bc601e774fb6b28f
> LIBNET := libnet-$(LIBNET_VERSION)
> LIBNET_SUFFIX := tar.gz
> -LIBNET_URL := $(call ptx/mirror, SF, libnet-dev/$(LIBNET).$(LIBNET_SUFFIX))
> +LIBNET_URL := https://github.com/libnet/libnet/releases/download/v$(LIBNET_VERSION)/$(LIBNET).$(LIBNET_SUFFIX)
> LIBNET_SOURCE := $(SRCDIR)/$(LIBNET).$(LIBNET_SUFFIX)
> LIBNET_DIR := $(BUILDDIR)/$(LIBNET)
>
> @@ -34,7 +34,18 @@ LIBNET_CONF_ENV := \
>
> LIBNET_CONF_OPT := \
> $(CROSS_AUTOCONF_USR) \
> + --disable-doxygen-doc \
> + --disable-doxygen-dot \
> + --disable-doxygen-man \
> + --disable-doxygen-rtf \
> + --disable-doxygen-xml \
> + --disable-doxygen-chm \
> + --disable-doxygen-chi \
> + --disable-doxygen-html \
> + --disable-doxygen-ps \
> + --disable-doxygen-pdf \
> --disable-samples \
> + --disable-tests \
> --with-link-layer=linux
>
> # ----------------------------------------------------------------------------
next prev parent reply other threads:[~2026-06-25 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 8:12 [ptxdist] [PATCH 0/2] libnet: version bump and add license information Alexander Dahl via ptxdist
2026-06-22 8:12 ` [ptxdist] [PATCH 1/2] libnet: version bump 1.1.6 -> 1.3 Alexander Dahl via ptxdist
2026-06-25 19:23 ` Michael Olbrich [this message]
2026-06-22 8:12 ` [ptxdist] [PATCH 2/2] libnet: Add license information Alexander Dahl via ptxdist
2026-06-25 19:23 ` [ptxdist] [APPLIED] " Michael Olbrich
2026-06-22 8:30 ` [ptxdist] [PATCH 0/2] libnet: version bump and add " Alexander Dahl via ptxdist
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=20260625192336.832641-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ada@thorsis.com \
--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