Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#5571 - unnecessary pacman parameter(s): '-A' and '-U'
Attached to Project:
Pacman
Opened by Finn (deTTo) - Wednesday, 11 October 2006, 20:01 GMT
Last edited by Aaron Griffin (phrakture) - Thursday, 13 March 2008, 19:34 GMT
Opened by Finn (deTTo) - Wednesday, 11 October 2006, 20:01 GMT
Last edited by Aaron Griffin (phrakture) - Thursday, 13 March 2008, 19:34 GMT
|
DetailsPacman has both, --add and --upgrade whereas --upgrade (-U) does the same as --add after it checked for an upgradeable version. This makes --add parameter completely unnecessary and we should think about naming a new parameter that does this upgrade/add thing. For example '-I' for install or the like.
Look at http://bbs.archlinux.org/viewtopic.php?t=25932 for further ideas and opinions. :) cheers, deTTo |
This task depends upon
Closed by Aaron Griffin (phrakture)
Thursday, 13 March 2008, 19:34 GMT
Reason for closing: Implemented
Additional comments about closing: Fixed in git, commit 797c190f93d24ff1e352549f320a0612cd04382b
Thursday, 13 March 2008, 19:34 GMT
Reason for closing: Implemented
Additional comments about closing: Fixed in git, commit 797c190f93d24ff1e352549f320a0612cd04382b
-A and -U are getting to the point where the distinction is a bit silly. I'm all for the -I/--install change, as it makes more sense to me.
That said, removing -A and -U at this point in time, so abruptly, is probably a bad move. So I suggest the following:
Add -I/--install. The -A and -U options will simply call that and output a little warning that the option is old / deprecated / being removed / whatever, and then pass all params to -I (exactly the way -A does not, except with a little message).
About making sense: It doesn't really matter what it means, how much sense does -S make? It only matters what people are used to, nobody will think about what -U once meant.
-I has problems of its own. For example, if I have foobar-2.0 installed and then I pacman -I foobar-2.1, I'd expect to have both versions installed. In fact, what I did here was upgrade, or installed AND removed. And, as a new user, I would try to use -I instead of -S to install all of my packages. I mean, I'm supposed to type pacman --sync to install a package from the repo and pacman --install to install locally? Where is the logic in that? (And finally, "I" in general is a bad argument because it looks like "l" :p).
There is no correct term that will cover every use case here. I personally think that -U covers the most common action action (upgrading), doesn't confuse the user with when they should use it versus -S, and is already something that 99% of users are familiar with. It's not broken so don't fix it, especially when the fix is no less confusing than current behavior.
http://code.toofishes.net/gitweb.cgi?p=pacman.git;a=shortlog;h=refs/heads/oven
Afaik, the remaining problems are :
1) clean libalpm too
2) check the add pactest to see if they have an upgrade equivalent. If not, convert them to upgrade (instead of removing them all)
I believe that help is highly welcome on any of these two points, since there was no progress for quite some times now.
2.) OFF: add013.py seems to be a bit strange to me.