Conversation
- add section to detect and use nix-env package manager - update error message: "Could not find a supported..."
| # IMPORTANT: Always check nix-env last. It is the default on NixOS, but on other systems it may be installed as a cross-platform package manager. | ||
| # Prioritize native package managers first to ensure proper system integration and avoid overriding system management. |
There was a problem hiding this comment.
Let's drop the comment, but the question about whether this is the best way to install remains. Are there other competing options to consider, or is this it?
There was a problem hiding this comment.
The arguments for the configuration.nix route highlighted by Ask Brave seem pretty compelling.
On the other hand, do we know how many changes have been made to that file since the last nixos-rebuild? It could be more risky/invasive to run from install.sh than the installation commands for other package managers. We also opted for the least invasive actions possible with rpm-ostree for similar reasons - we don't want to potentially break a system, or enable changes the user wasn't ready/intending to enable yet.
And then we also have the case of nixOS vs nix on another distro. Which might call for different approaches. Would this PR represent what the user would want in the "other distro" case?
It would be great to get some input from day-to-day nix(OS) users.
2 participants
Resolves #13