| 2 Oct 2025 |
 Niclas Overby Ⓝ | Ideally I would use lib, but how can you access nixpkgs from lib? | 17:19:17 |
| Niclas Overby Ⓝ | * Ideally I would use nix/lib.nix, but how can you access nixpkgs? | 17:20:33 |
| Niclas Overby Ⓝ | * Ideally I would use nix/lib.nix, but how can you access pkgs? | 17:21:47 |
 accelbread | Some folk put per-system things in lib like lib.x86_64-linux.mkShell. You can do that in flakelight either with nix/lib.nix:
{ genSystems, ... }: ({
# regular lib stuff
} // genSystems (pkgs: {
# per-system lib stuff
}))
| 17:44:31 |
| accelbread | * Some folk put per-system things in lib like lib.x86_64-linux.mkShell. You can do that in flakelight either with nix/lib.nix:
{ genSystems, ... }: ({
# regular lib stuff
} // genSystems (pkgs: {
# per-system lib stuff
}))
| 17:44:38 |
| accelbread | * Some folk put per-system things in lib like lib.x86_64-linux.mkShell. You can do that in flakelight with nix/lib.nix:
{ genSystems, ... }: ({
# regular lib stuff
} // genSystems (pkgs: {
# per-system lib stuff
}))
| 17:55:31 |
| accelbread | * Some folk put per-system things in lib like lib.x86_64-linux.mkShell. You can do that in flakelight with nix/lib.nix:
{ genSystems, ... }: ({
# regular lib stuff
} // genSystems (pkgs: {
# per-system lib stuff
}))
| 17:56:10 |
| 3 Oct 2025 |
| Niclas Overby Ⓝ | Is it possible to disable the nixDir feature? Or more fine-grained, disable autoloading of specific outputs in nixDir? | 08:50:02 |
| accelbread | yeah, can set it to a non-existing dir iirc. I could add a null option | 16:01:53 |
| accelbread | fine-grained, no | 16:02:15 |
| 4 Oct 2025 |
| Niclas Overby Ⓝ | That would be awesome! :) | 11:25:04 |
| 7 Oct 2025 |
| accelbread | nixDir can now be set to null: https://github.com/nix-community/flakelight/commit/eda172d7ead89292cb7f9e136a482e97e00873a4 | 06:27:30 |
| 8 Oct 2025 |
| Niclas Overby Ⓝ | Is there a reason, that the ./. argument is separate from the following attributeset?
Why this:
outputs = inputs:
inputs.flakelight ./. {
inherit inputs;
And not this:
outputs = inputs:
inputs.flakelight {
inherit inputs;
src = ./.;
| 11:40:24 |
| Niclas Overby Ⓝ | Some another questions :)
Other than populating the src attribute and detecting the nixDir directory, is ./. used for anything else?
Could it potentially be made optional?
| 11:42:45 |
| Niclas Overby Ⓝ | * Is there a reason, that the ./. argument is separate from the following attributeset?
Why this:
outputs = inputs:
inputs.flakelight ./. {
inherit inputs;
And not this:
outputs = inputs:
inputs.flakelight {
inherit inputs;
src = ./.;
I guess the first is a little shorter, but are there any other reason?
| 11:43:46 |
