FS#15581 - Needed: -Su foo and -Syu foo
Attached to Project:
Pacman
Opened by Scott H (stonecrest) - Sunday, 19 July 2009, 17:37 GMT
Last edited by Xavier (shining) - Saturday, 12 September 2009, 10:55 GMT
Opened by Scott H (stonecrest) - Sunday, 19 July 2009, 17:37 GMT
Last edited by Xavier (shining) - Saturday, 12 September 2009, 10:55 GMT
|
Details
The only way to currently install a new package is to use
pacman -Sy foo. Pretty much every documentation source
states this as the way to install a package without
explaining that, in fact, one really should issue a -Syu
afterwards. Otherwise, problems like
It seems to me that a standalone -Sy foo should be strongly discouraged then, but IMO, this can only happen if we actually have a command that installs a package that way it is intended to be done! That is, there should be -Su foo and -Syu foo commands that issue a (-S foo; -Su) or a (-Sy foo; -Su) respectively. Then we can update the documentation to officially sanction these operations and start to ween users off of issuing standalone -Sy foo's. The -Sy foo command would instead become more of an expert operation where one can update a package if they know what you're doing. Perhaps the command should even give a warning to this effect. |
This task depends upon
Closed by Xavier (shining)
Saturday, 12 September 2009, 10:55 GMT
Reason for closing: Implemented
Additional comments about closing: f53d9bab0ef2
Saturday, 12 September 2009, 10:55 GMT
Reason for closing: Implemented
Additional comments about closing: f53d9bab0ef2
http://wiki.archlinux.org/index.php?title=Special:Search&ns0=1&redirs=0&search=pacman+Sy&limit=500&offset=0
I would be more in favor of something like the options Allan proposed :
http://bugs.archlinux.org/task/15566#comment47190
Anyway, supporting -Su foo and -Syu foo doesn't hurt, so I am not against this.
I am just not convinced it will solve the problem.
On the other hand, having right dependencies would solve the problem.
I would also like to know how other distribs / package managers handle this.
It is a lot easier without rolling release. Debian names its libraries (e.g.) libfoo5 and libfoo6 so the soname is in the name of the package as so dependencies on libraries versions are obviously stated directly.
At least it has the big advantage that it would avoid any breakage.
Pacman alreay gives us the tools to stop -Sy being an issue; versioned dependencies and provides. Although, they are difficult to get perfect on a rolling release system.
I will just do it again, updating help/doc and stuff.