On Sun, Nov 03, 2013 at 04:08:18PM +0100, Kurt Roeckx wrote: > On Sun, Nov 03, 2013 at 10:47:16AM +0100, Mark Wielaard wrote: > > > > If you package libasm separately it does depend on backend internals > > so should depend on the exact version of libdw1 (in which the libebl > > backends are). > > The reason for elfutils to depend on libdw1 with the exact same > version was that libebl.a is used and contains a MODVERSION. It > seems that libasm is also doing that, and so should also have > this version requirement?
So after some changed I'm currently having this: Package: elfutils Version: 0.156-2 Depends: libasm1 (>= 0.132), libc6 (>= 2.14), libdw1 (= 0.156-2), libelf1 (= 0.156-2), libstdc++6 (>= 4.1.1) Package: libelf1 Version: 0.156-2 Depends: libc6 (>= 2.14) Package: libdw1 Version: 0.156-2 Depends: libbz2-1.0, libc6 (>= 2.14), libelf1 (>= 0.144), liblzma5 (>= 5.1.1alpha+20120614), zlib1g (>= 1:1.2.2.3) Package: libasm1 Version: 0.156-2 Depends: libc6 (>= 2.14), libelf1 (>= 0.132), libdw1 (= 0.156-2) And other packages will get Depends depending on the symbols they use. Do you think that makes sense? Or should the elfutils libasm1 Depends also be (= 0.156-2)? (It would now still be possible to have an older libasm1 installed, but once libasm1 >= 0.156-2 gets installed, it's Depends on libdw1 will has as effect that the same version as libdw1 should get installed and so all libraries will end up with the same version.) Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
