<Digit>mmm. guix on hurd. that's some enticing words there. ... i kinda wanna drop everything n go try that out. ... but barely got started with the last thing to have that effect on me. one geeking at a time. ... soon tho. hopefully.
<civodul>rekado: sorry i hadn't seen your question, but yeah, i think we should make a release once core-updates is merged
<civodul>jlicht: davexunit may be the right person :-)
<davexunit>jlicht: would be good to know what the exact issues are. I haven't used npm much since doing that upgrade
<rekado>another possible problem with the shared storage might be gzip compression. (Compression ratio is 2, but I don't think it's worth it if this turns out to be the reason why reads are so slow.)
<thomassgn>Curios,I've recently started using nixos, purely on a gut feeling it would be more... mature. But I'm kind of looking for guix to be "safe" enough to make the change for it. Anyone with experience running guix that can speak to its stability as a day to day OS?
<rekado>thomassgn: I'm running GuixSD on multiple machines.
<rekado>the primary issue with GuixSD is that it doesn't have as many packages as other popular GNU distributions.
<rekado>stability is definitely not an issue for me.
<rekado>if anything it's more stable as I cannot really break things anymore.
<rekado>(my workstation in the office is running Fedora and I break things often enough to find it annoying)
<thomassgn>nice, yes, that was my thought too. This way of managing a system is so much better/easier
<kraji>hello all! i used guix build to build a costumized package. how do I replace the package in base with the one I builted? I'm getting "collision messages" all the time
<bavier>I have a project that was released under gpl2+; later they decided to re-release under LGPL, but didn't change any of the source headers, which still read gpl2+. So, would I just need to list both licenses?
<lfam>kraji: If you mean what I think you mean by "collision messages", those collisions are in your profile (user's installed packages). So, uninstall the old package and keep the new one.
<bavier>but yes, I might contact the author to point out the situation
<lfam>kraji: The way I handle custom packages on GuixSD is to put them in a separate tree (where they inherit from the Guix-provided package), and then reconfigure with GUIX_PACKAGE_PATH pointing to my tree.