Github messages for voidlinux
 help / color / mirror / Atom feed
From: the-maldridge <the-maldridge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: obs-plugin-browser-bin-29.0.2
Date: Tue, 21 Feb 2023 21:07:19 +0100	[thread overview]
Message-ID: <20230221200719.9vQsEvRlpaxShaWjtkiq-B__kp8lpORSrlAW6K9sq1Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42383@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 736 bytes --]

There is an updated pull request by the-maldridge against master on the void-packages repository

https://github.com/the-maldridge/void-packages obs-browser-bin
https://github.com/void-linux/void-packages/pull/42383

New package: obs-plugin-browser-bin-29.0.2
I'm not sure this is a good idea.  It works, but its doing the same kind of stuff we do to make the google chrome package work.  It should probably work then as a result, but I suspect its pretty fragile.  I stuck GPL-2.0-ONLY on it which is the correct license for the source, but since this includes a full embedded chromium I suspect that isn't quite right.  Advice is appreciated.

A patch file from https://github.com/void-linux/void-packages/pull/42383.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-obs-browser-bin-42383.patch --]
[-- Type: text/x-diff, Size: 2180 bytes --]

From 0d80db4688cb0eff5ed9fada7a69a3f28f9c77ee Mon Sep 17 00:00:00 2001
From: Michael Aldridge <maldridge@voidlinux.org>
Date: Tue, 21 Feb 2023 14:02:32 -0600
Subject: [PATCH] New package: obs-plugin-browser-bin-29.0.2

---
 srcpkgs/obs-plugin-browser-bin/template | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)
 create mode 100644 srcpkgs/obs-plugin-browser-bin/template

diff --git a/srcpkgs/obs-plugin-browser-bin/template b/srcpkgs/obs-plugin-browser-bin/template
new file mode 100644
index 000000000000..1a99bd8fbf7b
--- /dev/null
+++ b/srcpkgs/obs-plugin-browser-bin/template
@@ -0,0 +1,25 @@
+# Template file for 'obs-plugin-browser-bin'
+pkgname=obs-plugin-browser-bin
+version=29.0.2 # This is actually the version of obs to extract the plugin from
+revision=1
+archs="x86_64"
+short_desc="CEF-based OBS Studio browser plugin"
+maintainer="Michael Aldridge <maldridge@voidlinux.org>"
+license="GPL-2.0-only"
+homepage="https://obsproject.com/kb/browser-source"
+distfiles="https://launchpad.net/~obsproject/+archive/ubuntu/obs-studio/+files/obs-studio_29.0.2-0obsproject1~kinetic_amd64.deb"
+checksum=1fcc84fa3c917c8bb60c8d70c1b0961ceeb4db6b8f09483611b9b1e015b268c4
+
+do_install() {
+	vinstall lib/x86_64-linux-gnu/obs-plugins/obs-browser.so 0644 usr/lib/obs-plugins/
+	vinstall lib/x86_64-linux-gnu/obs-plugins/libcef.so 0644 usr/lib/obs-plugins/
+	vinstall lib/x86_64-linux-gnu/obs-plugins/icudtl.dat 0644 usr/lib/obs-plugins/
+	vinstall lib/x86_64-linux-gnu/obs-plugins/v8_context_snapshot.bin 0644 usr/lib/obs-plugins/
+	vinstall lib/x86_64-linux-gnu/obs-plugins/resources.pak 0644 usr/lib/obs-plugins/
+	vinstall lib/x86_64-linux-gnu/obs-plugins/vk_swiftshader_icd.json 0644 usr/lib/obs-plugins/
+	vinstall lib/x86_64-linux-gnu/obs-plugins/libvk_swiftshader.so 0644 usr/lib/obs-plugins/
+	vinstall lib/x86_64-linux-gnu/obs-plugins/chrome-sandbox 0644 usr/lib/obs-plugins/
+	vinstall lib/x86_64-linux-gnu/obs-plugins/chrome_100_percent.pak 0644 usr/lib/obs-plugins/
+	vinstall lib/x86_64-linux-gnu/obs-plugins/chrome_200_percent.pak 0644 usr/lib/obs-plugins/
+	vinstall lib/x86_64-linux-gnu/obs-plugins/obs-browser-page 0755 usr/lib/obs-plugins/
+}

  parent reply	other threads:[~2023-02-21 20:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 20:05 [PR PATCH] " the-maldridge
2023-02-21 20:06 ` [PR PATCH] [Updated] " the-maldridge
2023-02-21 20:07 ` the-maldridge [this message]
2023-02-23  8:01 ` [PR PATCH] [Merged]: " the-maldridge

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=20230221200719.9vQsEvRlpaxShaWjtkiq-B__kp8lpORSrlAW6K9sq1Y@z \
    --to=the-maldridge@users.noreply.github.com \
    --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).