From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] chromium-widevine: update file structure for 78.0.3904.70
Date: Sat, 26 Oct 2019 16:33:06 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15810@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 529 bytes --]
There is a new pull request by pbui against master on the void-packages repository
https://github.com/pbui/void-packages chromium-widevine
https://github.com/void-linux/void-packages/pull/15810
chromium-widevine: update file structure for 78.0.3904.70
With the update to 78.0.3904.70, chromium now expects additional files
and a new file system layout for the widevine component.
This has been tested with Netflix and Amazon Prime.
A patch file from https://github.com/void-linux/void-packages/pull/15810.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-chromium-widevine-15810.patch --]
[-- Type: text/x-diff, Size: 2047 bytes --]
From c8595fe455d5be8ebcd831ea0d0d5eebfa771c19 Mon Sep 17 00:00:00 2001
From: Peter Bui <pbui@github.bx612.space>
Date: Sat, 26 Oct 2019 10:30:34 -0400
Subject: [PATCH] chromium-widevine: update file structure for 78.0.3904.70
With the update to 78.0.3904.70, chromium now expects additional files
and a new file system layout for the widevine component.
This has been tested with Netflix and Amazon Prime.
---
srcpkgs/chromium-widevine/INSTALL | 11 +++++++++--
srcpkgs/chromium-widevine/template | 2 +-
2 files changed, 10 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/chromium-widevine/INSTALL b/srcpkgs/chromium-widevine/INSTALL
index cc8b86d1410..4d9267196e3 100644
--- a/srcpkgs/chromium-widevine/INSTALL
+++ b/srcpkgs/chromium-widevine/INSTALL
@@ -9,9 +9,16 @@ post)
# Things that have to happen no matter what
cd $BUILD_DIR
ar x $PKGNAME.deb
- tar xf data.tar.xz --wildcards './opt/google/chrome/libwidevine*'
+ tar xf data.tar.xz --wildcards './opt/google/chrome/WidevineCdm/'
cd -
- mv $BUILD_DIR/opt/google/chrome/libwidevine* usr/lib/chromium
+ # Remove previous components
+ rm -fr /usr/lib/chromium/WidevineCdm /usr/lib/chromium/libwidevinecdm.so
+ # Move new components
+ mv $BUILD_DIR/opt/google/chrome/WidevineCdm /usr/lib/chromium/
+ ln -s /usr/lib/chromium/WidevineCdm/_platform_specific/linux_x64/libwidevinecdm.so /usr/lib/chromium/libwidevinecdm.so
+ [ ! -d /usr/lib/chromium-dev ] && mkdir /usr/lib/chromium-dev
+ ln -s /usr/lib/chromium/WidevineCdm /usr/lib/chromium-dev/WidevineCdm
+ # Cleanup
rm -r $BUILD_DIR
;;
esac
diff --git a/srcpkgs/chromium-widevine/template b/srcpkgs/chromium-widevine/template
index d598d343905..09122b8bee9 100644
--- a/srcpkgs/chromium-widevine/template
+++ b/srcpkgs/chromium-widevine/template
@@ -7,7 +7,7 @@ _channel="stable"
pkgname=chromium-widevine
version=78.0.3904.70
-revision=1
+revision=2
archs="x86_64"
create_wrksrc=yes
short_desc="Browser plugin designed for the viewing of premium video content"
next reply other threads:[~2019-10-26 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-26 14:33 voidlinux-github [this message]
2019-10-26 23:02 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-26 23:02 ` voidlinux-github
2019-10-27 5:41 ` [PR PATCH] [Merged]: " voidlinux-github
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15810@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).