From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] glib: Version bump. 2.72.2 -> 2.73.1
Date: Fri, 1 Jul 2022 13:05:38 +0200 [thread overview]
Message-ID: <Yr7VAmpUoTqeh9zO@pengutronix.de> (raw)
In-Reply-To: <20220628135454.3394558-1-christian.melki@t2data.com>
On Tue, Jun 28, 2022 at 03:54:54PM +0200, Christian Melki wrote:
> Bunch of features and bugfixes.
> https://gitlab.gnome.org/GNOME/glib/-/blob/main/NEWS
>
> Glib has "reuse"-ified the codebase.
> * Licensing conditions changed.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> ---
> rules/glib.make | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/rules/glib.make b/rules/glib.make
> index 144814c77..a0ab9f644 100644
> --- a/rules/glib.make
> +++ b/rules/glib.make
> @@ -15,17 +15,17 @@ PACKAGES-$(PTXCONF_GLIB) += glib
> #
> # Paths and names
> #
> -GLIB_VERSION := 2.72.2
> -GLIB_MD5 := 6874205c81e9634fb47f4efb73183d00
> +GLIB_VERSION := 2.73.1
I'd like to stick to stable releases for glib unless there is a very good
reason to use an unstable version.
Michael
> +GLIB_MD5 := 09864233dc900589a49135551eea89d6
> GLIB := glib-$(GLIB_VERSION)
> GLIB_SUFFIX := tar.xz
> GLIB_URL := $(call ptx/mirror, GNOME, glib/$(basename $(GLIB_VERSION))/$(GLIB).$(GLIB_SUFFIX))
> GLIB_SOURCE := $(SRCDIR)/$(GLIB).$(GLIB_SUFFIX)
> GLIB_DIR := $(BUILDDIR)/$(GLIB)
> -GLIB_LICENSE := LGPL-2.0-or-later
> +GLIB_LICENSE := LGPL-2.1-or-later
> GLIB_LICENSE_FILES := \
> - file://glib/glib.h;startline=1;endline=16;md5=48a2e189b0f5db4b3c3fd8f53bdb55a0 \
> - file://COPYING;md5=4fbd65380cdd255951079008b364516c
> + file://glib/glib.h;startline=1;endline=19;md5=22ff60c3523af881a2fbee898a4eaeac \
> + file://LICENSES/LGPL-2.1-or-later.txt;md5=41890f71f740302b785c27661123bff5
>
> # ----------------------------------------------------------------------------
> # Prepare
> @@ -39,7 +39,6 @@ GLIB_CONF_OPT := \
> $(CROSS_MESON_USR) \
> -Dbsymbolic_functions=true \
> -Ddtrace=false \
> - -Dfam=false \
> -Dforce_posix_threads=true \
> -Dglib_assert=true \
> -Dglib_checks=true \
> --
> 2.34.1
>
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2022-07-01 11:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 13:54 Christian Melki
2022-07-01 11:05 ` Michael Olbrich [this message]
2022-07-01 15:25 ` Christian Melki
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=Yr7VAmpUoTqeh9zO@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=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