public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Christoph Junghans" <kleiner_otti@gmx.de>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: sys-cluster/scalasca/
Date: Mon,  4 Apr 2011 22:03:12 +0000 (UTC)	[thread overview]
Message-ID: <fb051b07b748859c136499adc80bd028ffb601d9.kleiner_otti@gentoo> (raw)

commit:     fb051b07b748859c136499adc80bd028ffb601d9
Author:     Christoph Junghans <ottxor <AT> gentoo <DOT> org>
AuthorDate: Mon Apr  4 22:02:52 2011 +0000
Commit:     Christoph Junghans <kleiner_otti <AT> gmx <DOT> de>
CommitDate: Mon Apr  4 22:02:52 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/sci.git;a=commit;h=fb051b07

[sys-cluster/scalasca] version bump

(Portage version: 2.1.9.42/git/Linux i686, signed Manifest commit with key C2000586)

---
 sys-cluster/scalasca/ChangeLog                     |    6 ++++++
 ...scalasca-1.3.2.ebuild => scalasca-1.3.3.ebuild} |    9 +++++----
 2 files changed, 11 insertions(+), 4 deletions(-)

diff --git a/sys-cluster/scalasca/ChangeLog b/sys-cluster/scalasca/ChangeLog
index e619891..c842f1b 100644
--- a/sys-cluster/scalasca/ChangeLog
+++ b/sys-cluster/scalasca/ChangeLog
@@ -2,6 +2,12 @@
 # Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
 # $Header: $
 
+*scalasca-1.3.3 (04 Apr 2011)
+
+  04 Apr 2011; Christoph Junghans <ottxor@gentoo.org> -scalasca-1.3.2.ebuild,
+  +scalasca-1.3.3.ebuild:
+  Version bump
+
   10 Mar 2011; Christoph Junghans <ottxor@gentoo.org> -scalasca-1.3.1.ebuild,
   scalasca-1.3.2.ebuild:
   cleanup + url updates

diff --git a/sys-cluster/scalasca/scalasca-1.3.2.ebuild b/sys-cluster/scalasca/scalasca-1.3.3.ebuild
similarity index 88%
rename from sys-cluster/scalasca/scalasca-1.3.2.ebuild
rename to sys-cluster/scalasca/scalasca-1.3.3.ebuild
index 7e74cce..dacab5f 100644
--- a/sys-cluster/scalasca/scalasca-1.3.2.ebuild
+++ b/sys-cluster/scalasca/scalasca-1.3.3.ebuild
@@ -13,11 +13,11 @@ SRC_URI="http://www2.fz-juelich.de/zam/datapool/scalasca/${P}.tar.gz"
 LICENSE="scalasca"
 SLOT="0"
 KEYWORDS="~x86"
-IUSE="examples fortran mpi openmp"
+IUSE="examples fortran mpi openmp qt4"
 
 DEPEND="mpi? ( virtual/mpi )
-	x11-libs/qt-core:4
-	x11-libs/qt-gui:4"
+	qt4? ( x11-libs/qt-core:4
+		x11-libs/qt-gui:4 )"
 
 RDEPEND="${DEPEND}"
 
@@ -38,9 +38,10 @@ src_configure() {
 
 	#configure is not a real (autotools) configure
 
-	#only --disable-(omp/mpi) is supported by configure
+	#only --disable-XXX is supported by configure
 	use openmp || myconf="${myconf} --disable-omp"
 	use mpi || myconf="${myconf} --disable-mpi"
+	use qt4 || myconf="${myconf} --disable-gui"
 
 	./configure --prefix="${EPREFIX}"/usr ${myconf} || die "configure failed"
 }



             reply	other threads:[~2011-04-04 22:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 22:03 Christoph Junghans [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-02-08  4:30 [gentoo-commits] proj/sci:master commit in: sys-cluster/scalasca/ Christoph Junghans
2011-06-21 11:54 Justin Lecher
2011-04-17 13:09 Christoph Junghans
2011-04-16 11:49 Christoph Junghans
2011-03-10 20:57 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=fb051b07b748859c136499adc80bd028ffb601d9.kleiner_otti@gentoo \
    --to=kleiner_otti@gmx.de \
    --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