I love the AUR and install quit a few programs from it. But now and again if one of the biggies, which are compiled from source are to be updated in a very time consuming fashion, I got a
sudo timeout problem.
See, if I see the start if a compile-session I turn to another desktop and doing something else like surfing the Internet or watch a movie. So I often forget a about the long installation process and come back to my terminal only to see that
sudo timed out, i.e. I had to start from square one again.
I came to the conclusion that
--noconfirm is not an option with any AUR helper programs, because then every timeouts were final, even if the helper program ask for repeating entering password, because usually No (
[y/N]) is the default answer.
Unfortunately my favorite AUR helper
yaourt is deprecated, wich had a completely different tack of the
sudo timeout handling, it escalated the password to enter from the
sudo password to
root password and haltet indefinitely for it to be entered.
So my second best choice
trizen (the one that at least ask for another try entering the password) is itself an AUR program and therefore needs an manual installation or another AUR helper.
Do I miss options for
yay or the other AUR helper programs to prevent that kind of
sudo timeout, or is it possible to nudge the AUR helper programmer to incorporate such a handling ;o)?
So far I will stick with