From: Danny Milosavljevic <dannym@scratchpost.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: ldc: Update to 1.1.0.
Date: Fri, 3 Feb 2017 20:37:04 +0100 [thread overview]
Message-ID: <20170203203704.14c4051e@scratchpost.org> (raw)
In-Reply-To: <20170203164521.GA2411@macbook42.flashner.co.il>
Hi,
On Fri, 3 Feb 2017 18:45:22 +0200
Efraim Flashner <efraim@flashner.co.il> wrote:
> On Wed, Feb 01, 2017 at 10:51:32AM +0100, Danny Milosavljevic wrote:
> > ;; files left with the --keep-failed flag to guix build.
> > (patches (search-patches "ldc-1.1.0-disable-dmd-tests.patch")))))))))
> >
> > -(define-public ldc-beta ldc-1.1.0-beta6)
> > -
> Without having built it to test it out, I would replace this part with
> either having it superceded by ldc-1.1.0, or have ldc-beta point to
> ldc-1.1.0, so no one who relies on it finds it broken.
Ehhh. The variable "ldc-beta" would have existed for 5 days and was in no Guix release - not sure anyone saw it.
But we can do the latter so that people could rely on ldc-beta being the newest non-release ldc (if we ever packaged another ldc beta release or even git commit), kinda like guix-devel (corresponding to ldc-beta) vs. guix (corresponding to ldc). Sure.
next prev parent reply other threads:[~2017-02-03 19:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 9:51 [PATCH 0/2] Update ldc to 1.1.0 Danny Milosavljevic
2017-02-01 9:51 ` [PATCH 1/2] gnu: ldc: Rename ldc 0.17.2 to ldc-bootstrap Danny Milosavljevic
2017-02-10 11:16 ` Danny Milosavljevic
2017-02-01 9:51 ` [PATCH 2/2] gnu: ldc: Update to 1.1.0 Danny Milosavljevic
2017-02-03 16:45 ` Efraim Flashner
2017-02-03 19:37 ` Danny Milosavljevic [this message]
2017-02-09 16:38 ` Ludovic Courtès
2017-02-10 11:17 ` Danny Milosavljevic
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=20170203203704.14c4051e@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=efraim@flashner.co.il \
--cc=guix-devel@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).