Re: Minor CBLAS API changes

[Junichi Uekawa <dancer@netfort.gr.jp>]

> I have two choices:
> 
> 1) release blas/atlas packages with a new soname (3).  Advantages --
>    nothing will silently break, coexistence with existing stable
>    soname (2) packages.  Disadvantages -- everything depending on blas
>    must be recompiled  to use the new stuff, atlas is *huge* and it
>    will be in the archives twice.

I think 1 would be better, assuming that only a recompile is required
to get applications to compile with the new version.

> 2) release the new stuff with soname (2) and a big debconf warning.

This is rather unnice :P


regards,
	junichi