lukshuntim@gmail.com writes: > On 06/17/2012 04:24 AM, Sébastien Villemot wrote: >> lukshuntim@gmail.com writes: >> >>> Would that mean libblas, liblapack, libblas-dev, liblapack-dev are now >>> all virtual packages? That would be great! >> >> They already provide virtual packages (libblas.so.3gf / >> liblapack.so.3gf), and they already make use of the alternatives >> system. Nothing now on that side. > > Yes, that's true for the .so libraries. However, it's not so for the dev > packages. For example, currently libblas-dev (which liboctave-dev > depends on) is not virtual but comes from the (basic) blas package. But this is not really a problem, because the binary package of octave that is created has a dependency on "libblas3 | libblas.so.3 | libatlas3-base", so that any BLAS implementation can satisfy the dependency. Same for LAPACK. > I guess some of the conflicts/bugs mentioned in this thread are due to > different applications build-depending on different dev blas packages. > If they are API compatible with the netlib blas (which I don't know > whether it's true or not), a virtual dev package should be possible. I’m not sure to fully understand your problem, but I suggest to file a (wishlist) bug against blas/lapack packages with a more detailed description of the solution that you suggest. Best, -- Sébastien Villemot Researcher in Economics & Debian Maintainer http://www.dynare.org/sebastien Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594
Attachment:
pgpz5V45AZr7k.pgp
Description: PGP signature