From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Waybar: update to 0.9.3.
Date: Thu, 06 Aug 2020 19:03:28 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24108@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 330 bytes --]
There is a new pull request by ericonr against master on the void-packages repository
https://github.com/ericonr/void-packages waybar
https://github.com/void-linux/void-packages/pull/24108
Waybar: update to 0.9.3.
Tested on x86_64-musl.
A patch file from https://github.com/void-linux/void-packages/pull/24108.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-waybar-24108.patch --]
[-- Type: text/x-diff, Size: 2041 bytes --]
From 92f9090f2310a3778a4cdbda41a8b9e294d192e7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=89rico=20Rolim?= <erico.erc@gmail.com>
Date: Thu, 6 Aug 2020 14:02:37 -0300
Subject: [PATCH] Waybar: update to 0.9.3.
---
srcpkgs/Waybar/template | 15 ++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/srcpkgs/Waybar/template b/srcpkgs/Waybar/template
index 9b4c085ef1c..39087b4d5c8 100644
--- a/srcpkgs/Waybar/template
+++ b/srcpkgs/Waybar/template
@@ -1,7 +1,8 @@
# Template file for 'Waybar'
pkgname=Waybar
-version=0.9.2
+version=0.9.3
revision=1
+_date_version=3.0.0
create_wrksrc=yes
build_wrksrc=${pkgname}-${version}
build_style=meson
@@ -26,11 +27,11 @@ homepage="https://github.com/Alexays/Waybar"
changelog="https://github.com/Alexays/Waybar/releases"
# date library URLs and checksums taken from subprojects/date.wrap
distfiles="https://github.com/Alexays/Waybar/archive/${version}.tar.gz
- https://github.com/HowardHinnant/date/archive/v2.4.1.tar.gz
- https://github.com/mesonbuild/hinnant-date/releases/download/2.4.1-1/hinnant-date.zip"
-checksum="9740662de19dd6126c23efb69c9dc7f9d918443543af12aee770de39d415bdf8
- 98907d243397483bd7ad889bf6c66746db0d7d2a39cc9aacc041834c40b65b98
- 2061673a6f8e6d63c3a40df4da58fa2b3de2835fd9b3e74649e8279599f3a8f6"
+ https://github.com/HowardHinnant/date/archive/v${_date_version}.tar.gz
+ https://github.com/mesonbuild/hinnant-date/releases/download/${_date_version}-1/hinnant-date.zip"
+checksum="15cadd05c6a366fd99a92b0f149974c697902c4683c50e2af69f3e59571793e5
+ 87bba2eaf0ebc7ec539e5e62fc317cb80671a337c1fb1b84cb9e4d42c6dbebe3
+ 6ccaf70732d8bdbd1b6d5fdf3e1b935c23bf269bda12fdfd0e561276f63432fe"
build_options="libnl pulseaudio dbusmenugtk mpd"
build_options_default="libnl pulseaudio dbusmenugtk mpd"
@@ -40,7 +41,7 @@ desc_option_dbusmenugtk="Enable support for tray"
desc_option_mpd="Enable support for MPD"
post_extract() {
- mv date-2.4.1 ${build_wrksrc}/subprojects/
+ mv date-${_date_version} ${build_wrksrc}/subprojects/
}
post_install() {
next reply other threads:[~2020-08-06 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 17:03 ericonr [this message]
2020-08-08 21:18 ` [PR PATCH] [Merged]: " jnbr
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-24108@inbox.vuxu.org \
--to=ericonr@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).