From: Christopher Baines <mail@cbaines.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Implementing the guix-dameon in Guile
Date: Thu, 14 Sep 2023 09:22:05 +0100 [thread overview]
Message-ID: <871qf1tabx.fsf@cbaines.net> (raw)
In-Reply-To: <87zg1quhbn.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>> The transformation toward a Guile daemon is a point of consistency and
>> pride for the project and therefore unlikely to be second-guessed or
>> reverted. My recommendation is to replace the daemon gradually—working
>> from (apply system* (command-line) downward—and mainline your
>> incremental changes as quickly as possible.
>
> I had some musing about the daemon recently; I was thinking libguile
> could be added to our old C++ daemon, which could then replace its
> functions piece-wise with Scheme implemented ones?
>
> At the end, we'd have almost everything in Scheme, at which point we
> could rewrite the main loop to Scheme and say farewell to the old
> daemon.
>
> Would that approach makes any sense? I know of at least one C++ project
> integrating libguile, and that's the jami-daemon, so it could perhaps
> provide some clues as to how to proceed to do so.
I think it's a viable approach, but probably not one for me. Since I
don't really write C++, I think that trying to replace parts of the C++
code and keep things working would take more work than just writing
Guile.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2023-09-14 8:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 15:36 Implementing the guix-dameon in Guile Christopher Baines
2023-09-13 16:44 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-09-13 17:13 ` Maxim Cournoyer
2023-09-14 7:12 ` Simon Tournier
2023-09-14 8:22 ` Christopher Baines [this message]
2023-09-13 18:56 ` Vagrant Cascadian
2023-09-14 8:42 ` Christopher Baines
2023-09-14 15:35 ` Ludovic Courtès
2023-09-14 12:58 ` Josselin Poiret
2023-09-18 12:57 ` Christopher Baines
2023-09-14 13:29 ` Ludovic Courtès
2023-09-14 15:53 ` Christopher Baines
2023-09-14 16:36 ` Ludovic Courtès
2023-09-16 9:41 ` Mathieu Othacehe
2023-09-18 13:19 ` Christopher Baines
2023-09-18 19:12 ` Thompson, David
2023-09-14 17:31 ` Caleb Ristvedt via Development of GNU Guix and the GNU System distribution.
2023-09-18 12:58 ` Christopher Baines
2023-09-14 22:46 ` Mekeor Melire
2023-09-18 13:15 ` Christopher Baines
-- strict thread matches above, loose matches on Subject: below --
2023-12-30 12:57 Yarl via Development of GNU Guix and the GNU System distribution.
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=871qf1tabx.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.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).