From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pyinotify/
Date: Fri, 15 Jul 2022 13:45:08 +0000 (UTC) [thread overview]
Message-ID: <1657892697.12f1e77dbf7e281fc3e28c86b4b8bcfd80113295.arthurzam@gentoo> (raw)
commit: 12f1e77dbf7e281fc3e28c86b4b8bcfd80113295
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 15 12:30:07 2022 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Fri Jul 15 13:44:57 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=12f1e77d
dev-python/pyinotify: EAPI=8, PEP517
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
dev-python/pyinotify/pyinotify-0.9.6-r1.ebuild | 30 ++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/dev-python/pyinotify/pyinotify-0.9.6-r1.ebuild b/dev-python/pyinotify/pyinotify-0.9.6-r1.ebuild
new file mode 100644
index 000000000000..c91436e1f04b
--- /dev/null
+++ b/dev-python/pyinotify/pyinotify-0.9.6-r1.ebuild
@@ -0,0 +1,30 @@
+# Copyright 1999-2022 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+DISTUTILS_USE_PEP517=setuptools
+PYTHON_COMPAT=( python3_{7..10} pypy3 )
+PYTHON_REQ_USE="threads(+)"
+
+inherit distutils-r1
+
+DESCRIPTION="Python module used for monitoring filesystems events"
+HOMEPAGE="
+ https://pypi.org/project/pyinotify/
+ https://github.com/seb-m/pyinotify/"
+SRC_URI="https://seb.dbzteam.org/pub/pyinotify/releases/${P}.tar.gz"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux"
+IUSE="examples"
+
+python_install_all() {
+ if use examples; then
+ dodoc -r python3/examples
+ docompress -x /usr/share/doc/${PF}/examples
+ fi
+
+ distutils-r1_python_install_all
+}
next reply other threads:[~2022-07-15 13:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 13:45 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-11 19:23 [gentoo-commits] repo/gentoo:master commit in: dev-python/pyinotify/ Michał Górny
2023-09-26 15:59 WANG Xuerui
2023-06-22 14:36 Michał Górny
2022-08-17 19:40 Arthur Zamarin
2022-08-17 18:43 Arthur Zamarin
2022-07-15 13:45 Arthur Zamarin
2022-07-15 13:45 Arthur Zamarin
2021-07-16 10:56 Louis Sautier
2020-12-11 12:48 Michał Górny
2020-08-22 9:15 Michał Górny
2020-06-08 20:18 Michał Górny
2020-03-20 9:58 David Seifert
2019-05-05 20:04 Mikle Kolyada
2019-01-28 0:25 Matthew Thode
2018-06-09 19:42 Mikle Kolyada
2018-04-20 9:23 Mart Raudsepp
2018-01-20 18:04 Tobias Klausmann
2018-01-10 6:19 Markus Meier
2018-01-05 23:19 Michał Górny
2017-12-29 17:41 Sergei Trofimovich
2017-12-25 11:42 Markus Meier
2017-11-26 20:47 Sergei Trofimovich
2017-11-24 20:26 Sergei Trofimovich
2017-11-23 23:52 Matt Turner
2017-11-23 23:06 Sergei Trofimovich
2017-11-20 22:03 Sergei Trofimovich
2017-11-20 10:16 Jeroen Roovers
2017-11-10 17:00 Matt Turner
2017-11-10 10:16 Sergei Trofimovich
2017-11-07 22:44 Sergei Trofimovich
2017-06-23 5:20 Alexis Ballier
2017-05-19 21:44 Michael Weber
2017-05-04 16:40 Manuel Rüger
2016-01-25 8:31 Justin Lecher
2015-11-11 17:27 Justin Lecher
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=1657892697.12f1e77dbf7e281fc3e28c86b4b8bcfd80113295.arthurzam@gentoo \
--to=arthurzam@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