From: Christopher Baines <mail@cbaines.net>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Implementing the guix-dameon in Guile
Date: Mon, 18 Sep 2023 13:57:27 +0100 [thread overview]
Message-ID: <87msxjprje.fsf@cbaines.net> (raw)
In-Reply-To: <8734zg52tp.fsf@jpoiret.xyz>
[-- Attachment #1: Type: text/plain, Size: 1443 bytes --]
Josselin Poiret <dev@jpoiret.xyz> writes:
>> 2: https://nlnet.nl/project/GuixDaemon-Guile/
>>
>> Rewrites are risky because you only get the value right at the end,
>> therefore the priority is to get a minimal but viable implementation in
>> Guile that can be switched to, and not to get distracted on adding or
>> improving functionality unnecessarily. That is better done once the new
>> implementation has been adopted.
>>
>> While I think there's a substantial amount of work to do, progress
>> towards a Guile guix-daemon has already been made. There was a least one
>> GSoC project which did make progress, and there's Guile implementations
>> of some of the functionality in Guix already.
>>
>> Still though, I'd like to hear what people think about which direction
>> the implementation should go, and what features they'd like to see. Even
>> if those are not essential to make the Guile implementation viable, it
>> still might inform the direction to take.
>
> I think the #1 feature for me would be to have it completely
> unpriviledged using mount namespaces, so that you could still build
> software without needing to run the daemon on the system. You won't be
> able to run the built software without using namespaces as well though,
> but that still a step in the right direction imo.
>
> WDYT?
Thanks for the suggestion :)
I'm not quite sure what this would involve, but it sounds like it might
not be that hard to do.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2023-09-18 12:58 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87msxjprje.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=dev@jpoiret.xyz \
--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 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.