dxvk: refactor based on post-merge feedback and bump to 1.10.1 #163474
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes
I received some post-merge feedback on #161522 raising concerns that Darwin could block updates on Linux. I’ve refactored the derivation to address those concerns without cluttering up the derivation too much or requiring separate upstream sources for Darwin and Linux.
I also moved the DXVK compatibility patch to a passthru attribute on
darwin.moltenvk
. Per @Gcenx, I do not want to provide a package for a patched MoltenVK because it should never be used except with DXVK. Both derivations have several comments emphasizing this. The patch was moved in case different versions of MoltenVK require their own patches.@Atemu pinging you to see if this addresses your concerns
Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)nixos/doc/manual/md-to-db.sh
to update generated release notes