Conversation

Charlotte lotteheartplural/Cinny cinny_heart_plural thetadelta ursaminor treblesand

every time i deal with flakes i run into issues like ”the author has not specifically allow-listed my specific system” and the solution is to go fuck myself

1
0
1

@saphire the package output is fundamentally only available through a fixed nixpkgs instantiation with flake-fixed arguments. if you need other values you can go pound sand

also not every flake has an overlay. and sometimes the overlay just reexports the broken packages from the package output

1
0
0

@saphire nixpkgs is comparatively great at cross compiling so flakes naturally make it impossible without circumventing 100% of what flakes has over npins

1
0
0

@saphire the epitome of this got to be THE flake that ~everything useful depends on

github:NixOS/nixpkgs

a large amount of packages refuse to evaluate in the flakes and the only way to circumvent that is to either import nixpkgs directly (circumventing the flake…) or enabling impure eval mode which is only useful imperatively

1
0
0

@saphire the problem is like fundamentally that flake authors need to anticipate 100% of use cases and not just the ones they care about. without flakes it often times isn’t hard for a user to tweak it to fit your use cases. now it’s much harder. and the baseline is that you should actually intentionally not care about having a flake with functional outputs

0
0
0