public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Justin Lecher" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: dev-python/pysparse/
Date: Mon,  6 May 2013 08:26:55 +0000 (UTC)	[thread overview]
Message-ID: <1367828793.2eff40f1092b99e188e6ceca733e0abb39f71c5f.jlec@gentoo> (raw)

commit:     2eff40f1092b99e188e6ceca733e0abb39f71c5f
Author:     Justin Lecher <jlec <AT> gentoo <DOT> org>
AuthorDate: Mon May  6 08:26:33 2013 +0000
Commit:     Justin Lecher <jlec <AT> gentoo <DOT> org>
CommitDate: Mon May  6 08:26:33 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/sci.git;a=commit;h=2eff40f1

dev-python/pysparse: USe internal umfpack due to incompatibility with latest umfpack from tree

Package-Manager: portage-2.2.0_alpha174

---
 dev-python/pysparse/ChangeLog                |    3 +++
 dev-python/pysparse/pysparse-1.1.1-r1.ebuild |   11 ++++++-----
 2 files changed, 9 insertions(+), 5 deletions(-)

diff --git a/dev-python/pysparse/ChangeLog b/dev-python/pysparse/ChangeLog
index d441e3f..189c671 100644
--- a/dev-python/pysparse/ChangeLog
+++ b/dev-python/pysparse/ChangeLog
@@ -2,6 +2,9 @@
 # Copyright 1999-2013 Gentoo Foundation; Distributed under the GPL v2
 # $Header: $
 
+  06 May 2013; Justin Lecher <jlec@gentoo.org> pysparse-1.1.1-r1.ebuild:
+  USe internal umfpack due to incompatibility with latest umfpack from tree
+
 *pysparse-1.1.1-r1 (06 May 2013)
 
   06 May 2013; Justin Lecher <jlec@gentoo.org> -pysparse-1.1.ebuild,

diff --git a/dev-python/pysparse/pysparse-1.1.1-r1.ebuild b/dev-python/pysparse/pysparse-1.1.1-r1.ebuild
index 7638a14..7eac3e2 100644
--- a/dev-python/pysparse/pysparse-1.1.1-r1.ebuild
+++ b/dev-python/pysparse/pysparse-1.1.1-r1.ebuild
@@ -28,17 +28,18 @@ PATCHES=(
 	"${FILESDIR}"/${P}-superlu3.patch
 	)
 
-pc_libdir() {
-	$(tc-getPKG_CONFIG) --libs-only-L $@ | \
-	sed -e 's/^-L//' -e 's/[ ]*-L/:/g'
+pc_libs() {
+	$(tc-getPKG_CONFIG) --libs-only-l $@ | \
+	sed -e 's/[ ]-l*\(pthread\|m\)[ ]*//g' \
+	-e 's/^-l/"/' -e 's/[ ]*-l/","/g' -e 's/[ ]*$/"/g'
 }
 
 python_prepare_all() {
+	distutils-r1_python_prepare_all
 	sed \
 		-e "/libraries_list/s:'lapack', 'blas':$(pc_libs blas lapack):g" \
+		-e "/use_users_umfpack/s:True:False:g" \
 		-i setup.py || die
-
-	distutils-r1_python_prepare_all
 }
 
 python_test() {


             reply	other threads:[~2013-05-06  8:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06  8:26 Justin Lecher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-05-06  8:26 [gentoo-commits] proj/sci:master commit in: dev-python/pysparse/ Justin Lecher

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=1367828793.2eff40f1092b99e188e6ceca733e0abb39f71c5f.jlec@gentoo \
    --to=jlec@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