1 |
On Tue, Jan 21, 2014 at 07:47:48PM -0600, Steven Trogdon wrote: |
2 |
> On Wed, 22 Jan 2014 13:52:57 +1300 |
3 |
> François Bissey <fbissey@××××××××××××.nz> wrote: |
4 |
> |
5 |
> > We have yet another instance of someone emerging lapack-reference |
6 |
> > without |
7 |
> > a valid blas configuration in |
8 |
> > https://bugs.gentoo.org/show_bug.cgi?id=498490 |
9 |
> > (not their original problem). |
10 |
> > I think we should do something about this in lapack-reference and |
11 |
> > possibly |
12 |
> > other ebuilds. |
13 |
> > In pkg_setup, we could run |
14 |
> > eselect blas update |
15 |
> > to make sure that a valid configuration is active |
16 |
> > and display an informational message about the blas provider |
17 |
> > used with the output of |
18 |
> > eselect blas show |
19 |
> > |
20 |
> > Who thinks is a good/bad idea? |
21 |
> > |
22 |
> > Francois |
23 |
> > |
24 |
> |
25 |
> For one, I'm in favor of something like this - though I probably don't have |
26 |
> much say in the matter. I've been bitten by not eselecting {blas, cblas, |
27 |
> lapack} after an upgrade. And I've even posted on this forum the problem. |
28 |
> |
29 |
> http://article.gmane.org/gmane.linux.gentoo.science/1915 |
30 |
> http://article.gmane.org/gmane.linux.gentoo.science/1916 |
31 |
> |
32 |
> I resolved things, quite accidently, by re-eselecting the important |
33 |
> components which were eselected before the upgrade. |
34 |
> |
35 |
> Steve |
36 |
> |
37 |
|
38 |
I fixed provider selection during upgrades in overlay |
39 |
(yesterday). Now it should have valid provider set at any time. |
40 |
With that do you still think it would need this extra eselect |
41 |
update in ebuild? |
42 |
|
43 |
|
44 |
Reinis |