-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nix flake show
should be filterable by the current system
#6985
Comments
I think your suggestion is the correct UX default irrespective of IFD. For any nontrivial flake with a nontrivial amount of supported systems, the output way is just way too redundant to answer simple questions about platform support like a) what is the total set of derivations available on any platform, and b) what platforms does this derivation support. If those are use cases
|
Is this still an issue?
#6988 notes that the fix does not apply to Hydra jobs. Is this |
Also with Nix 2.15:
|
The prior error must have been because the build was a Hydra job. In this example
https://github.com/haskell/hackage-server/blob/master/flake.nix |
Is your feature request related to a problem? Please describe.
Often when one runs
nix flake show
nix tries to evaluate every well known output, though some of them depend on the system, and even worse, some of them use IFD, so to nix being able to show the information it needs to build for a foreign system.This leads to errors like this:
Describe the solution you'd like
nix flake show
becomes system aware and does not try to evaluate foreign systems, but instead just shows an ellipsis as child for foreign systems. A fictive example could look like this:An extra flag could be introduced to "try anway" similar to how we use
--legacy
to get the full list of packages inlegacyPackages
, perhaps--foreign-systems
as in the example above.Describe alternatives you've considered
Fully forbid any kind of IFD in flake contexts.
Additional context
Actually I would totally prefer the alternative, though I see that the community isn't there yet and instead we need to raise awareness about the issue.
The text was updated successfully, but these errors were encountered: