Oof, guix doesn't seem play nice with foreign distros, even stable ones like Debian. The guix system distro is out of the question because of my WiFi drivers and until nonguix is more mature there really isn't a good alternative for me.
I don't love it but I'll probably have to hop back over to nixos and see how the community changes play out. Good thing it takes like 2 minutes to get my old config back. Still, nix has made it tough to use anything else.
@abmurrow
Which part of it doesn't play nice with foreign distro? i've used it on Ubuntu 22.04 and also on multiple Manjaro, and I never faced even the slightest issue.
@Mehrad I used guix to install a lot of system packages on Debian, including git, and one of the big issues was that I couldn't got clone at all. Even with ca-certificates installed on the host system I got really inconsistent behavior. I could git clone if I was doing it in my shell but not if a bash script was doing it. I tried installing my doom emacs config with straight.el and emacs couldn't git clone either. I fiddled with it for two days and just gave up.
@Mehrad For context, my aim was to leave the host system as untouched as possible and let guix run the show, but the experience is far from seamless enough to do that quite yet. That, or I'm dumb.
@abmurrow
When you run a bash script, it is not run with same system environment that you have, instead it creates a subshell. For this reason, most probably you didn't have the #guix profile there at all. One way to bypass that is to use source script.sh instead of bash script.sh to run the content of the script in the current bash.
The way I use guix is to have certain tools and containers in guix on a rolling release distro like Arch or Manjaro as the host.
Add comment