Newest at the top
| 2026-01-16 13:57:32 +0100 | danz91856 | (~danza@user/danza) (Remote host closed the connection) |
| 2026-01-16 13:57:24 +0100 | danz91856 | (~danza@user/danza) danza |
| 2026-01-16 13:54:04 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds) |
| 2026-01-16 13:53:31 +0100 | <gentauro> | I'm guessing the `build` options https://nix.dev/manual/nix/2.18/command-ref/new-cli/nix3-build#options it seems possible to provide `--include` |
| 2026-01-16 13:51:48 +0100 | <gentauro> | anyway, I will read a bit more of -> https://nix.dev/manual/nix/2.18/command-ref/new-cli/nix |
| 2026-01-16 13:49:42 +0100 | <gentauro> | Vq: I have cloned a git repo and the `flakes.nix` is in the root of the project. When I state "theirs", I mean "flakes.nix in root of git repo" :) |
| 2026-01-16 13:49:27 +0100 | Googulator13 | (~Googulato@team.broadbit.hu) (Ping timeout: 272 seconds) |
| 2026-01-16 13:49:10 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-01-16 13:48:50 +0100 | pipsquak-bird | (~g@c-71-235-170-34.hsd1.ma.comcast.net) (Remote host closed the connection) |
| 2026-01-16 13:48:41 +0100 | <Vq> | gentauro: "their" is nixpkgs, no? That one is normal to refer to as an input in your flake. |
| 2026-01-16 13:46:29 +0100 | <gentauro> | Vq: can I make a `flake.nix` and wrap their `flake.nix`? Like inception? |
| 2026-01-16 13:45:55 +0100 | Googulator1 | (~Googulato@team.broadbit.hu) |
| 2026-01-16 13:45:55 +0100 | <Vq> | gentauro: Maybe you're getting the environment for building ghc itself? If you define your own mkShell (in a flake) and put ghc810 in its buildInputs it ought to use the same cached version. |
| 2026-01-16 13:43:34 +0100 | attlin | (~user@user/attlin) (Ping timeout: 246 seconds) |
| 2026-01-16 13:42:19 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds) |
| 2026-01-16 13:39:59 +0100 | <gentauro> | Vq: I can actually build the `flake.nix` package. That said, I would like to be able to tell the `nix build` «Hey, here is ghc8107 cached, please use that instead of building it from scratch". I will keep investigating and probably become wiser |
| 2026-01-16 13:39:44 +0100 | danza | (~danza@user/danza) danza |
| 2026-01-16 13:39:33 +0100 | trickard_ | (~trickard@cpe-82-98-47-163.wireline.com.au) |
| 2026-01-16 13:37:00 +0100 | <Vq> | gentauro: If you write your own flake you can define what the default package, shell and dev-shell is. Now I guess you're relying on what happens to be in nixpkgs. |
| 2026-01-16 13:35:30 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-01-16 13:34:35 +0100 | <gentauro> | :) |
| 2026-01-16 13:34:33 +0100 | <gentauro> | I'm guessing it's just me who don't know how to "flakes" |
| 2026-01-16 13:34:18 +0100 | <gentauro> | while I'n in `nix shell` with the GHC, I try to do the `nix build …` and point to the flakes.nix and … yeah, it decides to build the ghc8107 anyway |
| 2026-01-16 13:33:44 +0100 | <gentauro> | the `nix shell --exp … flakes` and the GHC compiler actually works |
| 2026-01-16 13:33:25 +0100 | <gentauro> | Vq: Oh, I knew that. That's how I have been doing it up til now. However, projects seem to have moved on to `flakes`. So I'm trying to "learn" how to do stuff like that, but in flakes. |
| 2026-01-16 13:33:15 +0100 | Lycurgus | (~juan@user/Lycurgus) (Quit: alsoknownas.renjuan.org ( juan@acm.org )) |
| 2026-01-16 13:32:24 +0100 | trickard_ | (~trickard@cpe-82-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
| 2026-01-16 13:29:14 +0100 | trickard_ | (~trickard@cpe-82-98-47-163.wireline.com.au) |
| 2026-01-16 13:28:58 +0100 | trickard | (~trickard@cpe-82-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
| 2026-01-16 13:28:26 +0100 | <Vq> | gentauro: That's the old fashioned way to do version pinning. |
| 2026-01-16 13:28:06 +0100 | <Vq> | gentauro: And then invoke it with: nix-shell ghc810_shell.nix |
| 2026-01-16 13:27:50 +0100 | <Vq> | gentauro: Put this in a file with a name like ghc810_shell.nix: with import (builtins.fetchTarball { name = "nixos-25.05-2026-01-16"; url = "https://github.com/nixos/nixpkgs/archive/ac62194c3917d5f474c1a844b6fd6da2db95077d.tar.gz"; sha256 = "sha256:0v6bd1xk8a2aal83karlvc853x44dg1n4nk08jg3dajqyy0s98np"; }) {}; mkShell { buildInputs = [ haskell.compiler.ghc810 ]; } |
| 2026-01-16 13:26:33 +0100 | <Lycurgus> | those were the lean years in comparison to now |
| 2026-01-16 13:25:36 +0100 | <Lycurgus> | https://eg.meansofproduction.biz/eg/index.php/NixOS |
| 2026-01-16 13:24:34 +0100 | <gentauro> | I seem to be stucked in "old-school" NixOS xD |
| 2026-01-16 13:24:31 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2026-01-16 13:24:11 +0100 | ttybitnik | (~ttybitnik@user/wolper) ttybitnik |
| 2026-01-16 13:23:15 +0100 | <Lycurgus> | a pkg |
| 2026-01-16 13:22:46 +0100 | <gentauro> | `ihp`? |
| 2026-01-16 13:22:33 +0100 | <Lycurgus> | also lemme say ftr, claude can strip nix outta ihp |
| 2026-01-16 13:21:51 +0100 | <Lycurgus> | devenv? |
| 2026-01-16 13:21:50 +0100 | <gentauro> | (sometimes you "just" want to try someting out in a sandbox, before installing it) |
| 2026-01-16 13:21:34 +0100 | xff0x | (~xff0x@2405:6580:b080:900:c589:6b53:dd18:5a14) |
| 2026-01-16 13:21:31 +0100 | <gentauro> | Vq: I'm looking for the `flakes` replacement to `nix-shell`. I though it would be as simple as `nix shell` :) |
| 2026-01-16 13:21:08 +0100 | <Lycurgus> | >: |
| 2026-01-16 13:19:44 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-01-16 13:19:41 +0100 | Googulator | (~Googulato@team.broadbit.hu) (Ping timeout: 272 seconds) |
| 2026-01-16 13:17:10 +0100 | <Vq> | gentauro: I have experience with flakes, but I haven't used 'nix shell'. |
| 2026-01-16 13:15:49 +0100 | <gentauro> | (invest time to learn that, if, it's not gonna be a thing) |
| 2026-01-16 13:15:40 +0100 | Googulator13 | (~Googulato@team.broadbit.hu) |