public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Justin Bronder" <jsbronder@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: sys-cluster/mpich/
Date: Mon, 20 Apr 2015 17:11:13 +0000 (UTC)	[thread overview]
Message-ID: <1429548939.29843cdf120dc60b320ffa7a94da0ae5fcb23d1f.jsbronder@gentoo> (raw)

commit:     29843cdf120dc60b320ffa7a94da0ae5fcb23d1f
Author:     Justin Bronder <jsbronder <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 20 16:55:39 2015 +0000
Commit:     Justin Bronder <jsbronder <AT> gentoo <DOT> org>
CommitDate: Mon Apr 20 16:55:39 2015 +0000
URL:        https://gitweb.gentoo.org/proj/sci.git/commit/?id=29843cdf

drop keywords from non-empi version

Every other version of the various MPI's supports empi so it was unexpected to
have that dropped.  However this version is still useful for porting/testing.

Package-Manager: portage-2.2.14

 sys-cluster/mpich/ChangeLog                                       | 8 ++++++++
 .../mpich/{mpich-3.1.3-r1.ebuild => mpich-3.1.3-r99.ebuild}       | 2 +-
 2 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/sys-cluster/mpich/ChangeLog b/sys-cluster/mpich/ChangeLog
index 3b7b197..8630c01 100644
--- a/sys-cluster/mpich/ChangeLog
+++ b/sys-cluster/mpich/ChangeLog
@@ -2,6 +2,14 @@
 # Copyright 1999-2015 Gentoo Foundation; Distributed under the GPL v2
 # $Header: $
 
+*mpich-3.1.3-r99 (20 Apr 2015)
+
+  20 Apr 2015; Justin Bronder <jsbronder@gentoo.org> +mpich-3.1.3-r99.ebuild,
+  -mpich-3.1.3-r1.ebuild:
+  drop keywords from non-empi version  Every other version of the various MPI's
+  supports empi so it was unexpected to have that dropped.  However this version
+  is still useful for porting/testing.
+
   21 Feb 2015; Christoph Junghans <ottxor@gentoo.org> mpich-3.1.3-r1.ebuild:
   added fortran hack for bug #540508
 

diff --git a/sys-cluster/mpich/mpich-3.1.3-r1.ebuild b/sys-cluster/mpich/mpich-3.1.3-r99.ebuild
similarity index 97%
rename from sys-cluster/mpich/mpich-3.1.3-r1.ebuild
rename to sys-cluster/mpich/mpich-3.1.3-r99.ebuild
index 0b75e60..0d3d9c0 100644
--- a/sys-cluster/mpich/mpich-3.1.3-r1.ebuild
+++ b/sys-cluster/mpich/mpich-3.1.3-r99.ebuild
@@ -15,7 +15,7 @@ SRC_URI="http://www.mpich.org/static/downloads/${PV}/${P}.tar.gz"
 
 SLOT="0"
 LICENSE="mpich"
-KEYWORDS="~amd64 ~hppa ~ppc ~ppc64 ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS=""
 IUSE="+cxx doc fortran mpi-threads romio threads"
 
 COMMON_DEPEND="


             reply	other threads:[~2015-04-20 17:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 17:11 Justin Bronder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-08-29 20:49 [gentoo-commits] proj/sci:master commit in: sys-cluster/mpich/ Christoph Junghans
2016-08-29 20:45 Justin Bronder
2016-08-29 20:45 Justin Bronder
2016-08-29 20:45 Justin Bronder
2016-08-29 20:45 Justin Bronder
2016-08-29 20:45 Justin Bronder
2015-12-21 13:48 Justin Bronder
2015-11-21 15:14 Christoph Junghans
2015-04-20 17:27 Justin Bronder
2015-04-20 17:11 Justin Bronder
2015-02-21  2:46 Christoph Junghans
2015-02-20  2:01 Christoph Junghans
2015-02-17  0:13 Christoph Junghans

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=1429548939.29843cdf120dc60b320ffa7a94da0ae5fcb23d1f.jsbronder@gentoo \
    --to=jsbronder@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