From: Taiju HIGASHI <higashi@taiju.info>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Maxime Devos <maximedevos@telenet.be>, 55612@debbugs.gnu.org
Subject: [bug#55612] [PATCH 0/2] Update guile-hall to 0.4.1.
Date: Sat, 04 Jun 2022 07:24:49 +0900 [thread overview]
Message-ID: <DF71FADA-B937-4083-8C2D-A70516FA7B3D@taiju.info> (raw)
In-Reply-To: <87y1ydh258.fsf_-_@gnu.org>
Hi Ludovic,
Thank you for the comment!
>How about one of these two options:
>
> 1. Provide both versions of guile-config, use the old one in GWL, at
> the risk of preventing installation of guile-hall + gwl in the same
> profile (which is probably not much of a problem in practice).
>
> 2. Patch GWL so it works with the latest guile-config.
>
>That should unblock the situation. WDYT?
The second option is preferable and is currently being worked on.
I have the patch reviewed for adequacy.
https://lists.gnu.org/archive/html/gwl-devel/2022-05/msg00010.html
https://lists.gnu.org/archive/html/gwl-devel/2022-06/msg00000.html
Cheers,
--
Taiju
next prev parent reply other threads:[~2022-06-03 22:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 13:26 [bug#55612] [PATCH 0/2] Update guile-hall to 0.4.1 Taiju HIGASHI
2022-05-24 13:29 ` [bug#55612] [PATCH 1/2] gnu: Add guile-config-0.5 Taiju HIGASHI
2022-05-24 13:29 ` [bug#55612] [PATCH 2/2] gnu: guile-hall: Update to 0.4.1 Taiju HIGASHI
2022-05-24 14:10 ` [bug#55612] [PATCH 0/2] Update guile-hall " Maxime Devos
2022-05-24 14:20 ` Taiju HIGASHI
2022-05-24 14:26 ` Maxime Devos
2022-05-26 1:10 ` Taiju HIGASHI
2022-06-03 21:23 ` Ludovic Courtès
2022-06-03 22:24 ` Taiju HIGASHI [this message]
2022-07-06 8:40 ` Ricardo Wurmus
2022-07-06 13:56 ` Taiju HIGASHI
2022-07-16 11:27 ` Taiju HIGASHI
2022-07-21 15:54 ` bug#55612: " Ricardo Wurmus
2022-07-22 0:05 ` [bug#55612] " Taiju HIGASHI
2022-07-06 13:46 ` [bug#55612] [PATCH v2 1/2] gnu: guile-config: Update to 0.5.1 Taiju HIGASHI
2022-07-06 13:46 ` [bug#55612] [PATCH v2 2/2] gnu: guile-hall: Update to 0.4.1 Taiju HIGASHI
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=DF71FADA-B937-4083-8C2D-A70516FA7B3D@taiju.info \
--to=higashi@taiju.info \
--cc=55612@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=maximedevos@telenet.be \
/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.