From: "Matt Turner" <mattst88@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/meld/
Date: Sun, 18 Apr 2021 15:19:56 +0000 (UTC) [thread overview]
Message-ID: <1618759174.13bde601e38ff110f6ddbb88cb1f7550b5e0bfbb.mattst88@gentoo> (raw)
commit: 13bde601e38ff110f6ddbb88cb1f7550b5e0bfbb
Author: Matt Turner <mattst88 <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 18 15:19:23 2021 +0000
Commit: Matt Turner <mattst88 <AT> gentoo <DOT> org>
CommitDate: Sun Apr 18 15:19:34 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=13bde601
dev-util/meld: BDEPEND on dev-python/distro
Closes: https://bugs.gentoo.org/771690
Signed-off-by: Matt Turner <mattst88 <AT> gentoo.org>
dev-util/meld/meld-3.20.3.ebuild | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/dev-util/meld/meld-3.20.3.ebuild b/dev-util/meld/meld-3.20.3.ebuild
index 93c774cbc35..a7542f75829 100644
--- a/dev-util/meld/meld-3.20.3.ebuild
+++ b/dev-util/meld/meld-3.20.3.ebuild
@@ -33,11 +33,16 @@ BDEPEND="
dev-util/intltool
dev-util/itstool
sys-devel/gettext
+ $(python_gen_cond_dep 'dev-python/distro[${PYTHON_USEDEP}]')
"
# dev-python/distro is soft-required in BDEPEND for python3.8 and onwards,
# but it's mainly needed for debian and derivatives - seems the fallback
# works fine, as we aren't a special_case, just an annoying warning.
+python_check_deps() {
+ has_version -b "dev-python/distro[${PYTHON_USEDEP}]"
+}
+
python_compile_all() {
mydistutilsargs=( --no-update-icon-cache --no-compile-schemas )
}
next reply other threads:[~2021-04-18 15:20 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 15:19 Matt Turner [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-15 6:48 [gentoo-commits] repo/gentoo:master commit in: dev-util/meld/ Sam James
2024-10-03 10:00 Sam James
2024-03-24 20:46 Mart Raudsepp
2024-03-03 18:10 Mart Raudsepp
2023-10-03 21:32 Mart Raudsepp
2022-12-04 17:15 Matt Turner
2022-10-13 16:26 Matt Turner
2022-10-01 19:20 Sebastian Pipping
2022-10-01 18:56 Matt Turner
2022-09-13 20:11 Matt Turner
2022-09-07 7:52 Michał Górny
2021-11-06 4:09 Sam James
2021-10-04 1:25 Sam James
2021-08-13 16:27 Mart Raudsepp
2021-08-13 16:27 Mart Raudsepp
2021-08-13 16:27 Mart Raudsepp
2021-02-15 2:19 Rick Farina
2021-02-14 21:42 Mart Raudsepp
2020-04-22 16:36 Mart Raudsepp
2020-04-20 20:30 Mart Raudsepp
2020-02-18 12:15 Mart Raudsepp
2019-05-18 19:59 Mart Raudsepp
2019-03-30 22:33 Mart Raudsepp
2019-03-30 21:56 Mart Raudsepp
2019-01-06 12:45 Mart Raudsepp
2018-11-17 15:32 Sebastian Pipping
2018-07-09 19:16 Mart Raudsepp
2018-07-09 16:14 Mikle Kolyada
2018-07-06 13:43 Thomas Deutschmann
2018-06-19 14:30 Mart Raudsepp
2018-01-18 8:13 Gilles Dartiguelongue
2017-12-20 20:23 Mart Raudsepp
2017-11-01 17:48 Mart Raudsepp
2017-11-01 17:48 Mart Raudsepp
2017-09-03 22:47 Gilles Dartiguelongue
2017-02-15 19:43 Mart Raudsepp
2017-01-04 22:37 Gilles Dartiguelongue
2016-10-01 20:02 Mart Raudsepp
2016-10-01 20:02 Mart Raudsepp
2016-07-30 10:50 Pacho Ramos
2016-07-30 10:50 Pacho Ramos
2016-07-02 10:43 Pacho Ramos
2016-05-28 15:49 Pacho Ramos
2016-03-25 12:07 Dennis Lamm
2016-03-06 16:43 Mikle Kolyada
2015-12-12 14:29 Pacho Ramos
2015-12-12 14:29 Pacho Ramos
2015-10-04 10:42 Pacho Ramos
2015-10-04 10:42 Pacho Ramos
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=1618759174.13bde601e38ff110f6ddbb88cb1f7550b5e0bfbb.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