mesa: Attempt to upgrade the drivers with a minimal rebuild impact #100712
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
See #44831, though this is a more extreme approach.
Not sure yet if this is a stupid idea or a good way to quickly apply Mesa updates. This mainly makes sense under the assumption that minor/patch releases only update the drivers (
mesa.drivers
) anyway. The plan would be to freezemesa
atX.Y.1
(first stable release of a series) and updatemesa_drivers
toX.Y.1+N
without going through staging first. Or another idea would be to simultaneously updatemesa
viastaging
andmesa_drivers
viamaster
.Personally I'm already using that approach to test Mesa updates and it seemed to be fine so far (though I only did very minimal testing). However with
lsof
I can always see a few references to the previous Mesa version, though mainly(/only?) forlibgbm
IIRC (e.g./nix/store/***-mesa-X.Y.Z/lib/libgbm.so.1.0.0
). For that reasons it might make sense to simultaneously updatemesa
viastaging
or implement the approach from #44831.Note: The update to
20.1.10
doesn't make sense since20.2.1
is already in staging, it only serves as an example.Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)