[GH-ISSUE #1106] Homebrew installer marked as deprecated #517

Open
opened 2026-02-28 14:49:38 +03:00 by kerem · 5 comments
Owner

Originally created by @kcirtapfromspace on GitHub (Oct 30, 2023).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/1106

Looks like in homebrew spotify-tui is marked as deprecated. Is this true?

Originally created by @kcirtapfromspace on GitHub (Oct 30, 2023). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/1106 Looks like in homebrew spotify-tui is marked as deprecated. Is this true?
Author
Owner

@sewnie commented on GitHub (Oct 30, 2023):

yes. if you look at the code page you can see that there have been no commits since 2021. this project is considered abandonware.

consider https://github.com/aome510/spotify-player/releases

<!-- gh-comment-id:1785451531 --> @sewnie commented on GitHub (Oct 30, 2023): yes. if you look at the code page you can see that there have been no commits since 2021. this project is considered abandonware. consider https://github.com/aome510/spotify-player/releases
Author
Owner

@monfresh commented on GitHub (Oct 31, 2023):

While it's true that there haven't been any commits in a couple of years, the reason why Homebrew marked spotify-tui as deprecated is because it uses OpenSSL 1.1, which has been deprecated. You can see this by running brew info spotify-tui.

<!-- gh-comment-id:1787718409 --> @monfresh commented on GitHub (Oct 31, 2023): While it's true that there haven't been any commits in a couple of years, the reason why Homebrew marked spotify-tui as deprecated is because it uses OpenSSL 1.1, which has been deprecated. You can see this by running `brew info spotify-tui`.
Author
Owner

@ed9w2in6 commented on GitHub (Nov 27, 2023):

@apprehensions Although I appreciate your effort in moving users to an actively maintained alternative with a certain level of feature parity, I disagree with your classification as abandonware, especially when the program still works and that the author is reachable.

As @monfresh have said the deprecation marking should be due to OpenSSL in which it will only affect builds. It can be fixed by running cargo update (ref: https://github.com/Rigellute/spotify-tui/pull/1041).

<!-- gh-comment-id:1827375584 --> @ed9w2in6 commented on GitHub (Nov 27, 2023): @apprehensions Although I appreciate your effort in moving users to an actively maintained alternative with a certain level of feature parity, I disagree with your classification as abandonware, especially when the program still works and that the author is reachable. As @monfresh have said the deprecation marking should be due to OpenSSL in which it will only affect builds. It can be fixed by running `cargo update` (ref: https://github.com/Rigellute/spotify-tui/pull/1041).
Author
Owner

@akankov commented on GitHub (Mar 5, 2024):

Any plans to fix this?

<!-- gh-comment-id:1978276610 --> @akankov commented on GitHub (Mar 5, 2024): Any plans to fix this?
Author
Owner

@ed9w2in6 commented on GitHub (Mar 5, 2024):

@akankov Try if https://github.com/Rigellute/spotify-tui/pull/1041 fix the build process for you, if it does maybe give this a reaction to push the author to merge it.

<!-- gh-comment-id:1978613020 --> @ed9w2in6 commented on GitHub (Mar 5, 2024): @akankov Try if https://github.com/Rigellute/spotify-tui/pull/1041 fix the build process for you, if it does maybe give this a reaction to push the author to merge it.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify-tui#517
No description provided.