Why re-invent the wheel? #26
ArjixWasTaken
started this conversation in
General
Replies: 6 comments 7 replies
|
Déjà-vu ... it feels like another 🗿 "oh we need to have this up in our toolbelt - let's create it" |
0 replies
|
They specifically mention gsudo in their blog post https://devblogs.microsoft.com/commandline/introducing-sudo-for-windows/ |
1 reply
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Comparison between gsudo and Microsoft sudo |
2 replies
|
If you are going to reinvent the wheel, why not make it work with all the other wheels out there? It's not that hard to make it so that everyone adopting your tool doesn't have to modify scripts to make it work. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
There has been an excellent project named gsudo and it has an alias for
sudoas well.It works just the way one would expect it to, and it has existed since 2019 (~5 years as of writing).
It is available on winget, scoop and chocolatey.
I'd assume it would make more sense to either sponsor that guy or to fork their project.
Why are you making your own from scratch?
Are you planning to have your version of sudo enabled by default once it is mature?
Would it conflict with gsudo?Update: It does indeed conflict, even when disabled...
Solution: Edit your system environment for PATH to have the gsudo directory before
C:\Windows\System32All reactions