if some executable `foo` depends on some specific behavior in some version of some library, it's fine. repoquery can help, but is kind of a hassle. On most computers (personal, home computers) the various lib dirs get scary after a while. want to try out some nightly build? no problem. I'm new to nix/nixos but gradually building up my environment. Then you could also use your own filters for ignoring files, rather than relying on the coupling to git and its staging area. This kind of copying would likely be a lot more acceptable if it was specified explicitly in flake.nix, rather than implicitly. There is an issue about making the copying of the entire directory into /nix/store lazy - though this doesn't really address the problem. This is terrible for mono-repos - and especially if it contains any large files. I've wasted more time than I'd like to admit wondering why what I'm building doesn't include my latest change.įlakes copy the entire directory into the nix store. You need to remember to stage changes whenever you do Ctrl+S in your editor before rebuilding. If you don't pin your third party flake urls they might also change under your nose as you run the same command again a day later.įlakes are coupled to git. The biggest show-stoppers for me with flakes is:īuilding third party flakes takes forever since every flake uses its own version of nixpkgs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |