<baconicsynergy>What if we were able to port the genode operating system framework to guixsd? What if allcomponenets including microkernel and essential userland components such as network stack, netbsd rump kernel, vfs, noux, etc were described as guile modules?
<baconicsynergy>It's a joy to build genode systems but it's all manually constructed with the help of some build scripts at the moment. What if we were able to declare custom system configurations in a static high level abstraction like guixsd already does?
<atw>baconicsynergy: pretty cool! Possible difficulties: non-free components, and that's a _lot_ of porting, right?
<atw>btw, I think the channel is more trafficed during European daytime
<baconicsynergy>atw: Yes it would be a lot of porting! It would definitely be a lot of work, but the benefits of a capability-based framework like Genode and it's microkernel-agnostic architechture are extremely important for software freedom. The good news: Almost all of the genode framework is licensed under the GPLv2! During the porting process, it would be our responsibility to curate what extraneous licensed
<atw>cool! I haven't gotten to see Manolis' talk from this year's FOSDEM yet, but I think that among the difficulties of porting/packaging hurd was glibc adjustments. Is GuixSD really kernel agnostic yet? Ideally, it should be, but I don't think we're there yet. Anyway, looking forward to Manolis' talk as I'd really like to use GuixSD to try out hurd.
<clacke[m]>I always get locale issues with guix. I think I have GUIXLOCPATH, LANG and LC* set appropriately for both the guix-daemon process and the guix process calling it, but I still get that warning message every time ... so obviously I think wrong. :-)
<adfeno>Get the gnus manual that says which procedure is called when pressing r or R or whichever reply-or-compose-like-key.
<adfeno>These should be somewhat customizable by you some how in your .emacs file.
<adfeno>Perhaps you could also force then to be so, like: define a *general* default message writter (I didn't say for debbugs usage only), then redefine the message compositing commands so that they can ask you which writter to use.
<adfeno>Although one must note that this is just an idea, as I don't know if all the writters accept the same arguments and options in the same order and such.
<rekado_>adfeno: no need to look up anything in the manual. “C-h k r” shows me the command that’s executed. But that’s not helping.
<rekado_>to reply with mu4e I need to get a couple of bits of information from the currently selected bug and pre-fill a few fields in the reply for mu4e.
<rekado_>it’s not hard, I just wanted to know if anyone else does that
<root_guix>Can I install software from source code into Guix?
<atw>root_guix: I've not done it, but you should be able to write a package definition and then do a guix package --install-from-file
<janneke>root_guix: there is debian/hurd and arch/hurd
<cantstanya>why would you think that's feasible? look at the output of `file /path/to/any/binary`. You can't just have a different kernel and expect to magically work with userspace binaries built for another kernel.