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
treewide: stdenv.lib -> lib #109425
treewide: stdenv.lib -> lib #109425
Conversation
Rebased on staging-next because of all the whitespace errors. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
assuming no rebuilds, or package changes
@jonringer Should I rebase on master? If this gets merged to master, and staging-next has my whitespace cleanups, won't we have a merge conflict when we try to merge staging-next into master? |
On second thought, this is a harmless change and the goal is quicker deprecation of |
0b796a4
to
fc186d5
Compare
@siraben can you please take a look at the rebuilds ofborg listed and move them to a separate PR? |
It is worldofgoo, sil and mendeley. |
@SuperSandro2000 I took a look at the changed paths.
None of these changes affect the build in any way. |
I am fine with those changes. The would otherwise affect the editorconfig ci check. |
Motivation for this change
Further progress on #108938. References to
stdenv.lib
are still plenty abound, to make reviewing and debugging easier I'm performing changes to entire subdirectories in separate commits (will be squashed at the end). The process was initially manual but I've mostly automated it.I would run the following command and discard changes on non-Nix files.
Then I made a
step.sh
Then I ran
Whenever an error appeared, I interrupted and fixed it manually. Some interesting errors I found after the replacement were
let lib = stdenv.lib
(leads to infinite recursion)applications
data
desktops
development
games
misc
os-specific
servers
shells
tools
top-level