From: "Ludovic Courtès" <ludo@gnu.org>
To: Z572 <873216071@qq.com>
Cc: 59726@debbugs.gnu.org
Subject: [bug#59726] [PATCH 0/2] gnu: g-wrap: Build with Guile 3.0.
Date: Fri, 02 Dec 2022 23:03:48 +0100 [thread overview]
Message-ID: <87o7slpinv.fsf_-_@gnu.org> (raw)
In-Reply-To: <tencent_3816FE1F9A0E6E7947095C2DDDE6742A5606@qq.com> (873216071@qq.com's message of "Thu, 1 Dec 2022 00:29:37 +0800")
Hi,
Z572 <873216071@qq.com> skribis:
> * gnu/packages/guile-xyz.scm(g-wrap)[source]: Modify configure to add Guile
> 3.0 support. move Modify configure guilemoduledir to it. dons't use removed
> api.
>
> [inputs]: add Guile 3.0, indent.
> [native-inputs]: add Guile 3.0.
> [propagated-inputs]: add libffi, remove guile-2.2.
> [arguments]:
> <#:configure-flags>: remove it.
> <#:parallel-build?>: set it to #f.
> <#:make-flags>: set it to '("GUILE_AUTO_COMPILE=0)".
> <#:phases>: add set-indent-program-path phase, remove pre-configure phase.
G-Wrap has only one user, Guile-GNOME, which is stuck on Guile 2.2.
Thus I think G-Wrap has to remain on 2.2.
Besides, G-Wrap has been unmaintained for some time and there are other,
more convenient ways to write bindings these days. I think we can leave
it as is.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2022-12-02 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1669825268.git.873216071@qq.com>
2022-11-30 16:29 ` [bug#59726] [PATCH 1/2] gnu: g-wrap: Build with Guile 3.0 Z572 via Guix-patches via
2022-12-02 22:03 ` Ludovic Courtès [this message]
[not found] ` <875yesdfhz.fsf@qq.com>
2022-12-03 9:04 ` bug#59726: [PATCH 0/2] " Z572 via Guix-patches via
2022-11-30 16:29 ` [bug#59726] [PATCH 2/2] gnu: g-wrap: Use gexp Z572 via Guix-patches via
2022-11-30 16:25 [bug#59726] [PATCH 0/2] gnu: g-wrap: Build with Guile 3.0 Z572 via Guix-patches via
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=87o7slpinv.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=59726@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).