when installing packages, particularly building them from AUR, pamac hangs on a password prompt right at the end of the installation process. Sometimes if the password prompt isn’t filled within some period of time, the installation will fail. Some of my builds and installations take a long time and when I come back to them and place in confirmation on said prompt, the installation fails. Until I figured out that built binaries are stored, this was even more of a problem because I would need to build the package again.
Even if the installation didn’t fail, It will also be convenient for the prompt to not come at the end. It is a hassle having to remember to focus the terminal to check after an indefinite amount time has passed.
would it be possible to make pamac ask for password at the beginning of the installation process along side confirmations instead?
–no-flag doesn’t help because it can’t be used for AUR packages.
As far as I know, the reason pamac waits intil the end, is because that’s actually the correct place to ask for the password: When the package is about to get installed.
As far as I know, most AUR helpers do this, so the build process is not run with sudo rights.
Pamac uses Polkit for authentication. Pamac asks for your password before starting the build process but if it’s too long (the time delay is defined by Polkit), the password can be asked again when installing packages.
I know this behavior can be annoying but it’s for security reasons.