I decided to give up on Pamac-all. I was not the creator of this PKGBUILD, it was given to me. But as I do not have any interest in this version, I decided to orphan it.
So, if you want a supported Pamac version, just use either pamac-aur-git (development version) or pamac-aur (stable one).
You’ll still maintain the archlinux-appstream-data-pamac package though I take it?
And no worries man, thanks for taking all the time in the past to work on it. I know many users have installed it. It’s possible someone else may pick it up or it may lay drifting throughout the sands of time for a bit, who truly knows! But after yet another recent pamac issue (i won’t discuss here, it’s off topic for this thread), I myself am in the process of relying less on pacmac for searching and instead utilizing pacman more via the terminal than I used to with searching for things in pamac
It won’t be a difficult adjustment, pacman itself is pretty awesome after all, but I will miss the convenience of having a GUI for some things.
The nerd within me tells me I’m probably better off sticking closer and closer the the terminal-centric approach anyways
i know a distro uses pamac-all, i hope they can maintain it now since they are using it by default, thanks for fixing the meson issue before orphaning it @FredBezies
Edit, i switched to your pamac-aur-git package instead.
I’m using pamac as a notifier and sometimes as a search/install tool… So
I’m keeping this package alive and kicking.
Pamac-all is bigger and more complex than the classic pamac-aur-git. I just don’t have time to keep it updated
As a long time user of Archlinux (since 2009), I’ve been used to some pacman aur wrapper, such as yaourt, pacaur, trizen or yay. Graphically speaking? Kalu and Pamac.
Pamac changed its way to manage both flatpak and snap packages. I’ve done a quick fix. Rewrite half of the PKGBUILD will needed anytime soon.