Le 2019-02-19 14:28, Jason Self a écrit :
On Tue, 2019-02-19 at 02:06 -0500, Leo Famulari wrote:
Why do you think this is the case?
We know Chromium comes with it. Have you looked through ungoogled-
chromium to see where it's being deleted?
Our package definition has two widevine-related headers listed as
preserved third-party stuff... I'm not sure how widevine normally
gets into chromium, but if we don't have it, I guess we should
not need these headers? There might actually be an issue, but
I'm not sure how to check. Where is widevine in upstream (non
ungoogled) chromium? Is it downloaded at runtime?
IIUC, the rest of this widevine directory is removed before
building anything, so maybe there's nothing to worry about
after all?
