Github messages for voidlinux
 help / color / mirror / Atom feed
From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: loudgain-0.6.8
Date: Fri, 21 Aug 2020 12:04:25 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24400@inbox.vuxu.org> (raw)

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

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

https://github.com/motorto/void-packages loudagaing
https://github.com/void-linux/void-packages/pull/24400

New package: loudgain-0.6.8
Asked on #23054 

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

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

From 29526f7590022d0618f53e20f0b63c30b01c9638 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Wed, 5 Aug 2020 20:23:52 +0100
Subject: [PATCH] New package: loudgain-0.6.8

New package: loudgain-0.6.8
---
 srcpkgs/loudgain/template | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)
 create mode 100644 srcpkgs/loudgain/template

diff --git a/srcpkgs/loudgain/template b/srcpkgs/loudgain/template
new file mode 100644
index 00000000000..80010331b83
--- /dev/null
+++ b/srcpkgs/loudgain/template
@@ -0,0 +1,20 @@
+# Template file for 'loudgain'
+pkgname=loudgain
+version=0.6.8
+revision=1
+build_style=cmake
+hostmakedepends="libebur128-devel ffmpeg-devel libavcodec libavformat libavutil libswresample libebur128 taglib-devel pkg-config"
+short_desc="Versatile ReplayGain 2.0 loudness normalizer,EBU R128/ITU BS.1770"
+maintainer="André Cerqueira <acerqueira021@gmail.com>"
+license="BSD-2-Clause"
+homepage="https://github.com/Moonbase59/loudgain"
+distfiles="https://github.com/Moonbase59/loudgain/archive/v${version}.tar.gz"
+checksum=1137c193ad941b366e87c5d84ccc95a7aa8571affc060db0bd1cf72c489aeaee
+
+pre_build() {
+	mkdir -p build && cd build
+}
+
+post_install() {
+	vlicense COPYING
+}

             reply	other threads:[~2020-08-21 10:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-21 10:04 motorto [this message]
2020-08-21 12:02 ` [PR REVIEW] " sgn
2020-08-21 12:11 ` motorto
2020-08-21 12:13 ` ericonr
2020-08-21 12:30 ` motorto
2020-08-21 12:32 ` motorto
2020-08-21 12:37 ` [PR PATCH] [Updated] " motorto
2020-08-21 15:32 ` [PR REVIEW] " sgn
2020-08-21 15:42 ` motorto
2020-08-31 14:52 ` Duncaen
2020-08-31 16:03 ` [PR PATCH] [Updated] " motorto
2020-08-31 16:03 ` [PR REVIEW] " motorto
2020-09-04 20:10 ` motorto
2020-09-04 20:11 ` motorto
2020-09-04 20:21 ` [PR REVIEW] " Duncaen
2020-09-04 22:29 ` [PR PATCH] [Updated] " motorto
2020-09-04 22:31 ` motorto
2020-11-22  5:06 ` the-maldridge
2020-11-22  5:06 ` [PR PATCH] [Closed]: " the-maldridge
2020-11-12 12:30 [PR PATCH] " kartikynwa

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