Wrapper: Generic Spotify-Binary

[SecUpwN]

Hey @pcworld, can you help me out with a quick fix? I am currently testing our script on openSUSE using the latest Spotify. Because Spotify is not yet officially available for openSUSE, I am using Spotify-Make which works awesome for a hassle-free install and provides the latest Spotify binary.

The only difference is the name, by which spotify starts: When using mentioned compilation method, the output filename of the Spotify binary is called my-spotify located in $HOME/bin/ - but our spotify-wrapper.sh tries to call just spotify. How to change this part of our code spotify "$@" > /dev/null 2>&1 & into a generic variable which calls the Spotify binary, no matter what it is named?

EDIT: This solution works: $HOME/bin/*spotify "" > /dev/null 2>&1 &. Issue closed for now.

[SecUpwN]

Reopened this Issue because I'd like to implement a universal fix for people like me who install their Spotify through Spotify-Make. I've solved the Issue for myself, but certainly that is no universal way to check if the Spotify script has been renamed to other names (in this specific case my-spotify). Would you please see if above solution can be improved, @OlegSmelov and @Feltzer? I see that you're still closely following our project here and I want to THANK YOU for your awesome help in maintenance! 👍

UPDATE: The solution was actually already in our own README. Closing this Issue again.

You can create a symbolic link, if necessary (e.g. linking my-spotify to spotify if you are using the user installation of spotify-make).