FS#8137 - upgrading by groups
Attached to Project:
Pacman
Opened by Stefan O. (hybrid) - Wednesday, 26 September 2007, 23:25 GMT
Last edited by Xavier (shining) - Tuesday, 13 May 2008, 19:59 GMT
Opened by Stefan O. (hybrid) - Wednesday, 26 September 2007, 23:25 GMT
Last edited by Xavier (shining) - Tuesday, 13 May 2008, 19:59 GMT
|
Details
I think it would be good if it was possible to be able to
choose from the command line which repositories pacman
should upgrade. For example if I only want to upgrade core
packages, I think it could be handy sometimes to quickly
tell pacman something like pacman -Syuw --rep=core. Sure
this can be done by editing the pacman.conf, so probably it
would be better to utilize the existing --groups switch.
Right now it only prints, but I think it'd be useful if eg.
pacman -Syu --groups base would update all packages in the
group.
Why? Well sometimes I don't want to upgrade everything at the same time and I'd be able to split it up. I was just gone for 6 weeks for example and over 600MB of updates have piled up in that time. So I'd like to be able to update the core first and then once I worked through a couple things do the rest. |
This task depends upon
Closed by Xavier (shining)
Tuesday, 13 May 2008, 19:59 GMT
Reason for closing: Works for me
Additional comments about closing: pacman -S group works for me.
If you need something like Nagy's --nonew option, please open a separate feature request.
Tuesday, 13 May 2008, 19:59 GMT
Reason for closing: Works for me
Additional comments about closing: pacman -S group works for me.
If you need something like Nagy's --nonew option, please open a separate feature request.
I like the second idea of reusing --groups, but the first idea about specifying repos, probably not a good idea.
Other opinions?
Couldn't this break the other packages?
IMO it's ok to have pacman.conf editing as a solution for repo-only upgrade and --ignorepkg as a solution for group-only upgrade.
However I don't mind groups-only upgrade feature if it's not hard to implement.
Also, while we're on it, I'd like to remind about this nice FR too:
FS#1592;-)FS#1592is on the 3.1 roadmap.[In this form the patch won't be accepted, but see the discussion about the feature.]
> + Pacman won't install new (not-yet-installed) packages, except if they are
> + needed by others (as dependency). This is mostly used in group
> + operations to restrict pacman to installed packages of the group.
> + For example 'pacman -S base --nonew --needed' will upgrade your
> + base group, but won't add new packages from base.
> +
Actually, this feature request doesn't mention at all the problem of adding new packages.
It was not even mentioned that you could just do 'pacman -S --needed base' to install/upgrade all packages from base.
So actually, this feature is already available.
pacman doesn't support the case of partially installed groups, but that's a corner case, it is not a problem, and it is not what this feature request was about.
Or am I missing something obvious?
If yes, then I would close this as 'wont implement', otherwise as 'already implemented' :)
If someone wants, he can open a new and clearer feature request asking for something like --nonew.