From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: virtual/mpi/
Date: Wed, 22 Jun 2022 04:09:40 +0000 (UTC) [thread overview]
Message-ID: <1655870969.a8d01355ef15745ba5650e0c5cd552d3d92c87f1.sam@gentoo> (raw)
commit: a8d01355ef15745ba5650e0c5cd552d3d92c87f1
Author: Sergey Torokhov <torokhov-s-a <AT> yandex <DOT> ru>
AuthorDate: Tue Jun 21 22:18:01 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Jun 22 04:09:29 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a8d01355
virtual/mpi: fix USE="nullmpi", update deps versions
Signed-off-by: Sergey Torokhov <torokhov-s-a <AT> yandex.ru>
Closes: https://github.com/gentoo/gentoo/pull/26028
Signed-off-by: Sam James <sam <AT> gentoo.org>
virtual/mpi/{mpi-2.0-r6.ebuild => mpi-2.0-r7.ebuild} | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/virtual/mpi/mpi-2.0-r6.ebuild b/virtual/mpi/mpi-2.0-r7.ebuild
similarity index 56%
rename from virtual/mpi/mpi-2.0-r6.ebuild
rename to virtual/mpi/mpi-2.0-r7.ebuild
index c9a731d9dabb..f6c05af2c2f2 100644
--- a/virtual/mpi/mpi-2.0-r6.ebuild
+++ b/virtual/mpi/mpi-2.0-r7.ebuild
@@ -1,7 +1,7 @@
# Copyright 1999-2022 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
-EAPI=7
+EAPI=8
inherit multilib-build
@@ -12,8 +12,8 @@ KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ~ppc ppc64 ~riscv sparc x86 ~amd64-
IUSE="cxx fortran romio threads nullmpi"
RDEPEND="|| (
- >=sys-cluster/openmpi-1.10.2-r1[${MULTILIB_USEDEP},cxx?,fortran?,romio?,threads(+)?]
- >=sys-cluster/mpich-3.2-r1[${MULTILIB_USEDEP},cxx?,fortran?,romio?,threads?]
- sys-cluster/nullmpi[${MULTILIB_USEDEP},cxx(-)?,fortran(-)?,romio(-)?,threads(-)?]
- nullmpi? ( sys-cluster/native-mpi )
+ >=sys-cluster/openmpi-4.1.2[${MULTILIB_USEDEP},cxx?,fortran?,romio?,threads(+)?]
+ >=sys-cluster/mpich-3.4.3[${MULTILIB_USEDEP},cxx?,fortran?,romio?,threads?]
+ sys-cluster/native-mpi
+ nullmpi? ( sys-cluster/nullmpi[${MULTILIB_USEDEP},cxx(-)?,fortran(-)?,romio(-)?,threads(-)?] )
)"
next reply other threads:[~2022-06-22 4:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 4:09 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-17 5:43 [gentoo-commits] repo/gentoo:master commit in: virtual/mpi/ Eli Schwartz
2023-06-03 9:50 WANG Xuerui
2022-03-07 4:29 Sam James
2022-02-04 9:15 Jakov Smolić
2022-01-29 10:27 David Seifert
2021-12-26 3:19 Sam James
2021-12-03 22:51 Sam James
2021-12-01 5:48 Arthur Zamarin
2021-12-01 5:48 Arthur Zamarin
2021-10-20 0:11 Sam James
2021-10-15 6:00 Agostino Sarubbo
2021-10-14 13:39 Agostino Sarubbo
2021-10-13 20:35 Sam James
2021-07-05 13:25 Marek Szuba
2020-10-24 14:51 David Seifert
2018-03-01 18:43 Michał Górny
2018-02-07 22:29 Justin Bronder
2017-06-23 5:20 Alexis Ballier
2017-04-02 23:41 Matt Turner
2017-03-17 6:36 Matt Turner
2017-03-17 6:36 Matt Turner
2017-03-10 10:59 Agostino Sarubbo
2017-03-10 9:09 Agostino Sarubbo
2017-02-24 18:18 Christoph Junghans
2017-01-03 15:28 Christoph Junghans
2016-11-17 21:44 Ian Stakenvicius
2016-09-27 13:12 Christoph Junghans
2016-09-12 1:32 Christoph Junghans
2016-09-06 0:18 Christoph Junghans
2016-08-29 21:22 Christoph Junghans
2016-08-11 7:55 David Seifert
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=1655870969.a8d01355ef15745ba5650e0c5cd552d3d92c87f1.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