| 1 |
I've just filled a bug #131974 |
| 2 |
concerning the incosistencies in the current |
| 3 |
support of blas/lapack/atlas in portage. |
| 4 |
|
| 5 |
I understand that this situation perhaps arises because |
| 6 |
we still have some obsolete packages in portage. |
| 7 |
|
| 8 |
He is my bug report (expressing my opinion on |
| 9 |
this issue): |
| 10 |
|
| 11 |
Opened: 2006-05-01 19:39 PST |
| 12 |
I think that blas/lapack/atlas support in portage |
| 13 |
has several inconsistencies. |
| 14 |
|
| 15 |
For example, there are three packages related |
| 16 |
to atlas |
| 17 |
|
| 18 |
sci-libs/atlas |
| 19 |
sci-libs/blas-atlas |
| 20 |
sci-libs/lapack-atlas |
| 21 |
|
| 22 |
However. sci-libs/atlas does not provide |
| 23 |
blas neither lapack. And if I emerge, blas-atlas |
| 24 |
and then lapack-atlas, I have to compile atlas |
| 25 |
twice!. This is quit frustrating, since Atlas takes |
| 26 |
a lot of time to compile. |
| 27 |
|
| 28 |
The most reasonable thing would be to have just |
| 29 |
one sci-libs/atlas package and that this package |
| 30 |
provides both virtual/blas and virtual/lapack. |
| 31 |
|
| 32 |
Another inconsistency is that we have both |
| 33 |
sci-libs/blas and sci-libs/blas-reference |
| 34 |
in portage. blas reference provides virtual/blas |
| 35 |
but blas does not! |
| 36 |
|
| 37 |
So I emerge blas, and it does not provide blas! |
| 38 |
(what seems rather absurd to me) |
| 39 |
|
| 40 |
(and what it is worst, the strange behavior of all |
| 41 |
this packages seems not to be documented anywhere) |
| 42 |
|
| 43 |
best regards |
| 44 |
Pablo De Napoli |
| 45 |
|
| 46 |
__________________________________________________ |
| 47 |
Do You Yahoo!? |
| 48 |
Tired of spam? Yahoo! Mail has the best spam protection around |
| 49 |
http://mail.yahoo.com |
| 50 |
-- |
| 51 |
gentoo-science@g.o mailing list |
Archives