From: Leo Famulari <leo@famulari.name>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: 30411-done@debbugs.gnu.org
Subject: [bug#30411] [PATCH] gnu: ldc: Update to 1.7.0.
Date: Fri, 23 Feb 2018 12:31:07 -0500 [thread overview]
Message-ID: <20180223173107.GA24390@jasmine.lan> (raw)
In-Reply-To: <20180223171008.GA6186@thebird.nl>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
On Fri, Feb 23, 2018 at 06:10:08PM +0100, Pjotr Prins wrote:
> On Fri, Feb 23, 2018 at 12:59:32PM +0100, Danny Milosavljevic wrote:
> > Yeah, I've applied it to master with some small changes a few days
> > ago. It builds and tests fine now.
>
> Thanks! Does this mean it can go into the new Guix release?
Yes. I don't know the maintainers' plans for the next release, but
whatever is on the master branch now will be in the release, barring any
surprises.
> i686 and armhf failing on lit-tests looking for make. I'll
> take a look when I have time in the coming days.
>
> We should consider changing the name of ldc.scm to dlang.scm. There
> are two other D compilers which are libre. Including a GNU one ;). At
> the same time the packages could be re-indented. wdyt?
Sure, patches welcome :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-02-23 17:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 14:12 [bug#30411] [FIXME] Dlang ldc and dub packages fail on core-updates Pjotr Prins
2018-02-18 6:09 ` [bug#30411] [PATCH] gnu: ldc: Update to 1.7.0 pjotr.public12
2018-02-18 12:34 ` Danny Milosavljevic
2018-02-18 21:58 ` Pjotr Prins
[not found] ` <20180218214110.GB9488@thebird.nl>
2018-02-20 9:47 ` Danny Milosavljevic
2018-02-21 1:26 ` Pjotr Prins
2018-02-22 1:42 ` Pjotr Prins
2018-02-23 11:59 ` bug#30411: " Danny Milosavljevic
2018-02-23 17:10 ` [bug#30411] " Pjotr Prins
2018-02-23 17:31 ` Leo Famulari [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=20180223173107.GA24390@jasmine.lan \
--to=leo@famulari.name \
--cc=30411-done@debbugs.gnu.org \
--cc=pjotr.public12@thebird.nl \
/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).