Skip to content

Replace yay with paru#43

Closed
martinmose wants to merge 2 commits into
basecamp:masterfrom
martinmose:feature/paru
Closed

Replace yay with paru#43
martinmose wants to merge 2 commits into
basecamp:masterfrom
martinmose:feature/paru

Conversation

@martinmose
Copy link
Copy Markdown
Contributor

paru for AUR?

Sorry if this has already been discussed - and maybe there are solid reasons why yay was the chosen AUR helper.

Buuut… the original maintainer of yay has moved on and created paru.
See the Reddit post here:
https://www.reddit.com/r/archlinux/comments/jjn1c1/paru_v100_and_stepping_away_from_yay/

I’d suggest that Omarchy switch to paru.

And if the name change feels too disruptive:

alias yay=paru

😇

@martinmose martinmose changed the title feat: replace yay with paru Replace yay with paru Jul 3, 2025
@dhh
Copy link
Copy Markdown
Member

dhh commented Jul 4, 2025

Appreciate this, but I actually really like the idea that yay is feature complete and not under further development. I have more than a few bones to pick with package managers that keep "evolving" after they've solved their primary problem. So unless someone presents very compelling arguments for why paru would be a big upgrade, I'd prefer to stick with yay.

@dhh dhh closed this Jul 4, 2025
@Beethoven-n
Copy link
Copy Markdown

So unless someone presents very compelling arguments for why paru would be a big upgrade, I'd prefer to stick with yay.

i do have some comment on this.
there's been a few notable malware outbreaks on the AUR the past couple of months. the biggest way to avoid getting hit with something like that is to review the PKGBUILD so that you know what you're installing, and how it's going to install.

paru has an automatic review feature that shows you the PKGBUILDs for each package you're about to install. in combination with the bin.FileManager option and a TUI file manager of your choice, you're able to do this in a way that's much more reasonable than the raw output of the pager. that makes it a total no-brainer to me, and it's a killer feature in my opinion.

sure, it has colored diffs like some people have mentioned, but the most important thing is the mindset shift. users should be paying far more attention to what is in the packages they're installing than the omarchy-pkg scripts indicate.

@Beethoven-n
Copy link
Copy Markdown

Beethoven-n commented Sep 28, 2025

i ran into this while trying to integrate the omarchy-pkg scripts specifically into my existing workflow. i like the way they're set up, except for the fact that they're using yay instead of paru.
on my system, i'm not entirely concerned. i can just sed -i 's/yay/paru/' $GIT_DIR/omarchy/bin/* and be off, but i'm more concerned about more unsuspecting users getting attacked by malware disguised as packages they intended to install.

some examples of these attacks include this one on firefox, librewolf and zen, as well as a similar attack on ttf-ms-fonts-all, ttf-all-ms-fonts, and vesktop-bin-patched (only mentioned in the arch linux discord grumble grumble)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants