Hi Carl, 2014-05-21 15:41:44 Carl Worth: > I'm interested in packaging (or helping to package) several programs and > libraries related to OpenGL, (such as apitrace, vogl, fips, and waffle). > > For each of these packages I have a question about best practices > related to supporting 32-bit libraries and binaries within a 64-bit > system. > > Imagine a package (waffle-utils, say) that installs a program > (/usr/bin/wflinfo, say) that reports some information about a library > (libGL.so, say) against which it is linked. > > So on either an -i386 or an -amd64 system, a user could install the > native package, run the program, and query the native library. > > But now imagine a user with an -amd64 system that has an alternate -i386 > library provided by a multilibs package (such as libgl1-mesa-glx:i386). > It would be useful for such a user to have both the native 64-bit > program and a 32-bit program available at the same time, (to be able to > query either library). If it's just version information the results across all architectures will be the same because you can only install one version of a Multi-Arch: same package. If you need more information consider doing it like libc: add a main() to the lib to display that information. Greetings Timo
Attachment:
signature.asc
Description: This is a digitally signed message part.