From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/libcifpp/
Date: Tue, 16 Nov 2021 03:14:20 +0000 (UTC) [thread overview]
Message-ID: <1637032450.7bb5230e3762a0fb07d7af810349052860a36903.sam@gentoo> (raw)
commit: 7bb5230e3762a0fb07d7af810349052860a36903
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Nov 16 03:13:34 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Nov 16 03:14:10 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7bb5230e
sci-libs/libcifpp: fix Boost dependency
We use Boost headers (=> DEPEND) and link against it (=> RDEPEND).
Signed-off-by: Sam James <sam <AT> gentoo.org>
.../libcifpp/{libcifpp-2.0.4.ebuild => libcifpp-2.0.4-r1.ebuild} | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/sci-libs/libcifpp/libcifpp-2.0.4.ebuild b/sci-libs/libcifpp/libcifpp-2.0.4-r1.ebuild
similarity index 90%
rename from sci-libs/libcifpp/libcifpp-2.0.4.ebuild
rename to sci-libs/libcifpp/libcifpp-2.0.4-r1.ebuild
index 1cbb3962edf8..3064d4f1e9b0 100644
--- a/sci-libs/libcifpp/libcifpp-2.0.4.ebuild
+++ b/sci-libs/libcifpp/libcifpp-2.0.4-r1.ebuild
@@ -2,6 +2,7 @@
# Distributed under the terms of the GNU General Public License v2
EAPI=8
+
inherit cmake
DESCRIPTION="Code to work with mmCIF and PDB files"
@@ -14,15 +15,11 @@ SRC_URI="
LICENSE="BSD-2"
SLOT="0"
KEYWORDS="~amd64"
-
IUSE="test"
RESTRICT="!test? ( test )"
-BDEPEND="
- >=dev-libs/boost-1.70.0:0=[threads(+)]
-"
-DEPEND=""
-RDEPEND=""
+DEPEND=">=dev-libs/boost-1.70:=[threads(+)]"
+RDEPEND="${DEPEND}"
src_configure() {
cp "${WORKDIR}"/components-${PV}.cif data/components.cif || die
next reply other threads:[~2021-11-16 3:14 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 3:14 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-13 16:44 [gentoo-commits] repo/gentoo:master commit in: sci-libs/libcifpp/ 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-09-04 12:23 David Seifert
2022-03-17 13:36 Jakov Smolić
2021-12-16 8:46 Pacho Ramos
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=1637032450.7bb5230e3762a0fb07d7af810349052860a36903.sam@gentoo \
--to=sam@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