From: Thomas Schwinge <thomas@codesourcery.com>
To: <guix-devel@gnu.org>
Cc: Marius Bakke <marius@gnu.org>
Subject: Re: GNU Make 4.4 released!
Date: Thu, 10 Nov 2022 11:57:12 +0100 [thread overview]
Message-ID: <878rkj2i2f.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <5723c169042b5edbedff1035b008f9bdc6f9fb37.camel@gnu.org>
Hi!
GNU Make 4.4 has recently been released, see
<https://lists.gnu.org/archive/html/info-gnu/2022-10/msg00008.html>,
which I'd like to get available in Guix.
In Guix master branch, 'gnu/packages/base.scm', 'define-public gnu-make',
I see 'version "4.3"', last updated from 'version "4.2.1"' by Marius
(CCed) in 2020-01-21 commit cdba91486a60bbba727d843707322f98f8286124
"gnu: make: Update to 4.3".
In 2020-03-28 commit 5fd0c288cf238e4369cc6bd0bfbee068a362a9f0
"gnu: OpenJDK: Build with GNU Make 4.2", Marius added a
'define-public gnu-make-4.2', because -- as I understand -- for certain
packages there have been issues with 4.3.
Thus my question: do we/I now just upgrade 'gnu-make' from 4.3 to 4.4, or
do we maintain 4.3 as default for the time being, and add a separate
'gnu-make-4.4' for now -- and what kind of testing does such a change
need?
I have not yet looked at the 4.3..4.4 source code differences to try
spotting any new things creep in that need special handling.
Grüße
Thomas
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
next parent reply other threads:[~2022-11-10 10:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5723c169042b5edbedff1035b008f9bdc6f9fb37.camel@gnu.org>
2022-11-10 10:57 ` Thomas Schwinge [this message]
2022-11-10 12:18 ` GNU Make 4.4 released! Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rkj2i2f.fsf@euler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=guix-devel@gnu.org \
--cc=marius@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).