Package Details: rmpc-git 0.4.0.r9.g02918bc-1

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.20
First Submitted: 2024-08-02 14:41 (UTC)
Last Updated: 2024-09-02 19:02 (UTC)

Dependencies (8)

Required by (0)

Sources (1)

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 running cargo 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 pkgver rmpc-git-0.4.0.r9.g02918bc-1

warning: `rmpc` (bin "rmpc" test) generated 18 warnings
error: could not compile `rmpc` (bin "rmpc" test) due to 20 previous errors; 18 warnings emitted
==> ERROR: A failure occurred in check().
    Aborting...
error: failed to build 'rmpc-git-0.4.0.r9.g02918bc-1': 
error: packages failed to build: rmpc-git-0.4.0.r9.g02918bc-1%
  • errors tldr:
# Error message
custom attribute panicked
rstest is present in `Cargo.toml` qed: Failed to get the path of the workspace manifest path.

# Files affected
src/config/keys/key.rs:186:5
src/config/keys/key.rs:245:5
src/mpd/proto_client.rs:309:9
src/mpd/proto_client.rs:318:9
src/mpd/proto_client.rs:327:9
src/mpd/proto_client.rs:343:9
src/ui/panes/album_art.rs:152:5
src/ui/panes/album_art.rs:186:5
src/ui/panes/playlists/tests.rs:108:9
src/ui/panes/playlists/tests.rs:133:9
src/ui/panes/playlists/tests.rs:159:9
src/ui/panes/playlists/tests.rs:185:9
src/ui/panes/playlists/tests.rs:202:9
src/ui/panes/playlists/tests.rs:223:9
src/ui/panes/playlists/tests.rs:240:9
src/ui/panes/playlists/tests.rs:257:9
  • Workaround - Installation via cargo works:
cargo install --git https://github.com/mierak/rmpc --locked

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

  1. I would prefer not to maintain the bin package, but i will create it at some point if nobody does.
  2. 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.
  3. aarch64 will happen when I get the time to setup prebuilt binaries aarch64 did happen as did the prebuilt binaries for next release. Armv7 maybe.
  4. The readme, fair point, putting a quick start and a bit more info in there won't hurt.
  5. The MDX files are for extended markdown. They are the source code for a static site generator named Astro. They can (and do) contain javascript so I am reluctant to just simply slap them there. There are also plain ts/js files next to them, but those could be filtered out.
  6. The PNG images alerady get optimized at build time by Astro into something more reasonable for the web so having huge pngs in the source code is fine. For example the image on the frontpage is 80kb of webp, that sounds reasonable to me.

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.

.... It is heavily inspired by ncmpcpp and ranger/lf file managers.

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:

More installation methods will come in the future.

Since rust is a "beast" and you already provide precompiled binaries on github. You could also provide a very simple PKGBUILD,

rmpc-bin

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

TITLE   TYPE    TAG NAME  PUBLISHED
v0.2.1  Latest  v0.2.1    about 13 days ago
v0.2.0          v0.2.0    about 14 days ago
v0.1.2          v0.1.2    about 1 month ago
v0.1.1          v0.1.1    about 1 month ago
v0.1.0          v0.1.0    about 1 month ago

$ gh thatlease https://github.com/mierak/rmpc v0.2.1

v0.2.1
github-actions[bot] released this about 13 days ago

  ## What's Changed

  • fix: yt-dlp ignore file extensions by @mierak in
  https://github.com/mierak/rmpc/pull/16
  • feat: handle resize events by @mierak in https://github.com/mierak/rmpc/pull/17

  Full Changelog: https://github.com/mierak/rmpc/compare/v0.2.0...v0.2.1

Assets
rmpc-v0.2.1-x86_64-unknown-linux-gnu.tar.gz  3.03 MiB
View on GitHub: https://github.com/mierak/rmpc/releases/tag/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 

arch=('x86_64')

to

arch=(x86_64 armv7 aarch64 etc)

Now finally, my biggest critic. Lack of documentation in "/usr/share/doc/rmpc/"

Ahh, well. There is a "README.md" there:

package() {
    ...
    install -Dm644 "README.md" "$pkgdir/usr/share/doc/$pkgname/README.md"
}

But then it says:

Get started

Description, configuration and installation methods can be found on the rmpc website

https://mierak.github.io/rmpc/

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,

docs/src/content/docs/index.mdx
docs/src/content/docs/overview.mdx

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

/usr/share/doc/rmpc/CHANGELOG
/usr/share/doc/rmpc/README.md
/usr/share/doc/rmpc/docs/configuration/.....md's
/usr/share/doc/rmpc/docs/guides/...lotz md's
....etc

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.