Closed shadowrylander closed 2 months ago
Actually, I might've fixed that; now I need to know why using the extended lib with imports
(before config
) is throwing errors that the names of my attribute sets for my paths in path.nix
are not options!
Pinging @hlissner; sorry! I'm just really, really stuck on this next bit!
Well that's strange; I somehow fixed the next error by not using the lib.my.paths
in my modules list...
And it seems I've come back full circle; some modules cannot seem to access certain variables in the lib
module, whether built-in, such as mkForce
, or my own.
Actually, it seems like I can't access anything from the extended module; the attributes are either seen as missing, or are confused for options by the Nix interpreter.
@hlissner: It would appear as though usage of your lib extension fails with the same errors as well.
Sorry for only noticing this issue now, but I imagine you must've gotten around this by this point. I've since restructured my local libs to further disambiguate them from nixpkgs.lib, so I'll assume it's been resolved at some point along the way. Thanks for bringing it to my attention, in any case!
Hello!
I can't seem to access the default lib modules after extending
nixpkgs.lib
; when trying to accessmkDefault
, for example, the error states that the attribute doesn't exist.Here are my
flake.nix
and mylib/default.nix
.Thank you kindly for the help!
Update: here's a reddit post I created as well.