From: "Matt Turner" <mattst88@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-libs/libXdamage/
Date: Sun, 4 Dec 2022 23:44:45 +0000 (UTC) [thread overview]
Message-ID: <1670197288.314459525a783a2653d1bedd73ae97e2332e4f49.mattst88@gentoo> (raw)
commit: 314459525a783a2653d1bedd73ae97e2332e4f49
Author: Matt Turner <mattst88 <AT> gentoo <DOT> org>
AuthorDate: Sun Dec 4 23:28:32 2022 +0000
Commit: Matt Turner <mattst88 <AT> gentoo <DOT> org>
CommitDate: Sun Dec 4 23:41:28 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=31445952
x11-libs/libXdamage: Version bump to 1.1.6
Signed-off-by: Matt Turner <mattst88 <AT> gentoo.org>
x11-libs/libXdamage/Manifest | 1 +
x11-libs/libXdamage/libXdamage-1.1.6.ebuild | 16 ++++++++++++++++
2 files changed, 17 insertions(+)
diff --git a/x11-libs/libXdamage/Manifest b/x11-libs/libXdamage/Manifest
index 93ac653df614..62a6a73aef0e 100644
--- a/x11-libs/libXdamage/Manifest
+++ b/x11-libs/libXdamage/Manifest
@@ -1 +1,2 @@
DIST libXdamage-1.1.5.tar.bz2 303750 BLAKE2B 78cb593365cc842cbc6fcb4dec94aa28293c385ad7ecfef032117d19e98c7b3f252c53b79559096b1c0b259d24a59220e9af7fb60d55c55f4474a33d117958de SHA512 a3ca6cc33b1727f717a3e2aa5593f660508a81a47918a0aa949e9e8fba105e303fe5071983b48caac92feea0fe6e8e01620805e4d19b41f21f20d837b191c124
+DIST libXdamage-1.1.6.tar.xz 257532 BLAKE2B 9b9e21c180fa2ddfeb15e97edc1e7665de722f7fdf9997273fead3348df78b8eec610181d7fd2ef41af7305286285ccf57b56fe7859ebd863b9d8bc1321247c8 SHA512 624dcefa1c79064569df952892f7f1351dc19ad338ce73d1a57041e406cb3e18abe531bab352b93d1f0f5c9b5c6b2652cc84a8f1fbfcbba648343812695a8acb
diff --git a/x11-libs/libXdamage/libXdamage-1.1.6.ebuild b/x11-libs/libXdamage/libXdamage-1.1.6.ebuild
new file mode 100644
index 000000000000..215c9bb3ae5e
--- /dev/null
+++ b/x11-libs/libXdamage/libXdamage-1.1.6.ebuild
@@ -0,0 +1,16 @@
+# Copyright 1999-2022 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+XORG_MULTILIB=yes
+XORG_TARBALL_SUFFIX="xz"
+inherit xorg-3
+
+DESCRIPTION="X.Org Xdamage library"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~sparc-solaris ~x64-solaris ~x86-solaris ~x86-winnt"
+
+RDEPEND=">=x11-libs/libX11-1.6.2[${MULTILIB_USEDEP}]"
+DEPEND="${RDEPEND}
+ >=x11-libs/libXfixes-5.0.1[${MULTILIB_USEDEP}]
+ x11-base/xorg-proto"
next reply other threads:[~2022-12-04 23:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 23:44 Matt Turner [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-26 17:47 [gentoo-commits] repo/gentoo:master commit in: x11-libs/libXdamage/ Matt Turner
2023-01-25 19:21 Arthur Zamarin
2023-01-24 18:29 Arthur Zamarin
2023-01-24 18:27 Arthur Zamarin
2023-01-24 1:00 Sam James
2022-05-17 7:56 WANG Xuerui
2019-05-01 20:47 Matt Turner
2019-05-01 18:24 Matt Turner
2019-04-28 20:59 Sergei Trofimovich
2019-04-28 9:35 Mikle Kolyada
2019-04-28 4:21 Matt Turner
2019-04-28 0:48 Matt Turner
2019-04-27 11:52 Mikle Kolyada
2019-04-27 11:47 Mikle Kolyada
2019-04-27 4:29 Aaron Bauman
2019-04-27 3:15 Aaron Bauman
2019-03-11 6:10 Matt Turner
2018-06-30 17:49 Mikle Kolyada
2017-01-29 21:11 Fabian Groffen
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=1670197288.314459525a783a2653d1bedd73ae97e2332e4f49.mattst88@gentoo \
--to=mattst88@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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