

8·
7 days agoAnd just to be very explicit why this is an issue: each time the package is upgraded through an automated update, the PKGBUILD may change (e.g. to adapt to different dependencies, file structure, etc introduced with new app version).
That also means an AUR maintainer can smuggle in malware with any of those updates, even if you checked the original PKGBUiLD when you installed. And, anyone can request taking over maintenance for unmaintained packages, so it can even happen if the original maintainer was benevolent.
Always check PKGBUILD files on upgrade, even if just a glance. If I remember correctly yay had a function to always show you PKGBUILD diffs before updates, not sure if that was automatically enabled.
While I do think the underlying pushes to per-wafer density will no doubt lead to cheaper memory prices per capacity, unfortunately I believe the vast majority of the over production in the near term won’t be useful for the consumer market since it’s all going into HBM right now and not modular sticks like the typical DDR SDRAMs.