[Pkg-octave-devel] The future of Atlas
lukshuntim at gmail.com
lukshuntim at gmail.com
Sun Jun 17 04:14:42 UTC 2012
On 06/17/2012 04:24 AM, Sébastien Villemot wrote:
> lukshuntim at 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.
>
> Best,
>
Hi Sébastien,
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.
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.
Thanks for the hard work done. :-)
ST
--
More information about the Pkg-octave-devel
mailing list