Github messages for voidlinux
 help / color / mirror / Atom feed
From: ftrvxmtrx <ftrvxmtrx@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: clapper-0.5.2
Date: Mon, 04 Jul 2022 17:33:03 +0200	[thread overview]
Message-ID: <20220704153303.F-RRn68k2GXMOs0iTL7-onFX4pPYJA-N9erB_Em7gKk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37841@inbox.vuxu.org>

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

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

https://github.com/ftrvxmtrx/void-packages clapper
https://github.com/void-linux/void-packages/pull/37841

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

#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
- I built this PR locally for these architectures:
  - aarch64-musl


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

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

From 51cc4a6a01e096818154492ec28aeb37ddbcd11f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Sigrid=20Solveig=20Hafl=C3=ADnud=C3=B3ttir?=
 <sigrid@ftrv.se>
Date: Mon, 4 Jul 2022 16:57:44 +0200
Subject: [PATCH] New package: clapper-0.5.2

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

diff --git a/srcpkgs/clapper/template b/srcpkgs/clapper/template
new file mode 100644
index 000000000000..2c499d013600
--- /dev/null
+++ b/srcpkgs/clapper/template
@@ -0,0 +1,16 @@
+# Template file for 'clapper'
+pkgname=clapper
+version=0.5.2
+revision=1
+build_helper="gir"
+build_style=meson
+hostmakedepends="pkg-config gettext gettext-devel glib-devel gjs"
+makedepends="gstreamer1-devel gst-plugins-base1-devel gtk4-devel gjs-devel"
+depends="gjs libadwaita"
+short_desc="GNOME media player built using GJS, GTK4, GStreamer and OpenGL"
+maintainer="Sigrid Solveig Haflínudóttir <sigrid@ftrv.se>"
+license="GPL-3.0-or-later"
+homepage="https://github.com/Rafostar/clapper"
+changelog="https://github.com/Rafostar/clapper/releases"
+distfiles="https://github.com/Rafostar/${pkgname}/archive/${version}.tar.gz"
+checksum=30b78e0fc45346aee6513dc9fcd974d2cf9752cb9de5c9e352f5521aa640f284

  parent reply	other threads:[~2022-07-04 15:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 15:28 [PR PATCH] " ftrvxmtrx
2022-07-04 15:31 ` [PR PATCH] [Updated] " ftrvxmtrx
2022-07-04 15:33 ` ftrvxmtrx [this message]
2022-07-07 14:53 ` ftrvxmtrx
2022-07-07 14:55 ` ftrvxmtrx
2022-07-20 21:54 ` [PR REVIEW] " paper42
2022-08-14 11:54 ` paper42
2022-11-13  8:50 ` github-actions
2022-11-28  2:04 ` [PR PATCH] [Closed]: " github-actions

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=20220704153303.F-RRn68k2GXMOs0iTL7-onFX4pPYJA-N9erB_Em7gKk@z \
    --to=ftrvxmtrx@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).