Re: *.so symlinks in shared lib package
Michael Wild <themiwi@users.sourceforge.net> writes:
> Do *.so development symlinks in a shared-library package constitute a
> policy violation? 8.1 Doesn't forbid them in the library package and 8.4
> only says the "should" be in the -dev package.
If the *.so development symlinks prevent two versions of the package with
different SONAMEs from coexisting, it's a violation of Policy 8.2:
If your package contains files whose names do not change with each
change in the library shared object version, you must not put them in
the shared library package. Otherwise, several versions of the shared
library cannot be installed at the same time without filename clashes,
making upgrades and transitions unnecessarily difficult.
Normally, the development symlinks will indeed violate this, since they'll
be of the form libfoo.so, which does not change with each change in the
library shared object version.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: