-
-
Notifications
You must be signed in to change notification settings - Fork 26k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge 'deb' and 'debian' plugins #529
Conversation
Instead of Also, not sure whether /me being the original author of the deb plugin. |
The real problem is that we have aptitude v. apt-get and su v. sudo, which results in a lot of permutations. I didn't mean to imply that one or the other is better. The reason I don't use sudo is that it was meant to give very specific superuser permissions to specific users, and I am the only user on most of my machines so I really have no use for it-- I trust myself to simply use root to do all administrative work. As for aptitude v. apt-get, that one is mostly a judgment call (except for I think maybe the best solution is to set two preference variables, and then write a function that incorporates those preferences into the aliases whereever possible. This will also avoid confusing namespace issues (e.g. "as" v. "aps"). I think I could finish this in a day or two. |
Another possibility is that I could write a function that uses |
Agreed.
Why not use aptitude if |
Are any project admins even reading the pull requests? |
Sometimes... just have a big backlog to work through. Merging in 3...2.. |
Merge 'deb' and 'debian' plugins
As far as I can tell, the deb plugins were already covered in the debian plugins. So there's really no need for the two separate plugin directories. However, the deb plugins used
sudo
(instead ofsu -c
) and had shorter alias names, so I incorporated them into the debian plugins so users will have more options. The reason that I kept the name debian is that it's a little less ambiguous.-dbb