From: fccapria <fccapria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: wired-notify-0.10.2
Date: Wed, 05 Oct 2022 14:19:24 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39736@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
There is a new pull request by fccapria against master on the void-packages repository
https://github.com/fccapria/void-packages fccapria
https://github.com/void-linux/void-packages/pull/39736
New package: wired-notify-0.10.2
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, x86_64
A patch file from https://github.com/void-linux/void-packages/pull/39736.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fccapria-39736.patch --]
[-- Type: text/x-diff, Size: 1231 bytes --]
From 5442d9bc4672399a39884bd214c70429fec5369a Mon Sep 17 00:00:00 2001
From: Francesco Carmelo Capria <francesco@capria.eu>
Date: Wed, 5 Oct 2022 14:02:33 +0200
Subject: [PATCH] New package: wired-notify-0.10.2
---
srcpkgs/wired-notify/template | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
create mode 100644 srcpkgs/wired-notify/template
diff --git a/srcpkgs/wired-notify/template b/srcpkgs/wired-notify/template
new file mode 100644
index 000000000000..e37a91fad81a
--- /dev/null
+++ b/srcpkgs/wired-notify/template
@@ -0,0 +1,20 @@
+# Template file for 'wired-notify'
+pkgname=wired-notify
+version=0.10.2
+revision=1
+archs="i686 x86_64"
+build_style=cargo
+hostmakedepends="pkg-config"
+makedepends="rust cargo pango-devel libXScrnSaver-devel libglib-devel"
+depends="dbus xorg cairo pango"
+short_desc="Lightweight notification daemon written in Rust"
+maintainer="Francesco Carmelo Capria <francesco@capria.eu>"
+license="MIT"
+homepage="https://github.com/Toqozz/wired-notify"
+#changelog=""
+distfiles="https://github.com/Toqozz/wired-notify/archive/refs/tags/${version}.tar.gz"
+checksum=7e1c522451887af67f76ddc3022ef26be918e01c44cec10c09d39cfa04b9785e
+
+post_install() {
+ vlicense LICENSE
+}
next reply other threads:[~2022-10-05 12:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 12:19 fccapria [this message]
2022-10-05 12:27 ` [PR PATCH] [Closed]: " fccapria
2022-10-05 12:29 [PR PATCH] " fccapria
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-39736@inbox.vuxu.org \
--to=fccapria@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).