Hi Jakub, > * Herbert Parentes Fortes Neto <[email protected]>, 2015-11-26, 12:15: > >I maintain a package which provides a .symbols file. But it uses a > >dh_makeshlibs in debian/rules[0]. > > > >override_dh_makeshlibs: > > dh_makeshlibs -plibgphoto2-$(major) \ > > -V 'libgphoto2-$(major) (>= $(SHLIBS))' \ > > -X/usr/lib/$(DEB_HOST_MULTIARCH)/libgphoto2/ > > dh_makeshlibs -plibgphoto2-port12 \ > > -V 'libgphoto2-port12 (>= $(SHLIBS))' \ > > -X/usr/lib/$(DEB_HOST_MULTIARCH)/libgphoto2_port/ > > > >[0] - > >http://anonscm.debian.org/cgit/pkg-phototools/libgphoto2.git/tree/debian/rules > > > >Am I confusing or the package uses the two systems ? > > It does. Vast majority of packages that have DEBIAN/symbols also have > DEBIAN/shlibs, because dh_makeshlibs generates both of them. If you have > DEBIAN/symbols, DEBIAN/shlibs is probably not very useful, but it > doesn't hurt either. > > That said, I wonder if there's any point in passing -V to dh_makeshlibs > if the package uses symbols. It doesn't seem useful. >
I will remove these 'dh_makeshlibs' entries from the debian/rules file. Thanks for replying. regards, -- Herbert Parentes Fortes Neto (hpfn)
