Replies: 3 comments 1 reply
-
|
Carving out my feedback on #206 here:
/* We should acknowledge that flake.nix will be the first place people look to, so after being stripped down via devos-as-a-library, we need to make sure this file properly represents an index and self-evident semantic overview of what is going on in the repo. |
Beta Was this translation helpful? Give feedback.
-
|
On a related note, I think a compact well-designed library is mentally cheaper than multiple "libraries" based on each concept (host, modules, suites) in a sub-flake. I think so, because devos — all in all — is a coherent set of concepts. |
Beta Was this translation helpful? Give feedback.
-
|
The only reason I support subflakes isn't to try and make sublibraries. It is because there is absolutely no computation allowed on existing inputs. Meaning with just a single flake, you are forced to declare all your inputs in a single place. As the curent flake.nix shows, this gets pretty unmanagable pretty quickly. If we could get nix to resolve this upstream with something like what I've mentioned in NixOS/nix#3978, we could ensure that the subflakes are kept as private information, by disallowing I'm actually thinking of implementing this myself as my first addition to upstream nix. |
Beta Was this translation helpful? Give feedback.
-
|
I guess, I've to better understand the use case, still. Some inaccurate rough image might have built up in my head. Is the main use case |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
If there is anything about this repository that users don't like or feel could be simplified, we probably want to address those concerns before flakes become the default mechanism in NixOS. Before opening an issues, I'd like to start an informal discussion for any ideas or enhancements anyone would like to suggest.
Beta Was this translation helpful? Give feedback.
All reactions