vaapiIntel: unstable-20190211 -> 2.4.0 #75342
Merged
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.
Motivation for this change
After 10+ months, Intel cut a new release of
intel-vaapi-driver
so we can get back to a stable release in nixpkgs.See: intel/intel-vaapi-driver#449
BTW: Why are this and other related packaged named so weirdly?
vaapiIntel
vsintel-vaapi-driver
? I'm more accustomed to seeing package names in nixpkgs follow their upstream package names?NOTE: As much as I want to trust Intel, I haven't tested this myself so I can't vouch for this yet. I'll move this out of Draft when I get a chance to test it.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers
cc @