Comment # 24 on bug 1223967 from Atri Bhattacharya

(In reply to Egbert Eich from comment #23)
> @Atri: the major issues I'm seeing with the approach in
> home:badshah400:lapackv3/lapack are lines in baselib.conf like this:
>   postin "ln -sf /etc/alternatives/libblas.so.3_<targettype>
> /usr/%_lib/libblas.so.3"
>   postin "/usr/sbin/update-alternatives --force --install
> /usr/%_lib/libblas.so.3 libblas.so.3_<targettype>
> /usr/%_lib/blas/libblas.so.3  50"
>   postun "/usr/sbin/update-alternatives --remove libblas.so.3_<targettype>
> /usr/%_lib/blas/libblas.so.3"
> 
> %_lib is a standard define which expands to /usr/lib or /usr/lib64. It
> doesn't expand to /usr/lib64/glibc-hwcaps/<targettype>:
> 
> home:badshah400:lapack-hwcaps/lapack/binaries$ rpm -q --scripts -p
> libcblas3-x86-64-v3-3.12.0-1.1.x86_64.rpm
> warning: libcblas3-x86-64-v3-3.12.0-1.1.x86_64.rpm: Header V3 RSA/SHA256
> Signature, key ID 4aeaf2b5: NOKEY
> postinstall scriptlet (using /bin/sh):
> /sbin/ldconfig
> ln -sf /etc/alternatives/libcblas.so.3_x86-64-v3 /usr/lib64/libcblas.so.3
> /usr/sbin/update-alternatives --force --install /usr/lib64/libcblas.so.3
> libcblas.so.3_x86-64-v3 /usr/lib64/blas/libcblas.so.3  50
> preuninstall scriptlet (using /bin/sh):
> /usr/sbin/update-alternatives --remove libcblas.so.3_x86-64-v3
> /usr/lib64/blas/libcblas.so.3
> 
> The only way to handle this I can think of would be to do something like
> this:
> 
>   postin "ldconfig -n /usr/%_lib/glibc-hwcaps/<targettype>/blas"
>   postin "case <targettype> in x86-64-v*) p=glibc-hwcaps/<targettype> ;;
> esac"
>   postin "/usr/sbin/update-alternatives --force --install
> /usr/%_lib/$p/libblas.so.3 libblas.so.3_<targettype> /usr/%_\
> lib/$p/blas/libblas.so.3  50"
>   postun "case <targettype> in x86-64-v*) p=glibc-hwcaps/<targettype> ;;
> esac"
>   postun "/usr/sbin/update-alternatives --remove libblas.so.3_<targettype>
> /usr/%_lib/$p/libblas.so.3"
> 
> Disclaimer: I haven't tested this.

The attempt in obs://home:badshah400:lapackv3/lapack is to generate the
x86-64-v3 libs purely as a separate flavour, *without* the baselibs.conf coming
into play at all in so far as these -v3 libs are concerned.

Baselibs.conf is still used to produce 32-bit biarch packages for pure x86_64
in this case, but it simply does not matter for x86-64-v3 flavour since there
aren't i586-v3 equivalents.

But perhaps I misunderstand your question?