starred/spotify-player

Fork 0

mirror of https://github.com/aome510/spotify-player.git synced 2026-04-26 17:35:50 +03:00

[GH-ISSUE #902] [FEATURE] Add spotify-player-git AUR package for latest commits #544

New issue

Closed

opened 2026-03-02 23:48:32 +03:00 by kerem · 11 comments

kerem commented

2026-03-02 23:48:32 +03:00

Owner

Originally created by @bbpltergiest on GitHub (Dec 27, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/902

Describe the solution you'd like
It would be great to have a -git version of the package in the AUR, called spotify-player-git, that automatically builds from the latest commit of the main repository (https://github.com/aome510/spotify-player).

This way users could have access to the most recent fixes (like the rate limit / too many requests issue) without needing to manually build from source every time.

Describe alternatives you've considered

Manually cloning the repository and building/installing with cargo install --path . every time there's an update (very inconvenient)

Additional context
Having a -git variant would be the perfect middle ground between stability (regular package) and cutting-edge fixes (git version), which is a very common and useful pattern in the Arch ecosystem.

Originally created by @bbpltergiest on GitHub (Dec 27, 2025). Original GitHub issue: https://github.com/aome510/spotify-player/issues/902 **Describe the solution you'd like** It would be great to have a `-git` version of the package in the AUR, called **`spotify-player-git`**, that automatically builds from the latest commit of the main repository (https://github.com/aome510/spotify-player). This way users could have access to the most recent fixes (like the rate limit / too many requests issue) without needing to manually build from source every time. **Describe alternatives you've considered** - Manually cloning the repository and building/installing with `cargo install --path .` every time there's an update (very inconvenient) **Additional context** Having a `-git` variant would be the perfect middle ground between stability (regular package) and cutting-edge fixes (git version), which is a very common and useful pattern in the Arch ecosystem.

kerem

2026-03-02 23:48:32 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-02 23:48:33 +03:00

Author

Owner

@DizzyJune commented on GitHub (Dec 30, 2025):

you can just git pull inside of the repo directory instead of cloning every time. and aur helpers will build anyways so all that changes is that it updates with that aur helper 🤷

@DizzyJune commented on GitHub (Dec 30, 2025): you can just `git pull` inside of the repo directory instead of cloning every time. and aur helpers will build anyways so all that changes is that it updates with that aur helper 🤷

kerem commented

2026-03-02 23:48:33 +03:00

Author

Owner

@bbpltergiest commented on GitHub (Dec 31, 2025):

imo it's easier to just update with yay -S spotify-player-git, even if only for organizational purposes

@bbpltergiest commented on GitHub (Dec 31, 2025): imo it's easier to just update with yay -S spotify-player-git, even if only for organizational purposes

kerem commented

2026-03-02 23:48:34 +03:00

Author

Owner

@ypurpl commented on GitHub (Jan 1, 2026):

theres a spotify-player-full-git that does this, but modifies the default features. You can use paru to modify that and remember it during updates

@ypurpl commented on GitHub (Jan 1, 2026): theres a `spotify-player-full-git` that does this, but modifies the default features. You can use paru to modify that and remember it during updates

kerem commented

2026-03-02 23:48:34 +03:00

Author

Owner

@fcoelhomrc commented on GitHub (Jan 12, 2026):

+1 for a spotify-player-git package that doesn't change the defaults

@fcoelhomrc commented on GitHub (Jan 12, 2026): +1 for a `spotify-player-git` package that doesn't change the defaults

kerem commented

2026-03-02 23:48:34 +03:00

Author

Owner

@ypurpl commented on GitHub (Jan 24, 2026):

I uploaded a package that has the defaults + additional features under spotify-player-feats-git

@ypurpl commented on GitHub (Jan 24, 2026): I uploaded a package that has the defaults + additional features under `spotify-player-feats-git`

kerem commented

2026-03-02 23:48:34 +03:00

Author

Owner

@ypurpl commented on GitHub (Jan 24, 2026):

imo it's easier to just update with yay -S spotify-player-git, even if only for organizational purposes

if you use yay you can add --devel to yay -Syu and itll check development ( -git) packages along with regular system update.
paru automatically does this

@ypurpl commented on GitHub (Jan 24, 2026): > imo it's easier to just update with yay -S spotify-player-git, even if only for organizational purposes if you use yay you can add `--devel` to `yay -Syu` and itll check development ( `-git`) packages along with regular system update. `paru` automatically does this

kerem commented

2026-03-02 23:48:34 +03:00

Author

Owner

@bbpltergiest commented on GitHub (Feb 7, 2026):

mb for the delay, tysm for it !!

imo it's easier to just update with yay -S spotify-player-git, even if only for organizational purposes

if you use yay you can add --devel to yay -Syu and itll check development ( -git) packages along with regular system update. paru automatically does this

@bbpltergiest commented on GitHub (Feb 7, 2026): mb for the delay, tysm for it !! > > imo it's easier to just update with yay -S spotify-player-git, even if only for organizational purposes > > if you use yay you can add `--devel` to `yay -Syu` and itll check development ( `-git`) packages along with regular system update. `paru` automatically does this

kerem commented

2026-03-02 23:48:34 +03:00

Author

Owner

@bbpltergiest commented on GitHub (Feb 7, 2026):

imo it's easier to just update with yay -S spotify-player-git, even if only for organizational purposes

if you use yay you can add --devel to yay -Syu and itll check development ( -git) packages along with regular system update. paru automatically does this

will you continue to maintain and update it, or does this process happen automatically in some way?

@bbpltergiest commented on GitHub (Feb 7, 2026): > > imo it's easier to just update with yay -S spotify-player-git, even if only for organizational purposes > > if you use yay you can add `--devel` to `yay -Syu` and itll check development ( `-git`) packages along with regular system update. `paru` automatically does this will you continue to maintain and update it, or does this process happen automatically in some way?

kerem commented

2026-03-02 23:48:34 +03:00

Author

Owner

@ypurpl commented on GitHub (Feb 7, 2026):

The one I uploaded?

Since it uses the latest commit it's automatic. I also use it myself so I will maintain it

@ypurpl commented on GitHub (Feb 7, 2026): The one I uploaded? Since it uses the latest commit it's automatic. I also use it myself so I will maintain it

kerem commented

2026-03-02 23:48:34 +03:00

Author

Owner

@bbpltergiest commented on GitHub (Feb 7, 2026):

alright good thanks!

@bbpltergiest commented on GitHub (Feb 7, 2026): alright good thanks!

kerem commented

2026-03-02 23:48:34 +03:00

Author

Owner

@bbpltergiest commented on GitHub (Feb 7, 2026):

for reference: https://aur.archlinux.org/packages/spotify-player-feats-git

@bbpltergiest commented on GitHub (Feb 7, 2026): for reference: https://aur.archlinux.org/packages/spotify-player-feats-git

kerem referenced this issue

2026-03-14 14:07:00 +03:00

[GH-ISSUE #544] The Spotify generated Daily Mix playlists don't update #1249

kerem referenced this issue

2026-03-14 14:07:21 +03:00

[GH-ISSUE #544] The Spotify generated Daily Mix playlists don't update #1249