FYI: yay is no longer maintained (Untrue! See response here). Use paru instead Consider paru as an alternative option; it’s written in Rust and has better version tracking for *-git packages (won’t miss upgrades if the AUR version isn’t tracked, won’t do pointless upgrades if the AUR version changes but HEAD remains unchanged)
Huh! I appear to have fallen victim to misinformation. I stand corrected and I apologize for not properly confirm such a strong claim before repeating it like that.
I suppose a more accurate way to put it is that yay has been slower to adopt new features (e.g.: yay#336 vs paru#260), but otherwise remains a current and well-maintained piece of software.
I was about to throw my computer out the window when you said that because I literally just implemented a bunch of ansible playbooks using yay to configure my machines and after yogurt et. al. being abandoned, I couldn’t take another change. Not yet. I’ll check out paru at some point though.
FYI:
yayis no longer maintainedUseConsiderparuinsteadparuas an alternative option; it’s written in Rust and has better version tracking for*-gitpackages (won’t miss upgrades if the AUR version isn’t tracked, won’t do pointless upgrades if the AUR version changes but HEAD remains unchanged)The latest release of
yaywas 3 weeks ago. Where are you seeing that it’s not maintained anymore?Huh! I appear to have fallen victim to misinformation. I stand corrected and I apologize for not properly confirm such a strong claim before repeating it like that.
I suppose a more accurate way to put it is that
yayhas been slower to adopt new features (e.g.: yay#336 vs paru#260), but otherwise remains a current and well-maintained piece of software.I was about to throw my computer out the window when you said that because I literally just implemented a bunch of ansible playbooks using
yayto configure my machines and afteryogurtet. al. being abandoned, I couldn’t take another change. Not yet. I’ll check outparuat some point though.