MPV Player 0.35.1 Released With Wayland & PipeWire Fixes

[Adventurer_Kun]

gentlemen, is it possible to move the hotkey notification to another place on the screen? it is a certain line and not all lines.
on the example of this line
f1 show-text "audio-exclusive on" ; apply-profile "audio-exclusive on"

[geearf]

Best way still is to join the IRC(#archlinux on libera.chat) and ask if there is any chance to become a maintainer. Tell them what you want to push to the repo, what you additionally can/want to maintain:

• Orphaned
• Out-Of-Date

And later on who you are (I'm sure they will ask :P)

Awesome, thank you!

[lumks]

What's the proper path for this?

Best way still is to join the IRC(#archlinux on libera.chat) and ask if there is any chance to become a maintainer. Tell them what you want to push to the repo, what you additionally can/want to maintain:

• Orphaned
• Out-Of-Date

And later on who you are (I'm sure they will ask :P)

[geearf]

I think you still need to be on the AUR. But for the lookup process you only need to show that you're trustworthy and can do work with packaging, conflict resolving and such stuff. Your PKGBUILDs/packages will for some time still be validated by a "senjor"-maintainer at least before they go to the repo.

What's the proper path for this?
I've been maintaining a few AUR packages for years and would like to have some pre-built for my users.
Years ago I contacted some TU or devs about that for 1 package but never got a single reply.

[Quackdoc]

Maybe Tumbleweed with your own repo in OBS (OpenSUSE Build Service) for your custom builds?

I am very unfamiliar with suse outside of a couple of hours using it and debugging a specific application, so I will for sure jot this down

[dwagner]

I for one have largely no reason to complain about Arch'es update speed. Sure, if you have a special interest in the bleeding edge version of some application (like I actually have for 'mpv'), then I compile the application on my own from the source code - NOT replacing the version I got with Arch, but putting it in /usr/local.

And on more than one occasion I was happy that I could easily run /usr/bin/mpv instead of my bleeding-edge /usr/local/bin/mpv, because sometimes bleeding edge is buggy and you do not have time immediately to fix the bugs.

Regarding the speed of adoption of ksomething applications - that was at times "too fast" for my taste. "kdenlive", for example, was updated to the "rewritten" version at a time when it was way too unstable and lacked relevant features the older version had. Luckily, "kdenlive" did mature again since then, but for quite a while I needed to retain a much older version to be able to work on video projects.

IMHO there is no comparison to Fedora - Fedora is not giving you the same freedom of choices what software to use if there are competing implementations.

[Berniyh]

Because Arch maintainers do not bother. It has been a problem with Arch for years. Too many developers simply do not care for the project and are only involved for their self-serving reasons, while they refuse to let in new people to replace them. Many packages take too long to get an update. The only thing you can count on Arch to have in its repos immediately is KDE, everything else may take even many months before it gets updated.

Take for example Netbeans, an IDE i like personally. It is still version 14 in the repos, version 16 upstream. Hasn't been updated for half a year. They just don't see anything wrong with that. They have become Ubuntu.

Those people have lives, too, you should respect that.

If you think you can do better, feel free to step in, but also be ready to take the blame when something bad happened and you were responsible.
i.e. because you bumped something to quick or you didn't test it properly.
I've been doing packaging (although not on Arch) for more than 10 years now, trust me, I know what it takes and how badly you can mess up …

Also, my experience with Arch packages really isn't what you described. Most packages are updated relatively soon after a release, not only KDE, but most other packages as well.

[Berniyh]

Because Arch isn’t rolling release.

Uhm, what???

[evasb]

I'm eyeing OpenSUSE Tumbleweed too.

The problem is the many Arch users like me won't do the jump because they maintain packages on AUR and learning OBS, remaking all the scripts is tedious.

I would love to see some tool to "convert" PKGBUILDs to .spec files.

[openminded]

Besides flipping the ownership of those two distros, Rawhide and Tumbleweed aren't comparable at all in terms of stability / suitability as a daily driver for the overwhelming majority of people.

Esp Rawhide. Last time I checked, their kernel update policy was quite venturesome, to say the least. Using RC kernels isn't what laypeople would want.