From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Brett Gilio <brettg@posteo.net>
Cc: 33482@debbugs.gnu.org
Subject: [bug#33482] [PATCH] gnu: meson: Update to 0.48.2
Date: Tue, 27 Nov 2018 13:43:12 +0100 [thread overview]
Message-ID: <20181127124312.w743rxx2leebax3a@thebird.nl> (raw)
In-Reply-To: <874lc6jgpf.fsf@posteo.net>
One good reason for the meson upgrade is that it has D support.
The GNU D compiler is now part of the GCC project:
https://phoronix.com/scan.php?page=news_item&px=GCC-9-Merges-D-Language
Pj.
On Sat, Nov 24, 2018 at 03:42:04PM -0600, Brett Gilio wrote:
>
> Ludovic Courtès writes:
>
> > Brett Gilio <brettg@posteo.net> skribis:
> >
> >> ---
> >> gnu/packages/build-tools.scm | 4 ++--
> >> 1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/gnu/packages/build-tools.scm b/gnu/packages/build-tools.scm
> >> index a52ee480a..e87d4fa2c 100644
> >> --- a/gnu/packages/build-tools.scm
> >> +++ b/gnu/packages/build-tools.scm
> >> @@ -158,7 +158,7 @@ files and generates build instructions for the Ninja build system.")
> >> (define-public meson
> >> (package
> >> (name "meson")
> >> - (version "0.47.1")
> >> + (version "0.48.2")
> >
> > This would entail 868 rebuilds according to:
> >
> > guix refresh -l -e '(@ (gnu packages build-tools) meson-for-build)'
> >
> > so I think we’ll wait until ‘core-updates’ has been merged. One thing
> > at a time. :-)
> >
> > Thanks,
> > Ludo’.
>
> My apologies. I forgot to look into the dependencies for rebuild.
>
>
>
next prev parent reply other threads:[~2018-11-27 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 6:22 [bug#33482] [PATCH] gnu: meson: Update to 0.48.2 Brett Gilio
2018-11-24 21:39 ` Ludovic Courtès
2018-11-24 21:42 ` Brett Gilio
2018-11-27 12:43 ` Pjotr Prins [this message]
2018-12-04 19:07 ` bug#33482: " Marius Bakke
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=20181127124312.w743rxx2leebax3a@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=33482@debbugs.gnu.org \
--cc=brettg@posteo.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.