Github messages for voidlinux
 help / color / mirror / Atom feed
From: Bnyro <Bnyro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: avizo-1.2.1
Date: Tue, 06 Feb 2024 14:20:10 +0100	[thread overview]
Message-ID: <20240206132010.BE4BE238CC@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47209@inbox.vuxu.org>

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

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

https://github.com/Bnyro/void-packages avizo
https://github.com/void-linux/void-packages/pull/47209

New package: avizo-1.2.1
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### 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**

#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - armv6l-musl (cross)


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

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

From 312aaecd6c46ebb2d96a2098fe0fdee504056894 Mon Sep 17 00:00:00 2001
From: Bnyro <bnyro@tutanota.com>
Date: Mon, 13 Nov 2023 17:49:56 +0100
Subject: [PATCH] New package: avizo-1.2.1

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

diff --git a/srcpkgs/avizo/template b/srcpkgs/avizo/template
new file mode 100644
index 0000000000000..1fdc5e2316421
--- /dev/null
+++ b/srcpkgs/avizo/template
@@ -0,0 +1,20 @@
+# Template file for 'avizo'
+pkgname=avizo
+version=1.2.1
+revision=1
+build_style=meson
+hostmakedepends="vala pkg-config cmake gobject-introspection glib-devel gdk-pixbuf"
+makedepends="gtk+3-devel gtk-layer-shell-devel glib-devel"
+depends="bash light pamixer"
+short_desc="Neat notification daemon"
+maintainer="Bnyro <bnyro@tutanota.com>"
+license="GPL-3.0-only"
+homepage="https://github.com/misterdanb/avizo"
+distfiles="https://github.com/misterdanb/avizo/archive/refs/tags/${version}.tar.gz"
+checksum=efd4763db7c802d22e8939dac909d4886f5967aefbfc3fd526735da2a814b91b
+
+pre_build() {
+	if [ "$CROSS_BUILD" ]; then
+		export GI_TYPELIB_PATH="${XBPS_CROSS_BASE}/usr/lib/girepository-1.0"
+	fi
+}

  parent reply	other threads:[~2024-02-06 13:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 17:29 [PR PATCH] " Bnyro
2023-11-13 19:25 ` [PR PATCH] [Updated] " Bnyro
2024-02-05 22:30 ` [PR REVIEW] " Piraty
2024-02-06 13:20 ` Bnyro [this message]
2024-02-06 13:20 ` Bnyro
2024-02-10  2:15 ` Piraty
2024-02-10  2:18 ` [PR PATCH] [Closed]: " Piraty
2024-02-10  8:34 ` Bnyro

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=20240206132010.BE4BE238CC@inbox.vuxu.org \
    --to=bnyro@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).