Re: gdk-imlib needs imlib-dev to work
On Sat, Feb 20, 1999 at 05:46:23PM -0600, Ossama Othman wrote:
> I think I've just about tracked down the `.so' link problem with
> gdk_imlib. Since gdk_imlib switched to using dynamically loadable modules
> for the different image formats, it uses a glib function called:
> I added some printfs to the module loading code and got the following:
> OSSAMA: modname --> imlib-gif
> OSSAMA: path --> /usr/lib/libimlib-gif.so
> Apparently the dynamic module loading code looks for modules ending in
> `.so' hence the reason why gdk_imlib depends on the `.so' links.
> What do you think I should do about this? Perhaps since the `.so' links
> in question are related more to run-time operation (i.e. dynamic
> loading) than development I should move them to the gdk-imlib1 run-time
> library package. Since this is a run-time issue and not a development
> issue, this shouldn't violate Debian policy, right? If it does violate
> policy, then I'd appreciate suggestions.
I think it's a bug in the upstream source: it should load the
libimlib-gif.so.whatever file to cope with future changes in the binary
interface (it's a bit tricky to do in a portable way, tough)...
You can leave the .so links of the support libraries in the runtime package,
while things change upstream.