You are not logged in.

#1 2015-04-13 12:53:19

spupy
Member
Registered: 2009-08-12
Posts: 218

The Spotify PKGBUILD on 32bit systems

This is the PKGBUILD of the Spotify package in AUR.
If you look closely, you will notice that the pkgver and source get changed if you are using i686. That's because the latest version of the Spotify client for Linux exists only for 64bit systems; the rest are limited to the older version. The PKGBUILD works around that by installing the proper version of the application depending on what your system is. 

But since the 32bit version is 0.9.4 while the PKGBUILD is 0.9.17, it has an unfortunate side-effect on 32bit systems: the 'spotify' package is always considered in need to be updated. It's never up-to-date, according to pacaur, at least. I think yaourt did the same thing back when I was still using it, but I'm not really sure. 

Is this a problem with pacaur? 
Or is the PKGBUILD badly written? 
Is there even a better solution in this scenario?

Last edited by spupy (2015-04-13 12:54:35)


There are two types of people in this world - those who can count to 10 by using their fingers, and those who can count to 1023.

Offline

#2 2015-04-13 15:49:37

Alad
Wiki Admin/IRC Op
From: Bagelstan
Registered: 2014-05-04
Posts: 2,420
Website

Re: The Spotify PKGBUILD on 32bit systems

That PKGBUILD has far worse issues than the version (like some of those symlinks). But with cower you could do

cower -u --ignore=spotify

Otherwise you could use pkgbase, which is essentially multiple packages for one PKGBUILD.


Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby

Offline

Board footer

Powered by FluxBB