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: dev-lang/ispc/
Date: Tue,  8 Jan 2013 04:36:43 +0000 (UTC)	[thread overview]
Message-ID: <1357619795.51824bb37562772d7a02adabda11528e4f091886.kleiner_otti@gentoo> (raw)

commit:     51824bb37562772d7a02adabda11528e4f091886
Author:     Christoph Junghans <ottxor <AT> gentoo <DOT> org>
AuthorDate: Tue Jan  8 04:35:19 2013 +0000
Commit:     Christoph Junghans <kleiner_otti <AT> gmx <DOT> de>
CommitDate: Tue Jan  8 04:36:35 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/sci.git;a=commit;h=51824bb3

fixed python dep

Package-Manager: portage-2.2.0_alpha149

---
 dev-lang/ispc/ChangeLog        |    5 ++++-
 dev-lang/ispc/ispc-9999.ebuild |   10 ++++++++--
 2 files changed, 12 insertions(+), 3 deletions(-)

diff --git a/dev-lang/ispc/ChangeLog b/dev-lang/ispc/ChangeLog
index 81a6141..e87b0c0 100644
--- a/dev-lang/ispc/ChangeLog
+++ b/dev-lang/ispc/ChangeLog
@@ -1,7 +1,10 @@
 # ChangeLog for dev-lang/ispc
-# Copyright 1999-2012 Gentoo Foundation; Distributed under the GPL v2
+# Copyright 1999-2013 Gentoo Foundation; Distributed under the GPL v2
 # $Header: $
 
+  08 Jan 2013; Christoph Junghans <ottxor@gentoo.org> ispc-9999.ebuild:
+  fixed python dep
+
   26 Aug 2012; Christoph Junghans <ottxor@gentoo.org> ispc-9999.ebuild:
   sync with gx86
 

diff --git a/dev-lang/ispc/ispc-9999.ebuild b/dev-lang/ispc/ispc-9999.ebuild
index f1c5130..e65b5c1 100644
--- a/dev-lang/ispc/ispc-9999.ebuild
+++ b/dev-lang/ispc/ispc-9999.ebuild
@@ -1,10 +1,12 @@
-# Copyright 1999-2012 Gentoo Foundation
+# Copyright 1999-2013 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 # $Header: /var/cvsroot/gentoo-x86/dev-lang/ispc/ispc-1.3.0.ebuild,v 1.2 2012/07/20 19:58:21 ottxor Exp $
 
 EAPI=4
 
-inherit base toolchain-funcs
+PYTHON_DEPEND="2"
+
+inherit base toolchain-funcs python
 
 DESCRIPTION="Intel SPMD Program Compiler"
 HOMEPAGE="http://ispc.github.com/"
@@ -32,6 +34,10 @@ DEPEND="
 	sys-devel/flex
 	"
 
+pkg_setup() {
+	python_set_active_version 2
+}
+
 src_compile() {
 	emake LDFLAGS="${LDFLAGS}" OPT="${CXXFLAGS}" CXX="$(tc-getCXX)" CPP="$(tc-getCPP)"
 }


             reply	other threads:[~2013-01-08  4:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08  4:36 Christoph Junghans [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-07-13 15:31 [gentoo-commits] proj/sci:master commit in: dev-lang/ispc/ Christoph Junghans
2016-05-30 20:14 Christoph Junghans
2014-10-25  4:04 Christoph Junghans
2014-05-12  2:17 Christoph Junghans
2014-01-06 19:27 Justin Lecher
2014-01-06 17:41 Justin Lecher
2013-06-26  0:29 Christoph Junghans
2013-06-14 11:21 [gentoo-commits] proj/sci:fixing " Justin Lecher
2013-06-14 11:21 ` [gentoo-commits] proj/sci:master " Justin Lecher
2013-06-04 11:59 Justin Lecher
2013-05-31 23:26 Christoph Junghans
2012-08-26 18:32 Christoph Junghans
2012-06-18 22:04 Sebastien Fabbro
2012-06-17  2:39 Christoph Junghans
2012-06-14 18:31 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=1357619795.51824bb37562772d7a02adabda11528e4f091886.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