public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: "François Bissey" <fbissey@slingshot.co.nz>
To: gentoo-science@lists.gentoo.org
Subject: [gentoo-science] blas selection in lapack-reference
Date: Wed, 22 Jan 2014 13:52:57 +1300	[thread overview]
Message-ID: <589fdf2e04e21f3fad949727e20880b6@slingshot.co.nz> (raw)

We have yet another instance of someone emerging lapack-reference 
without
a valid blas configuration in 
https://bugs.gentoo.org/show_bug.cgi?id=498490
(not their original problem).
I think we should do something about this in lapack-reference and 
possibly
other ebuilds.
In pkg_setup, we could run
eselect blas update
to make sure that a valid configuration is active
and display an informational message about the blas provider
used with the output of
eselect blas show

Who thinks is a good/bad idea?

Francois


             reply	other threads:[~2014-01-22  0:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22  0:52 François Bissey [this message]
2014-01-22  1:47 ` [gentoo-science] blas selection in lapack-reference Steven Trogdon
2014-01-22  9:47   ` Reinis Danne
2014-01-22  9:54     ` François Bissey
2014-01-22 10:02       ` Reinis Danne

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=589fdf2e04e21f3fad949727e20880b6@slingshot.co.nz \
    --to=fbissey@slingshot.co.nz \
    --cc=gentoo-science@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