Wait, isn’t it the other way around? I thought ; only executed the next command if the previous one succeeded, and && executed the next command regardless of exit status.
juipeltje
I’d just like to interject for a moment…
- 0 Posts
- 5 Comments
I’m on Void right now, but am i still a chad if i switch to GNU Guix? I’m assuming yes because NixOS is also in the chad tier 🗿
Yes, NixOS and GNU Guix are both technically source-based, but they pull from a binary cache server by default to prevent it from building everything. You could disable it, but i don’t really see the point since as far as i’m aware, nix and guix don’t have the use flags stuff like Gentoo has.
Void and NixOS in S tier is based, my two favorite distros. Because of me using void though i kinda miss using Runit when i want to use a declaritive system like nix. I’m working on a gnu guix config in a vm now to see if i can use that as an alternative instead. It’s not runit per se, but who knows, maybe i’ll still like shepherd better than systemd.


Ah yes you’re right, had to look it up to see for myself. It’s weird because i remember specifically changing some of my &&s for ; instead because i wanted it to not continue if exit wasn’t zero, but i must’ve misread it at the time. Time to change it back i guess lol.