| 23 Aug 2025 |
 emily | the NixOS module calls the package with its own Nixpkgs input anyway | 23:13:16 |
| emily | in the flake | 23:13:28 |
| emily | so most users will be using their actual Nixpkgs if they set the follow | 23:13:30 |
| emily | in any case any new changes to a Lix release branch will never hit EOL Nixpkgs versions and I'm assuming that using Lix from the repo with EOL Nixpkgs versions is also not supported, so testing EOL versions in CI makes little sense for any branch | 23:14:16 |
| emily | aloisw: btw, one of the problems with keeping the old toml11 is that we need the new one for the CMake 4 bump | 23:14:46 |
| emily | so I would strongly prefer to just fix this | 23:14:57 |
| emily | (by need I mean: the old one will cause problems with CMake 4) | 23:15:41 |
 raitobezarius | In reply to @emilazy:matrix.org
so most users will be using their actual Nixpkgs if they set the follow i'm a non flake user :D | 23:18:14 |
| emily | actually it is not even about the flake input, I was wrong | 23:18:51 |
| emily | it sets an overlay | 23:18:53 |
| raitobezarius | yeah | 23:18:57 |
| emily | so it will be using the NixOS system's package set, regardless | 23:18:59 |
| raitobezarius | hm yep | 23:19:10 |
| 24 Aug 2025 |
 Lunaphied | Uhhhh | 00:28:08 |
| Lunaphied | hm something about that seems off | 00:28:13 |
| Lunaphied | In reply to @raitobezarius:matrix.org
i'm a non flake user :D I really need to get around to that change with supporting overrides in flake-compat | 00:28:36 |
| raitobezarius | just give me https://git.afnix.fr/sprinkles/sprinkles | 00:29:20 |
| Lunaphied | o.o what's this exactly? | 00:34:46 |
| raitobezarius | Charles attempts to bring a flake structure to the non-flake world | 00:35:05 |
| raitobezarius | i personally like it, it's growing on me certainly | 00:35:16 |
| Lunaphied | hm, I guess we should look at that | 00:45:17 |
| emily | "source and input must be the only variables defined in the let binding." maintaining the vital flakes property of not being Nix I see :P | 01:03:49 |
 Charles | that's mainly there to keep the structure consistent; if you want to define arbitrary stuff i usually have a let binding inside output like
{
output = self:
let
inherit (self.input) nixpkgs;
foo = 4;
in
{
shell.default = nixpkgs.callPackage ./shell/default { inherit foo; };
};
}
for example. other major difference from flakes is that e.g. source = import ./lon.nix; works and is a totally reasonable thing to do
| 01:23:08 |
| Charles | if you really don't want to follow a convention, then not following the convention is also an option, but then you don't get the benefits of following the convention | 01:24:40 |
| Charles | * that's mainly there to keep the structure consistent and make overrideability more consistently available; if you want to define arbitrary stuff i usually have a let binding inside output like
{
output = self:
let
inherit (self.input) nixpkgs;
foo = 4;
in
{
shell.default = nixpkgs.callPackage ./shell/default { inherit foo; };
};
}
for example. other major difference from flakes is that e.g. source = import ./lon.nix; works and is a totally reasonable thing to do
| 01:26:23 |
| Charles | * that's mainly there to keep the structure consistent and make overrideability more consistently available; if you want to define arbitrary stuff i usually have a let binding inside output like
# [stuff]
{
# [stuff]
output = self:
let
inherit (self.input) nixpkgs;
foo = 4;
in
{
shell.default = nixpkgs.callPackage ./shell/default { inherit foo; };
};
}
for example. other major difference from flakes is that e.g. source = import ./lon.nix; works and is a totally reasonable thing to do
| 01:27:02 |
| emily | re "make overrideability more consistently available", is there non-Nix stuff parsing these files? (I'm struggling to understand what forbidding other let bindings achieves) | 01:32:12 |
| Charles | nope | 01:32:28 |
| Charles | when i say overrideability i mean the ability to do someSprinkle.override { source = { ... }; input = source: { ... }; } and have it affect everything in someSprinkle that should be affected | 01:33:50 |
| Charles | there's not that much code for sprinkles.new but it is pretty dense, might help to try reading that to get an idea of what's going on?
- https://git.afnix.fr/sprinkles/sprinkles/src/branch/v1/nix/lib/default.nix
- https://git.afnix.fr/sprinkles/sprinkles/src/branch/v1/nix/lib/private.nix
| 01:35:14 |
