Previously, chromium automatically downloaded Widevine via its
component updater when encountering DRM protected content for the first
time or when manually opening chrome://components.
This commit disables that and also prevents previously downloaded
Widevine blobs (usually in ~/.config/chromium/WidevineCdm/) from being
loaded and executed.
Widevine now only works using
~~~
chromium.override { enableWideVine = true; }
~~~
making Widevine truly opt-in, as it's supposed to be.
Using that override also sets meta.license to unfree, making the
end user aware that Widevine is in fact unfree.
See issue 115275 for further details.
ungoogled-chromium, the only remaining consumer of this patch (due to
the version range), caught up with chromium.
Meaning this patch is no longer needed.
Ref: 85dfe83a86
Ref: fb10ea41b2
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.
Historically, `google-chrome` used the version info and debian package
FOD provided by `chromium`.
This was very efficient, because `chromium` uses parts of the debian
tarball for Widevine (opt-in, via `.override`).
Meaning `chromium` has to track that debian tarball with each update
anyway.
And they always release in sync.
So why keep seperate `google-chrome` from `chromium` now?
- The current `chromium` maintainers are already at capacity
maintaining `chromium` and have no time for `google-chrome`.
- `chromium` bumps become sometimes a bottleneck for `google-chrome`.
This is because `chromium` is built from source and a lot more time
consuming and significantly more complex.
- Lately, `chromium` and `google-chrome` both had an upstream issue
under wayland with `--ozone-platform-hint`, rendering it unusable.
For `chromium` we were able to patch it, since unlike `google-chrome`
it's built from source.
The `chromium` maintainers simply forgot that `google-chrome` might
have the same issue, continued to merge the PR, rendering
`google-chrome` broken.
This PR also removes primeos from `meta.maintainers` since they only
added themself to `google-chrome` because it inherited `chromium`'s
version, stating they don't actually use `google-chrome`.
Furthermore, primeos no longer maintains `chromium`.
Ref 477e7d6b60
They're not autogenerated files any longer, and have been shipped as part
of the source tree since roughly Aug 2022.
Related: mozbz#1787977 ("Include configure in the tree")
Closes: #306937
