> but it would require a fresh install to avoid conflicts.
Not really! Nix basically only touches /nix/..., which Pacman doesn't mess around with, so there are no file conflicts.
Nix packages are generally hard-coded to use the specific libraries/external tools that they are built again, so Arch packages won't interfere with Nix packages.
Nix also doesn't expose dynamic libraries or executables from dependencies, so the only vector for conflict in the other direction is if you have your Nix profile before /bin in $PATH, you have installed the same executable with both package managers, and some Arch program doesn't work with the executable from the Nix version.
Not really! Nix basically only touches /nix/..., which Pacman doesn't mess around with, so there are no file conflicts.
Nix packages are generally hard-coded to use the specific libraries/external tools that they are built again, so Arch packages won't interfere with Nix packages.
Nix also doesn't expose dynamic libraries or executables from dependencies, so the only vector for conflict in the other direction is if you have your Nix profile before /bin in $PATH, you have installed the same executable with both package managers, and some Arch program doesn't work with the executable from the Nix version.