You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In flakes, the packages output should contain things that a user might want to install or run. It shouldn't contain arbitrary derivations that are not of interest to the user. But Nix's own packages.<system> output contains 293 packages:
This is bad UX because it hides the useful packages (i.e. nix) among all the irrelevant stuff. The vast majority of these should be removed: the tests, the cross builds (probably), all the *Stdenv stuff, dockerImage and changelog-d.
Probably the only ones that should be in there are default, nix and nix-static.
Steps To Reproduce
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
A clear and concise description of what you expected to happen.
Would it be okay to create a new output attrset for the cross compiled packages, for example?
The tests I think can live under the checks output, I guess.
This relates to the "recipes vs CI test points" thing we were discussing the other day. The idioms flakes are intended to promote are far from clear. The proper downstream usage is also not clear.
Describe the bug
In flakes, the
packages
output should contain things that a user might want to install or run. It shouldn't contain arbitrary derivations that are not of interest to the user. But Nix's ownpackages.<system>
output contains 293 packages:This is bad UX because it hides the useful packages (i.e.
nix
) among all the irrelevant stuff. The vast majority of these should be removed: the tests, the cross builds (probably), all the*Stdenv
stuff,dockerImage
andchangelog-d
.Probably the only ones that should be in there are
default
,nix
andnix-static
.Steps To Reproduce
Expected behavior
A clear and concise description of what you expected to happen.
nix-env --version
outputAdditional context
Add any other context about the problem here.
Priorities
Add 👍 to issues you find important.
The text was updated successfully, but these errors were encountered: