| 5 Jan 2024 |
 K900 | nix-env -i . is absolutely the wrong thing | 17:48:12 |
| K900 | You just tried to install every package with a dot in its name | 17:48:20 |
 @qbit:tapenet.org | like installing everything | 17:48:22 |
| @qbit:tapenet.org | heh | 17:48:36 |
 Vladislav Vasilev | Oh, sorry, I'm new in nix | 17:49:10 |
| @qbit:tapenet.org | i would avoid using nix-env | 17:49:25 |
| Vladislav Vasilev | Then it's enough to have <drv>/bin dir to see it in path ? | 17:49:42 |
| @qbit:tapenet.org | you need to either add it to nixpkgs or your configuration if you want it to be persistent | 17:50:05 |
| Vladislav Vasilev | In reply to @qbit:tapenet.org
i would avoid using nix-env And me using it's everywhere, heh | 17:50:07 |
| @qbit:tapenet.org | otherwise it will get GCd | 17:50:31 |
| Vladislav Vasilev | In reply to @k900:0upti.me
You just tried to install every package with a dot in its name How can I install it from local source otherwise? | 17:55:08 |
| @qbit:tapenet.org | that's not really how things are done in nixos :P | 17:55:36 |
| @qbit:tapenet.org | you can do a shell.nix file and build / run it locally from source.. | 17:56:13 |
| @qbit:tapenet.org | but TheWay is to upstream it or add it to your configuration.nix | 17:56:35 |
| @qbit:tapenet.org | as stated like 30 times before :P | 17:56:42 |
| Vladislav Vasilev | Oh, sorry for that. Okay, I think I got it | 17:57:15 |
| @qbit:tapenet.org | typically the shell.nix stuff is used for development - like you are going to be making changes to the software.. and need to install all the deps and what not | 17:58:05 |
| @qbit:tapenet.org | it's not used for "installing software into the system" | 17:58:19 |
| Vladislav Vasilev | okay, the right thing then do that:
nix-shell -E 'let pkgs = import <nixpkgs-unstable> { }; in pkgs.callPackage ./neutron/default.nix { }' | 17:59:56 |
| Vladislav Vasilev | Or whatever nixpkgs in system currently installed | 18:00:18 |
| @qbit:tapenet.org | if you want it installed and usable across reboots / nixos rebuilds you must put it in your configuration.nix or nixpkgs upstream | 18:00:53 |
| Vladislav Vasilev | So, and how paths are adding to PATH ? I have no custom installation phase, hovewer, I can see neutrond drv in /nix/store. How to add it to shell ? | 18:10:57 |
| Vladislav Vasilev | * So, and how paths are adding to PATH when shell launching ? I have no custom installation phase, hovewer, I can see neutrond drv in /nix/store. How to add it to shell ? | 18:11:08 |
| Vladislav Vasilev | * So, and how paths are adding to PATH when shell launching ? I have no custom installation phase, hovewer, I can see neutrond drv in /nix/store. How to add it's bin to shell ? | 18:11:18 |
| Vladislav Vasilev | Probably add it to buildInputs | 18:12:55 |
| Vladislav Vasilev | Yep, one moment | 18:12:58 |
| @qbit:tapenet.org | no | 18:13:07 |
| @qbit:tapenet.org | https://jorel.dev/NixOS4Noobs/installingprogs.html | 18:14:02 |
| @qbit:tapenet.org | environment.systemPackages | 18:14:30 |
| Vladislav Vasilev | anyway I did this, but I don't think it's a good solution even for a temporary package
let
pkgs = import <nixpkgs-unstable> { };
in pkgs.mkShell rec {
buildInputs = [
(pkgs.callPackage ./. { })
];
}
| 18:19:22 |
