From: "Ludovic Courtès" <ludo@gnu.org>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: <guix-devel@gnu.org>, Marius Bakke <marius@gnu.org>
Subject: Re: GNU Make 4.4 released!
Date: Thu, 10 Nov 2022 13:18:24 +0100 [thread overview]
Message-ID: <87k043hujz.fsf@gnu.org> (raw)
In-Reply-To: <878rkj2i2f.fsf@euler.schwinge.homeip.net> (Thomas Schwinge's message of "Thu, 10 Nov 2022 11:57:12 +0100")
Hi Thomas!
Thomas Schwinge <thomas@codesourcery.com> skribis:
> 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?
Yes. In ‘master’ you would definitely define ‘gnu-make-4.4’ since
changing the default one would incur a world rebuild.
In ‘core-updates’, where world rebuilds are allowed, we may or may not
default to 4.4, depending on the amount of breakage.
BTW, for immediate use, you can also try:
guix build make --with-source=mirror://gnu/make/make-4.4.tar.gz
with the understanding that source won’t be authenticated.
Better would be to run:
guix build make --with-latest=make
… but there’s currently a bug preventing this:
<https://issues.guix.gnu.org/59168>.
‘--with-source’ and ‘--with-latest’ work with all the tools:
https://guix.gnu.org/manual/devel/en/html_node/Package-Transformation-Options.html
HTH,
Ludo’.
prev parent reply other threads:[~2022-11-10 12:19 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 ` GNU Make 4.4 released! Thomas Schwinge
2022-11-10 12:18 ` Ludovic Courtès [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
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=87k043hujz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=marius@gnu.org \
--cc=thomas@codesourcery.com \
/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).