From: 4ricci <4ricci@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] grim: update to 1.4.0.
Date: Wed, 20 Apr 2022 20:18:23 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36782@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
There is a new pull request by 4ricci against master on the void-packages repository
https://github.com/4ricci/void-packages grim
https://github.com/void-linux/void-packages/pull/36782
grim: update to 1.4.0.
<!-- 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 [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- 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, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/36782.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-grim-36782.patch --]
[-- Type: text/x-diff, Size: 1470 bytes --]
From 76673ab163160e56df792b420a5b4659b97e1d6e Mon Sep 17 00:00:00 2001
From: Roberto Ricci <ricci@disroot.org>
Date: Wed, 20 Apr 2022 20:15:38 +0200
Subject: [PATCH] grim: update to 1.4.0.
---
srcpkgs/grim/template | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/grim/template b/srcpkgs/grim/template
index 89af643b6a7f..f42ed188f1f4 100644
--- a/srcpkgs/grim/template
+++ b/srcpkgs/grim/template
@@ -1,18 +1,22 @@
# Template file for 'grim'
pkgname=grim
-version=1.3.2
+version=1.4.0
revision=1
+wrksrc="grim-v${version}"
build_style=meson
configure_args="-Djpeg=enabled -Dwerror=false"
hostmakedepends="pkg-config wayland-devel scdoc"
-makedepends="wayland-devel wayland-protocols cairo-devel libjpeg-turbo-devel"
+makedepends="wayland-devel wayland-protocols pixman-devel libjpeg-turbo-devel
+ libpng-devel"
short_desc="Grab images from a Wayland compositor"
maintainer="Derriick <derriick.ensiie@yahoo.com>"
license="MIT"
homepage="https://wayland.emersion.fr/grim/"
-distfiles="https://github.com/emersion/grim/archive/v${version}.tar.gz"
-checksum=42c2952e98389506156c08e40e0c37afdc2ec5ef4d55a5a4febde6acdac4d1c8
+distfiles="https://git.sr.ht/~emersion/grim/archive/v${version}.tar.gz"
+checksum=66729ae654546404f50ed163055310dd23ed52cc5a881d39752c0cd076e3d7aa
post_install() {
vlicense LICENSE
+ vcompletion contrib/completions/bash/grim.bash bash
+ vcompletion contrib/completions/fish/grim.fish fish
}
next reply other threads:[~2022-04-20 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 18:18 4ricci [this message]
2022-04-21 21:58 ` [PR PATCH] [Merged]: " Piraty
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-36782@inbox.vuxu.org \
--to=4ricci@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).