I think NixOS explicitly states they are NOT POSIX compliant
I think NixOS explicitly states they are NOT POSIX compliant
Hyeah
Hit's pretty much the point
AMore like "oh you're supposed to use env" to get executables
AAnyway it's a pain and I hate it
Hyou can boot with like, /boot and /etc/nixos being the only existing paths
that's about as cursed as it can be
that's about as cursed as it can be
KI see, from what I heard if I remember correctly, from Casey Muratori is to just static libs, at least for games it seems fairly reasonable since they already use a bunch of storage anyways
Hglibc still has to be dynamically linked unfortunately
Hand glibc is a giant source of pain
SI was using NixOS until some time ago, but honestly, all the workarounds needed to get some stuff working weren't worth being able to say "I use a fully declarative distro" to brag to my friends and strangers on the internet
Hi find the pointless tinkering fun, and generally the concept is interesting
but it's nowhere near adoption ready lmao, and it probably will never be
but it's nowhere near adoption ready lmao, and it probably will never be
AWell people decide to run it on their handhelds as a Linux experiment
AAnd I get the support workload
Hfun as an experiment on desktop and ok for ci
CI really don't get the point of setting up a declarative system for one deployment
CFor a bunch of systems it's extremely cool, but for desktop?
SAlso, latest drama pushed me further away. Now I'm using a version of Fedora Atomic, because it seems I love having to use workarounds to do basic stuff, like setting a QMK dev environment
Hthere's no practical merit on the desktop aside from being able to reconstruct the system if you do something incredibly stupid
Heg dd'ing your main drive
Hbut yeah honestly the only truly practical applications is either deploying a fuckton of machines without manual work, or CI style stuff
CWhy don't people just install Gentoo instead? lol
Hbecause gentoo has all of the issues of regular distros with none of the benefits?
Hxd
CBut if the practical benefit is bragging rights
SI used to run Gentoo, many, many years ago. It seems it's a trend of me really liking using gimmicky stuff that has little to no benefit
KOh talking about declarative stuff, I trashed my distrobox the other day trying to install and get Docker working for Microsoft thing and ended learning about the .ini stuff
After a night fighting it because I was already dumbed down of working for a bunch of straight hours at that point, there's one thing I couldn't figure out...
The Distrobox is using Fedora and I can't add the Microsoft .repo on the ini file
After a night fighting it because I was already dumbed down of working for a bunch of straight hours at that point, there's one thing I couldn't figure out...
The Distrobox is using Fedora and I can't add the Microsoft .repo on the ini file
SLeaving the PC running all night to compile a browser is really fun
Hi mean if that's the goal then sure
KSame here hah
SYeah, I was wondering here, I think I'll need to run Docker, and was thinking on how to best approach it. So the better solution is to use distrobox and install docker inside it, right?
ZNixos manages to solve an issue that many distros have. And that is dependency hell
SA container inside a container
SContainerception
Jpeople have been doing this for years, for some reason new nix users think that you have to use nix to do this, which is weird.
Kiirc I set up QMK without any problem
JMy desktop comes up the exact way I want on install every time, I'm not using nix.
KI don't know I ended up layering it with ostree 
Htrue but like
i don't like ansible and other stuff lmao
i don't like ansible and other stuff lmao
KJust in a distrobox, I had no problem
Hmostly because i can't even install it here without hoops
Jdon't like it either, that's why we built on bash and python instead of ansible, if ublue was built on ansible then that'd be cool, but no one would contribute
SI tried installing and setting it up through pip but got rekt by the dependencies, probably because it can´t deal with ostree shenanigans
KI couldn't get it working through containerception lol
Jif you're doing a bunch of that stuff it might make sense to just make your own container image
KThe issue was the systemd service having an error
KAh, makes sense than
ZSystemd?
CI read contraception, had to double take
KI think I set it up through pip as well, just, through an F40 distrobox
SSo I was thinking of using the docker thing, but then I don´t have docker. I´d need to either layer it (which is not recommended) or do some weird stuff like containerception
ZI think I had the same issue, had to add the
--additional-packages systemd