Search Criteria
Package Details: rmpc-git 0.4.0.r9.g02918bc-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/rmpc-git.git (read-only, click to copy) |
---|---|
Package Base: | rmpc-git |
Description: | A beautiful and configurable TUI client for MPD |
Upstream URL: | https://mierak.github.io/rmpc/ |
Licenses: | BSD-3-Clause |
Conflicts: | rmpc |
Provides: | rmpc |
Submitter: | mrk |
Maintainer: | mrk |
Last Packager: | mrk |
Votes: | 1 |
Popularity: | 0.22 |
First Submitted: | 2024-08-02 14:41 (UTC) |
Last Updated: | 2024-09-02 19:02 (UTC) |
Dependencies (8)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR, glibc-eac-rocoAUR)
- cargo (rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup-stubAUR, rust, rustup) (make)
- git (git-gitAUR, git-glAUR) (make)
- ffmpeg (ffmpeg-nvcodec-11-1-gitAUR, ffmpeg-amd-full-gitAUR, ffmpeg-cudaAUR, ffmpeg-full-gitAUR, ffmpeg-gitAUR, ffmpeg-fullAUR, ffmpeg-decklinkAUR, ffmpeg-headlessAUR, ffmpeg-amd-fullAUR, ffmpeg-libfdk_aacAUR, ffmpeg-obsAUR, ffmpeg-ffplayoutAUR) (optional) – for youtube playback
- python-mutagen (python-mutagen-gitAUR) (optional) – for youtube playback
- ueberzugpp (optional) – for alternative album art method
- yt-dlp (yt-dlp-gitAUR) (optional) – for youtube playback
Latest Comments
mrk commented on 2024-12-03 22:29 (UTC)
I tried installing with
paru -S rmpc-git
,yay -S rmpc-git
as well as building in a clean chroot as described in the wiki and all of them succeeded. The pkgbuild does not do anything special other than runningcargo test --release --frozen
, which also happens in CI. So I really have no idea how to resolve the issue as I cant seem to reproduce it.dendarrion commented on 2024-12-03 15:58 (UTC)
Installing with
paru -S rmpc-git
fails to build for pkgverrmpc-git-0.4.0.r9.g02918bc-1
mrk commented on 2024-08-10 11:36 (UTC) (edited on 2024-09-06 23:45 (UTC) by mrk)
Hi, thank you for your kind words. To address your points
The comments you see there are generated by Github from commits on master. I will see if I can somehow automate putting them into a changelog file.Changelog was added.aarch64 will happen when I get the time to setup prebuilt binariesaarch64 did happen as did the prebuilt binaries for next release. Armv7 maybe.m040601 commented on 2024-08-10 05:18 (UTC) (edited on 2024-08-10 05:28 (UTC) by m040601)
Thanks for creating this tool and coming here to the Arch to register for providing the PKGBUILD.
Yeahh. That's what really caught my attemption. I'm a long long time power user of mpd/cli clients. Really eager to try this out thoroughly and provide you feedback. There is not much "competition" or "evolution" for ncmpcpp. Development seems to have stalled.
Really nice to see someone working on this kind of tools for heavy command line users/fanatics.
Here are some of my preliminary comments and suggestions:
Since rust is a "beast" and you already provide precompiled binaries on github. You could also provide a very simple PKGBUILD,
Very simple PKGBUILD. Just pulls and copies whatever you have release on github.
Some users might not wish to download the megabytes of rust tools just to compile this.
$ gh thoseleases https://github.com/mierak/rmpc
$ gh thatlease https://github.com/mierak/rmpc v0.2.1
Ahh. Very nice you provide some comments. But you should really provide a "CHANGELOG" text file next to the "README.md". Nice to keep up for the end user if this tool is gonna have a long future.
Assets. There is only x86. I assume you are using Github free infrastructure to build the binaries.
It would be very very useful if you could provide arm binaries for small less powered systems like the Chromebooks, Raspberry etc. It is not feaseable to compile there. But thery are excellent as mpd clients.
You would then change the PKGBUILD
Now finally, my biggest critic. Lack of documentation in "/usr/share/doc/rmpc/"
Ahh, well. There is a "README.md" there:
But then it says:
What ? So the README says to go somewhere else ? This doesnt make any sense. You use a terminal tool and have to open web browser and go online for learning how to use it ?
You already have lots of those "mdx" files for generating the website,
I'm not familiar with all these javascript build tools. (built with "Astro" ??)
But I assume they are almost like simple markdown files. Simple to read on the offline computer. No tool needed. No need for complicated things now. Maybe in the future you will have a proper man pages. But for now it would be more than sufficient if you could make sure they all land on
Something like that.
Also, my personal opinion. Dont put the "png" and images there. They are just too big. Even for the website. Maybe you should try some tool to optimize and reduce the size of those huge "png" images.
Thanks in advance.