paru icon indicating copy to clipboard operation
paru copied to clipboard

Please consider run as root -> de-escalate as the strategy for paru in the future.

Open aTosser opened this issue 3 years ago • 5 comments

Please consider a strategy of running paru as root and dropping permssions for the fetch/build processes. This would be an inversion of the current practice and would no longer rely on calling sudo/doas externally. This would allow for all of the sudoloop code to be dropped completely.

It would solve several issues that can be seen through the tracker. To name just a couple:

  • Unattended installs - Without sudoloop and the correct runtime options. Paru can perform complete upgrades without user interaction. (My preference would be to see paru run completely without any user interaction by default and only ask for confirmations if the user passes flags)
  • managing multiple privledge escalation tools - simply invoking sudo paru or doas paru should be sufficient to grant necessary install permissons. If some new privlege escalation tool comes along, paru will support it by default.
  • Various container related permission issues.

Thanks for reading.

aTosser avatar Aug 02 '22 01:08 aTosser

does this work now?

romanstingler avatar Dec 17 '24 01:12 romanstingler

My preference would be to see paru run completely without any user interaction by default and only ask for confirmations if the user passes flags

Will never happen as paru mirrors pacman and is a user tool first. It's not built for 0 interaction.

does this work now?

No but it may be a thing one day

Morganamilo avatar Dec 27 '24 04:12 Morganamilo

at the very least paru shouldn't let you run it with sudo since it (reasonably) refuses to build packages anyway

TipsyTheCat avatar Sep 05 '25 21:09 TipsyTheCat