public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kacper Kowalik" <xarthisius@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: dev-lang/path64/
Date: Sat, 23 Jul 2011 11:57:06 +0000 (UTC)	[thread overview]
Message-ID: <011a4e82323ebf60f0c4c03907933740981d2653.xarthisius@gentoo> (raw)

commit:     011a4e82323ebf60f0c4c03907933740981d2653
Author:     Kacper Kowalik (Xarthisius) <xarthisius <AT> gentoo <DOT> org>
AuthorDate: Sat Jul 23 11:56:59 2011 +0000
Commit:     Kacper Kowalik <xarthisius <AT> gentoo <DOT> org>
CommitDate: Sat Jul 23 11:56:59 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/sci.git;a=commit;h=011a4e82

[dev-lang/path64] gcc:4.2 is no longer a strict dep

---
 dev-lang/path64/ChangeLog          |    3 +++
 dev-lang/path64/path64-9999.ebuild |    8 +-------
 2 files changed, 4 insertions(+), 7 deletions(-)

diff --git a/dev-lang/path64/ChangeLog b/dev-lang/path64/ChangeLog
index 51da084..fdebe77 100644
--- a/dev-lang/path64/ChangeLog
+++ b/dev-lang/path64/ChangeLog
@@ -3,6 +3,9 @@
 # $Header: $
 
   23 Jul 2011; Kacper Kowalik <xarthisius@gentoo.org> path64-9999.ebuild:
+  gcc:4.2 is no longer a strict dep
+
+  23 Jul 2011; Kacper Kowalik <xarthisius@gentoo.org> path64-9999.ebuild:
   Unset all fortran vars
 
   23 Jul 2011; Kacper Kowalik <xarthisius@gentoo.org> path64-9999.ebuild:

diff --git a/dev-lang/path64/path64-9999.ebuild b/dev-lang/path64/path64-9999.ebuild
index 6c1e883..0db2e99 100644
--- a/dev-lang/path64/path64-9999.ebuild
+++ b/dev-lang/path64/path64-9999.ebuild
@@ -28,16 +28,10 @@ SLOT="0"
 KEYWORDS="~amd64"
 IUSE="assembler custom-cflags debugger fortran +native +openmp"
 
-DEPEND="!native? ( sys-devel/gcc:4.2[vanilla] )
+DEPEND="!native? ( sys-devel/gcc[vanilla] )
 	native? ( || ( dev-lang/ekopath-bin dev-lang/path64 ) )"
 RDEPEND="${DEPEND}"
 
-pkg_setup() {
-	if use !native && [[ $(gcc-version) != 4.2 ]] ; then
-		die "To bootstrap Path64 you'll need to use gcc:4.2[vanilla]"
-	fi
-}
-
 src_unpack() {
 	git-2_src_unpack
 	cd "${S}"



             reply	other threads:[~2011-07-23 11:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-23 11:57 Kacper Kowalik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-01-29 14:20 [gentoo-commits] proj/sci:master commit in: dev-lang/path64/ Justin Lecher
2014-01-06 19:27 Justin Lecher
2013-06-14 11:21 [gentoo-commits] proj/sci:fixing " Justin Lecher
2013-06-14 11:21 ` [gentoo-commits] proj/sci:master " Justin Lecher
2012-05-23 20:18 Kacper Kowalik
2012-05-23 19:56 Kacper Kowalik
2012-02-27 11:36 Kacper Kowalik
2012-02-25 19:44 Kacper Kowalik
2011-10-24 19:12 Justin Lecher
2011-08-15 13:39 Kacper Kowalik
2011-07-29 17:48 Kacper Kowalik
2011-07-29  7:51 Kacper Kowalik
2011-07-29  7:46 Kacper Kowalik
2011-07-27  9:48 Kacper Kowalik
2011-07-25 19:48 Kacper Kowalik
2011-07-25 19:40 Kacper Kowalik
2011-07-25  8:34 Kacper Kowalik
2011-07-23 12:31 Kacper Kowalik
2011-07-23 11:55 Kacper Kowalik
2011-07-23 11:27 Kacper Kowalik
2011-07-23 10:07 Kacper Kowalik
2011-07-23  7:32 Kacper Kowalik
2011-07-20 11:41 Kacper Kowalik
2011-07-20 11:15 Kacper Kowalik
2011-07-20  8:56 Kacper Kowalik

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=011a4e82323ebf60f0c4c03907933740981d2653.xarthisius@gentoo \
    --to=xarthisius@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