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