FS#50173 - Keep system in "full" sync with remote repository

Attached to Project: Pacman
Opened by Hiroki Yamamoto (hirokiyamamoto) - Thursday, 28 July 2016, 09:13 GMT
Last edited by Allan McRae (Allan) - Thursday, 28 July 2016, 11:56 GMT
Task Type Feature Request
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 5.0.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:

'Pacman -Syu' currently keeps a system up to date according to a list of already installed packages and their dependencies. However, it does not detect newly added repository packages nor does it take removed repository packages into account.

Request to extend Pacman's capabilities by allowing it to keep an Arch Linux installation in sync with the, complete (all packages), repository. This includes package removals and package additions.

Currently, this can be achieved by (manually) generating lists generated by pacman that contain newly added repository packages and removed repository packages. One can then feed that information to pacman to do a removal of packages and subsequently add newly added packages. A switch in Pacman that keeps a system 'in sync' instead of doing 'only upgrades' would be a cleaner solution making a wrapper script doing the comparison obselete.

The assumption / system owner's responbility is that all packages within a repository are compatible with eachother and can co-exist. e.g. One can either apply this to a custom repository or to a whole Arch Linux system where 'core' would be a private repository that does not come from upstream Arch but is maintained internally instead.

Steps to Reproduce:

None.
This task depends upon

Closed by  Allan McRae (Allan)
Thursday, 28 July 2016, 11:56 GMT
Reason for closing:  Won't implement
Comment by Allan McRae (Allan) - Thursday, 28 July 2016, 10:27 GMT
Do you want all packages that are newly added to the repository installed on your computer?
Comment by Hiroki Yamamoto (hirokiyamamoto) - Thursday, 28 July 2016, 10:59 GMT
Yes. And in addition to that, all packages removed from the repository should be removed from the Arch Linux system as well. Therefore, what is in the repo, should be on a Arch Linux system. The repository controls the system.

This allows for a pool of Arch Linux machines to be controlled using a single action in a shared repository. Therefore eleminating the need for (post) cfg. mgmt. or similar.
Comment by Allan McRae (Allan) - Thursday, 28 July 2016, 11:56 GMT
There are many tools to handle pools of machines. Pacman is not one.

Loading...