From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] picom: update to 11.2.
Date: Tue, 13 Feb 2024 12:21:01 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48691@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
There is a new pull request by 0x5c against master on the void-packages repository
https://github.com/0x5c/void-packages update/picom
https://github.com/void-linux/void-packages/pull/48691
picom: update to 11.2.
<!-- 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 [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-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/48691.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update/picom-48691.patch --]
[-- Type: text/x-diff, Size: 1436 bytes --]
From 9384040c13d69a6ba63f6d734e6d635356b42120 Mon Sep 17 00:00:00 2001
From: 0x5c <dev@0x5c.io>
Date: Tue, 13 Feb 2024 06:19:43 -0500
Subject: [PATCH] picom: update to 11.2.
---
srcpkgs/picom/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/picom/template b/srcpkgs/picom/template
index 040845f6f7679..58e70dce62342 100644
--- a/srcpkgs/picom/template
+++ b/srcpkgs/picom/template
@@ -1,12 +1,12 @@
# Template file for 'picom'
pkgname=picom
-version=11.1
+version=11.2
revision=1
build_style=meson
configure_args="-Dwith_docs=true"
hostmakedepends="pkg-config asciidoc"
-makedepends="MesaLib-devel dbus-devel libconfig-devel libev-devel pcre2-devel
- pixman-devel xcb-util-image-devel xcb-util-renderutil-devel
+makedepends="MesaLib-devel dbus-devel libconfig-devel libepoxy-devel libev-devel
+ pcre2-devel pixman-devel xcb-util-image-devel xcb-util-renderutil-devel
libxdg-basedir-devel uthash"
depends="desktop-file-utils"
short_desc="Lightweight compositor for X11 (previously a compton fork)"
@@ -14,7 +14,7 @@ maintainer="0x5c <dev@0x5c.io>"
license="MIT, MPL-2.0"
homepage="https://github.com/yshui/picom/"
distfiles="https://github.com/yshui/picom/archive/v${version}.tar.gz"
-checksum=96f2a33a93064a74b557942d0300a2ac77ac853f50efbbf6466849fcc7542ec8
+checksum=1c1063936faf09ed9bba726e7737a562564b7a5f8cdef79d48fcdaf3669a4df4
post_install() {
vlicense LICENSES/MIT
next reply other threads:[~2024-02-13 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 11:21 0x5c [this message]
2024-02-14 3:22 ` [PR PATCH] [Merged]: " cinerea0
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-48691@inbox.vuxu.org \
--to=0x5c@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).