<jluttine>why guixsd uses shepherd/dmd instead of systemd?
<alezost>jluttine: why would it use systemd instead of shepherd? :-)
<alezost>jluttine: shepherd is written in guile, and we love guile
<jluttine>alezost: ok :) i just have the impression that systemd is mature, very widely used and supported, so kind of "why to reinvent the wheel" instead of using a good(?) existing tool
<jluttine>shepherd is actually one of my main concerns now that i'm thinking about trying guixsd
<jluttine>but i don't have any deep understanding about shepherd nor systemd, just wondering
<alezost>jluttine: many people don't think that systemd is a good wheel :-)
<alezost>It's not the reason though: we just try to use guile as much as possible, that's it
<wingo>i think the reason is somewhat different afaiu? like, yes, guile preference is part of it, but there's the whole staging/static linking thing; we have to generate the equivalent of "service" files all the time
<wingo>taht are linked directly to /gnu/store/blablabla-.../ and that having the service definitions be scheme code is pretty convenient in that regard
<alezost>yeah, I meant that using a real programming language (especially guile code which suits the other Guix parts) is much more convenient than using "dumb" systemd services
<jluttine>i'm new to this.. can someone describe a bit the differences between nixos and guixsd, and what are the advantages of guixsd? nixos uses systemd+nix, guixsd uses shepherd+guix, that much i know.
<jluttine>i'm trying to understand why to choose guixsd using shepherd instead of nixos using mature systemd
<jluttine>(i'm sorry if i sound harsh, don't mean to, just trying to understand these distros as i just discovered them yesterday)
<alezost>for me the main advantage of Guix(SD) is that I can use a general-purpose programming language in my various guix-related configurations
<alezost>And the fact that this language is from the lisp family adds many pluses to this
<alezost>I don't need matureness, I want a possibility to program my configurations, and with Guix and Shepherd I have this possibility.
<alezost>ACTION uses emacs, stumpwm and conkeror for the same reason
<ng0>jluttine: also guix uses still parts of the nix daemon (iirc), some of us have given talks on this over the last years :)
<rekado>I have a problem with Guix on Fedora. I do "guix environment guix" to be able to reconfigure and run "make".
<ng0>afaik, i have some logs, but i'm currently not working on that computer or even ebuild
<ng0>and -bin version fails, while source of guix works but gets scattered all across (logical) gentoo locations
<ng0>origin git://cheettyiapsyciew.onion/youbroketheinternet-overlay <- readable there in sys-apps/guix/, but it's just a work in progress version, the user creation process should be clear without understanding ebuild dialect though.
<rekado>I wished there was something we could do to speed up NFS here.
<kyamashita>I just need a few more tweaks to get Red Eclipse packaged for Guix. The binary builds fine, but the data files need to be extracted in a very particular manner.
<kyamashita>I was planning on using tar's "--transform" option to run a regex on the data files as they were extracted to get the folder names right, but I didn't know if Guix had a procedure for things like that.
<bavier>kyamashita: I think using tar's --transform would be find