On Tue, Mar 31, 2009 at 10:17:47PM +0200, Marco d'Itri wrote: > On Mar 31, Mike Hommey <m...@glandium.org> wrote:
> > If you don't want to depend on libcomerr2, don't depend on it. It's not > > because libkrb5-3 already depends on it that it's a proper thing to > > remove the dependency that way. What happens when libkrb5-3 depends > > on libcomerr3 ? > Plenty of segfaults because both would provide the same unversioned > symbols? But this case is detectable via the package system *if* you aren't bypassing dpkg-shlibdeps. If you do bypass dpkg-shlibdeps, no one will notice that your package needs an upgrade at the same time. It's more robust to leave the dep (--> recommends) on libcomerr2 in place. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
