Arch Linux User Repository

ATTENTION:

This package is no longer needed for Chromium, it can download the component itself. With Chromium 81, you can either use this or let it download the component, but when Chromium 83 is updated in the Arch repos, it will ignore this package all together.

I'll maintain this package for a while for the other systems that use it.

@Scimmia, I'm sorry for the confusion, but I didn't expect anybody to delete the repo immediately afterwards. If I had known that was the intention, I would have done some more tests to fully confirm. This said, I'll restore the repo, although as you said, all votes and comments will be gone.

Thank you.

You specifically said that you didn't need vivaldi-widevine if you had chromium-widevine installed. Now you're saying that's not the case? A previous comment from someone else had said that it worked, too :(.

The git repo for vivaldi-widevine would still exist, so remaking it is simple, but the votes and comments are gone. It should remove chromium-widevine from the conflicts, too, in that case (it never actually conflicted).

It looks like vivaldi comes with an update-widevine program, where does it put it? If it really has to be in /opt/google/chrome/, what would you think of just having a symlink in a separate package, so we aren't duplicating effort? I'm not willing to make this conflict with google-chrome.

@Scimmia, I think I might make a mistake in my previous answer. To the point I've been able to find out, Vivaldi is only able to find out widevine plugin under /opt/google/chrome/. So, using chromium-widevine as a replacement of vivaldi-widevine doesn't work currently. The reason is that chromium-widevine places the plugin under /usr/lib/chromium/. However, by just creating a symlink libwidevinecdm.so -> /usr/lib/chromium/libwidevinecdm.so under /opt/google/chrome/ solves the problem. Without it, it simply doesn't work to me.

Thoughts?

@Scimmia, that's the reason why this package conflicts with chromium-widevine and google-chrome packages. In other words, if you have already one of these, you don't need vivaldi-widevine.

Thank you.

So vivaldi finds the plugin in /usr/lib/chromium/? This is now just a duplicate of chromium-widevine?

Updated to version 4.10.1503.4.

Enjoy!

That's going to differ from this PKGBUILD in pretty much every way. Not really something that's doable in this package.

@manuel-192, although _chrome_ver doesn't have the latest version, it still contains the very same version of widevine plugin. So, the same binary is packaged regardless. Because of this, I'll reset the out-of-date flag.

Thank you.

I've edited my previous comment.

Based on what upstream binary?