Github messages for voidlinux
 help / color / mirror / Atom feed
From: Vulldozer <Vulldozer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: wlrobs-1.1
Date: Sun, 13 Nov 2022 13:07:19 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40502@inbox.vuxu.org> (raw)

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

There is a new pull request by Vulldozer against master on the void-packages repository

https://github.com/Vulldozer/void-packages add-wlrobs
https://github.com/void-linux/void-packages/pull/40502

New package: wlrobs-1.1
#### Testing the changes
- I tested the changes in this PR: **YES**

#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**

This template packages version 1.1 of wlrobs and addresses the issues in https://github.com/void-linux/void-packages/pull/29773

    What's the difference between this plugin and a proper setup with pipewire and portals?

The output you choose to capture and the crop/scale will be remembered, no need to use a tool to pick which display to capture every time, which allows smoother transitions between scenes.

Note: sorry for creating two pull requests (#40501) I made a mistake that I didn't know how to fix.

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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-add-wlrobs-40502.patch --]
[-- Type: text/x-diff, Size: 1038 bytes --]

From eb8f40d3f1159819b204f5d8d9fe7eaf5f9985ee Mon Sep 17 00:00:00 2001
From: Vulldozer <mhmd.ara56@gmail.com>
Date: Sun, 13 Nov 2022 13:59:23 +0200
Subject: [PATCH] New package: wlrobs-1.1

---
 srcpkgs/wlrobs/template | 13 +++++++++++++
 1 file changed, 13 insertions(+)
 create mode 100644 srcpkgs/wlrobs/template

diff --git a/srcpkgs/wlrobs/template b/srcpkgs/wlrobs/template
new file mode 100644
index 000000000000..3e3a862c8a2b
--- /dev/null
+++ b/srcpkgs/wlrobs/template
@@ -0,0 +1,13 @@
+# Template file for 'wlrobs'
+pkgname=wlrobs
+version=1.1
+revision=1
+build_style=meson
+hostmakedepends="pkg-config"
+makedepends="libdrm-devel libX11-devel obs-devel wayland-devel wlroots-devel"
+short_desc="OBS plugin to screen capture wlroots based wayland compositors"
+maintainer="Vuldozer <mhmd.ara56@gmail.com>"
+license="GPL-3.0-or-later"
+homepage="https://hg.sr.ht/~scoopta/wlrobs"
+distfiles="https://hg.sr.ht/~scoopta/wlrobs/archive/v${version}.tar.gz"
+checksum=5311c434316577b27803b272cb57011515f853705ef5d7e604ed73c483fa14be

             reply	other threads:[~2022-11-13 12:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13 12:07 Vulldozer [this message]
2022-12-21 19:59 ` [PR PATCH] [Updated] " Vulldozer
2022-12-21 20:02 ` Vulldozer
2022-12-21 20:26 ` Vulldozer
2022-12-26 20:05 ` [PR PATCH] [Updated] " Vulldozer
2022-12-26 20:21 ` JamiKettunen
2023-03-27  1:53 ` github-actions
2023-04-11  1:51 ` [PR PATCH] [Closed]: " github-actions
  -- strict thread matches above, loose matches on Subject: below --
2022-11-13 10:53 [PR PATCH] " Vulldozer

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-40502@inbox.vuxu.org \
    --to=vulldozer@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).