Hi, Jarno Elonen wrote: > > 1) Ok, as you ship a uno package you can't use dpkg-shlibdeps, right. > > (Can't you hack around to run dpkg-shlibdeps on the pkgs contents?). > > Good idea. Had to do this in debian/rules, however, and it doesn't look too > neat: > > rm -f debian/shlibs.local > for PKG in "openoffice.org-common" "openoffice.org-core"; do > dpkg -L $$PKG | grep "^.*\.so\.[0-9]*$$" | \ > sed -r "s/.*\/(lib.*)\.so\.([0-9]+)/\1 \2 $$PKG (>= 2.0.2)/" >> > debian/shlibs.local; > done
-core should be enough, but it looks ugly, yes. I only wanted that for libstlport4.6 for example, but making it for openoffice.org itself might make sense, too, yes. > If there is some reason why the OOo packages can't announce the libs through > shlibs, could they perhaps provide the lists separately so that I could do > something like... > > cat /usr/lib/openoffice/debian_shlibs/* > debian/shlibs.local > > ...instead of the scanning them in 'rules' (or adding manually)? No, just not done yet. The problem with .shlibs is that external packages don't really get it in many cases since the libs are not in /usr/lib. Hmm. I am not sure whether last one also will work in all cases... And till now, -soikko is the only binary extension someone wanted to package (in fact, the only one anyway) I'll play with it. Regards, Rene
signature.asc
Description: Digital signature
