Package Base Details: spotifyd

Git Clone URL: (read-only)
Submitter: bertptrs
Maintainer: bertptrs
Last Packager: bertptrs
Votes: 13
Popularity: 0.520851
First Submitted: 2018-05-28 10:44
Last Updated: 2019-08-09 11:43

Pinned Comments

bertptrs commented on 2019-04-15 12:07

New users: you may be wondering which package to use for spotifyd. If you're not sure, just use the plain spotifyd package. This installs just the features that upstream has marked as default.

If you need more features, use spotifyd-full. This package includes all optional features (that are applicable to Arch Linux).

Since there are currently 32 possible feature sets, I will be discontinuing the other variants. Both the spotifyd-pulseaudio and spotifyd-dbus-mpris are deprecated in favour of the spotifyd-full package and will be removed with a future release.

Latest Comments

« First ‹ Previous 1 2 3

bertptrs commented on 2018-06-13 16:01

@NicoHood I've tested running spotifyd-pulseaudio without libpulse installed, and quite predictably it errors out, since it cannot find the dynamic libraries.

It's probably possible to change the binary to dynamically load that library only when needed, but that's not really my forte. If anyone has a suggestion I will look into it.

Varakh commented on 2018-06-12 16:00

I did not consider that they build differently. I'll keep all of them and the bin pkg too as I use it on my Pi.

NicoHood commented on 2018-06-12 15:57

@Varakh They cannot really be merged, as they all build different.

You could argument that the -bin package is not required anymore, but it could be helpful for ARM devices (which are actually not supported by Arch Linux itself). However due to optimization and correct linkage I always prefer to rebuild the package, even if I have to wait a few hours. Building on ARM took me ~1 hour or so, but thats doable. And the makedeps are very small too. I'd go for a deletion of the-bin package

The git package should stay there. I did not review it, but you guys could do co-maintain each other.

About the conflict: You only need to conflict against the main spotifyd package. All ther conflicts are not required, unless each package has "provides" set.

@bertptrs: He updated the packages, so you can remove the conflicts. For the pulseaudio package you would then do a conflict and provide with "spotifyd". But as previously said, maybe there is no need for a split package at all :)

Varakh commented on 2018-06-12 15:35

Should we merge all spotifyd packages bertptrs? If you like, you can maintain them.

NicoHood commented on 2018-06-12 15:14

Thanks for the detailed answer, no need to delete it though.

About the pulseaudio package: Isnt it possible to build the package by default with pulseaudio support enabled (makedep), but make the backend support optional (optionaldep)? I have not tried, but it should fall back to/use by default alsa anyways? A makedependency would not hurt at all.

And I got another question about running multiple spotifyd's. Maybe you can help here too:

bertptrs commented on 2018-06-11 12:13

@NicoHood, I've created a split package for pulseaudio. The only warnings that remain are the ones concerning the unnecessary link to, and I don't know how to fix that.

NicoHood commented on 2018-06-10 11:46

Have you also considered enabling pulseaudio support?

NicoHood commented on 2018-06-10 09:30

Hi, some PKGBUILD suggestions from my side:

  • The conflict is not required, as this is the 'main' package. The other packages should rather conflict and provide against this package.
  • The git makedependency seems not to be required, even though I see some git output.

Questions: The .crates.toml, can't this get removed upstream instead? Looks weird to me, or is this normal for rust builds? I get the following 2 warnings. The first one is possibly an upstream build system problem. About the second I am not sure. Is openssl really required?

spotifyd W: Unused shared library '/usr/lib/' by file ('usr/bin/spotifyd') spotifyd W: Dependency included and not needed ('openssl')