Skip to content
Experimental, third-party installer for native linux spotify client
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Spotify installer README

This is an attempt to create something which installs the spotify debian package[1] in a distro independent way. The goal is to support three usecases:

  • User-only install without root privileges.
  • System-wide FHS-compliant installs in e. g., /usr/local or /usr.
  • Temporary installs used in a packaging context.



        Spotify has released a new version. There is
        some provisionary support for this in the devel branch,
        but the new version seems buggy.


        Spotify has released a new version
        no 32-bit support. There is some work needed to handle the
        new version, until that point spotify-make will not work. Stay


    Spotify has released a new version There
        is still no 32-bit build, see below. According to preliminary
        tests spotify-make works out of the box with the new version.


        Support for new version 0.9.10 available (64-bits hosts only,
        see below).


        Preliminary support for 0.9.10 available in the devel branch.
        Note that this only builds 0.9.10 for x86_64 hosts, the i386
        code is stll at 0.9.4 - this depends on upstream which havn't
        built a i386 version at this point. Testing and bugs appreciated!


There is a forum thread on spotify-make at


Either use git:

    $ git clone
    $ cd spotify-make

or download a tarball and use that:

    $ wget
    $ tar xzf spotify-make.tar.gz
    $ cd leamas-spotify-make-*


Although not based on automake in any way it's run in the same way using configure, make and make install. Some examples:

Making a user install without root privileges installs in ~/.local/share with a binary in ~/bin, downloading sources as required:

    $ ./configure --user
    $ make download
    $ make install
    $ make register
    $ ~/bin/my-spotify

Installing in system directories e. g., installing in /opt/local/lib and /opt/local/share with a binary in /usr/bin. (yes, bad example, I know):

    $ ./configure  --prefix=/opt/local --bindir=/usr/bin
    $ make download
    # make install
    # make register
    $ spotify

Installing in a temporary dir e. g. in a packaging context with all sources already in place and the % substitutions available. The --package flag disables downloading of any data from spotify.

    $ ./configure --prefix=/usr --libdir=%{_libdir} --package=%{SOURCE1}
    $ make install DESTDIR=/tmp/spotify

Other variants are possible using e. g. the --bindir or --libdir arguments to configure. Use configure -h to find out. The register target notifies system about new icons etc. To uninstall the thing:

    $ cd "The $(datadir) used when installing"
    $ make uninstall

As of now, this is just an experiment although there are successful usecases from Fedora, Ubuntu, Mageia and SUSE. There are certainly fixes needed to stabilize things though.


This is an installer, not a package. It has no automatic dependencies. That said, the configure script tries to check the buildtime dependencies and reports them as ERROR e. g.,

   $ ./configure --user
   Checking build and support dependencies
       make: ERROR: Not found

You are on your own here: you must find out the package which provides make and install it.

The Makefile tracks the runtime dependencies from spotify using ldd. It tries to symlink to existing system libraries in simple cases. This is reported as INFO: lines. Unresolved runtime dependencies in spotify is reported as WARNING: lines e. g.:

    $ make install
    WARNING; cant resolve spotify dependency:

Likewise, here you have to find the package providing and install it.

User installs

User installs have some caveats:

  • The binary is called my-spotify, to allow parallel install with a system-wide 'spotify' installation.
  • The binary is by default installed in ~/bin.
  • The desktop file and icons are installed under ~/.local/share. This is according to freedesktop specs, and most tools will find them there.
  • Some systems (notably Ubuntu/unity) requires a logout-login sequence to pickup the installation in the menus.
  • Manpage goes to ~/.local/share/man/man1. Your MANPATH will probably need an update to include $HOME/.local/share/man. Change dir with --mandir= to ./configure. Manpage isn't that useful anyway.


These files are in public domain, you can do whatever you like with them. Remember that Spotify's own terms are unclear but ATM said to be "non-redistributable, no changes permitted"

System notes


  • Works occasionally. 12.10 32- and 64-bits minimally tested. 13.10 success stories reported.
  • Bundles the correct Debian libssl0.
  • Desktop (unity) does not pick up the newly installed package until after logout-login.


  • Solves the libssl0.9.8 problem by bundling.
  • Works, both 64 and 32-bit.


  • Current spec actually Conflicts libssl0.9.8, linking to 1.0.0 seems to work OK.
  • Have some discussion about possible merging of spotify-make into current spec and installer, a fork is available [7].
  • 32-bit release 12.2 and upcoming 12.3 (Factory) minimally tested.


Minimally tested on version 2, 32-bit desktop release. Package bundles libqtdbus4-4.8.1 required by spotify; system version is 4.8.2


  • Success stories reported for Wheezy 7.0, bug fixed for 7.1 (issue #13)


  • Partial success story on CentOS 6.4 in [6]

Linux Mint

Handled the same way as Ubuntu. Version 14 32-bit minimally tested.









You can’t perform that action at this time.