From: bitterhalt <bitterhalt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: i3bar-river-1.0.1
Date: Wed, 20 Nov 2024 14:31:11 +0100 [thread overview]
Message-ID: <20241120133111.9FF8F2F83C@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52750@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
There is an updated pull request by bitterhalt against master on the void-packages repository
https://github.com/bitterhalt/void-packages i3bar-river
https://github.com/void-linux/void-packages/pull/52750
New package: i3bar-river-1.0.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**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64 glibc)
A patch file from https://github.com/void-linux/void-packages/pull/52750.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-i3bar-river-52750.patch --]
[-- Type: text/x-diff, Size: 1126 bytes --]
From 9b03d19cb844936fdbadbdf6ffa89aaecc86f4e4 Mon Sep 17 00:00:00 2001
From: bitterhalt <bitterhalt@disroot.org>
Date: Mon, 21 Oct 2024 18:24:14 +0300
Subject: [PATCH] New package: i3bar-river-1.1.0
---
srcpkgs/i3bar-river/template | 14 ++++++++++++++
1 file changed, 14 insertions(+)
create mode 100644 srcpkgs/i3bar-river/template
diff --git a/srcpkgs/i3bar-river/template b/srcpkgs/i3bar-river/template
new file mode 100644
index 00000000000000..6b7506b5e9ec2d
--- /dev/null
+++ b/srcpkgs/i3bar-river/template
@@ -0,0 +1,14 @@
+# Template file for 'i3bar-river'
+pkgname=i3bar-river
+version=1.1.0
+revision=1
+build_style=cargo
+hostmakedepends="pkg-config"
+makedepends="cairo-devel pango-devel"
+short_desc="Port of i3bar for wlroots-based compositors"
+maintainer="bitterhalt <bthalt@disroot.org>"
+license="GPL-3.0-or-later"
+homepage="https://github.com/MaxVerevkin/i3bar-river"
+changelog="https://github.com/MaxVerevkin/i3bar-river/releases"
+distfiles="https://github.com/MaxVerevkin/i3bar-river/archive/refs/tags/v${version}.tar.gz"
+checksum=3e616979c7baf0130b4ace7bcd53ddcdbc65bf239fb5a669860f16620f36bfa5
next prev parent reply other threads:[~2024-11-20 13:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 12:00 [PR PATCH] " bitterhalt
2024-10-23 12:14 ` [PR PATCH] [Updated] " bitterhalt
2024-10-23 12:17 ` bitterhalt
2024-10-23 12:17 ` bitterhalt
2024-10-23 17:03 ` [PR REVIEW] " tranzystorekk
2024-10-23 17:11 ` [PR PATCH] [Updated] " bitterhalt
2024-10-23 17:20 ` tranzystorekk
2024-10-23 17:23 ` bitterhalt
2024-10-23 17:32 ` [PR PATCH] [Updated] " bitterhalt
2024-10-23 17:36 ` bitterhalt
2024-10-23 17:38 ` tranzystorekk
2024-10-23 17:55 ` [PR PATCH] [Updated] " bitterhalt
2024-10-30 21:04 ` bitterhalt
2024-10-30 21:15 ` bitterhalt
2024-11-20 13:29 ` bitterhalt
2024-11-20 13:31 ` bitterhalt [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-17 14:22 [PR PATCH] " bitterhalt
2024-10-17 15:01 ` [PR PATCH] [Updated] " bitterhalt
2024-10-17 15:05 ` bitterhalt
2024-10-21 14:58 ` bitterhalt
2024-10-21 15:00 ` bitterhalt
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=20241120133111.9FF8F2F83C@inbox.vuxu.org \
--to=bitterhalt@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).