So there are valid use cases to keep them both. If you prefer to remove sudo 
completely and make the sudo-rs binary replace it, that's your choice. But 
there will be some cases where one will inevitably hit a wall by doing so.
This is exactly the benefit the sudo-is-sudo-rs package provides.

You're just trying to do something unexpected / unsupported (yet at least). 
Again, sudo-rs is not meant to fully replace sudo as of now.
I started using sudo-rs as a drop-in replacement for sudo on my systems a few weeks ago (that's why I crafted this very simple package) and thought it might be of use for others. Until now, I did not hit a wall in regard to features.

While I accept your decision to remove the package from the AUR, I'm a bit confused about the reason to do so.

You argued before that "removing the sudo package from the system is users' choice". The cleanest option I see to achieve this would be a meta package that ships the necessary files and fulfils the dependencies.
sudo-is-sudo-rs did exactly that, thus providing some benefit.


Regards, weva

Reply via email to