From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/rr/
Date: Mon, 13 Feb 2017 21:19:22 +0000 (UTC) [thread overview]
Message-ID: <1487020753.cdf5b5392ca1f171e9a422b8206984f3b348a282.vapier@gentoo> (raw)
commit: cdf5b5392ca1f171e9a422b8206984f3b348a282
Author: Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Mon Feb 13 21:09:39 2017 +0000
Commit: Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Mon Feb 13 21:19:13 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cdf5b539
dev-util/rr: clean up build/test deps
We only need zlib & gdb at runtime. All the other deps in here
are for building & testing only, so drop them from RDEPEND.
dev-util/rr/rr-4.5.0.ebuild | 29 ++++++++++++++++++++---------
1 file changed, 20 insertions(+), 9 deletions(-)
diff --git a/dev-util/rr/rr-4.5.0.ebuild b/dev-util/rr/rr-4.5.0.ebuild
index 6624a53814..b83875db0e 100644
--- a/dev-util/rr/rr-4.5.0.ebuild
+++ b/dev-util/rr/rr-4.5.0.ebuild
@@ -16,15 +16,18 @@ SRC_URI="https://github.com/mozilla/${PN}/archive/${PV}.tar.gz -> mozilla-${P}.t
LICENSE="MIT BSD-2"
SLOT="0"
KEYWORDS="~amd64 ~x86"
-IUSE=""
-
-DEPEND="dev-python/pexpect[${PYTHON_USEDEP}]
- sys-libs/zlib
- ${PYTHON_DEPS}"
-
-RDEPEND="
- sys-devel/gdb[xml]
- ${DEPEND}"
+IUSE="test"
+
+DEPEND="sys-libs/zlib"
+RDEPEND="${DEPEND}
+ sys-devel/gdb[xml]"
+# Add all the deps needed only at build/test time.
+DEPEND+="
+ test? (
+ dev-python/pexpect[${PYTHON_USEDEP}]
+ sys-devel/gdb[xml]
+ )
+ ${PYTHON_DEPS}"
pkg_setup() {
if use kernel_linux; then
@@ -39,3 +42,11 @@ src_prepare() {
sed -i 's:-Werror::' CMakeLists.txt || die #609192
}
+
+src_configure() {
+ local mycmakeargs=(
+ -DBUILD_TESTS=$(usex test)
+ )
+
+ cmake-utils_src_configure
+}
next reply other threads:[~2017-02-13 21:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 21:19 Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-13 13:27 [gentoo-commits] repo/gentoo:master commit in: dev-util/rr/ Sam James
2025-01-25 5:37 Sam James
2025-01-24 15:45 Sam James
2024-10-03 10:05 Sam James
2024-10-03 10:00 Sam James
2024-05-25 7:35 Sam James
2024-04-29 21:48 Sam James
2023-10-03 23:38 Sam James
2023-04-25 19:49 Sam James
2023-01-10 4:32 Sam James
2023-01-10 4:32 Sam James
2022-10-17 21:45 Sam James
2022-10-17 21:45 Sam James
2022-08-20 13:29 Luca Barbato
2022-08-14 8:04 Luca Barbato
2021-09-27 8:55 Luca Barbato
2021-05-15 13:58 Sergei Trofimovich
2021-02-01 16:32 Sam James
2020-11-10 23:49 Sergei Trofimovich
2020-11-02 10:21 Sergei Trofimovich
2020-10-30 23:19 Sergei Trofimovich
2020-10-01 21:49 Sergei Trofimovich
2020-10-01 21:49 Sergei Trofimovich
2020-03-23 23:58 Sergei Trofimovich
2020-02-09 16:25 Michał Górny
2019-12-19 22:25 Sergei Trofimovich
2019-11-12 22:52 Sergei Trofimovich
2019-11-12 22:45 Sergei Trofimovich
2019-11-10 21:00 Sergei Trofimovich
2019-05-09 22:37 Sergei Trofimovich
2019-05-09 22:26 Sergei Trofimovich
2018-09-28 14:46 Luca Barbato
2018-06-10 16:29 Sergei Trofimovich
2018-03-12 16:50 Ettore Di Giacinto
2017-10-24 11:29 Luca Barbato
2017-04-20 20:48 David Seifert
2017-02-13 21:51 Mike Frysinger
2017-02-13 21:19 Mike Frysinger
2017-02-13 21:19 Mike Frysinger
2017-02-12 18:39 Ettore Di Giacinto
2017-02-12 18:15 Luca Barbato
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=1487020753.cdf5b5392ca1f171e9a422b8206984f3b348a282.vapier@gentoo \
--to=vapier@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