Dynamically linked SFML on Fedora

[pdinklag]

I recently tried to run SFML on Fedora 17, only to get an error that I was missing libjpeg8. The problem here is that the Fedora repositories do not maintain libjpeg but only libjpeg-turbo, hence I had to grab it from an external source as an RPM package.

Now the SFML build I tried is one that I linked on an Ubuntu system, where I linked against libjpeg. The API of libjpeg-turbo is downward-compatible to that of libjpeg, so in theory, it should all just be fine. However, the package name is different, and that's where the problems begin

Is there any way I can link SFML (or modify the shared objects) so that both libjpeg and libjpeg-turbo are supported? Or will I have to link specifically against libjpeg-turbo to make things work for Fedora?
Do the SFML build scripts have any special rules for this, btw?

[Laurent]

I think it's your distribution that should create a link libjpeg -> libjpeg-turbo, so that all applications linked against libjpeg can work out of the box. I don't think that every library should have a special rule because some distribution has a jpeg lib with a different name.

[pdinklag]

OK, good to know.
I'm surprised nobody seemed to have tried this on Fedora yet, because I'm sure they would have had the same issue. Either a lucky incidence or I'm doing something terribly wrong.

[Laurent]

There has to be a simple official solution. I can't believe they would live with such a difference.