From: "Ludovic Courtès" <ludo@gnu.org>
To: Z572 <873216071@qq.com>
Cc: 56191-done@debbugs.gnu.org
Subject: bug#56191: [PATCH] gnu: guile-8sync: Update to 0.4.2-0.183b4f0.
Date: Sat, 25 Jun 2022 23:52:49 +0200 [thread overview]
Message-ID: <87r13cs95a.fsf@gnu.org> (raw)
In-Reply-To: <tencent_8124AA76685324B5240BE54F52C7BD7CAC05@qq.com> (873216071@qq.com's message of "Fri, 24 Jun 2022 21:48:43 +0800")
Hi,
Z572 <873216071@qq.com> skribis:
>>From a2aa4195d38fde080415afd120881d90d34927ac Mon Sep 17 00:00:00 2001
> Message-Id: <a2aa4195d38fde080415afd120881d90d34927ac.1656078354.git.873216071@qq.com>
> From: Z572 <873216071@qq.com>
> Date: Fri, 24 Jun 2022 21:34:18 +0800
> Subject: [PATCH 1/2] gnu: guile-8sync: Update to 0.4.2-0.183b4f0.
>
> * gnu/packages/guile-xyz.scm (guile-8sync): Update to 0.4.2-0.183b4f0.
> [source]: use git source.
> [native-inputs]: replace guile-2.2 with guile-3.0.
> [description]: remove some tips.
> <#:phases>: remove it.
> <#:make-flags>: set GUILE_AUTO_COMPILE in it.
Applied, thanks!
>>From 90a5f19ff4591c3172eec6a9293bce46c121f2d4 Mon Sep 17 00:00:00 2001
> Message-Id: <90a5f19ff4591c3172eec6a9293bce46c121f2d4.1656078354.git.873216071@qq.com>
> In-Reply-To: <a2aa4195d38fde080415afd120881d90d34927ac.1656078354.git.873216071@qq.com>
> References: <a2aa4195d38fde080415afd120881d90d34927ac.1656078354.git.873216071@qq.com>
> From: Z572 <873216071@qq.com>
> Date: Fri, 24 Jun 2022 21:45:19 +0800
> Subject: [PATCH 2/2] gnu: Add guile2.2-8sync.
>
> * gnu/packages/guile-xyz.scm (guile2.2-8sync): New variable.
After some hesitation, I did not apply this one.
Please let me know if you need it; otherwise I think it makes little
sense to add ‘guile2.2-’ variants at this point.
Ludo’.
prev parent reply other threads:[~2022-06-25 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y1xmuq64.fsf@qq.com>
2022-06-24 13:48 ` [bug#56191] [PATCH] gnu: guile-8sync: Update to 0.4.2-0.183b4f0 Z572 via Guix-patches via
2022-06-25 21:52 ` 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=87r13cs95a.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=56191-done@debbugs.gnu.org \
--cc=873216071@qq.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).