3 ms·

I use NixOS daily, and the rough areas now are mostly lack of really thorough documentation and dealing with software that is not packaged for Nix and has an un

by nextos 9y ago

I use NixOS daily, and the rough areas now are mostly lack of really thorough documentation and dealing with software that is not packaged for Nix and has an unclean way of getting built. It's surprising how many pieces of software have hardcoded paths to e.g. Python binaries. My temporary fix for the latter is using a Docker with Arch for quick and dirty one-time things.

AnIdiotOnTheNet 9y ago
> the rough areas now are mostly lack of really thorough documentation and dealing with software that is not packaged for Nix So basically the same problems as every other Linux distribution? Only AppImage doesn't work out of the box either. The more things change the more they stay the same.
- deleted 9y ago
  [deleted]
pxc 9y ago
Did you know Flatpak support is on the way? I'm hoping that it can help fill the void for applications which haven't made it into Nixpkgs yet. (And maybe for things we can't build from source, as much as I try to stay away from those.) https://github.com/NixOS/nixpkgs/pull/33371 https://github.com/NixOS/nixpkgs/pull/33371
- nextos 9y ago
  Yes, my use-case is more complex sadly. It's more about installing some scientific binaries which are generally really dirty to build, in a quick and easy way. I need them to reproduce other papers so I cannot stay away, sadly. I think a better FHS or Steam.Env would help me more.