You are not logged in.
It's 2025, can't a system wide upgrade be done in the background after just one command and initial sudo request.
Am I supposed to stare at the terminal while it updates? What in the world , do we have to submit password numerous times?
Please, it's frustrating, I know this stuff is open source, but it really sucks.
Offline
By the nature of what yay does it has to spawn distinct subprocesses, it has a sudoloop option you'll garner from their man page/help output you can also save persistently with the --save option.
2025 and peope can't even read the manpage of the tools they are using that really sucks smh ... and FWIW since the timeout mostly happens after compilation, yes you are somewhat expected to be doing that at the very least with the PKGBUILDs since they are unvetted and potentially malicious.
Moving to AUR issues
Last edited by V1del (2025-01-26 19:40:17)
Offline
Am I supposed to stare at the terminal while it updates?
as you're likely building from source - YES, you ARE
another option: use a different AUR helper which first gets the source - compiles it - puts it in a repo - and then you can call pacman just once
or you can look if the package you seem to keep building has a -bin substitued - which simply gets a pre-built binary, repacks it into a arch package and passes it to pacman
so - although there'Re several options - NO, you are NOT supposed to "unlock" your system to what every script and have that run in the background for hours - that's what these timeouts are in place for - same as for why you'Re not supposed to run makepkg or yay as root / via sudo in the first place
Offline
It's 2025, can't a system wide upgrade be done in the background after just one command and initial sudo request.
Am I supposed to stare at the terminal while it updates? What in the world , do we have to submit password numerous times?
Please, it's frustrating, I know this stuff is open source, but it really sucks.
instead of complaining, why don't you do something about it? make a fork of yay that allows sudo and thus doesn't need your password to install any packages
Offline
To be frank, yay's setup is somewhat smart in that all PKGBUILD checking will have happened by the time it starts compiling, so if you don't run into a compilation error and did your due diligence in verifying the PKGBUILD does what it's supposed to, there's really not much harm in having the sudoloop option enabled so this happens without being asked again (caveat, since to sudoloop is running and needs to keep your cached credentials alive, there's a potential danger that a third party/drive by could get root access by canceling yay/5mins after installation has completed) so don't forget to lock if you leave it unattended in a space where access could happen)
Offline
sudoloop won't help against https://bbs.archlinux.org/viewtopic.php … 2#p2206312 ?
Or does yay then intercept the password and use sudo -S?
None of that however changes anything about the AUR not being a trusted source and therefore "running yay as sudo and leave the system alone for an hour" is as dumb in 2025 as it was in 2020 or 2010 and you're then as now required to read https://wiki.archlinux.org/title/Arch_User_Repository and https://wiki.archlinux.org/title/AUR_he … n_wrappers and wrt "yay" and "smart" also https://bbs.archlinux.org/viewtopic.php?id=291007
The cause isn't "open source, so it's lousy" but "the internet is a hostile environment, so get some armor" - you're welcome.
Offline
ah forgot about that, probably not.
Offline