"Matteo F. Vescovi" <mfv.deb...@gmail.com> writes: > Then I guess you need to explain me how to do this ;-P
You'd add the tag "(optional)" at the start of each line: libOpenColorIO.so.1 libopencolorio1 #MINVER# (optional)_ZN11OpenColorIO2v110ColorSpace11setBitDepthENS0_8BitDepthE@Base 1.0.8~dfsg0 (optional)_ZN11OpenColorIO2v110ColorSpace12setTransformERKNSt3tr110shared_ptrIKNS0_9TransformEEENS0_19ColorSpaceDirectionE@Base 1.0.8~dfsg0 etc. > My hatred for C++ symbols is consolidated by OpenImageIO maintenance and > I usually delay their preparation more than I can ;-) That's fair, as they are often a nuisance; if maintaining them proves more trouble than it's worth (a distinct possibility for packages likely to accumulate only a few reverse dependencies), you can do away with them altogether in favor of the traditional shlibs system. > Hope you could help me in same way about that. As I noted, a lot of developers find pkgkde-symbolshelper from pkg-kde-tools to be of use. However, I can't offer much specific advice on using it because I haven't needed to do so myself -- my only C++ library packages are of FLTK, whose symbols don't vary much across architectures. (It's historically refrained from using the STL, which is a big source of such variation.) -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
