On Wed, May 05, 2004 at 03:40:52PM +0200, Jeroen van Wolffelaar wrote: > If these are shared libraries, which they very much seem to be, then the > soname should be set to libnss_dns.so.2 (in this case), and a shlibs > entry for programs who wish to use that same library too. For the > latter, you'll also need to add the static library in the -dev package > (the .a file).
I don't see any reason to humor policy in this fashion. > It is actually a policy violation as it is now, but since it'd be very > unfortunate if changes to these files turn out to have unforseen > implications (I doubt it, but you can better play safe) this close to > the Sarge release, I won't inflate the severity now. Adding a soname is > quite zero-risk though: add '-Wl,-soname,libnss_dns.so.2' to the gcc > line compiling libnss_dns-2.3.2.so (etc). Also extra shlibs entries > don't hurt. And the strange filename is both quite unimportant, not > clear it's wrong at all (just not like it is done usually), and of > course way too risky to change right now. There is nothing wrong with the file naming. There is also no point to having a SONAME, because we do not ship a .so symbolic link; the linker will do the right thing. If you think that any change is low risk you've obviously never worked with glibc :) I also think lintian should just ignore the NSS libraries, one way or another. They are shared libraries meant to be accessed by dlopen. They have to live in $libdir because that's where everything will look for them. -- Daniel Jacobowitz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]