From: harrisonthorne <harrisonthorne@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] i3lock-color: update to version 2.12.c.5
Date: Sat, 08 Aug 2020 02:12:13 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24133@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
There is a new pull request by harrisonthorne against master on the void-packages repository
https://github.com/harrisonthorne/void-packages update-i3lock-color
https://github.com/void-linux/void-packages/pull/24133
i3lock-color: update to version 2.12.c.5
Updates `i3lock-color` to allow for 4-byte rgba colors and more features.
The maintainer of i3lock-color has also been changed to Raymo111, so the appropriate change has been reflected in the revised template file.
(Disclaimer: I'm still a little new to xbps templates, gently let me know if I did something wrong :))
A patch file from https://github.com/void-linux/void-packages/pull/24133.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-i3lock-color-24133.patch --]
[-- Type: text/x-diff, Size: 1523 bytes --]
From 59f19ca3112f4e0a6f94d035e63776ea7f7b72de Mon Sep 17 00:00:00 2001
From: Harrison Thorne <harrison.thorne@gmail.com>
Date: Tue, 4 Aug 2020 21:37:12 -0600
Subject: [PATCH] i3lock-color: update to version 2.12.c.5
---
srcpkgs/i3lock-color/template | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/srcpkgs/i3lock-color/template b/srcpkgs/i3lock-color/template
index 07bd585c69d..7f5572f99d6 100644
--- a/srcpkgs/i3lock-color/template
+++ b/srcpkgs/i3lock-color/template
@@ -1,8 +1,7 @@
# Template file for 'i3lock-color'
pkgname=i3lock-color
-version=2.12
-revision=2
-wrksrc="${pkgname}-${version}.c"
+version=2.12.c.5
+revision=1
build_style=gnu-configure
hostmakedepends="pkg-config automake"
makedepends="libev-devel cairo-devel pam-devel libxkbcommon-devel xcb-util-devel
@@ -10,9 +9,9 @@ makedepends="libev-devel cairo-devel pam-devel libxkbcommon-devel xcb-util-devel
short_desc="Screenlocker forked from i3lock with more features"
maintainer="jtalowell <jtalowell@protonmail.com>"
license="MIT"
-homepage="https://github.com/PandorasFox/i3lock-color"
-distfiles="https://github.com/PandorasFox/i3lock-color/archive/${version}.c.tar.gz"
-checksum=c2ba4cfa51fee3fd2cab439805d213d8614407d93cf8eecbd4e6fa5cb4c9b7a3
+homepage="https://github.com/Raymo111/i3lock-color"
+distfiles="https://github.com/Raymo111/i3lock-color/archive/${version}.tar.gz"
+checksum=62c9bdff2759186426b184ed45e4c1aae1dc3c582499d94da68d9b08662a96a9
conf_files="/etc/pam.d/i3lock"
conflicts="i3lock"
next reply other threads:[~2020-08-08 0:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 0:12 harrisonthorne [this message]
2020-08-08 9:48 ` PaperMountainStudio
2020-08-08 16:42 ` [PR PATCH] [Updated] " harrisonthorne
2020-08-08 16:43 ` harrisonthorne
2020-08-10 15:47 ` [PR PATCH] [Closed]: i3lock-color: update to 2.12.c.5 ahesford
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-24133@inbox.vuxu.org \
--to=harrisonthorne@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).