-
-
Notifications
You must be signed in to change notification settings - Fork 17.2k
treewide: drop flattenInclude hack #348483
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
Conversation
|
Does this cause issues or is just a cleanup? If the later we could just schedule it for next stable to be on the chilled side. |
|
Technically, it can cause issues. In practice, I really doubt it will. |
|
I get that it solves the linked issue, too? (an argument to have this PR in 24.11) |
|
For this specific package, yes. Generally, this is a buildEnv / symlink loops issue, and I think the endgame should be to just ban symlink loops treewide. |
|
@ofborg eval |
1 similar comment
|
@ofborg eval |
af549eb to
0b9aa54
Compare
This may have been relevant 10 years ago ([DOUBT]), but it sure as hell isn't now, and recursive symlinks are evil. May it burn in hell, as that is where it belongs.
0b9aa54 to
54874b3
Compare
|
Bisect says 54874b3 |
|
Proposed |
This may have been relevant 10 years ago ([DOUBT]), but it sure as hell isn't now, and recursive symlinks are evil.
May it burn in hell, as that is where it belongs.
I've built both Qt versions and all three GTKs, which should hopefully contain most of the blast radius, but there's definitely a chance of a lot of random leaf packages breaking here, so I'm not sure if we want to rush it in before 24.11.
Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Add a 👍 reaction to pull requests you find important.