From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-text/xiphos/
Date: Fri, 1 May 2020 10:02:34 +0000 (UTC) [thread overview]
Message-ID: <1588327345.3c4a83102994ee8b691dd8070729f8a4126f9d5c.leio@gentoo> (raw)
commit: 3c4a83102994ee8b691dd8070729f8a4126f9d5c
Author: Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Fri May 1 10:02:25 2020 +0000
Commit: Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Fri May 1 10:02:25 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3c4a8310
app-text/xiphos: drop python req on libxslt and gnome-doc-utils
gnome-doc-utils had its python2 revision dropped, breaking the tree for
xiphos. Instead of removing it, dropping the PYTHON_MULTI_USEDEP requirement
here, as xiphos appears to only call xml2po and xsltproc utilities, not
import any of the gnome-doc-utils or libxslt python API.
Also PYTHON_MULTI_USEDEP doesn't make sense for a BDEPEND.
Package-Manager: Portage-2.3.84, Repoman-2.3.20
Signed-off-by: Mart Raudsepp <leio <AT> gentoo.org>
app-text/xiphos/xiphos-4.0.6a-r2.ebuild | 6 ++----
app-text/xiphos/xiphos-4.1.0-r2.ebuild | 6 ++----
2 files changed, 4 insertions(+), 8 deletions(-)
diff --git a/app-text/xiphos/xiphos-4.0.6a-r2.ebuild b/app-text/xiphos/xiphos-4.0.6a-r2.ebuild
index 4ca64d0c5aa..dd5177d45fa 100644
--- a/app-text/xiphos/xiphos-4.0.6a-r2.ebuild
+++ b/app-text/xiphos/xiphos-4.0.6a-r2.ebuild
@@ -39,10 +39,8 @@ DEPEND="${RDEPEND}
>=net-libs/biblesync-1.1.2-r1[-static]
virtual/pkgconfig
sys-devel/gettext
- $(python_gen_cond_dep '
- app-text/gnome-doc-utils[${PYTHON_MULTI_USEDEP}]
- dev-libs/libxslt[${PYTHON_MULTI_USEDEP}]
- ')
+ app-text/gnome-doc-utils
+ dev-libs/libxslt
"
pkg_setup() {
diff --git a/app-text/xiphos/xiphos-4.1.0-r2.ebuild b/app-text/xiphos/xiphos-4.1.0-r2.ebuild
index 159e9351269..24314a606c4 100644
--- a/app-text/xiphos/xiphos-4.1.0-r2.ebuild
+++ b/app-text/xiphos/xiphos-4.1.0-r2.ebuild
@@ -37,10 +37,8 @@ DEPEND="${RDEPEND}
>=net-libs/biblesync-1.1.2-r1[-static]
virtual/pkgconfig
sys-devel/gettext
- $(python_gen_cond_dep '
- app-text/gnome-doc-utils[${PYTHON_MULTI_USEDEP}]
- dev-libs/libxslt[${PYTHON_MULTI_USEDEP}]
- ')
+ app-text/gnome-doc-utils
+ dev-libs/libxslt
"
pkg_setup() {
next reply other threads:[~2020-05-01 10:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 10:02 Mart Raudsepp [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-15 9:29 [gentoo-commits] repo/gentoo:master commit in: app-text/xiphos/ Ulrich Müller
2023-05-19 8:52 Marek Szuba
2023-05-19 8:52 Marek Szuba
2023-02-24 16:50 Marek Szuba
2022-06-30 9:02 Marek Szuba
2022-06-30 7:01 Agostino Sarubbo
2022-05-29 22:07 Marek Szuba
2022-04-12 21:04 Sam James
2020-09-18 10:36 Marek Szuba
2020-07-27 18:37 Marek Szuba
2020-07-27 14:43 Marek Szuba
2020-06-27 20:45 Andreas K. Hüttel
2019-02-28 2:06 Chris Reffett
2018-08-21 5:26 Mart Raudsepp
2018-06-20 1:21 Chris Reffett
2017-12-30 2:26 Chris Reffett
2017-12-29 18:40 Mikle Kolyada
2017-08-21 0:55 Chris Reffett
2017-01-10 23:14 Chris Reffett
2017-01-10 14:56 Agostino Sarubbo
2016-05-25 23:47 Chris Reffett
2016-05-24 23:44 Chris Reffett
2016-01-03 15:06 Chris Reffett
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=1588327345.3c4a83102994ee8b691dd8070729f8a4126f9d5c.leio@gentoo \
--to=leio@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