From: "David Seifert" <soap@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/libcifpp/
Date: Sun, 4 Sep 2022 12:23:07 +0000 (UTC) [thread overview]
Message-ID: <1662294155.9be8f560449065f89cdd879c203b14e4625e17d9.soap@gentoo> (raw)
commit: 9be8f560449065f89cdd879c203b14e4625e17d9
Author: David Seifert <soap <AT> gentoo <DOT> org>
AuthorDate: Sun Sep 4 12:22:35 2022 +0000
Commit: David Seifert <soap <AT> gentoo <DOT> org>
CommitDate: Sun Sep 4 12:22:35 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9be8f560
sci-libs/libcifpp: remove boost[threads(+)] usedep
Signed-off-by: David Seifert <soap <AT> gentoo.org>
sci-libs/libcifpp/libcifpp-2.0.4-r1.ebuild | 4 ++--
sci-libs/libcifpp/libcifpp-3.0.0.ebuild | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/sci-libs/libcifpp/libcifpp-2.0.4-r1.ebuild b/sci-libs/libcifpp/libcifpp-2.0.4-r1.ebuild
index 3064d4f1e9b0..e01339f95bce 100644
--- a/sci-libs/libcifpp/libcifpp-2.0.4-r1.ebuild
+++ b/sci-libs/libcifpp/libcifpp-2.0.4-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2021 Gentoo Authors
+# Copyright 1999-2022 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
@@ -18,7 +18,7 @@ KEYWORDS="~amd64"
IUSE="test"
RESTRICT="!test? ( test )"
-DEPEND=">=dev-libs/boost-1.70:=[threads(+)]"
+DEPEND=">=dev-libs/boost-1.70:="
RDEPEND="${DEPEND}"
src_configure() {
diff --git a/sci-libs/libcifpp/libcifpp-3.0.0.ebuild b/sci-libs/libcifpp/libcifpp-3.0.0.ebuild
index 78a60b686a26..69f465d5133f 100644
--- a/sci-libs/libcifpp/libcifpp-3.0.0.ebuild
+++ b/sci-libs/libcifpp/libcifpp-3.0.0.ebuild
@@ -17,7 +17,7 @@ KEYWORDS="~amd64 ~x86"
IUSE="test"
RESTRICT="!test? ( test )"
-DEPEND=">=dev-libs/boost-1.70:=[threads(+)]"
+DEPEND=">=dev-libs/boost-1.70:="
RDEPEND="${DEPEND}"
src_configure() {
next reply other threads:[~2022-09-04 12:23 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 12:23 David Seifert [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-05 9:11 [gentoo-commits] repo/gentoo:master commit in: sci-libs/libcifpp/ Pacho Ramos
2025-10-05 9:11 Pacho Ramos
2025-06-25 16:17 Arthur Zamarin
2025-05-22 14:07 Pacho Ramos
2025-05-13 14:32 Pacho Ramos
2025-04-13 16:44 Pacho Ramos
2025-04-13 16:44 Pacho Ramos
2025-01-31 18:35 Pacho Ramos
2025-01-31 18:35 Pacho Ramos
2025-01-13 12:56 Sam James
2024-12-02 13:00 Pacho Ramos
2024-10-17 11:56 Pacho Ramos
2024-10-17 8:51 Pacho Ramos
2024-10-17 8:51 Pacho Ramos
2024-09-15 12:25 Pacho Ramos
2024-05-18 10:06 Pacho Ramos
2024-05-18 10:06 Pacho Ramos
2023-10-20 13:14 Pacho Ramos
2023-08-23 14:49 Pacho Ramos
2023-08-23 14:49 Pacho Ramos
2023-08-08 9:20 Pacho Ramos
2023-08-08 9:20 Pacho Ramos
2023-06-08 12:33 Pacho Ramos
2023-06-08 12:33 Pacho Ramos
2023-06-08 9:39 Pacho Ramos
2023-04-25 13:14 Pacho Ramos
2023-04-18 15:08 Pacho Ramos
2023-02-26 15:51 Pacho Ramos
2022-12-04 14:50 Pacho Ramos
2022-12-04 14:50 Pacho Ramos
2022-09-04 13:03 David Seifert
2022-03-17 13:36 Jakov Smolić
2021-12-16 8:46 Pacho Ramos
2021-11-16 3:14 Sam James
2021-11-06 9:13 Pacho Ramos
2021-11-06 9:13 Pacho Ramos
2021-10-19 21:04 Pacho Ramos
2021-10-10 20:48 Sam James
2021-10-03 18:45 Pacho Ramos
2021-09-26 10:18 Pacho Ramos
2021-09-02 12:01 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=1662294155.9be8f560449065f89cdd879c203b14e4625e17d9.soap@gentoo \
--to=soap@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