Open Rigellute opened 5 years ago
I use ubuntu 18.04 and I can install the lastest spotify-tui
with following command; snap install spt --channel edge
.
To install through snap
, no configuration is required and I think this is easy enough for ubuntu users (Sorry, I have never used other distributions and I do not know about them). Or, woud you like to use other package manager like apt
instead of snap
?
Made a start in #161.
Thank you both for this info.
I made a copr repository for Fedora containing spotifyd
and spotify-tui
as an alternative to using snaps, intended for personal use, and plan to keep it recent. But feel free to use the SPEC as a template or start for building your own RPMs.
It can be installed after a dnf copr enable zeno/spotify-rust
with dnf install spotify-tui
.
I am the package maintainer for the spotify-tui nix package (nix is the package manager used by NixOS). I will keep the package there up to date as long as I can. The package is currently in the unstable channel of Nix and is added to the stable channel when a new stable channel version comes out.
The nix package manager can be used on all distributions.
For Archlinux, there is already a package maintained in the AUR (Archlinux user repository). I am not the maintainer, but here is the link. It is kept updated fairly regularly. I would guess that version 0.10.0 will be updated soon.
Awesome, thanks @zenofile @jwijenbergh and @trames57 .
Please feel free to add the installation instructions for these package managers to our README.
I'll start to work on the flatpak version.
@Odilhao have you started working on it? I'm looking into learning Flatpak packaging and would be interested in helping!
Update: I'm no longer interested in this.
I noticed SPT is not actually pushed to snap stores from commits here? Is there any interest in this?
I've been interested in it, but Alan Pope (@popey) uploaded it originally, and I'm not sure how it would be able to transfer to another maintainer.
Aivree,
I can talk to Alan, about it. If you are interested I'd be happy to take it on.
On Wed, Jan 29, 2020 at 4:38 PM Aivree notifications@github.com wrote:
I've been interested in it, but Alan Pope (@popey https://github.com/popey) uploaded it originally, and I'm not sure how it would be able to transfer to another maintainer.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Rigellute/spotify-tui/issues/160?email_source=notifications&email_token=ABMJBTN4ZEDXVLQBIJYHVMDRAIHPTA5CNFSM4JQRO6N2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKJFGXY#issuecomment-580014943, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMJBTPEZ6IVCQLCEM26TK3RAIHPTANCNFSM4JQRO6NQ .
-- Regards,
Carlos Hernandez
@Odilhao have you started working on it? I'm looking into learning Flatpak packaging and would be interested in helping!
I've already started to work on it, just commited this repo , I'm trying to set the PATH with the installation, after that I'll send one PR to the upstream flathub.
@AivreeG @hurricanehrndz happy to transfer spt over to an upstream developer. Just let me know who has the account, and I'll put the request in to transfer it :D
Apologies for not updating the snap, this was an error in my monitoring / build system. It should be up to date now and will be kept up to date.
Hey folks, There's a pending dispute/transfer request (filed Feb 8th) by someone who looks like @hurricanehrndz . Are you (people from the spotify-tui project, potentially @Rigellute) OK with him owning the snap package? do you want someone else to own it?
Let me know.
Thanks @Roadmaster. Fine by me!
@Rigellute,
Once the transfer is complete, I will re-release you're last release. From there on workflows can do release into the beta channel.
Windows: https://scoop.sh/
Would love to use scoop
, contributions for setting it up are very much appreciated!
Would love to use
scoop
, contributions for setting it up are very much appreciated!
I'm somewhat familiar with it (I tried to add Cronical, but it integrates with the Windows system very closely with admin permissions and the way it does that would be user-configurable and ...), if I you ping me once a week, I might have the time and mood to do everything.
I'm not exactly sure, if spotify-tui should go to the main or extras bucket The questionable criteria are:
note to self: if I do get around adding spotify-tui, add id.ee as well (got to have the national pride of somewhat broken security)
Maybe on Windows for chocolatey as well? https://chocolatey.org/docs/create-packages
Maybe on Windows for chocolatey as well? https://chocolatey.org/docs/create-packages
https://github.com/lukesampson/scoop/wiki/Chocolatey-Comparison
In addition, I'm not familiar with packaging to Choco.
I beg your pardon. Here is my scoop bucket with spotify-tui
https://github.com/littleli/scoop-garage
I don't think it belongs to the main
bucket. Maybe scoop-extras
, or even create your own bucket, it's fairly easy.
Nice one @littleli! Are you able to make a pull request adding your work to this repo?
Nice one @littleli! Are you able to make a pull request adding your work to this repo?
I would suggest:
scoop-bucket
managed by you, you can reuse it eventually for your other projects you want to be installable this wayspotify-tui
manifest in the repospotify-tui
repoThe reason for (1) is that scoop uses git as a distribution mechanism, so manifests should be in general in separate repos (buckets) without source code.
@littleli thanks again, are you able to look over this repo and see if it's all good? https://github.com/Rigellute/scoop-bucket
Feel free to add to the docs
Looks good. Also see this PR with the first version bump.
Winget is the new package manager for Windows 10 and Windows 11 https://github.com/microsoft/winget-cli
Winget is the new package manager for Windows 10 and Windows 11 https://github.com/microsoft/winget-cli
Would love to see this on Winget! Packages can be submitted via the winget-pkgs repo.
@russellbanks
It seems standalone executables (including zipped ones) are not yet supported. Quote from the project description:
Note: At this time installers must either be MSIX, MSI or .exe application installers. Standalone or portable executables, > compressed .zip files, and fonts are not currently supported.
@russellbanks
It seems standalone executables (including zipped ones) are not yet supported. Quote from the project description:
Note: At this time installers must either be MSIX, MSI or .exe application installers. Standalone or portable executables, > compressed .zip files, and fonts are not currently supported.
Couldn't we create an installer for this program with a utility such as Inno Setup? One example of a project that has done this is Onefetch where they used a workflow to create an installer for their Rust project using Inno Setup, which was then able to be submitted to winget-pkgs.
@russellbanks
It seems standalone executables (including zipped ones) are not yet supported. Quote from the project description:
Note: At this time installers must either be MSIX, MSI or .exe application installers. Standalone or portable executables, > compressed .zip files, and fonts are not currently supported.
Winget 1.3 is now released as stable (release notes) and the headline feature might be support for portable/standalone apps. I think they implemented it so that winget automatically adds whatever shims it wants to as if it was e.g. MSIX installed.
Winget 1.3 is now released as stable (release notes) and the headline feature might be support for portable/standalone apps.
This is only standalone .exe
files at the moment. Support for zipped files are coming in Winget 1.4.
If anyone knows how we can use the various package managers, please let me know!