I think you might just be making things up and regurgitating them half-chewed.
If you had done an ounce of research into this subject you might realize that KDE has much the same opinion on packagekit as Arch does - it doesnt work on arch, dont use it.
I dont expect, and certainly see no movement, to somehow ‘rectify’ that situation.
packagekit itself is simply not a good solution - in whatever form.
Or what … you think … KDE is going to create a new framework just for Arch … and then Arch will adopt that?
I really dont know how your logic is working here.
Discover is fine for widgets, themes, and other such things got through the API of store.kde.org (pling) … but is absolutely not supported, not working, and not secure, for system package management on Arch and Arch based distros.
Pamac isnt the best choice … in either its previous or current form … but discover is not the answer.
I meant a complete new backend to add to Discover, like how Pamac does it, they already did it together with Fedora devs for system upgrades so why not for Archlinux or Manjaro where new Pamac support was restricted to only GNOME desktop.
https://pagure.io/fedora-kde/SIG/issue/3#comment-848145
…that is packagekit.
…If somehow the KDE Devs create or incorporate a way to handle ALPM … then sure … I just dont get where you got the idea that is likely to happen … or even more incredibly … that the KDE Devs are going to work to create a new packaging framework that Arch or Manjaro will adopt.
You can believe what you want to believe I guess.