Bugzilla – Bug 141735
Allow using Banshee with upstream RealPlayer RPMs
Last modified: 2006-11-05 12:27:54 UTC
Banshee currently uses HELIX_LIBS to find the RealPlayer libraries and sets that in the "/usr/bin/banshee" shell wrapper; the path is currently hard-coded: export HELIX_LIBS="/usr/lib/RealPlayer10" If RealNetworks releases another version, people can install it (unsupported by SuSE, of course); the RPM dependencies are still satisfied, but the Helix backend stops working unless the shell wrapper is edited. The following change would allow users to install an upstream RealPlayer RPM (e.g. the soon-to-be-released Balto version with playlists and ALSA support) and still use Banshee without manual changes: if [ -e /usr/lib/RealPlayer10/common/clntcore.so ] ; then export HELIX_LIBS="/usr/lib/RealPlayer10" elif [ -e /usr/local/RealPlayer/common/clntcore.so ] ; then export HELIX_LIBS="/usr/local/RealPlayer" elif [ -e /usr/local/HelixPlayer/common/clntcore.so ] ; then export HELIX_LIBS="/usr/local/HelixPlayer" else # Maybe there should be a warning here? fi "/usr/local/RealPlayer" and "/usr/local/HelixPlayer" are the default installation paths of the upstream RealPlayer and HelixPlayer RPMs.
I don't see how this conflicts - you can have both installed if the alternate installs to /usr/local
It's an RPM that has the same name ("RealPlayer"), so it uninstalls the previously installed one by default.
I don't think this should really be assigned to me. At my level, all I care about is having a proper RP install in HELIX_LIBS. Maybe we could install RealPlayer in a non-upstream location to avoid this. Not sure. Assigning to JP, I guess, and CCing gekker.
After thinking about this a bit, isn't it simply a set of search paths in the helix backend?
The code has changed so much in the meantime that this request doesn't apply anymore => INVALID.