Comment # 16 on bug 1223967 from Atri Bhattacharya

(In reply to Richard Biener from comment #14)
> 
> Note this is where it might be important that the hwcaps and non-hwcaps
> variant alternatives come from the same implementation unless the ABIs
> are 100% the same.  So I think ideally the alternatives setup would
> have a link group and a single config to adjust.  Not sure if it's done
> this way and whether it's possible at all if the group is split between
> two packages.

We should probably implement a main and slave alternatives setup anyway so that
both libblas.so.* and liblapack.so.* come from the same implementation. At the
moment, my understanding is that one could theoretically use blas from
implementation A (say, openblas) while still using cblas and lapack from the
implementation B (reference netlib library, for example). I do not know whether
this kind of usage is advisable.