Re: Virtual packages for shared libraries?
Previously Camm Maguire wrote:
> 1) Is this setup OK? I.e., can I just have atlas2 in shlibs.local?
> My plan is to change the soname whenever backward compatibility
> breaks, so I really don't need the source version -- the soname is
> in the virtual package name.
That's ok.
> 2) My real question pertains to search directories. These packages
> also provide libblas.so.2 and liblapack.so.2, but no naming
> convention/-soname= compile option that I'm aware of will allow
> these libs to coexist with the versions supplied by blas and lapack
> together in the same /usr/lib directory. As I wanted people to be
> able to switch the libs at runtime without recompiling, I stuck
> them in /usr/lib/atlas. So these packages 'provide' blas and
> lapack ONLY when LD_LIBRARY_PATH is set at runtime. Is it still OK
> to list these provides, and make a note in README.Debian?
No, you can't do the provide here.
Wichert.
--
_________________________________________________________________
/ Nothing is fool-proof to a sufficiently talented fool \
| wichert@wiggy.net http://www.liacs.nl/~wichert/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
Reply to: