| 5 Jan 2024 |
 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 |
| Vladislav Vasilev | * 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 |
| Vladislav Vasilev | * 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:20:09 |
| 6 Jan 2024 |
|  eyJhb set a profile picture. | 14:00:01 |
| 7 Jan 2024 |
 Paul Meyer (katexochen) | https://github.com/NixOS/nixpkgs/pull/276685
https://github.com/NixOS/nixpkgs/pull/278115 | 09:31:18 |
| 8 Jan 2024 |
| Paul Meyer (katexochen) | https://github.com/NixOS/nixpkgs/pull/279391 | 07:47:28 |
| 9 Jan 2024 |
 SYMYƧ | Hi folks, I am trying to understand how to actually build a module with buildGoModule. I have tried, for example:
nix-build '<nixpkgs>' ./shell.nix
result:
nix-build '<nixpkgs>' ./shell.nix
error: Please be informed that this pseudo-package is not the only part of
Nixpkgs that fails to evaluate. You should not evaluate entire Nixpkgs
without some special measures to handle failing packages, like those taken
by Hydra.
| 23:55:11 |
