cross-posted from: https://lemmy.ca/post/17456633

  • OS: Void Linux x86_64 musl
  • Icons: Nordzy
  • GTK Theme: Nordic
  • Qt Theme: Custom (Nord)
  • Cursors: Nordzy-Cursors
  • Layout: Supremo
  • Wallpaper: Galaxy (Nord)
  • Main Font: Cantarell
  • Monospace Font: Hack
  • Shell: Zsh
  • OMZ Theme: Gallifrey
  • Filesystem: Btrfs for /; Ext4 for ~; Ext4 for ~/Music
  • Browser: Mullvad
  • File Manager: Nemo
  • Terminal: foot
  • Music Player: qmmp
  • Editor: Micro
  • gun@lemmy.ml
    11·
    8 months ago

    New to linux. I tried this same thing in a virtual machine. I got a lot of stuff to work, but it seems like any services and daemons have to be installed on xbps because the ones from nix can’t be enabled for Runit, or at least require doing that in a different way. So I would install those services through XBPS and everything else with Nix-Env which was enough to get a WM up, but I kept running into issues installing other things.

    Now I’m running Void directly on my computer and I’m sticking to XBPS and so far it has gone a lot smoother, but I’ve heard about this Void + Nix thing a lot, but never really seen mentioned what the recommended approach to that is

    • Hellfire103@lemmy.caOPEnglish
      1·
      8 months ago

      I’m not sure what the general consensus is, but I’ve been using XBPS for everything, and then nix-env for anything not available on the default repos or in srcpkgs. On my system, it’s essentially just a replacement for Flatpak and AppImage, as I’ve had trouble running Flatpaks on Sway, and AppImages aren’t yet supported on musl libc.

      • gun@lemmy.ml
        2·
        8 months ago

        Ok, that’s sort of what I figured. I’ll probably do that going forward. Thanks