From: "Mike Gilbert" <floppym@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/ceres-solver/
Date: Sat, 29 Oct 2016 23:15:02 +0000 (UTC) [thread overview]
Message-ID: <1477782898.568207e87bf3984958b885af081f4c59bf5bfa3e.floppym@gentoo> (raw)
commit: 568207e87bf3984958b885af081f4c59bf5bfa3e
Author: Mike Gilbert <floppym <AT> gentoo <DOT> org>
AuthorDate: Sat Oct 29 23:12:26 2016 +0000
Commit: Mike Gilbert <floppym <AT> gentoo <DOT> org>
CommitDate: Sat Oct 29 23:14:58 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=568207e8
sci-libs/ceres-solver: fix REQUIRED_USE
Package-Manager: portage-2.3.2
sci-libs/ceres-solver/ceres-solver-1.11.0.ebuild | 2 +-
sci-libs/ceres-solver/ceres-solver-1.9.0.ebuild | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/sci-libs/ceres-solver/ceres-solver-1.11.0.ebuild b/sci-libs/ceres-solver/ceres-solver-1.11.0.ebuild
index 3be25f7..f027bf4 100644
--- a/sci-libs/ceres-solver/ceres-solver-1.11.0.ebuild
+++ b/sci-libs/ceres-solver/ceres-solver-1.11.0.ebuild
@@ -17,7 +17,7 @@ SLOT="0/1"
KEYWORDS="~amd64 ~x86 ~amd64-linux ~x86-linux"
IUSE="cxsparse c++11 doc examples gflags lapack openmp +schur sparse test"
-REQUIRED_USE="test? ( gflags ) sparse? ( lapack ) doc? ( ${PYTHON_REQUIRED_USE} )"
+REQUIRED_USE="test? ( gflags ) sparse? ( lapack )"
RDEPEND="
dev-cpp/glog[gflags?]
diff --git a/sci-libs/ceres-solver/ceres-solver-1.9.0.ebuild b/sci-libs/ceres-solver/ceres-solver-1.9.0.ebuild
index 80e0ea0..d69cbab 100644
--- a/sci-libs/ceres-solver/ceres-solver-1.9.0.ebuild
+++ b/sci-libs/ceres-solver/ceres-solver-1.9.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2014 Gentoo Foundation
+# Copyright 1999-2016 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Id$
@@ -17,7 +17,7 @@ SLOT="0/1"
KEYWORDS="~amd64 ~x86 ~amd64-linux ~x86-linux"
IUSE="cxsparse doc examples gflags lapack openmp protobuf +schur sparse static-libs test"
-REQUIRED_USE="test? ( gflags ) sparse? ( lapack ) doc? ( ${PYTHON_REQUIRED_USE} )"
+REQUIRED_USE="test? ( gflags ) sparse? ( lapack )"
RDEPEND="
dev-cpp/glog[gflags?]
next reply other threads:[~2016-10-29 23:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 23:15 Mike Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-29 11:47 [gentoo-commits] repo/gentoo:master commit in: sci-libs/ceres-solver/ Sam James
2024-03-18 15:26 Andrew Ammerlaan
2024-03-10 15:51 Andrew Ammerlaan
2023-08-16 20:17 Michael Orlitzky
2023-02-23 13:41 Andrew Ammerlaan
2022-12-19 14:47 Andreas Sturmlechner
2022-09-26 15:05 Jakov Smolić
2022-08-19 8:14 Andreas Sturmlechner
2022-05-14 21:30 David Seifert
2022-05-05 0:11 Sam James
2021-11-03 20:38 Jakov Smolić
2021-06-05 13:03 Andrew Ammerlaan
2021-06-05 13:03 Andrew Ammerlaan
2020-05-01 20:32 Andreas Sturmlechner
2020-04-20 10:16 Agostino Sarubbo
2020-04-09 21:37 Andreas Sturmlechner
2020-04-09 21:37 Andreas Sturmlechner
2020-03-22 0:32 Andreas Sturmlechner
2020-03-19 13:23 Andreas Sturmlechner
2020-03-19 13:23 Andreas Sturmlechner
2020-02-10 13:26 Michał Górny
2019-05-20 11:03 Mikle Kolyada
2017-01-22 10:21 Justin Lecher
2016-04-07 23:13 Sebastien Fabbro
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=1477782898.568207e87bf3984958b885af081f4c59bf5bfa3e.floppym@gentoo \
--to=floppym@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