Yeah, nix only ever creates things in the store, linking happens by auxiliary tools which appear to be nix, though actually are just shallow wrappers.
I don’t have much experience with nix and honestly the terminology is a bit confusing, I was refering to something provided by nixos, not the nix package manager itself.
What I mean is, did you edit some file? If yes, which? Did you ran any commands? Which?
I added the package to environment.systemPackages, I think that’s what you mean. The command I use to build my config is
sudo nixos-rebuild switch --flake .#.
Nix does not manage your configuration, auxiliary tools do.
I still think the dotfiles have to be managed by those tools in order to work, at least it didn’t have any effect when I tried it using home manager.
This is deemed to fail. Either use HM on the other distros or maintain seperate repositories.
If that was true I’d probably give up nixos tbh, but I’ve seen plenty of people talk about using your existing dots and I don’t see why this couldn’t work. (Almost all of my config works already, this is one of the few remaining problems)
Linking it "somewhere in
PATH " doesn’t gain you anything.
Shouldn’t I be able to source it if it’s on my path? It’s my understanding that the shell would resolve the symlink.
And the link has to get updated everytime you rebuild the system.
Which is why I want to add this as part of my nix config, from what I’ve read on them, (which is not much) overlays or flakes seem like they might work, but since I’m very new to nix I don’t know how to use them properly.
This again is one of the reasons why I asked how you built/installed in the first place, as further steps depend on this.
As I said above, from the offical nixpkgs. (unstable channel)