From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] libconfuse: Version bump. 3.0 -> 3.3.
Date: Mon, 21 Nov 2022 23:03:36 +0100 [thread overview]
Message-ID: <20221121220336.541948-1-christian.melki@t2data.com> (raw)
Almost 6 years since last update.
Bunch of bugfixes, leaks and whatnots.
https://github.com/libconfuse/libconfuse/releases
* Change URL, stands on its own libconfuse github page.
* Change compression format, as we are given choices on the download.
Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
rules/libconfuse.make | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/rules/libconfuse.make b/rules/libconfuse.make
index 93ca3c8f6..bcbf31704 100644
--- a/rules/libconfuse.make
+++ b/rules/libconfuse.make
@@ -14,11 +14,11 @@ PACKAGES-$(PTXCONF_LIBCONFUSE) += libconfuse
#
# Paths and names
#
-LIBCONFUSE_VERSION := 3.0
-LIBCONFUSE_MD5 := bf03099ef213647451c70e54ad4b6e81
+LIBCONFUSE_VERSION := 3.3
+LIBCONFUSE_MD5 := a183cef2cecdd3783436ff8de500d274
LIBCONFUSE := confuse-$(LIBCONFUSE_VERSION)
-LIBCONFUSE_SUFFIX := tar.gz
-LIBCONFUSE_URL := https://github.com/martinh/libconfuse/releases/download/v$(LIBCONFUSE_VERSION)/$(LIBCONFUSE).$(LIBCONFUSE_SUFFIX)
+LIBCONFUSE_SUFFIX := tar.xz
+LIBCONFUSE_URL := https://github.com/libconfuse/libconfuse/releases/download/v$(LIBCONFUSE_VERSION)/$(LIBCONFUSE).$(LIBCONFUSE_SUFFIX)
LIBCONFUSE_SOURCE := $(SRCDIR)/$(LIBCONFUSE).$(LIBCONFUSE_SUFFIX)
LIBCONFUSE_DIR := $(BUILDDIR)/$(LIBCONFUSE)
LIBCONFUSE_LICENSE := ISC
--
2.34.1
next reply other threads:[~2022-11-21 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 22:03 Christian Melki [this message]
2022-11-23 6:57 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20221121220336.541948-1-christian.melki@t2data.com \
--to=christian.melki@t2data.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