Hi Bart
To be honest, my preference would still be to merge both packages under the "widevine" name. I'm willing to maintain such a merged package.
It won't happen as chromium-widevine is way more more popular, still maintained, has a huge number of votes and comments, while widevine is a mere duplicated package with a very strict use case, mainly to support different architectures not supported by Arch Linux with only 1 vote and only 6 months old.
Supporting evidence: - chromium-widevine downloads the entire chrome browser to only extract the lib. The widevine package downloads the separately packaged lib directly from google. This is much more efficient.
The straightforward solution would be to use the widevine source in the chromium-widevine package, but I doubt the maintainer is willing to do that. In the case the chromium-widevine package would be abandoned, you could maintain it, but until that moment arrives, I think there's no point in keeping the duplicated package, only for supporting the unsupported architectures or to add thirdy part browsers. Unfortunately after one month of discussion I still cannot find any reasons to keep this package. The package will be removed in the next days. Regards -- Fabio Castelli aka Muflone