Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Thanks for sharing!

Leaning on and only waving to yay might do the reader a disservice and cause more confusion by making the context very easy to skip over, and without that it will probably just be frustrating to keep using Arch and keep treating yay like a traditional pacman-style package manager... Doing it via makepkg first gets you some understanding of "what's going on under the hood" and what's basically the same regardless of which wrapper you use. Might be a game-changer in X years whenever the community moves on to the next wrapper.

You have some cases where yay is being used to actually install repository packages (not AUR). Would recommend changing these from yay to pacman. Like from:

    yay -S mesa mesa-demos mesa-utils vulkan-intel intel-media-driver intel-gpu-tools
to

   pacman -S mesa mesa-demos mesa-utils vulkan-intel intel-media-driver intel-gpu-tools
It looks like aside from the nvidia drivers, the post is not actually installing anything from the AUR?

Could consider instead an approach like "There's this thing called AUR ([Link]). [Brief explainer]. Some people use a helper like yay([current link]) aurutils or aurch. [Proceed to show manual build-and-installation via git-clone and makepkg, as well as how to rebuild/update later]"



Thank you for the feedback! As you and other have suggested, I removed the "yay" requirement and added a brief explanation that its install instruction can be found in the other guide




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: