| 5 Jan 2024 |
@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 |
@faust403:matrix.org | 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 |
@faust403:matrix.org | * 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 |
@faust403:matrix.org | * 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 |
@faust403:matrix.org | Probably add it to buildInputs | 18:12:55 |
@faust403:matrix.org | 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 |
@faust403:matrix.org | 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 |
@faust403:matrix.org | * anyway I did this, but I don't think it's a good solution even for a temporary shell
let
pkgs = import <nixpkgs-unstable> { };
in pkgs.mkShell rec {
buildInputs = [
(pkgs.callPackage ./. { })
];
}
| 18:19:32 |