xbps VS mpv

I wrote the ignorepkg feature for xbps, specifically for cases like this. https://github.com/void-linux/xbps/pull/62

xbps-remove -O: this deletes outdated packages from the cache, the confusion probably comes from that it does not remove packages that are not installed anymore. I have an open PR for xbps to implement cleaning packages that are not installed anymore uptodate. https://github.com/void-linux/xbps/pull/530

More info about xbps flags can be found on the respective man pages and on the xbps github

This is knowwn bug of xbps without released fix as for now https://github.com/void-linux/xbps/issues/312.

void-linux/xbps/issues/57 is the issue to follow, but i doubt it will happen soon...

BUGS Probably, but I try to make this not happen. Use it under your own responsibility and enjoy your life. Report bugs at https://github.com/void-linux/xbps/issues

mpv and the xbps package manager both come to mind. I read them casually and found them very easy to grasp.

It’s the default package manager used by Void Linux. It’s praised for being fast and reliable. more info

And here is the commit removing all references to the old name in xbps https://github.com/void-linux/xbps/commit/ba296b8e2c30f151417f0f0daa935653aacd3238

So for context, I'm attempting to port the xbps to another distro that isn't Void Linux using the instructions over at https://github.com/void-linux/xbps.

https://mpv.io/ has yt-dlp support, if yt-dlp is installed you just need to throw the URL at it and it plays the video (without download).

See https://github.com/mpv-player/mpv/issues/9053

I apologise for not following procedure. I am in the middle of building mpv 0.37 from source. Irrespective of the outcome I will document what I had to do in addition to the instructions on mpv.io and if the problem perststs, where it happens and where not with kernel version, mpv version taken from the screen, and the terminal output.

Use MPV. Partticularily shinchiro's builds. Extract the folder where you want its installation directory to be, if you decide to install it. Otherwise, just drag and drop files on top of its window or executable.

Author of ripgrep here.

Like automatic encoding detection and transparently searching UTF-16?

Or simple ways for composing character classes, e.g., `[\pL&&\p{Greek}]` for all codepoints in the Greek script that are letters. Another favorite of mine is `\P{ascii}`, which will search for any codepoint that isn't in the ASCII subset.

Or more sophisticated filtering features that let you automatically respect things like gitignore rules.

Those are all things that ripgrep does that grep does not. So I do not favor this explanation personally.

ripgrep has just about all of the functionality that GNU grep does. I would say the two biggest missing pieces at this point are:

* POSIX locale support. (But this might be a feature[1].)

* Support for "basic" regexes or some equivalent that flips the escaping rules around. i.e., You need to write `\+` to match 1 or more things, where as `+` will just match `+ literally.

Otherwise, ripgrep has unfortunately grown just about as many flags as GNU grep.

[1]: https://github.com/mpv-player/mpv/commit/1e70e82baa9193f6f02...

- https://github.com/mpv-player/mpv/issues/8692

https://mpv.io played it without fuss.