From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] procps-ng: Version bump 3.3.17 -> 4.0.0
Date: Fri, 8 Apr 2022 13:32:34 +0200 [thread overview]
Message-ID: <YlAdUgYdfrNbJyPF@pengutronix.de> (raw)
In-Reply-To: <20220331121031.3486660-1-christian.melki@t2data.com>
On Thu, Mar 31, 2022 at 02:10:31PM +0200, Christian Melki wrote:
> Approx 1 year worth of changes.
> A major release, afaiu, denoting newlib compatibility.
> Changelog: https://gitlab.com/procps-ng/procps/-/releases
>
> * Remove configure option without-elogind.
> * Library renamed to libproc-2. This might cause issues
> if anyone is depending on a specific library name and SO library versions.
It's needed by igt-gpu-tools. There is an upstream issue[1] but no fix for
it. I'll drop this for now.
Michael
[1] https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/116
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> ---
> rules/procps.make | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/rules/procps.make b/rules/procps.make
> index 42fec7bfe..15326ea45 100644
> --- a/rules/procps.make
> +++ b/rules/procps.make
> @@ -17,8 +17,8 @@ PACKAGES-$(PTXCONF_PROCPS) += procps
> #
> # Paths and names
> #
> -PROCPS_VERSION := 3.3.17
> -PROCPS_MD5 := d60613e88c2f442ebd462b5a75313d56
> +PROCPS_VERSION := 4.0.0
> +PROCPS_MD5 := eedf93f2f6083afb7abf72188018e1e5
> PROCPS := procps-ng-$(PROCPS_VERSION)
> PROCPS_SUFFIX := tar.xz
> PROCPS_URL := $(call ptx/mirror, SF, procps-ng/Production/$(PROCPS).$(PROCPS_SUFFIX))
> @@ -60,8 +60,7 @@ PROCPS_CONF_OPT := \
> --without-libiconv-prefix \
> --without-libintl-prefix \
> --$(call ptx/wwo, PTXCONF_PROCPS_USES_NCURSES)-ncurses \
> - --$(call ptx/wwo, PTXCONF_PROCPS_WITH_SYSTEMD)-systemd \
> - --without-elogind
> + --$(call ptx/wwo, PTXCONF_PROCPS_WITH_SYSTEMD)-systemd
>
>
> # ----------------------------------------------------------------------------
> @@ -77,7 +76,7 @@ $(STATEDIR)/procps.targetinstall:
> @$(call install_fixup, procps,AUTHOR,"Clemens Gruber <clemens.gruber@pqgruber.com>")
> @$(call install_fixup, procps,DESCRIPTION,missing)
>
> - @$(call install_lib, procps, 0, 0, 0644, libprocps)
> + @$(call install_lib, procps, 0, 0, 0644, libproc-2)
>
> ifdef PTXCONF_PROCPS_FREE
> @$(call install_copy, procps, 0, 0, 0755, -, /usr/bin/free)
> --
> 2.32.0
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
>
--
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 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2022-04-08 11:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 12:10 Christian Melki
2022-04-08 11:32 ` 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=YlAdUgYdfrNbJyPF@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