Latest RPMs does not create libSDL.so symbolic links

Hi all,
I was just wondering if the RPMs on libsdl.org are supposed to create
libSDL.so or libSDL_image.so etc type symbolic links during installation.

At the moment the only symbolic links that are created are ones named
libSDL-1.2.so.0 and libSDL_image-1.2.so.0 etc when installing the
SDL-1.2.7-1.i386.rpm for example. Except for the libSDL_ttf RPM which
seems to create a libSDL_ttf.so symbolic link.

If I am releasing a game/application for Linux which symbolic link
should I be looking for. What is the correct way to ensure that my
game/application will work on the various Linux distros? I thought the
the libSDL.so type format was the standard way of getting around
DLL/Shared Object hell. Is this not the case?

Thanks,

Dominique.

Hi all,
I was just wondering if the RPMs on libsdl.org are supposed to create
libSDL.so or libSDL_image.so etc type symbolic links during installation.

The development RPMs should, but not the runtime RPMs.
Is that not what’s happening?

See ya,
-Sam Lantinga, Software Engineer, Blizzard Entertainment