Option to disable the redundant "continue installing" question.

[bernimoses]

Would it be possible to remove one of the redundant "Continue installing? [Y/n]" / "Proceed with installation? [Y/n]" questions, or make it configurable via /etc/pakku.conf? Maybe even both since we already answered "Proceed with building? [Y/n]"?

...
==> Leaving fakeroot environment.
==> Finished making: pakku 0.12-3
:: Continue installing? [Y/n] 
loading packages...
warning: pakku-0.12-3 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) pakku-0.12-3

Total Installed Size:   0,71 MiB
Net Upgrade Size:      -0,05 MiB

:: Proceed with installation? [Y/n]
...

[kitsunyan]

Would it be possible to remove one of the redundant "Continue installing? [Y/n]" / "Proceed with installation? [Y/n]" questions

They aren't redundant. For instance, sudo requires a password input which has timeout. You can be away from your PC at the moment when pacman was called via sudo, which will lead to failure. So I always ask before running sudo.

That's the only reason for this behavior. It's not necessary to ask twice when you run pakku via sudo yourself, and I don't do that. You can also enable SudoExec in config, in this case pakku will be executed via sudo automatically.

Maybe even both since we already answered "Proceed with building? [Y/n]"?

That's much more complex task. This behavior is named "batch interaction" on arch wiki page, and pakku is marked as Partial since it can't handle these cases. The complexity proceeds from the fact that packages may conflict, and blind --noconfirm won't be enough for that.

[bernimoses]

They aren't redundant. For instance, sudo requires a password input which has timeout. You can be away from your PC at the moment when pacman was called via sudo, which will lead to failure. So I always ask before running sudo.

Oh ok, i didn't know there was a technical reason.

That's the only reason for this behavior. It's not necessary to ask twice when you run pakku via sudo yourself, and I don't do that. You can also enable SudoExec in config, in this case pakku will be executed via sudo automatically.

Nice, that will do it for me.

That's much more complex task. This behavior is named "batch interaction" on arch wiki page, and pakku is marked as Partial since it can't handle these cases. The complexity proceeds from the fact that packages may conflict, and blind --noconfirm won't be enough for that.

Is this maybe something that's coming in the future?

[kitsunyan]

Is this maybe something that's coming in the future?

Maybe, but I'm not sure that it will be the default behavior then.

[bernimoses]

OK, looking forward to it. 😉

I think this can be closed?

[kitsunyan]

Let's keep it open for "batch interaction" feature request.