| 8 Feb 2024 |
|  symys joined the room. | 07:22:01 |
| 9 Feb 2024 |
|  shift joined the room. | 12:06:24 |
| 12 Feb 2024 |
|  lunchtime joined the room. | 02:17:50 |
|  @cephoto:matrix.org joined the room. | 05:42:39 |
|  @lunchtime:envs.net joined the room. | 10:46:07 |
 @martiert:matrix.org | I'm building a custom linux kernel on one of my aarch64-linux machines. I want to add it to packages so I can do build .#customKernel on a buildmachine, and copy the kernel over to my weaker device. However, nix flake show --all-systems complains that the kernel is not a derivation. The package is instantiated with: packages.aarch64-linux.custom = recurseIntoAttrs (callPackage (linuxPackagesFor (callPackage (buildLinux (args ... ))))); | 19:18:37 |
| @martiert:matrix.org | any ideas? | 19:18:45 |
| @martiert:matrix.org | what I want in the end is to have my hydra atuomatically build the kernel for me, and that would probably be easier if it was all in packages. | 19:21:10 |
| @martiert:matrix.org | found it out, in the packages I need the .kernel output of the call to linuxPackagesFor. Then I can build it | 20:21:31 |
| shift changed their display name from Vincent Palmer to shift. | 21:21:59 |
| 13 Feb 2024 |
| @cephoto:matrix.org changed their display name from PhantomProphet - NixOS makes simple things complicated.™ to PhantomProphet - NixOS makes simple things complicated.™ (and vice-versa). | 23:36:54 |
| 15 Feb 2024 |
|  tengkuizdihar joined the room. | 11:48:20 |
| 16 Feb 2024 |
|  @seb.sto:matrix.org joined the room. | 07:13:06 |
| @seb.sto:matrix.org left the room. | 07:13:27 |
|  lord-valen joined the room. | 18:46:59 |
| 18 Feb 2024 |
|  link2xt joined the room. | 02:42:49 |
 mr-qubo | When I do e.g. nix shell 'nixpkgs#htop' only htop is added to path. But if I create flake with devShell and htop in buildInputs, and use nix develop dependencies are added into the PATH as well, like with nix-shell -p htop. Is it possible to have this work as nix shell?
Also, as a second question, is it possible to group multiple packages and link all bins in one path, so only one entry in PATH is added instead of separate entry for each package? | 15:25:16 |
 tomberek | The devShell: if you are using mkShell, then use the "packages" argument.
You can use buildEnv, then put that into mkShell. | 15:51:21 |
| mr-qubo | Seems like using packages changed the order of things in PATH but I still have unwanted paths in PATH. | 16:50:26 |
| mr-qubo | * Seems like using packages changed the order of things in PATH but I still have unwanted paths in PATH. | 16:50:33 |
| mr-qubo | * Seems like using "packages" changed the order of things in PATH but I still have unwanted paths in PATH. | 16:50:44 |
| mr-qubo | Thanks for "buildEnv", it does exactly what I wanted! | 16:51:20 |
| mr-qubo | That's weird, I also get unwanted paths when using empty list of packages. | 16:54:13 |
 netpleb | with a flakes enabled system does it still make sense to use system.autoUpgrade at all? or do you usually manage upgrading manually by updating your flake inputs? | 19:29:25 |
 @loving-melody:matrix.org | I use it, autoUpgrade doesnt have to update the flake inputs | 20:52:00 |
| mr-qubo | In reply to @loving-melody:matrix.org
I use it, autoUpgrade doesnt have to update the flake inputs What's the purpose of autoUpgrade with flakes? | 21:07:42 |
| @loving-melody:matrix.org | Mutli system flakes, can apply changes to other systems | 21:10:23 |
| 19 Feb 2024 |
 samasaur | you could also update your flake in CI, and then use autoUpgrade to upgrade to that newer version | 00:27:50 |
|  rhizomes joined the room. | 04:27:25 |
| mr-qubo | I have a simple flake like this:
{
outputs = { self, nixpkgs, flake-utils }:
flake-utils.lib.eachDefaultSystem (system:
let
pkgs = nixpkgs.legacyPackages.${system};
in {
devShell = pkgs.mkShell {};
});
}
When I do nix develop I get things like gcc, patchelf, file, etc. in my PATH. I don't want that, anyone knows where does that come from and how can I get rid of that?
| 16:32:17 |
