Issue description
As was already noted in #342338, the name of the --use-remote-sudo flag is very confusing. It has nothing to do with "remote" stuff. It just runs sudo only when this is required, i.e., when activating a new profile (running an activation script).
There are 2 approaches to this: rename the existing flag by introducing a breaking change, or add a new flag/alias to the existing one (and probably deprecating the old one). We should discuss which approach is better and which name would be a better representation of the flag's behavior. As a result, the documentation (#342338) would have to use the new name instead.
CC @Aleksanaa @cafkafk @SigmaSquadron
Issue description
As was already noted in #342338, the name of the
--use-remote-sudoflag is very confusing. It has nothing to do with "remote" stuff. It just runs sudo only when this is required, i.e., when activating a new profile (running an activation script).There are 2 approaches to this: rename the existing flag by introducing a breaking change, or add a new flag/alias to the existing one (and probably deprecating the old one). We should discuss which approach is better and which name would be a better representation of the flag's behavior. As a result, the documentation (#342338) would have to use the new name instead.
CC @Aleksanaa @cafkafk @SigmaSquadron