fix: Not need touch bash.bashrc #233
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Owner
|
That alias is a remnant from older versions that I didn't really have time to revisit. You're welcome to clean that up from other packagings as well if you can |
Signed-off-by: 4ntsy <228124712+4ntsy@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I don't know if you hate it or if you like of
aliaslol…But in the sudo ASKPASS you removed it, I don't really know why, since in this case it makes sense for example if a script asks for sudo_rq, and a download or some task ends up taking a long time it will ask for sudo through the terminal, besides with the alias it wouldn't even be necessary to call sudo_rq, if a script just calls sudo and sudo needs to ask for the password it will invoke zenity, but anyway you decide…
Now, regarding adding the alias to bash.bashrc, there is no apparent reason for this behavior, since immediately after installation the app becomes available in the PATH environment variable, making it accessible?
This goes for the other packages as well.