Arch Linux User Repository

@IslandC0der , Sorry for taking the nuclear rout, I wasn't trying to steal it away from you. I'm surprised you haven't been receiving my emails, seeing as I've sent out multiple. Here's the first one of the few I've sent you over the past months (typos and all, lol.) I've reviewed your PKGBUILDs and they're perfect. You're a bit mistaken about the Arch packagers changing the packaging scheme, x11extras was deprecated entirely by the QT devs.

Greetings, @Rustmilian!

I'm afraid I haven't received any email from you, have you left a comment somewhere? I used to be missing notifications for some packages I've adopted, since they don't get enabled automatically; I thought that was fixed, but in any case, please point me to the packages where you left the comments, so I can promptly rectify that issue.

Anyways, as I'm sure you know, there have been some rapid developments with Qt6 in KDE, which results in dependencies quickly changing as the changes ripple downstream. When I was porting everything to Qt6, I saw that the Qt6 counterpart of qt5-x11extras didn't exist yet (some people also mentioned it in the comments), so I was working on creating that package, until I eventually realized the Arch packagers had changed that packaging scheme entirely.

With this in mind, consider flagging the packages as out-of-date next time, instead of jumping straight to submitting an orphan request with a message like "I have a fix". Simply sharing the easy fix on an out-of-date message would've saved everyone a lot of time and headaches.

I understand you're probably eager to contribute, but this is supposed to be an open-source, collaborative effort; not a rush to find fixes, keep them close-sourced, and then using them as leverage to take over packages. I mean, I'd have been more than happy to add you as a co-maintainer, had you just asked... No need to go the nuclear route!

But regardless, I'm pretty confident I've addressed those remaining problems now, as the packages seem to be building again with the updated dependencies; but please do let me know if I've missed anything.

@dr460nf1r3

I've got notifications enabled for all of the packages I've requested for, you can contact me here and I will be notified. Just wouldn't rather give my email out atm, it'll be added eventually.

Don't worry, I'm not going to go MIA without first disowning the packages if it comes to it at any point, that's a promise.

I have already reached out to @IslandC0der aka João Figueiredo, @pmattern & @Zan aka Zanny months ago as well as recently about their packages and got no response.

I've been working to fix these and many more for the past few days. Seeing as @IslandC0der had made changes recently but didn't actual fix the packages properly I had hopped it'd grab his attention when my emails & others comments failed too, if he doesn't get to them in time the packages will eventually move to me. If they do I'll be sure to double and triple check they work before pushing.

Lastly its safe to say @pmattern is MIA. while @Zan is pretty inactive and slow at maintaining the packages to the point their basically MIA on a few of them (how now I'm the maintainer of this one) & their PKGBUILDs aren't exactly high quality having a v in the version number, etc.

My PKGBUILDs are more in line with other maintainers.

The deletion requests were done by mistake, sorry about that. I only meant to do the orphan requests.

You might want to put an email into your contributions as there is no way to contact you but commenting here. What were you thinking when filing the deletion/orphan requests for several kde-git packages? All of these are actually maintained and instead of just filing those requests you could've easily commented the supposed fix. That is not how AUR works.

@davispuh Builds now.

Doesn't build anymore. Need to add -DQT_MAJOR_VERSION=6 CMake option now.

I had to install gperf to compile kcodecs-git.