I've just filled a bug #131974 concerning the incosistencies in the current support of blas/lapack/atlas in portage.
I understand that this situation perhaps arises because we still have some obsolete packages in portage. He is my bug report (expressing my opinion on this issue): Opened: 2006-05-01 19:39 PST I think that blas/lapack/atlas support in portage has several inconsistencies. For example, there are three packages related to atlas sci-libs/atlas sci-libs/blas-atlas sci-libs/lapack-atlas However. sci-libs/atlas does not provide blas neither lapack. And if I emerge, blas-atlas and then lapack-atlas, I have to compile atlas twice!. This is quit frustrating, since Atlas takes a lot of time to compile. The most reasonable thing would be to have just one sci-libs/atlas package and that this package provides both virtual/blas and virtual/lapack. Another inconsistency is that we have both sci-libs/blas and sci-libs/blas-reference in portage. blas reference provides virtual/blas but blas does not! So I emerge blas, and it does not provide blas! (what seems rather absurd to me) (and what it is worst, the strange behavior of all this packages seems not to be documented anywhere) best regards Pablo De Napoli __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- [email protected] mailing list
