On Jan 9, Robert Bihlmeyer ([EMAIL PROTECTED]) wrote: > "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> writes: > > > > 3) "non-dev-pkg-with-shlib-symlink /usr/lib/libMSGUI.so.0.0.0 > > > /usr/lib/libMSGUI.so" (warning) This package is an interpreter, and the > > > shared > > > libraries are for running that, NOT to be linked against, so I think > > > this is > > > benign and I can ignore them. Yes or no? > > > > libfoo.so is ONLY used to link a program with, otherwise the libfoo.so.X.X > > is > > used. So you should not ship a .so except in a -dev package. > > In addition, shared objects that are not intended for general use > (i.e. are not really "shared libraries") should not go into /usr/lib, > but some subdirectory (e.g. /usr/lib/aplus). For example, mozilla-* > uses /usr/lib/mozilla/components/. A soname is also not mandatory in > this case.
OK, that sounds appropriate for this package. Then, since the libraries will not be in the standard directories, should I let the binary contain the rpath, or remove it and put the directories into ld.so.conf, or do something else? -- Neil L. Roeth [EMAIL PROTECTED]
