diff options
| author | emilylange <git@emilylange.de> | 2024-05-02 02:12:22 +0200 |
|---|---|---|
| committer | emilylange <git@emilylange.de> | 2024-05-02 02:12:22 +0200 |
| commit | 85dfe83a86658f3fba80c050a774195f08fb378d (patch) | |
| tree | 550eec44dc8337a7398c166f8276f141be0c075e /pkgs | |
| parent | b71eeb5b2d7a3c7aed0cb089bfad25b23cc008fc (diff) | |
chromium: lower version range of `--ozone-platform-hint` patch
Ref: fb10ea41b2a080cb4ecac34aa12cf056d8d3f90e We had to apply this patch from M125 to M124 because at the time, chromium hasn't backported this to M124 yet. Until now! Or at least somewhat. 124.0.6367.118 shipped and has an equivalent patch now, which means that this patch is no longer needed. (Ignoring the fact that it no longer applies because of this anyway) At least on chromium. The thing is, ungoogled-chromium hasn't caught up with chromium yet, meaning it is still on < .118 and thus still needs that patch.
Diffstat (limited to 'pkgs')
| -rw-r--r-- | pkgs/applications/networking/browsers/chromium/common.nix | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/pkgs/applications/networking/browsers/chromium/common.nix b/pkgs/applications/networking/browsers/chromium/common.nix index df33a2bbe7571..a59efb64d9356 100644 --- a/pkgs/applications/networking/browsers/chromium/common.nix +++ b/pkgs/applications/networking/browsers/chromium/common.nix @@ -248,8 +248,8 @@ let # Partial revert of https://github.com/chromium/chromium/commit/3687976b0c6d36cf4157419a24a39f6770098d61 # allowing us to use our rustc and our clang. ./patches/chromium-121-rust.patch - ] ++ lib.optionals (chromiumVersionAtLeast "124" && !chromiumVersionAtLeast "125") [ - # M124 shipped with broken --ozone-platform-hint flag handling, which we rely on + ] ++ lib.optionals (chromiumVersionAtLeast "124" && !chromiumVersionAtLeast "124.0.6367.118") [ + # M124 < 124.0.6367.118 shipped with broken --ozone-platform-hint flag handling, which we rely on # for our NIXOS_OZONE_WL (wayland) environment variable. # See <https://issues.chromium.org/issues/329678163>. # This is the commit for the fix that landed in M125, which applies clean on M124. |