-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New issues with SUSE 12.2 and newest spotify #8
Comments
Thanks. I was holding off on updating to 0.8.8 in case they released a .zip edition soon, but would still welcome a pull request introducing 0.8.8 support. |
I just tried your approach. The |
I am now working on updating the script. Hopefully should be done this weekend. See also issue #9. |
I have finished a revamp of the script, and it now works with 0.8.8. Please note the installation process has changed - see the README. |
(1) Need to update with the newest version
FNAME="spotify-client_0.8.8.323.gd143501.250-1"
(2)The script does not create /usr/share/spotify/spotify, even though the script completes successfully.
Converting .deb to .rpm using alien; this will take a few moments ...
(you can safely ignore an error from find during this step)
Warning: Skipping conversion of scripts in package spotify-client: postinst prerm
Warning: Use the --scripts parameter to include the scripts.
spotify-client-0.8.8.323.gd143501.250-1.x86_64.rpm generated
find: `spotify-client-0.8.8.323.gd143501.250': No such file or directory
Install Spotify...
Created symbolic links for Spotify library compatibility...
Create a wrapper script to include the compatibility libraries...
Spotify can now be run via /usr/bin/spotify - happy listening!
more /usr/bin/spotify
!/bin/sh
LD_LIBRARY_PATH=/usr/lib64/spotify /usr/share/spotify/spotify "$@"
but /usr/share/spotify/ is empty
I just removed the cleanup step and did:
sudo rpm -i --force --nodeps --quiet spotify-client-0.8.8.323.gd143501.250-1.x86_64.rpm
which puts the executable in /usr/bin/spotify, I did not need the wrapper.
The text was updated successfully, but these errors were encountered: