On 07/27/2012 10:34 AM, Russ Allbery wrote: > Michael Wild <them...@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. >
Thanks Ansgar and Russ That's just the answer I needed to make #682943 a RC bug ;-) Michael -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50125de5.2090...@gmail.com
