@guix I held back on digging into guix for the last couple of years - now finally going back in as package manager on top of Ubuntu as practice.

Combined with guile scripting front and center the potential is definitely there, I just wish I could give guix the time it deserves.

@guix Other than as package manager on top of #archlinux, I’m using #guix for electronics design, mostly #vhdl and #fpga related stuff.

I run simulations with help of #hdlmake using #ghdl compiler, #osvvm for verification, #cocotb for testbenches, #yosys for synthesis, #nextpnr for placement and routing and #openFPGALoader for flashing. Finally, I use my own Guix channel to package gateware and run #ci tests on #sourcehut Guix image. A demo toy example of this runs here

https://builds.sr.ht/~csantosb/job/1585413

@guix I'd like to get the Guix config I've used on some other machines working on my Reform and Pocket Reform

Relatedly, I'd like to see if I can come up with a cleaner way to abstract away hardware-specific needs from the rest of the config. NixOS seems to do this pretty well with nixos-hardware, and it feels like we're lacking some of that on Guix. Other folks have gotten Guix running on the Reform, but integrating that into my own config feels harder than it should be

@guix I use #guix system as a system for about two years already. I use it on two home laptops and on one VPS. Before that I have used Guix as a package manager on the top of Debian GNU/Linux.

Now I'm trying to implement import (for guix import hexpm) from mix.lock for better BEAM packaging. The most parts of code are stolen from the work, related to cargo/crates. Still I'm not sure, if this approach will fit for BEAM.

Building a new home server to replace my Mini-PC. It's getting too hot working as an offload server and Cuirass build server for my channels. And with a more stable build with RAID etc, I can get off Google Photos, Google Drive and Dropbox.

@guix

@guix
To learn guix (and C++) I'll try to implement a feature while developing on guix only. Kind of a real world usage test of both guix and my own configuration and workflow

Started strong by getting the thing to compile and implement some basic stuff! Hopefully all that's left is to finish it

https://codeberg.org/aninternettroll/biboumi/compare/e95bb7a6e7a734c867678bb3742cbb1628b91e32..user/luca/message-tags-tmp

Guix in particular also helps with this task because it can easily set up and manage prosody, which makes testing during developing trivial

https://git.lucamatei.com/dotfiles.git/tree/system-turret-config.scm?h=guix-system-turret&id=94b17ca4b1233c04761e780b19387c219ee57b75#n160

In addition running ergo with podman was really easy. Just following the manuals
(Not running as a full service as it's not really needed for development. But I could)

https://github.com/ergochat/ergo/blob/stable/docs/MANUAL.md#docker

https://guix.gnu.org/manual/devel/en/html_node/Miscellaneous-Services.html#index-rootless_002dpodman_002dservice_002dtype

@guix

Currently, I'm just using it as my main desktop and laptop distro, but once I get some time I'd really like to get back into running it as my router OS again. The things that stopped me at that time were largely around building for aarch64 on x86_64. Many cross compiles didn't work, but what did work more often than not was running builds with Qemu user mode emulation, but this was slowwww. I mostly just needed a custom kernel configuration so my needs aren't that extensive.

When I get the time I'd like to look into what was going wrong with cross compilation, because it seems like something that should be doable.